USB device not detected, BSOD Drive Power State Failure

[gabusch]

Hi everyone,

I am using a Toshiba Satellite A505-S6025 laptop running Windows 7 Pro 64-bit, 4GB RAM, Nvidia 310M graphics card.

Things have been working well for a couple of months until yesterday, after I installed a Western Digital Mybook World Edition (1TB) and the most recent Windows updates. After these installations, I have been having 2 problems:

1.) First thing I noticed is that shutdown takes forever, and ends with a BSOD with DRIVER_POWER_STATE_FAILURE message.

2.) Secondly, none of my USB devices are being recognized anymore. Sometimes when I have these devices plugged BEFORE powering Windows on they get recognized properly, but if I plug any USB devices after Windows loads I do not get any recognition at all.

I've tried updating to the latest video drivers, BIOS, and uninstalling the programs that came with the WD drive (MioNet and WD Anywhere Backup) but the problems haven't gone away.

Analyzing the memory dump led to this message:

On Thu 5/13/2010 2:28:10 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003B85040, 0xFFFFF80000B9C510)
Error: Unknown
Dump file: C:\windows\Minidump\051310-17097-01.dmp
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

---
Any help on this matter is greatly appreciated.

 

[Jonathan_King]

Welcome!

First, some basic troubleshooting tips. Disconnect the new hard drive and do a system restore to get to a point before the troubles.

Uninstall the Toshiba HDD Protection Program.

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May 13 10:26:56.095 2010 (GMT-4)
System Uptime: 0 days 0:34:58.733
BugCheck 1000009F, {4, 258, fffffa8003b85040, fffff80000b9c510}
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May 13 05:53:57.120 2010 (GMT-4)
System Uptime: 0 days 0:56:05.743
BugCheck 1000009F, {4, 258, fffffa8003b85b60, fffff80000b9c510}
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May 13 04:57:24.180 2010 (GMT-4)
System Uptime: 0 days 4:23:15.413
BugCheck 1000009F, {4, 258, fffffa8003b85040, fffff80000b9c510}
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 12 23:21:56.142 2010 (GMT-4)
System Uptime: 0 days 15:10:54.765
BugCheck 1000009F, {4, 258, fffffa8003b7a040, fffff80000b9c510}
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 12 08:10:05.301 2010 (GMT-4)
System Uptime: 0 days 1:49:51.924
BugCheck 1000009F, {4, 258, fffffa8003b86680, fffff80004b54510}
*** WARNING: Unable to verify timestamp for thpdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for thpdrv.sys
Probably caused by : thpdrv.sys ( thpdrv+26d9 )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 12 05:40:44.286 2010 (GMT-4)
System Uptime: 0 days 2:36:22.909
BugCheck 1000009F, {4, 258, fffffa8003b6b040, fffff80004b52510}
*** WARNING: Unable to verify timestamp for thpdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for thpdrv.sys
Probably caused by : thpdrv.sys ( thpdrv+26d9 )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
 [/FONT]

Update these old drivers:

lmimirr.sys  Tue Apr 10 18:32:45 2007 (461C108D)- LogMeIn
radpms.sys   Tue Apr 10 21:21:23 2007 (461C3813)- LogMeIn
secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 (487B7E50)- LogMeIn

Better yet, uninstall LogMeIn completely, or at the very least, install a fresh copy.

Follow these instructions for enabling Driver Verifier, and upload the new dmps. Please empty your minidump folder now to avoid confusion.

http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[gabusch]

Thank you for the quick reply.

Before I go off and follow your instructions, just a few quick questions:

Uninstall the Toshiba HDD Protection Program.

I assume that this program is next to useless which is why you are recommending its installation?

Better yet, uninstall LogMeIn completely, or at the very least, install a fresh copy.

I've already uninstalled LogMeIn, but the drivers seem hard to get rid of completely? Do they do any damage just by sitting there even though the program has been uninstalled?

Thanks again - I'll go follow the instructions on your post now.

 

[Jonathan_King]

The old drivers from LogMeIn are still being loaded, and may be causing the problem. I suggest deleting lmimirr.sys, radpms.sys, and LMIRfsDriver.sys from the C:\Windows\System32\Drivers folder.

The Toshiba HDD Protection program is listed as the probable cause for two of your dmps:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 12 08:10:05.301 2010 (GMT-4)
System Uptime: 0 days 1:49:51.924
BugCheck 1000009F, {4, 258, fffffa8003b86680, fffff80004b54510}
*** WARNING: Unable to verify timestamp for thpdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for thpdrv.sys
Probably caused by : thpdrv.sys ( thpdrv+26d9 )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 12 05:40:44.286 2010 (GMT-4)
System Uptime: 0 days 2:36:22.909
BugCheck 1000009F, {4, 258, fffffa8003b6b040, fffff80004b52510}
*** WARNING: Unable to verify timestamp for thpdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for thpdrv.sys
Probably caused by : thpdrv.sys ( thpdrv+26d9 )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System

 

[gabusch]

I followed the steps outlined above, except for System Restore as I unfortunately did not have a restore point.

Annoyingly enough, while Driver Verifer is on the BSOD stopped at "Preparing the disk for the dump file" and did not actually write the dump file. The only file I have here is the dump file written by Windows when I shut down the PC as I started Verifier, which means it was not yet on at this point.

By the way, I had my iPod Touch connected to the USB drive before starting Windows and it detected upon startup; after disconnecting it and connecting it again, it wouldn't detect anymore (as with my USB mouse).

I hope you can help me out; I am almost ready to wipe the slate clean with a fresh re-install of Windows, although I'm still hoping for a fix.

 

[Jonathan_King]

Here you go:

[FONT=lucida console]Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 12 08:10:05.301 2010 (GMT-4)
System Uptime: 0 days 1:49:51.924
BugCheck 1000009F, {4, 258, fffffa8003b86680, fffff80004b54510}
*** WARNING: Unable to verify timestamp for thpdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for thpdrv.sys
Probably caused by : thpdrv.sys ( thpdrv+26d9 )
BUGCHECK_STR:  0x9F[/FONT][FONT=lucida console]
PROCESS_NAME:  System[/FONT]

Uninstall that Drive Protection.

 

[gabusch]

Doh! I exited the program from memory and promptly forgot about it. My bad.

After reinstalling, I rebooted and - voila - my USB drives are working! I promptly tried a reboot and and it shut down correctly after a few seconds.

Thanks so much for the help! Any idea why a previously good program would go wrong like that?

 

[Jonathan_King]

Poorly written drivers most likely. If the developers didn't anticipate or accommodate particular situations, bad stuff happens.

I can't really say, though. I'm not a programmer.