sidebottom
New member
- Local time
- 3:58 PM
- Messages
- 1
The BSODs do not seem to happen at any specific time.
The computer is an HP with a Pegatron 2A86 Mobo.
I plan on running MemTest86 and will have images uploaded tonight.
For now, here are my WhoCrashed logs and (attached) is the SF files.
Thank you in advance for any help. My feeling right now is bad RAM, but I'm hoping it's just a driver issue I can easily fix.
Edit: one quick edit, the previously configuration had minidumps. I've changed it to kernel dumps, so if I BSOD again in the future, there will, hopefully, be more information.
--------- BEGIN WHOCRASHED DUMP -----------
System Information (local)
computer name: HPDESKTOP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 9654304768 total
VM: 2147352576, free: 1881632768
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 2/28/2013 9:18:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-41355-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x22751)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000108CF8, 0xE240000072C54867, 0xFFFFFA800BF31180)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a severe memory management error occurred.
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.
On Thu 2/28/2013 5:25:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-39717-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680000582F0, 0xF95000024A5D2867, 0xFFFFFA800D76D3E0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Wed 2/27/2013 10:56:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-40076-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030D3B45, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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 Sun 2/24/2013 2:43:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022313-53133-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x4E (0x99, 0x22FADF, 0x2, 0x1C73DE)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 2/11/2013 3:11:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021013-65380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x2, 0x1F7F42, 0x26FFFF, 0x2900)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 Fri 2/8/2013 6:39:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020813-45255-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x8886, 0xFFFFFA8005D7D6D0, 0xFFFFFA8006B4FF00, 0x503)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Fri 2/8/2013 1:14:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020713-38594-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x2, 0x21D19C, 0x26FFFF, 0x2500)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 Thu 1/17/2013 6:57:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-47299-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x41, 0x2, 0x1, 0xFFFFF800030AC468)
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.
Conclusion
8 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
The computer is an HP with a Pegatron 2A86 Mobo.
I plan on running MemTest86 and will have images uploaded tonight.
For now, here are my WhoCrashed logs and (attached) is the SF files.
Thank you in advance for any help. My feeling right now is bad RAM, but I'm hoping it's just a driver issue I can easily fix.
Edit: one quick edit, the previously configuration had minidumps. I've changed it to kernel dumps, so if I BSOD again in the future, there will, hopefully, be more information.
--------- BEGIN WHOCRASHED DUMP -----------
System Information (local)
computer name: HPDESKTOP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 9654304768 total
VM: 2147352576, free: 1881632768
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 2/28/2013 9:18:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-41355-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x22751)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000108CF8, 0xE240000072C54867, 0xFFFFFA800BF31180)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a severe memory management error occurred.
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.
On Thu 2/28/2013 5:25:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-39717-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680000582F0, 0xF95000024A5D2867, 0xFFFFFA800D76D3E0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Wed 2/27/2013 10:56:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-40076-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030D3B45, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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 Sun 2/24/2013 2:43:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022313-53133-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x4E (0x99, 0x22FADF, 0x2, 0x1C73DE)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 2/11/2013 3:11:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021013-65380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x2, 0x1F7F42, 0x26FFFF, 0x2900)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 Fri 2/8/2013 6:39:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020813-45255-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x8886, 0xFFFFFA8005D7D6D0, 0xFFFFFA8006B4FF00, 0x503)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Fri 2/8/2013 1:14:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020713-38594-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x2, 0x21D19C, 0x26FFFF, 0x2500)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 Thu 1/17/2013 6:57:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-47299-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x41, 0x2, 0x1, 0xFFFFF800030AC468)
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.
Conclusion
8 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
My Computer
At a glance
Windows 7 64 bit home premium.
- Computer type
- PC/Desktop
- OS
- Windows 7 64 bit home premium.
