Stubborn and varied BSoDs

LazyCoder · 11 Apr 2016

This might be a bit long, I apologize, but I like to give details.

Every once in a while, my computer locks up entirely, with no input nor output happening. It was happening every few minutes, much worse than before, so I sent it back to the company to get the hardware checked out. The diagnosed it to be the RAM and replaced it under the warranty. They formatted the disk, probably so that they could access it or something. It still has the problem, but nowhere near as often. This leads me to believe that drivers or software may be to blame.

Yesterday, it had the problem for the first time since I got it back four days ago. I booted it up and it shut itself down before starting completely. I never associated things like that with the problem, but I'm starting to think it might be connected.
It keeps getting BSoDs. Previously, BSoDs were rare because output would lock up before the screen displayed the error in 9/10 cases. Right now, the computer is a lot more reliable and these problems are less severe and further between.

But I am still having the same BSoDs as I was before. There is a DirectX driver that keeps crashing, but that only happens on a specific game (Or seems to), and I don't think it is the culprit.

Even bad ideas are better than my own, don't hesitate to post your thoughts.

Arc · 12 Apr 2016

LazyCoder said:

The diagnosed it to be the RAM and replaced it under the warranty.
......................................................................................
......................................................................................

Yesterday, it had the problem for the first time since I got it back four days ago.

There are crash dumps of 05/04, 09/04, 10/04 and 11/04. other than those of 11/04, all are reporting to be memory corruption. The last two are apparently driver related, but I would suggest you to do it from the root. Do test the RAM modules yourself. Be sure that the replacement RAM are good.

MemTest86+ - Test RAM

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.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

After seeing the results, we will decide our next step. OK? :)

LazyCoder · 12 Apr 2016

Thanks. I figured it might be the RAM based on some searches, but after testing for 24 passes, there was nothing detected. Thanks for the reply though. :)
I will be gone for a little bit to test my processor since it can't hurt, right?
The Dxg2mms.sys only happens when playing a specific game, but I will still check if anything needs updating.

Arc · 12 Apr 2016

LazyCoder said:

Thanks. I figured it might be the RAM based on some searches, but after testing for 24 passes, there was nothing detected. Thanks for the reply though. :)

Nice. If you run Memtest86+ for 24 passes and it does not show the error, there is no problem. But it should take a long time. Make it sure that you used Memtest86+.

LazyCoder said:

I will be gone for a little bit to test my processor since it can't hurt, right?

You can do it. Stress test the CPU.

Prime95 - Stress Test Your CPU

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

LazyCoder said:

The Dxg2mms.sys only happens when playing a specific game, but I will still check if anything needs updating.

If it happens with only one game, there is not much to be worried of.

Next, 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.

Vince Massi · 12 Apr 2016

LazyCoder, try Arc's method first. If that doesn't work, I recently solved the same problem when I learned that my video driver had not installed properly.

Type Device Manager into Cortana. Select Display Adapters, and when your video card appears, select it. In the box that appears, you will probably be told that the device is functioning correctly and that you have the latest driver. However, click the tab for "Events." Select the date that Win 10 was installed (Okay, select all the dates, starting with the last) and find one that states whether or not the driver was installed properly.

If it was not installed properly, SET A RESTORE POINT FIRST, and then uninstall the driver. Do not delete it. 10 will automatically install a generic driver, so your screen won-t go blank. Reboot. It might give you a choice of installing the driver or might do it automatically. Give it a minute and then check Events to see if it installed properly. Even if it did, you must reboot.

LazyCoder · 12 Apr 2016

Okay, here are the results of the stress testing.
Attachment 74473

I will check on the drivers and events, Vince, thanks for the help. :)

For the record, my primary concern isn't the BSoDs, but I am just investigating if they are related to the freezing.

Arc · 12 Apr 2016

It shows .....

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4642368045, expected less than 0.4
Hardware failure detected, consult stress.txt file.

So it is hardware failure.

Are you overclocking? If so, set all the hardware components to default and run Prime95 again.

If you dont overclock, RMA the CPU.

LazyCoder · 12 Apr 2016

Okay, I figured it was something like that. I will double check my overclocking in case I bumped something (Hopefully not, I'm deathly afraid of overclocking). Thanks for the help, I should be able to get it resolved now. :)

Arc · 13 Apr 2016

OK, let us know what you have done and what it resulted. :)