Intermittent BSODs over the past few months

Danj · 25 Jan 2014

Ever since I built this PC I've had BSODs every so often. I've not been able to trace them to any particular source, but lately they seem to be getting a lot more frequent and I am getting fed up, so I figured I would try asking here.

I've used the SF Diagnostic Tool to gather the requested information and attach it to this thread.

The most recent one seems to suggest a problem with the CPU. It's been suggested to me that my CPU might need a microcode update - I installed SiSoft Sandra Lite which is able to check the CPU microcode level and indeed it does suggest it isn't on the latest version, but as far as I can tell there is no procedure for manually updating microcode, you just have to wait and hope it comes down through Windows Update or something.

Can anyone help?

YoYo155 · 25 Jan 2014

Welcome to SF Dan :).

The dump files are not showing a definitive cause but most of them are 0x1A, so the best course
of action in these type of situations is detailed in the quote below.

Arc said:

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Arc said:

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

If memtest comes free from errors, 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.