Requesting help/analysis of sleep-related BSODs ...

Omnimaxus · 10 Oct 2015

Thanks, axe0. I'm sorry, but that wasn't what I was looking for. I was referring to changing the name of my user profile. The link you provided even says that the method discussed won't work for that purpose (see post # 6). (Just FYI - but thanks.) Anyway, I went online and found a NFO file editor, and used that to edit out all personally identifiable information from the MSINFO32 file. I also edited all other files, and saved them in their original format. Now you should be able to view everything (especially the MSINFO32 file) without any problems (use the System Information utility to open MSINFO32). OK? I really appreciate your time and help.

(See attached ZIP file below.)

Please let me know what you find. Thanks again.

P.S.: Everyone - the NFO editor I found is named NFOPad. Can find it here.

axe0 · 10 Oct 2015

As you stated that within a few minutes the temperature of the GPU is coming at around 80C and you have cancelled it because of that.
But, can you try to run Furmark again? Running on temperatures around 85C is only something to worry when it is very frequently and the GPU could run around 90-95C with a good cooler.

Note

This information counts only for this GPU

What cooling system do you have?

There are lots of errors from Windows applications.
Please try following:

Open an admin command prompt
Copy/paste "sfc/scannow" (without quotes) and press enter
When it finished reboot your system
Open again an admin command prompt
Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

In case of

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:

Please check logitech for driver updates
Please check the following links for driver updates
http://www.carrona.org/drivers/drive...d=wdcsam64.sys

http://www.wacom.com/en/customercare/drivers.aspx for the Wacom drivers

http://www.carrona.org/drivers/drive...id=rawdsk3.sys

http://www.egistec.com/oem-acer001/program-update.aspx

Code:

3: kd> lmvm wdcsam64
start             end                 module name
fffff800`75940000 fffff800`75943880   wdcsam64   (deferred)             
    Image path: \SystemRoot\System32\drivers\wdcsam64.sys
    Image name: wdcsam64.sys
    Timestamp:        Wed Apr 16 10:39:08 2008 (4805BB2C) // Needs updating!
    CheckSum:         0000D887
    ImageSize:        00003880
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


3: kd> lmvm wacomrouterfilter
start             end                 module name
fffff800`733f0000 fffff800`733fa000   wacomrouterfilter   (deferred)             
    Image path: \SystemRoot\System32\drivers\wacomrouterfilter.sys
    Image name: wacomrouterfilter.sys
    Timestamp:        Wed Aug 06 20:10:12 2014 (53E26F84)
    CheckSum:         0000921E
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


3: kd> lmvm wachidrouter
start             end                 module name
fffff800`729e0000 fffff800`729fd000   wachidrouter   (deferred)             
    Image path: \SystemRoot\System32\drivers\wachidrouter.sys
    Image name: wachidrouter.sys
    Timestamp:        Wed Aug 06 20:10:05 2014 (53E26F7D)
    CheckSum:         00023A5F
    ImageSize:        0001D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


3: kd> lmvm rawdsk3
start             end                 module name
fffff800`73090000 fffff800`7309c000   rawdsk3    (deferred)             
    Image path: \??\C:\Windows\system32\drivers\rawdsk3.sys
    Image name: rawdsk3.sys
    Timestamp:        Tue Feb 11 22:10:17 2014 (52FA91B9)
    CheckSum:         0000B993
    ImageSize:        0000C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


3: kd> lmvm PDFsFilter
start             end                 module name
fffff800`759d0000 fffff800`759e8000   PDFsFilter   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\PDFsFilter.sys
    Image name: PDFsFilter.sys
    Timestamp:        Thu Aug 23 23:57:13 2012 (5036A739)
    CheckSum:         0001A15A
    ImageSize:        00018000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


3: kd> lmvm lvbflt64
start             end                 module name
fffff800`72860000 fffff800`72864b80   lvbflt64   (deferred)             
    Image path: \SystemRoot\System32\drivers\lvbflt64.sys
    Image name: lvbflt64.sys
    Timestamp:        Tue Oct 23 04:10:38 2012 (5085FC9E) // Logitech
    CheckSum:         0000DCDF
    ImageSize:        00004B80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


3: kd> lmvm lvuvc64
start             end                 module name
fffff800`75400000 fffff800`75887d80   lvuvc64    (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\lvuvc64.sys
    Image name: lvuvc64.sys
    Timestamp:        Tue Oct 23 04:12:08 2012 (5085FCF8) // Logitech
    CheckSum:         004912C7
    ImageSize:        00487D80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


3: kd> lmvm lvrs64
start             end                 module name
fffff800`761f0000 fffff800`76244000   lvrs64     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\lvrs64.sys
    Image name: lvrs64.sys
    Timestamp:        Tue Oct 23 04:11:24 2012 (5085FCCC) // Logitech
    CheckSum:         00058CF8
    ImageSize:        00054000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Omnimaxus · 10 Oct 2015

Thanks - unfortunately, I do not have the time today to devote myself 100% to this problem today. I will try tomorrow. I should add that when I had Windows 8.1 (with "Update") installed, I did not have this problem. It emerged only after installing Windows 10. Not sure if that will help. I will follow your advice, but not right now. Meantime, do you have any actual thoughts about what is going on? Unsure about when I will check back here again, but it will be later. Thanks again.

axe0 · 10 Oct 2015

Omnimaxus said:

Thanks - unfortunately, I do not have the time today to devote myself 100% to this problem today. I will try tomorrow. I should add that when I had Windows 8.1 (with "Update") installed, I did not have this problem. It emerged only after installing Windows 10. Not sure if that will help. I will follow your advice, but not right now. Meantime, do you have any actual thoughts about what is going on? Unsure about when I will check back here again, but it will be later. Thanks again.

Because Windows 10 is still new, it has lots of bugs, but with upgrading there are only more bugs.

I think this is a known problem with Windows 10, but before we can say that it is a problem with the sleep mode we need to rule out a few things.

Omnimaxus · 11 Oct 2015

Major update:

On a whim, I uninstalled the NVIDIA drivers from NVIDIA's website using Display Driver Uninstaller, and allowed my computer to obtain the necessary display driver via Windows Update. After installation, I discovered that my computer no longer gets the BSOD. It goes to sleep, and wakes up just fine now. So, it appears to have been a driver issue after all. Not hardware-related (e.g. GPU or RAM). Really wish NVIDIA would get it together. From what I have seen online, their latest drivers have been really buggy.

However, I did see that the update available for "Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3, Graphics Adapter WDDM2.0, Other hardware" did fail to install, and when I tried to run Windows Update again to try again, it wouldn't detect the update again. Maybe Microsoft is preventing installation of the updated WDDM files? I don't know. But I'm glad things seem to be working 100%. That's what counts. Thanks, axe0, for all your help and time. Marked as "solved."

axe0 · 11 Oct 2015

Thank you for sharing what you have done to solve the problem and you're welcome :)

Omnimaxus · 11 Oct 2015

Update:

Still no BSODs upon going into sleep mode and waking up the system, but I got one "Display driver stopped responding and has recovered" message with a blinking screen which reverted back to normal after a few seconds. I wasn't doing anything special at the time; just switching between windows on my desktop. At least it's not a BSOD, but I figured some people may be interested in knowing this, because it really does point to it being a driver issue. If this keeps up, I may be forced to dump NVIDIA and go with AMD.

Omnimaxus · 12 Oct 2015

Final update:

Broke down and bought a mid-range budget card (Gigabyte AMD R7 370 2 GB) that's a notch above my old GTX 660. Uninstalled the NVIDIA display drivers, gave the inside of the computer a good cleaning out with compressed air, and everything works perfectly with the latest AMD drivers direct from AMD's website. The computer goes to sleep, and wakes up without a hitch.

Runs my games a bit better, too. No "display driver stopped responding" errors (so far!). NVIDIA may make great hardware, but their driver quality has gone to the dogs. Probably will stick with AMD from this point on. Anyway, if anyone else is having similar problems as I did, consider going with AMD for your next video card purchase. Thanks again to axe0 for all his help. The end!