BSOD/immediate reboot when waking from sleep

Griff01 · 23 Feb 2017

When waking from sleep, the PC beeps, then reboots. The BSOD is not displayed due to the monitor not waking up in time. I know it is a BSOD due to the error message details after reboot.
The simple answer is to turn off sleep, but like a doctor giving medicine for the cold, this only masks the symptoms, but doesn't cure it.
Feel free to consider this a "low" priority thread, since the BSOD doesn't occur at any time besides sleep. Games are fine (except Guild Wars 2 which is due to a switch in Rhode Island timing out, which has nothing to do with this thread except me complaining).

So, ISSUE: BSOD on wake from sleep.
CCleaner was wiping my dump files, but I should have 3 attached now from today alone.
No other PC issues. Drivers appear up to date, Windows update runs regularly, video cards downloaded directly from manufacturer and up to date (no Betas).
Thoughts?

Lastly, where can I "learn" to read these files I'm uploading to you all? I am reasonable at shell scripting and networking, but much of this looks like gibberish because I've never learned it.

Thanks.

ICIT2LOL · 23 Feb 2017

Hello Griff mate now this is really odd because I see you have AMD graphics yet the last dump files are showing a problem with NVidia graphics

So are your specs up to date as in have you changed the GPU?? If so this may explain the BSOD's

Code:

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`08ff5a48 fffff880`0830f1f0 : 00000000`00000116 fffffa80`0ec70010 fffff880`07d82114 ffffffff`c000009a : nt+0x70400
fffff880`08ff5a50 00000000`00000116 : fffffa80`0ec70010 fffff880`07d82114 ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5d1f0
fffff880`08ff5a58 fffffa80`0ec70010 : fffff880`07d82114 ffffffff`c000009a 00000000`00000004 00000000`00000018 : 0x116
fffff880`08ff5a60 fffff880`07d82114 : ffffffff`c000009a 00000000`00000004 00000000`00000018 fffffa80`0ec70010 : 0xfffffa80`0ec70010
fffff880`08ff5a68 ffffffff`c000009a : 00000000`00000004 00000000`00000018 fffffa80`0ec70010 fffff880`082e2913 : nvlddmkm+0x97b114
fffff880`08ff5a70 00000000`00000004 : 00000000`00000018 fffffa80`0ec70010 fffff880`082e2913 fffff880`07d82114 : 0xffffffff`c000009a
fffff880`08ff5a78 00000000`00000018 : fffffa80`0ec70010 fffff880`082e2913 fffff880`07d82114 fffffa80`0d66f000 : 0x4
fffff880`08ff5a80 fffffa80`0ec70010 : fffff880`082e2913 fffff880`07d82114 fffffa80`0d66f000 00000000`00000000 : 0x18
fffff880`08ff5a88 fffff880`082e2913 : fffff880`07d82114 fffffa80`0d66f000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`0ec70010
fffff880`08ff5a90 fffff880`07d82114 : fffffa80`0d66f000 00000000`00000000 ffffffff`c000009a fffffa80`0d65e410 : dxgkrnl+0x30913
fffff880`08ff5a98 fffffa80`0d66f000 : 00000000`00000000 ffffffff`c000009a fffffa80`0d65e410 fffffa80`0d72ad50 : nvlddmkm+0x97b114
fffff880`08ff5aa0 00000000`00000000 : ffffffff`c000009a fffffa80`0d65e410 fffffa80`0d72ad50 fffffa80`0d72a810 : 0xfffffa80`0d66f000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+97b114
fffff880`07d82114 48ff25e5cce6ff  jmp     qword ptr [nvlddmkm+0x7e7e00 (fffff880`07beee00)]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+97b114

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:wrong_symbols

FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner

Griff01 · 23 Feb 2017

Strange. I changed to the NVIDIA GeForce GTX1070 several weeks ago. When I did, I ran DDU v17.0.4.3 to remove all AMD graphics drivers. I was just in the process of updating my system specs when I noticed you had replied.
DDU is supposed to remove all old drivers, so I could do a clean install of the NVIDIA. Apparently the NVIDIA drivers are causing issues?

ICIT2LOL · 24 Feb 2017

Hello Griff yes mate you do need to do the driver for that card perhaps it did not install properly first time.
NVIDIA DRIVERS GeForce Game Ready Driver WHQL

ICIT2LOL · 24 Feb 2017

Griff I have just thought too you can check the Device Manager to see what device you have installed and the details of the driver see pic. So if you now have NVidia there then all should be ok.

Griff01 · 24 Feb 2017

ICIT2LOL, I do see one .dll that doesn't appear to be from NVidia. It has "generic" in the name. For testing and possible resolution. I am going to uninstall drivers, run DDU again, reboot while off the net, and install the drivers from the NVidia link you provided. Since this issue only occurs when I allow the computer to sleep, it may be a day or two before I post an update (or mark as solved and add to Rep), as I'll be on the system most of today and won't have a chance to let it sleep.
Thanks again, and wish me luck.

ICIT2LOL · 24 Feb 2017

Ok Griff that sounds like a go to me and don't worry about getting back real quick the forum's going nowhere and nor am I (banged up in hospital for a while) LOL!!
John:)

Griff01 · 01 Mar 2017

John,
I hope all is going well and that the hospital stay is close to being over. Whatever you did to get banged up, don't do that again.

I have still been experiencing the same issues, and am uploading a new file of just the minidumps since the original post. If you want me to re-run the DM Log Collector to repost all the files, let me know. I'm just assuming that the minidumps are key, and most likely the only thing that changed except for my complete removal and reinstall of the graphics drivers.
Cody

ICIT2LOL · 01 Mar 2017

Hiyya Griff now the dumps have our old friend the NVidia graphics driver.

Code:

BugCheck 116, {fffffa800fe4d010, fffff88013a44010, ffffffffc000009a, 4}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Now can you try updating the driver yet again and if the machine is still throwing those blue screens - it might be an idea to go back a version of the driver because that can sometimes fix the problem and I have an idea that drivers in any case vary form version to version sometimes only in very minor details.
Drivers | GeForce the current one is 378.66 and the previous 378.49 and before that 376.33 but I think the latter may be just a little too old.

I have Googled your board too and see that it came with Norton security trial and if it were me I would be uninstalling that crap altogether not just because I think it is rubbish but because it is clutter and who knows what issues it may cause. But I shall leave that up to you just to say you will need to use the Norton removal tool and if necessary delete the Symantec entries in the registry. But lets get this driver issue settled first.

Now yes my son has banned me from step ladders - well any form of ladders because I fell from one hanging some curtains I had washed and broke my leg near the hip. That was back on 27th December and I am still only 30% weight bearing on the limb and another three weeks just over before I see the surgeon again for a review. But hey there are worse off than me eh?/ and suffice to say look after yourself mate because a broken leg is no fun!!

Edit: Griff mate I just saw this in the specs for your board and as the board looks to be fussy about what to do with what can you make sure it is in the PCIEX16 slot

(Note 3) For optimum performance, if only one PCI Express graphics card is to be installed, be sure to install it in the PCIEX16 slot. see pic

Griff01 · 09 Mar 2017

John, I've run for about a week now with no recurrence. Of course, now NVIDIA is asking me to update my drivers, due to a new release. I never had to roll them back, just did a reinstall. Thanks for all of your help. I added to your rep, but it only let me do it once. That's unfair since I thought you deserved two thumbs up. Get well soon, and watch out for ladders, step-stools, even standing on chairs. Good luck mate, and thanks again.
Cody