BSoD and computer not waking up from sleep

LaneyD · 12-27-2011, 01:50 PM

Hello - I've been having this problem since I got the computer. Any help would be very much appreciated!

What happens is that periodically when the computer goes to sleep (either by itself or from me closing it) it will not wake back up. The key boards will sometimes light and the fans will come back on but the screen remains off. The only way to fix it is to do a hard shut down. Less frequently I'll get a BSoD when it reboots or I'll just notice that I have one after I've walked way from the computer for a while. No idea what's going on but the most recent BSoD stated "Driver_Power_State_Failure".

I was unable to run the system health report - got the following message:

An error occured while attempting to generate the report.
The wait for the report generation tool to finish has timed out.

Here is what I could find of the requested information
Windows 7 Home Premium SP 1
x64
This is the OS that came installed
Its OEM
The system is less than a year old
Intel Core i7-263QM CPU @ 2.00GHz
GeForce GTX 560M
Not sure of the motherboard or power supply
Asus G53S

If you need anything else or the information I couldn't provide let me know and I'll try and find out.

Thanks so much!
Laney

**usasma** · 12-28-2011, 10:49 AM

NOTE: I have severe eye problems. If I do not respond to your postings, please PM another staff member for assistance.

MSINFO32 shows that the drivers for your USB Bluetooth device(s) aren't installed. Please visit the Asus support website and install these drivers immediately. There are some drivers installed, but the missing one's are listed below:

Quote:

Bluetooth Peripheral Device BTHENUM\{936DA01F-9ABD-4D9D-80C7-02AF85C822A8}_VID&0001000F_PID&0000\8&1C65FBBE&0&2013E05D0153_C00000000 The drivers for this device are not installed.

Bluetooth Peripheral Device BTHENUM\{453994D5-D58B-96F9-6616-B37F586BA2EC}_VID&0001000F_PID&0000\8&1C65FBBE&0&2013E05D0153_C00000000 The drivers for this device are not installed.

MSINFO32 shows 8 STOP 0x9F BSOD's over the last 2½ months
2 blame a Bluetooth driver (btfilter.sys)
4 blame a Windows USB driver (usbhub.sys)
2 blame the kernel (core) of the OS (not likely as you'd have more problems other than an occasional BSOD if this was the case).

I'm uncertain if your Trend Micro Internet Security is at fault here - but the easy test is to uninstall it and then reinstall the latest version from Trend Micro to see if that fixes things.

While I'm waiting for the memory dumps to run, let's discuss the black screen problem.
In most cases, a black screen issue like this isn't easily fixable - but there are steps to take to see if it's something easy to fix. At work we've spent weeks trying to fix these issues (without success) only to resort to wiping the hard drive and reinstalling Windows.

We now resort to this procedure:
- Update ALL Windows Updates and then ALL drivers.
- Try a System Restore to a date before these problems started happening.

**usasma** · 12-28-2011, 10:51 AM

The memory dumps seem to indicate a USB problem - but they don't specifically mention any particular device. Please remove any attached USB devices (particularly any USB BlueTooth devices), then update the BlueTooth drivers and the Chipset drivers. Then monitor to see if there are any further BSOD's.

Also, please try Driver Verifier (according to the following instructions) to see if it can force the system to name the driver that's causing this:

Quote:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool" and "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\122711-26566-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Dec 27 15:25:14.996 2011 (UTC - 5:00)
System Uptime: 1 days 19:26:39.995
Probably caused by : usbhub.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_usbhub.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`099ec060 fffff800`00ba2748 fffffa80`0b82a110
BiosVersion = G53SW.203
BiosReleaseDate = 02/15/2011
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\121511-62072-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Dec 15 07:45:24.452 2011 (UTC - 5:00)
System Uptime: 5 days 13:06:26.451
Probably caused by : usbhub.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_btfilter_IMAGE_usbhub.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`09819060 fffff800`00b9c3d8 fffffa80`063be450
BiosVersion = G53SW.203
BiosReleaseDate = 02/15/2011
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\110411-28392-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Nov  3 22:42:15.641 2011 (UTC - 5:00)
System Uptime: 4 days 12:11:55.368
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`0616c8e0 fffff800`00b9c4d0
BiosVersion = G53SW.203
BiosReleaseDate = 02/15/2011
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101511-18470-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Oct 15 12:32:30.833 2011 (UTC - 5:00)
System Uptime: 2 days 17:36:52.942
Probably caused by : usbhub.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_usbhub.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`09bab060 fffff800`00b9c4d8 fffffa80`0ae47790
BiosVersion = G53SW.203
BiosReleaseDate = 02/15/2011
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

**usasma** · 12-28-2011, 10:57 AM

Just FYI, here's the !irp output from the latest memory dump:

Quote:

0: kd> !irp fffffa800b82a110
Irp is active with 10 stacks 8 is current (= 0xfffffa800b82a3d8)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 e1 fffffa80099ec060 00000000 fffff800030c6430-fffffa8010ebad80 Success Error Cancel pending
\Driver\usbhub nt!IopUnloadSafeCompletion
Args: 00014400 00000001 00000001 00000002
[ 16, 2] 0 e1 fffffa8009912a00 00000000 fffff800030c6430-fffffa8006104420 Success Error Cancel pending
\Driver\usbccgp nt!IopUnloadSafeCompletion
Args: 00014400 00000001 00000001 00000002
[ 0, 0] 0 0 00000000 00000000 00000000-fffffa8005763340

Args: 00000000 00000000 00000000 00000000

LaneyD · 12-29-2011, 06:09 AM

Thanks for your replies! I'll will try all of this after work tonight and report back.