Hello,
I have a custom pc that is acting up again. The first problem may be unrelated, but I had to hold down the memtest button to let the pc cycle over and over again. Until I could go into bios and update it. Asus had a thing where you have to update the bios or windows won't start.
Could be related, might not be.
That was about a year ago. Today, the pc is having blue screens of death errors. I have not seen those in years! I have two hdd set up on the pc. One is the c drive with windows and all the programs. Then I have a second hdd with documents and pictures etc. So I'm not 100% worried about personal data.
Since it crashed 4 times, I have the WhoCrahsed report:
computer name: ASUSP8H67V
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel® CoreĀ i5-2400 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 34322919424 total
VM: 2147352576, free: 1888636928
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 9/8/2013 1:07:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090813-17253-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0xBD76, 0xBD7300017AEA)
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 Sun 9/8/2013 1:07:50 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltGetIrpName+0x117)
Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0xBD76, 0xBD7300017AEA)
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 Sun 9/8/2013 12:55:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090813-18127-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x403, 0xFFFFF6800106D038, 0xEBA00002676A1867, 0xFFFFF6FD405B74A8)
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 Sun 9/8/2013 12:52:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090813-17347-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x3606, 0x3606FFFFFFFE)
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.
Conclusion
4 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.
thanks in advance!