Random BSODs on custom built PC

[Arc]

You should have disabled all the startup items other than MSC. Nothing else is required there. It is suggested to you because there is a specific reason.

If it BSODs even after disabling all unnecessary startup items, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
________________________________________________

BugCheck 50, {ffffea800db1a9b8, 0, fffff8000331be9a, 7}


Could not read faulting driver name
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGet+52 )

Followup: MachineOwner
---------

 

[nikhilnh]

Thanks. I have disabled all startup items. I assume I don't have to disable any services.

 

[nikhilnh]

I disabled all the startup process on Nov 23rd. Got a few more BSOD's after that. I had enabled the Driver Verifier for almost 2 days.

The first BSOD was on Nov 24th caused by iusb3hub.sys, the second was on Nov 30th. The 3rd was on Dec 2nd (MEMORY_MANAGEMENT). I enabled Driver Verifier after the 3rd BSOD, which caused another Blue Screen. This time the offending driver was PxHlpa64.sys. I let the Driver Verifier run for almost 2 days and didn't have any more BSOD.

 

[Arc]

The latest BSOD in the zip is of December, which was caused by PxHlpa64.sys.

BugCheck C9, {228, fffff880015cc074, fffff98003608d80, 0}

*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+3074 )

Followup: MachineOwner
---------

This module is used by a lot of CD/DVD playing/burning programs; and you have a few of them installed. So it is difficult to point out the exact root.

It would be the best for you to opt for a clean reinstall.

 

[nikhilnh]

Thanks. I'll do a clean reinstall.

 

[nikhilnh]

I finally got a chance to do reinstall the Windows. This time instead I purchased an OEM Win 7 Home premium copy and did a clean install with it. Unfortunately after the installation, the no. of BSOD's increased. Earlier I used to get about 4-6 BSOD's a month. However after the new installation, the computer has blue screened about 9 times in 2 weeks. As per the previous suggestions, I have disabled all the startup programs except for MS Security Essentials. I have attached the file I got after running the DM log collector.

 

[Arc]

There is no logic or similarity in the crash dumps. All are of different types. Which gives a hint of memory malfunction.

As per post #19, you have already done memtest86+ test. If you are sure about the result that it resulted no error, then remove the RAM and apply them in the remaining two slots. See how it goes.

If the issue persists, RMA the motherboard.

 

[nikhilnh]

Thanks Archie. I'll try the remaining two memory slots.