Laptop crashes
Images are sometimes not shown due to bandwidth/network limitations. Refreshing the page usually helps.
You are currently reading a thread in /g/ - Technology
You are currently reading a thread in /g/ - Technology
Well /g/, normally I help a lot of people but now I need your help!
>>55558166
OP Here:
I've done:
> Windows 7 reinstalled with the official CD and Driver CD
> Remove all dust
> Memtest no errors
> BIOS settings reset
install gentoo
>>55558193
this, or a variance thereof
>>55558166
witnessed
also google the code for fucks sake
also you didint give us any info so fuck off.
>>55558193
The one time this meme is good advice.
Ditch Windows, OP.
>>55558166
use whocrashed and read the crash dump.
>>55558166
When does it crash/What are you doing when it crashes
Can you boot and get into Windows fine, and then it crashes after a certain amount of time, or what?
If you actually helped people you'd know not to leave out crucial information. Looks like a driver issue or a hardware conflict. If you've not installed any new hardware lately, I would bet it's drivers.
I would look in BIOS and make sure that your devices are set up properly, too. Not just resetting it to default settings.
>>55558166
My magical abilities tell me it's an Acer, in which case it's fucking up as intended.
>>55558435
OP here,
Sorry for not giving enough information.
Google search only says it could by anything.
It happened always randomly. Sometimes 4 days not and then 20 times at boot or just randomly browsing the Internet.
Bios setting are set correctly.
>>55558471
>>>55558166 (OP)
>My magical abilities tell me it's an Acer, in which case it's fucking up as intended.
No sir, it's a Terra Mobile 1547Q.
>>55558476
>always randomly. Sometimes 4 days not and then 20 times at boot or just randomly browsing the Internet.
definitely a driver issue. use whocrashed and read the dump.
>>55558476
shutting itself down because of overheat?
have you fucked with the internals recently?
Could be the PSU. The stranger the issue, the more likely it's the cause.
>>55558536
>>>55558476 (You)
>shutting itself down because of overheat?
>have you fucked with the internals recently?
I've looked at that. The laptop has only been open to remove dust safely. And no internals were touched / damaged in the progress. Also this problem has turned up way after the last dust removal. No overheating in anyway.
>>55558514
>>>55558476 (You)
>>always randomly. Sometimes 4 days not and then 20 times at boot or just randomly browsing the Internet.
>definitely a driver issue. use whocrashed and read the dump.
Will do sir.
Last 2 whocrashed dump:
On Wed 7/13/2016 4:35:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071316-19156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0xA (0xFFFFFA8027AB2158, 0x2, 0x1, 0xFFFFF80002D314E6)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 7/13/2016 4:35:54 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA8027AB2158, 0x2, 0x1, 0xFFFFF80002D314E6)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
>>55558662
ok, this one is tricky. make sure your ram works properly. test it.
then update all of your drivers.
>>55558662
Uninstall any shit you installed since around the time it started crashing.
>>55558801
That would be my drivers, Chrome, Firefox, Skype, and WinRAR.
I've reinstalled Windows 7 many times trying to maybe fix this.
Yet it comes back sometimes even with a clean install it happens out of fucking nowhere.
>>55558792
I'll redo a memtest and come back with the results.
https://sourceforge.net/projects/snappy-driver-installer/ do eeeet faggot
>>55558662
You've found the problem , now remove it. Delete /system32
>>55558848
Fuck off :/
>>55558843
>I'll redo a memtest and come back with the results.
Out of curiosity, how do you do memtest? Do you just run through it until it says 100% and consider yourself done?
Because you should like run it over the night, At least test your RAM like 8 times over in one go.
>>55558860
cjwck em
>>55558873
I run http://www.memtest.org/
Let it run till it's complete.
But 8 times?
>>55558921
>But 8 times?
Yeah, otherwise you might as well not do the test. Think I might have found the problem.
>>55558476
It's almost certainly a fecked driver, it's trying to access memory space it's not got permission to access or it's set an IRQ number that conflicts with another. It's most likely the graphics driver because they're buggers for this, it's probably conflicting with an older driver and either pinging as an IRQ conflict or double booking memory and trying to shunt information into a another program's reserved memory space.
>>55558967
I'll do as you said sir and come back later after I ran 8, as you said 8 tests.
>>55559021
If the memtest won't come out good, I'll reinstall once again with another CD and I'll get the drivers from the manu's site.
>>55559023
It depends a little on how much RAM you have. The point is, you'd like to get a full pass once your RAM has gotten warm. You'll find most errors with just 1 pass, but subtler errors only show after the RAM has heated up.
>>55559065
I've got 1x 4GB DDR3 and 1x 2GB DDR3
>>55559079
Guess you should run it for an hour or thereabouts.
>>55558166
Bad drivers?
AHCI mode enabled in bios?
Anything related to Windows Update?
Registry corrupted?
Any USB hardware connected?
Is RAM working as it should?
If you can get into Windows try running "sfc /scannow" in cmd
>>55558166
There is a switch on your motherboard. Switch it. It resets the Bios.
If it does not work change the motherboard's battery for a new one.
Flash a new bios.
>>55558166
Install Gentoo.
>>55558353
>One
Lmao @ u
>>55559263
I'm going
>>55559282
I'll try that after this.
>>55559282
Me
>>55559329
Similiar shit happened to my dad's PC, this fixed it. He only needed to reset it but it went shit again after a month so bought a new one but it could work for you.
>>55559438
Thanks, Will try it now.
>>55559263
>>55559468
Windows has a built-in troubleshooter for RAM. Try it out. Can be found searching for that from start menu.
>>55559500
Did that, no errors to be found.
I'm currently trying memtest.org's software.
>>55558476
Try resetting all the connectors in the device, ensure they're not loose, and clean of dust.
>>55558166
The only time I saw that specific bsod was when I had a driver conflict. I believe I tracked down the cause by opening up the bsod dmp file in WinDbg and using the advanced analysis.
>>55558166
Im gonna call it right now, its the gpu. ( or one of those ram sticks). Yeah, im really helpfull, youre welcome.
>>55558166
Reinstall windows but if you have some important files in the computer with any operating sistem's live usb i would use ubuntu for that.
>>55558166
Message means is a driver, GPU or RAM related if you are using a IGPU.
