New Windows 7 Pro Install - BSOD After Resume From Sleep

itsBpK

Commendable
Aug 17, 2016
3
0
1,510
Would someone mind looking at my DMP file to try and help me figure out why I'm getting a BSOD shortly after resuming from sleep please?

This is a new Win7 Pro install, all Windows Update performed.

EVGA Z170 FTW
i7-6700k
32GB Corsair 3000Mhz

https://drive.google.com/open?id=0Bx1OI6OWhTm7OE9BVDlnTnlZSTQ

(I also have the 900mb dmp file from the driver verifier tool that I enabled if that is needed)
 
Solution
basically the system told the keyboard to change its power state and it did not respond. A timeout period happened and the system bugchecked because windows thinks the hardware failed. Windows 7 shipped with most of the low power functions turned off, starting with windows 8 and above most hardware drivers will install with these functions turned on by default. The problem is many windows 7 system have bugs where the functions don't actually work and driver vendors make a version of the driver and assume the functions work. I would guess your new razer drivers have the functions on when you updated the driver.
you might go into windows control panel, find the razer devices, right click to get properties and turn off the power...

itsBpK

Commendable
Aug 17, 2016
3
0
1,510
After about 6 hours of trial-and-error, uninstalling programs and motherboard drivers, I determined the culprit was the EVGA USB 3.0 Intel eXtensible Host Controller driver.

The computer would sleep and resume just fine multiple times after uninstalling that driver.

Then I found this FAQ from EVGA, followed it precisely regarding in what order to install drivers, and then to reboot and disable Windows 7 Boot Option in BIOS, and it seems to be working ok now with the USB drivers installed.

http://www.evga.com/support/faq/afmviewfaq.aspx?faqid=59652

...
12. Download the most CURRENT DRIVERS from EVGA in a primary directly called Z170 Motherboard Drivers, which are:
a. .NET Driver, Version 45 or higher
b. Audio Driver, Version 431 or higher
c. Chipset Driver, Version 10.1.1.7 or higher
d. Chipset Network Driver, Version 30.100.1519.08 or higher
e. Intel HD Graphics (optional)
f. Intel ME (optional)
g. USB 3.0 Driver, Version 4.0.0.36, or higher

13. Upon all MOST CURRENT drivers downloaded from EVGA, follow the order of loading of the updated drivers:
a. Chipset Driver
b. Chipset Network Driver (you will see at the end of the update, a reference to the I/O being updated.
c. .NET Driver
d. Audio Driver
14. The LAST UPDATE should be the USB 3.0 Driver, most current version.
When this update is performed, you WILL LOSE all USB conductivity for approximately 40 seconds to about a minute;
however the keyboard, mouse and all other USB ports will be fully operation after that.
15. If the system wants to restart after this, BE SURE TO ENTER THE BIOS upon the RESTART, enter through the BOOT tab
and DISABLE the Windows 7 Installation. Save and exit.
.
.
.
.
 
basically the system told the keyboard to change its power state and it did not respond. A timeout period happened and the system bugchecked because windows thinks the hardware failed. Windows 7 shipped with most of the low power functions turned off, starting with windows 8 and above most hardware drivers will install with these functions turned on by default. The problem is many windows 7 system have bugs where the functions don't actually work and driver vendors make a version of the driver and assume the functions work. I would guess your new razer drivers have the functions on when you updated the driver.
you might go into windows control panel, find the razer devices, right click to get properties and turn off the power management features. so the device is not put into a low power state. to work around the problem if you can not find a fix.

you are using a 2016 version of a bios with old drivers from 2010. be sure to install your motherboard drivers that match your bios version. I would apply all of the motherboard drivers windows 7 updates.

looks like the system broke in some power management function in a keyboard driver. (razer drivers? the system was up 20 hours)
you would have to change your memory dump type to kernel for the debug info not to be removed from the memory dump.

you can also, start cmd.exe as an admin and run
powercfg.exe /energy
and look at the report to see if errors are detected.


you have verifier functions turned on, you might want to turn them off:
start cmd.exe as an admin then run
verifier.exe /reset

 
Solution

TRENDING THREADS