BSOD When booting, or logging into Windows

Hi, I hope you're feeling better :) .
The latest bugcheck is the of the type that the culprit is no longer around when the fault is discovered
which makes us have to work a little harder to find it.

Please follow the procedure detailed below, to try and find the culprit.

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.

Windows Memory Diagnostic Tool, is not a good enough of a test.
Even Memtest86+ is not perfect and by no means 100% fault-proof.
You can test all of the sticks simultaneously, it's fine, but no it won't be specific as to which
is failing that is where trail and error comes in.

moocows said:

Hello,
Sorry for the lack of communication, i have had a good amount on my plate and was only recently able to get a disc to burn memtest on to. I am in the middle of the test, 7 passes and 0 errors so far, so hoping that i get an 8th pass. I had a question about the driver verifier. Once it BSODs from the verifier will the driver that caused the BSOD be listed on the screen, in the minidump, or both? Thank you very much. I feel like im one giant step closer to fixing this.

It's OK, we all have life to deal with :) .

Yes Driver Verifier is especially designed to catch drivers red-handed, so hopefully it will prove revealing.
Most of the times the offending driver is being displayed at the BSOD itself but not all the time.