BSOD after long freeze - just web browsing

Trawler · 13 Oct 2017

Hi all,

Over the last few months my desktop has started experiencing BSODs following a freeze/lock up of around 60 seconds.

I've not been doing anything on my PC other than web browsing with Chrome. It more commonly occurs when a video is playing in Facebook or Twitter. Once I experienced the problem as soon as I tried playing a video in HPC-MC.

Sometimes my PC doesn't BSOD after a freeze. In this case after the machine unfreezes the Realtek HD Audio Manager's Input Device popup appears - even though I haven't changed anything with my audio connection. I tried changing to Realtek's latest driver but that didn't help, so I went back to Gigabyte's driver which is quite old.

I've tried updating drivers. I've performed a clean install of Nvidia drivers after running DDU under safe mode to remove the old drivers.

I've noticed my PC is more sluggish than I remember, especially browsing sites like Facebook or Twitter. Seems my phone is faster!

Thanks in advance for your help.

Trawler · 14 Oct 2017

I think I may have self-diagnosed after catching up on a few other threads I decided to run some HW monitoring tests. Found my internals and CPU were overheating. Opened up my box and found my CPU heatsink covered in dust. Gave everything a good clean out and now temperatures are at normal.

I'll keep this thread open for a day or two in case it hasn't resolved the issue, but it's likely I'm all good now.

Trawler · 15 Oct 2017

I just got another BSOD.

Computer is far more responsive since I cleaned it out and temps are under control and has been working perfectly up until this crash.

Here's a new dump taken just now after restarting from the latest crash.

Ztruker · 15 Oct 2017

You're runn the Insider 16299.15 build. There are no symbols for it so it's impossible to do any dump debugging.

The 10/14 dump does indicate a problem with nvlddmkm.sys.

Code:

BugCheck 133, {1, 1e00, fffff803b1a91370, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

You have the latest Nvidia driver version 387.92. All I can suggest it to completely uninstall it then reinstall just the driver and see if that helps.

Remove and install latest Nvidia drivers:

I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

Then do a custom install of only the NVidia graphics driver and the PhysX driver.

See if that gets rid of the problem. If not you could try down leveling the Nvidia driver.

Trawler · 15 Oct 2017

Thanks Zstruker,

I've used DDU and reverted to 382.33 and hopefully have blocked off the nvidia driver from auto updating. Will see how that goes. May also try to get off the Insider program.

Trawler · 20 Apr 2018

Hi everyone,
Reviving this old thread as I'm still having BSOD issues. I've recently opted out of the Insiders channels so no longer seeing the GSOD - perhaps it will be easier to diagnose? I've uploaded my latest diagnostic dump now that I'm off an Insiders build.
The crash only ever happens after a cold boot. When I first turn on my PC after about 30 mins of use (usually just web browsing) the system will start to stutter (if video or music playing, the sound stutters badly) before locking up. A minute or two later I'll see the BSOD. After a restart, everything works fine for as long as I keep the PC or on Restart.

Ztruker · 21 Apr 2018

Both dumps show a lot of activity with your Nvidia card right at the time of failure.
One has this:

Code:

BugCheck 133, {1, 1e00, fffff8004b479378, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

The other has this:

Code:

BugCheck 133, {1, 1e00, fffff8038126f378, 0}
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!NtTokenManagerCreateCompositionTokenHandle+243c )

dxgkrnl.sys is also video related so ties into your Nvidia card/driver.

When you reverted to 382.33, did that make any difference?

There is a new version available:

Version:

	391.35 ^WHQL
Release Date:	2018.3.27
Operating System:	Windows 10 64-bit
Language:	English (US)
File Size:	445.39 MB

You could give that a try using DDU first.

Trawler · 25 Apr 2018

Thanks for the help Ztruker.

I reverted to 382.33 some time back but that didn't solve the problem. I've been waiting to get off the Insiders ring before trying to get it fixed.

Anyway I did as you suggested, removed current drivers with DDU in safe mode and installed latest.

Having had the machine off for a few days I just got a BSOD about an hour after turning it on, uploaded latest crash dump.

Real odd that it only happens after a cold boot. I guess I could try a Win10 reinstall? Otherwise perhaps it's a hardware fault?

cwsink · 25 Apr 2018

Trawler said:

Real odd that it only happens after a cold boot. I guess I could try a Win10 reinstall? Otherwise perhaps it's a hardware fault?

The system uptime suggests to me it's more likely coming out of deep sleep rather than a cold boot:

Code:

Windows 10 Kernel Version 17133 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17133.1.amd64fre.rs4_release.180323-1312
Machine Name:
Kernel base = 0xfffff800`4b01c000 PsLoadedModuleList = 0xfffff800`4b3d92f0
Debug session time: Thu Apr 19 20:57:18.568 2018 (UTC - 7:00)
System Uptime: 0 days 20:28:35.906

Windows computers (by default) go into a deep sleep akin to hibernation when told to shutdown through the Start menu or physical power button. This has been the case since Windows 8.x. I've seen quite a few motherboards have issues with it but I've also seen many start working properly after updating the BIOS. The BIOS you're currently running:

Code:

0: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 0, Size=3050]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = F3
BiosReleaseDate = 04/17/2013
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z87X-UD3H

looks a bit out of date if this is the correct support page for your motherboard. I'd recommend updating to the latest if it is.

Trawler · 25 Apr 2018

cwsink said:

Windows computers (by default) go into a deep sleep akin to hibernation when told to shutdown through the Start menu or physical power button. This has been the case since Windows 8.x. I've seen quite a few motherboards have issues with it but I've also seen many start working properly after updating the BIOS. The BIOS you're currently running:

Code:

0: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 0, Size=3050]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = F3
BiosReleaseDate = 04/17/2013
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z87X-UD3H

looks a bit out of date if this is the correct support page for your motherboard. I'd recommend updating to the latest if it is.

Great point that and thanks for spotting the old bios revision. I just flashed to the latest non-beta version (F9 2014/03/19) and will report back later.