Laptop Crashing Often For No Obvious Reason

Wopaer

Reputable
Apr 30, 2015
1
0
4,510
Hi, I've been having a very frustrating problem. My laptop has been experience crashes with varying frequency. Sometimes it goes weeks without crashing and yesterday it crashed six times in one day.

It seems to have SOME connection with gaming, as that's where it is most often, but it doesn't correlate exactly. It's happened when I've just been browsing. A side note on gaming: It doesn't matter how intensive the game is. Battlefield 3 works just fine while it may crash during Team Fortress.

I've tested for overheating and that does not seem to be the cause. In fact, I've tried so many thing that I do not wish to/can not list them all here. I've opened it up and checked the fans and even re-installed Windows 8 completely.

Now, I've done so many different fixes and tests that I can give you any information you need, it's just I don't want to have to decide what to put in this initial post. Any and all help is appreciated! This stated happening in January and I've gone this long, but now I really do not some personal help. I will end this with a WhoCrashed Analysis for the most recent crash. Keep in mind this isn't the only crash error that occurs. They seem to vary wildly and I can most more if needed. Thanks!

On Thu 4/30/2015 9:05:17 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\043015-45687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x19 (0x20, 0xFFFFE0014B0C6850, 0xFFFFE0014B0C68E0, 0x4090012)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time