BSOD, multiple issues - nvlddmkm.sys ntsokrnl.sys dxgmms1.sys hal.dll

[Arc]

Roll back the display driver to the earlier version.
Device Manager - Roll Back Driver

 

[Ghostofdelta]

Roll back the display driver to the earlier version.
Device Manager - Roll Back Driver

I followed the link, and the roll back driver option is grayed out.

Wait, did you mean for the Nvidia or Intel driver?

 

[Arc]

Nvidia driver. Is it grayed out? Then use Display Driver Uninstaller to uninstall it and install 314.22 WHQL.

 

[Ghostofdelta]

Yes it was grayed out. Used DDU and installed the one you linked to.

Thanks for your continued help!

 

[Arc]

You are welcome mate.

 

[Ghostofdelta]

Bsod once again. Dump uploaded

 

[Arc]

Display crash again.

BugCheck D1, {ffffba800f97a028, 2, 1, fffff8800432ab3d}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d )

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

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

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

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

Let us know the results.

 

[Ghostofdelta]

Display crash again.

BugCheck D1, {ffffba800f97a028, 2, 1, fffff8800432ab3d}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d )

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

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

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

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

Let us know the results.

Oddly enough I already use speccy (amazing for a novice like myself, no?) and used Furmark earlier (as per your advice previously in this thread) with no issues at all. Heat on all drives is well within normal range, even when stress testing the graphics card.

Currently all drives/cpu/graphics/mb is running under 40 degrees Celsius. MB and my storage drives are all 30 or just under. When playing Diablo at 2560 by 1440 at max everything the graphics card is usually just over 60 degrees at the worst.

Link to current speecy screenshot http://speccy.piriform.com/results/SFVeb71Vhf1pD3k7dZePrYV

When I stress tested with Furmark the card got up to 89 degrees and stayed at that for over 10 minutes and was all fine, nothing weird on the screen, no bluescreen, nothing.

Used memtest previously but only for two passes. Will set it to run for 8 passes tonight. I would love for it to be a ram issue because it is so cheap to replace.

 

[Arc]

Speccy is a very common and very widely used program to monitor hardware performance.

Let us know about the memtest, too.

 

[Ghostofdelta]

Speccy is a very common and very widely used program to monitor hardware performance.

Let us know about the memtest, too.

Actually just realised some older information may be handy, especially since it relates to the display driver. When I last reinstalled windows there was issues flagged with the 4600 graphics from my i7-4770. I managed to fix it after a few attempts.

At the time i thought that would fix the blue screens, but they continued. They still occurred even when I had the driver disabled.

Maybe there are more issues with the cpu that haven't become apparent yet. Is there anything you would recommend to test it with?

 

[Arc]

4600 graphics is onboard, a component of the motherboard. Unfortunately we cannot test the board.

You should contract the vendor and ask for a replacement.

 

[Ghostofdelta]

GREAT NEWS FINALLY!

Memtest was a great call. On the 3rd pass it came up with an error. I assume the next step is to test one stick at a time?

Also now that I think about it, having a bluescreen while installing drivers/windows update (which could have included drivers) may have been the problem with the 4600.

 

[Arc]

I assume the next step is to test one stick at a time?

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

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:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

Also now that I think about it, having a bluescreen while installing drivers/windows update (which could have included drivers) may have been the problem with the 4600.

We have to look at it. For sure. Let us detect and rule out the memory issue at first?

 

[Ghostofdelta]

Quick update

I have been really busy with Uni and work and haven't had much time to test the ram and slots (The PC is in my room and i cannot sleep well with it on).

I have managed to find that 2 of the sticks and 2 slots of ram are perfectly fine (found that out the night and next day after you posted), and my pc has been running like a dream since. Having 8 of 16gb of ram isn't really much of a problem and over the next few days I will test the remaining slots and sticks and see how that goes.

My prediction is one of the sticks of ram is faulty, as running mem test for around 5 hours revealed only one error (this is the bit where you shoot me down for making silly predictions).

Thank you so much for your continued help. Its great having a stable build for nearly a week.

 

[Arc]

Good news.
Let us know for any further issue.