BSOD Usually on Wake From Sleep

Brucex64 · 15 Apr 2015

I am not a tech pro, I didn't realize about the Intel chipset but yes that's right, this board does have the Intel chipset.. And as easy as it was, it didn't occur to me to look in the device manager to find my version. I see it now, mine is outdated.

I checked the latest updates from both Intel & Gigabyte's site and they both have different version numbers. I went with the Gigabyte version because on the Readme sheet it says its for 4th gen Core; the other one from Intel only says 2nd gen Core i7. The Haswell CPU is 4th gen. It installed successfully so I will see if it crashes.

Arc · 16 Apr 2015

Brucex64 said:

It installed successfully so I will see if it crashes.

Report us back when needed.

Brucex64 · 28 Apr 2015

Well, its back. I had 1 crash yesterday and 1 today on wake. Attached is the zip file with the latest system info.

Arc · 28 Apr 2015

A new thing this time.

Code:

BugCheck 3B, {c0000005, fffff8000308d0cb, fffff88008e3de00, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )

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

Code:

fffff880`08e3d7e8  fffff880`05978385Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xd0385

It is the latest 350.12 WHQL display driver. I havent tried it myself yet, but not so many members report for it. Your issue is the second one most probably.

An improper update to the display driver can rightly cause the stop 0x3B issue. So if teh update is done by GeForce Experience, we need to take some actions there.

Uninstall the installed display driver using Display Driver Uninstaller. Then download 350.12 WHQL and install it as follows:

Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

That means, you ire installing two things only, the display driver and PhysX.

One more thing. Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus. You may keep Rainmemter too, that is harmless.
Apply > OK
Accept then restart.

Report us for any further issue.

Brucex64 · 05 May 2015

Well I did that with no issues, but I got another two BSODs. Here's the log collected details. It seems that its a different thing each time.

Arc · 06 May 2015

Now it is the time to take it seriously. There should not be random failing drivers after every few days. Do memtest86+ test as suggested earlier. Before closing the program after 8 passes, take a camera snap of the memtest86+ screen and let us see it.

We need to be confirmed what the memtest86+ says.

Brucex64 · 07 May 2015

Ok, actually got more than 9 passes in. Here's a screenshot of it.

Arc · 07 May 2015

Your RAM ....

Attachment 358473

Apparently the RAM is not listed in the QVL for the motherboard. Check it: Attachment 358470

For 1600 MHz ....

Attachment 358471

For 1300 MHz ....

Attachment 358472

Boot into the BIOS and disable XMP. See how it works. Let us know.

Brucex64 · 07 May 2015

I just checked the bios and extreme memory profile was already set to "disable".

Arc · 08 May 2015

If it is not XMP enabled, then why memtest86+ shows it as XMP? And should not it be 1333 MHz without XMP enabled?