Win 8.1 BSOD - DRIVER_POWER_STATE_FAILURE

[JonB]

Hi all,
I've had several BSODs over the last few months, all related to putting my laptop to sleep (or waking up?) and apparently caused by the USBSTOR.SYS driver, but I don't really know what that is (guessing a USB driver) or how to fix it. Can anyone help? I've attached the zip file per the BSOD posting instructions. Please let me know if you need anything else from me. Thank you in advance!

Best,
Jon B.

 

[MrPepka]

Update (or uninstall):
Lenovo HD disk driver (parto of LHDMgr)

 

[JonB]

Thank you very much for your help. I'm unable to find this driver (LhdX64.sys) on the Lenovo site or anywhere else. Also, several folks have posted in other forums that when they uninstalled this driver, their laptop no longer booted, so I'd rather not do that. Any ideas on how to update this driver? Thanks!

 

[MrPepka]

Look for this driver in the Snappy Driver program - Download

 

[JonB]

Thanks. I've downloaded it (actually Snappy Driver Installer Origin). The driver in question (LhdX64.sys) does not appear to be there - I even looked through the hundred-plus Standard Drivers, though I could have missed it, since there doesn't seem to be a search function and I had to scroll through manually. I get the impression this is a system file and not intended to be updated like other drivers, since I can't find it anywhere - so now I'm wondering if that's actually the driver you mean. Can you confirm?

My drivers are current to the versions posted on the Lenovo product support page (Ideapad Y510P) but the laptop is several years old so they don't seem to be updating that page any more. SDIO listed a number of drivers where there were "more current & more optimal" versions, so I updated all of those. One of them has caused BlueTooth not to function - SDIO now says the Bluetooth driver is not installed at all and, when I install it, it says it succeeded - and then refreshes and says the Bluetooth driver is not installed. So apparently they weren't all more optimal. Will roll back to a previous restore point and try to identify which one caused the problem, as soon as I get a chance.