Hi. My PC recently blue screened seemingly out of nowhere. I'm not very tech savvy but I do have information from WhoCrashed and my PC's specs.
GPU: GeForce GT 610
CPU: Intel(R) Pentium(R) CPU G630 @ 2.70 GHz
Memory: 6.00 GB RAM
Driver version: 340.52
OS: Microsoft Windows 7 Home Premium
And here's the information from WhoCrashed:
On Mon 9/1/2014 9:54:52 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\090114-46067-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0058060E0, 0xFFFFF8A005806750, 0x5670304)
Error: BAD_POOL_HEADER
file path: C:\windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR 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.
On Mon 9/1/2014 9:54:52 PM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltReferenceContext+0xAB)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0058060E0, 0xFFFFF8A005806750, 0x5670304)
Error: BAD_POOL_HEADER
file path: C:\windows\system32\drivers\fltmgr.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
I would very much appreciate any help that anyone might have to offer for this problem. Thanks for your time.
GPU: GeForce GT 610
CPU: Intel(R) Pentium(R) CPU G630 @ 2.70 GHz
Memory: 6.00 GB RAM
Driver version: 340.52
OS: Microsoft Windows 7 Home Premium
And here's the information from WhoCrashed:
On Mon 9/1/2014 9:54:52 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\090114-46067-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0058060E0, 0xFFFFF8A005806750, 0x5670304)
Error: BAD_POOL_HEADER
file path: C:\windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR 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.
On Mon 9/1/2014 9:54:52 PM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltReferenceContext+0xAB)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0058060E0, 0xFFFFF8A005806750, 0x5670304)
Error: BAD_POOL_HEADER
file path: C:\windows\system32\drivers\fltmgr.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
I would very much appreciate any help that anyone might have to offer for this problem. Thanks for your time.
Facebook
Twitter
Instagram