Computer Won't Wake from Sleep - Bluescreens often

vecral

Distinguished
Jun 5, 2008
19
0
18,510
Hello! I've been fighting with this problem for about 3 weeks now. I've tried pretty much every solution I could find online and have been unable to make progress, so now I've admitted defeat and am begging for any help anyone can offer. Here's what's going on:
CSS:
New homebuilt computer is having trouble waking from longer sleeps. Short sleeps are fine, but after a certain (seemingly random) length of time, the computer has a kind of sleepy crash. The flashing sleep LED stops flashing, the keyboard won't respond, and the only recourse is to hard reset the computer.

Sometimes, I get lucky and the blinking light still blinks. I press a button to wake up the computer, and it wakes up into a BSOD (again, this is only for longer sleeps - short sleeps are ok). It's usually a different BSOD every time (argh!). I have three minidump files I can append to the bottom of this question.

The really aggravating thing about troubleshooting this is that I have to wait >2-3 hours for the problem to appear, so I can only try a few fixes per day. Speaking of fixes...

Components:
Motherboard: MSI 970 Gaming AM3+
CPU: AMD FD6300WMHKBOX FX-6300
GPU: SAPPHIRE 100366-2L Radeon R7 260X 2GB
RAM: Crucial Ballistix Sport 8GB Model BLS8G3D1609DS1S00
PSU: ENERMAX REVOLUTION X't ERX430AWT
SSD: SanDisk Ultra Plus SDSSDHP-256G-G25 (Boot drive)
HDD: WD BLACK SERIES WD2003FZEX
OS: Windows 7 Home Premium

Attempted Fixes:

1. Tried changing BIOS sleep settings from S3 to S1. No change. Reverted back to S3.
2. Tried very slightly increasing RAM and CPU voltage (MB auto settings were a bit below what was on the specs). No change. Reverted back to MB auto settings.
3. Tried EVERYTHING in power options - turning off hibernate, turning off hybrid sleep, turning off selective suspend, disabling PCI link, setting turn off Hard Disk to "never..." No change. Kept settings as listed here.
4. Turned off wake on PCI and Network in BIOS. No change. Left off.
5. Tried to only allow wake on OS (rather than BIOS). Computer wouldn't wake up at all, ever. Reverted back to BIOS.
6. Disabled computer wake on network in network settings. No change.
7. Re-flashed MB BIOS. No change.
8. Unseated and re-seated all PSU connections. Changed SSD connection to different plug on different string. No change.
9. Ram Memtest86. No problems found. Changed RAM slot anyway. No change.
10. Reformatted SSD and reinstalled Windows. Did not test before installing drivers, but after Windows Updates and drivers were installed... no change.
11. Cried a little bit. Felt better for a while. No change.

So I have some theories:

I'm wanting to point my finger either at the SSD (because a lot of people are talking about SSD problems in forums about sleep), but I don't know how. It seems to be working perfectly otherwise.

I also want to point my finger at the Motherboard network adapter. It's a Killer e2200 integrated into the Motherboard and some of my errors point at that as the cause. I've tried updating the drivers, installing the software, uninstalling the software, etc. Nothing's making progress, but I did just follow MSI's directions for what to do if you get BSOD because of the e2200. I'll update if that makes a difference, but I don't have much hope.

Any suggestions? Any information at all I can provide to you? Please let me know and I'll get it to you right away!

Most recent minidump follows. There others too if you want them! Thank you so, so much!


Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062915-10998-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`030a5730
Debug session time: Mon Jun 29 10:21:25.535 2015 (UTC - 4:00)
System Uptime: 0 days 0:58:12.799
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002edc5f8, fffff88006f0bd40, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiCancelTimer+28 )

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

ESPclipse

Reputable
May 27, 2014
364
0
4,960
This is a tough one. ntkrnlmp.exe is a Windows component file, so something somewhere else may have initiated the crash. A bad driver, perhaps? Load to safe mode and test to see if the problem persists. I would also like to know where you get your driver updates. Some third-party driver update softwares will install garbage unsigned drivers that do this to people, and it can be difficult to track. In this case, software like BlueScreenView is a must. Anyhow, if the problem does not persist in safe mode, then I would naturally assume the issue is caused by some driver. Also, whenever you are working in normal boot mode, open a Command window and check your system for errors with

sfc /scannow

and check disk integrity with

chkdsk /f

These may not return anything, but it's worth a shot. Also, please post as many minidump reports as you can. I really do not want to have to suggest that you clean reinstall, but that may be the only option for you. I hope you can find a fix!
 

vecral

Distinguished
Jun 5, 2008
19
0
18,510
Awesome - thanks for the suggestions! I'll try safe mode in a moment, but because it'll take about 4 hours to determine if the solution worked or not, it'll be a bit before I get back on that one.

I'm getting the drivers straight from the MSI website for chipset, USB3, and Ethernet drivers. Straight from AMD for the Catalyst Control Center drivers for GPU.

More minidumps at the end of this post!

sfc /scannow reported back that Windows Resource Protection did not find any integrity violations.

Will run chkdsk at next reboot and will report back ASAP.

Minidump time!

------------------------------


Loading Dump File [C:\Windows\Minidump\062915-10389-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`02e52000 PsLoadedModuleList = 0xfffff800`03099730
Debug session time: Mon Jun 29 13:33:48.749 2015 (UTC - 4:00)
System Uptime: 0 days 0:45:38.029
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88001560b26, fffff880031942e8, fffff88003193b40}

Probably caused by : rasl2tp.sys ( rasl2tp!GetRegistrySettings+24 )

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

--------------------


Loading Dump File [C:\Windows\Minidump\062915-6692-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03060730
Debug session time: Mon Jun 29 09:17:24.225 2015 (UTC - 4:00)
System Uptime: 0 days 7:26:40.144
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88003c68ffc, 0, fffff88006ab5b00, 0}

*** WARNING: Unable to verify timestamp for xhcdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for xhcdrv.sys

Could not read faulting driver name
Probably caused by : xhcdrv.sys ( xhcdrv+4b00 )

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

These are the only two I have left since I reinstalled windows. That's the thing about a clean reinstall suggestion - I just did that this morning :-(
 

vecral

Distinguished
Jun 5, 2008
19
0
18,510
Here's the chkdsk results - testing safe mode now!:



Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
178432 file records processed. File verification completed.
348 large file records processed. 0 bad file records processed. 0 EA records processed. 47 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
231248 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
178432 file SDs/SIDs processed. Cleaning up 210 unused index entries from index $SII of file 0x9.
Cleaning up 210 unused index entries from index $SDH of file 0x9.
Cleaning up 210 unused security descriptors.
Security descriptor verification completed.
26409 data files processed. CHKDSK is verifying Usn Journal...
37050056 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

250056703 KB total disk space.
94681868 KB in 151388 files.
111412 KB in 26410 indexes.
0 KB in bad sectors.
289539 KB in use by the system.
65536 KB occupied by the log file.
154973884 KB available on disk.

4096 bytes in each allocation unit.
62514175 total allocation units on disk.
38743471 allocation units available on disk.

Internal Info:
00 b9 02 00 92 b6 02 00 ce 50 05 00 00 00 00 00 .........P......
4e 00 00 00 2f 00 00 00 00 00 00 00 00 00 00 00 N.../...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
 

jt_sday

Reputable
Feb 18, 2015
2
0
4,510
Usually a BSOD indicates a bad driver or software conflict. Have you installed new hardware or software recently? If so, when? Maybe a simple system restore would do the trick.
 

vecral

Distinguished
Jun 5, 2008
19
0
18,510
It's all new hardware, unfortunately. The system, since built, has never not had this problem. I'm open to getting an RMA on individual pieces of hardware - I just don't know which to RMA or if that's even the best solution.

Thank you!
 

jt_sday

Reputable
Feb 18, 2015
2
0
4,510
You may also want to check compatibility of the hardware you are connecting to the MOBO. I have seen issues where the manufacturer says yes its compatible, but the system begins to have problems such as the one you are experiencing. I would disconnect all peripherals except the mouse and keyboard and begin my process of elimination there.

 

ESPclipse

Reputable
May 27, 2014
364
0
4,960
Did some research and thought I'd share what I've found. xhcdrv.sys is a driver for a USB host controller, so update that whenever you find time. Do that with Device Manager, preferably. I actually use IObit's Driver Booster software to get my system drivers, and have not run into any bad drivers thusfar (*knock on wood*). Next, and the likely larger concern, is rasl2tp.sys, an old proprietary WAN driver that hasn't been updated since XP, and has been plaguing fresh builds since. Considering its age and necessity of implementation, rasl2tp.sys has been the butt of a number of system errors. I found one case in which it interrupts Windows' hibernation process, so you should play around with your system's hibernation/power management options (Control Panel -> Hardware & Sound -> Power Options) to see how often the problem is reproducible, or if a certain configuration will run successfully for you. Oh, and update your network drivers when you can as well. Also would like to know if you have any software provided by MSI, probably associated with your motherboard. ASUS and Gigabyte have notoriously bad motherboard management software, but I do not know about MSI. Keep testing, and keep digging. I have been building, troubleshooting, and repairing personal computers for years and have yet to resort to total system reinstall, even with Windows. Your issue is certainly not unique, and so there must be a fix out there somewhere. Keep fighting my man
 

vecral

Distinguished
Jun 5, 2008
19
0
18,510
Thanks for continuing to look into my issue!

Some updates on my end:

I can't put the computer to sleep in safe mode, so I can't test whether the problem occurs there or not.

Not currently running any of MSI's MB management software (I tried to install it all the first time I ran into the problem, but have since reinstalled Windows).

All of the hardware is listed by the MSI as compatible with the system.

I turned off EHCI Hand-Off - no change.

I ran IObit's Driver Booster per your recommendation and... it found a ton of out of date updates! That's awesome. I wanted to make sure that everything was running cleanly, though, so I formatted my hard drive and started over again.

Brand new Windows install on clean hard drive. Ran IObit's software, got all the drivers up and running. Ran just "Important" Windows Updates until they didn't show up any more (about 4 rounds of updates and restarts). Put the computer to sleep, left it overnight, went to wake it up in the morning and...

It shut down. I pressed the spacebar on the keyboard, it looked like it was going to wake up for about two seconds, then it just cut power. On reboot, it indicated that Windows didn't shut down properly, but there was no BSOD or minidump available. But hey, no BSOD is progress!!!

On a whim, I decided to see what would happen if I turned sleep OFF and just let it sit idly. I set the monitor to turn off after 10 minutes, but otherwise the computer remain on. After an hour I came back to discover that I couldn't get back to Windows. The monitor "woke up" but was just showing a black screen. No amount of mouse moving or key mashing would do anything until I finally hit Ctrl+Alt+Del, which brought everything back to life. Gah!

Here's what's next: I'm going to remove the PSU and replace it with another PSU I have lying around. If that doesn't change anything, I'll go through the list and replace RAM, then GPU. If that doesn't work I'm stuck with the CPU/MB combo or the SSD, but at least I'll have a much smaller list to RMA.

Again, many thanks, and any further suggestions you have would be amazing!