BSOD random, error 0x00000050

stephenp · 27 May 2015

Hi there,

I have a custom built system running Win7 Pro x64. Recently I've been getting a nasty BSOD (maybe 2x a week for the past several weeks). I don't recall if happening after anything specific update and it appears to be almost entirely random. One day I was simply typing in a web browser. Today it happened while rendering a high-resource video.

I believe my system specs are shown below in my signature. I researched the error code 0x00000050 and found: https://support.microsoft.com/en-us/kb/2719594 which says there's a hot fix but only to use it if it's identical to their noted issue. It looks similar but I don't see any " (parameter1, parameter2, parameter3, parameter4)" on my bsod as indicated on the Microsoft Hot Fix note.

Attached is a screen shot of the bsod, which can also be found here:
Microsoft services

Also attached is the log file I generated following the forum suggestion.

I'm wondering how I should begin tackling this thing...

Thank you for any suggestions or ideas!

-Stephen

Arc · 28 May 2015

The crash dumps are not very precise as to what is the issue. And there are multiple crash dumps. Such a situation gives an impression of memory failure.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, 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.

stephenp · 28 May 2015

Thank you Arc! I was hoping not to have to test the RAM because I know 64GB will take some time

But, I'll try it tonight and see where I get.
Thank you again and I'll post my findings as I get them.
-Stephen

stephenp · 29 May 2015

Well, after 7.5 hours it only ran 1.5 passes on the 64GB...

Since I have 8 slots on my motherboard, can I pull 6 sticks at a time and test overnight for the next few nights? I know the memory is supposed to be in specified slots when you have fewer than 8 sticks installed, but is that a performance thing- I mean, for testing the integrity of the RAM would it be ok to have them in different slots? I assume we want to test all sticks AND all slots since there could be a faulty slot, right?

Thank you,
-Stephen

Arc · 29 May 2015

I assume we want to test all sticks AND all slots since there could be a faulty slot, right?

Yes, it is right. But all those tests will take a very long tome for all 64 GBs. And it is always the best to test all the RAM sticks in their present slot at first, then for any other permutation and combination.