[DRIVER_POWER_STATE_FAILURE] Random (rarely occurring) BSOD

[Maxiride]

As instructed I attach the zip created by the suggested tool. Don't mind the "android" name of the pc as I have set it so manually for reasons.

This BSOD happened three times so far (shown in the dump files 052618-23790-01.dmp, 052318-27066-01.dmp and DRIVER_POWER_STATE_FAILURE) the other two dump files might or might not be related.

Thing is all five BSOD happened during different activities which I think are not related together, playing a video game, working on excel etc.

One thing that is shared between all the five crashes is that after the reboot the WiFi card doesn't work, opening the Device Manager to disable and re-enable the card doesn't restore its functionality, also after another immediate reboot the WiFi is not restored. Weirdly enough if I leave the laptop shut down for half an hour or more, when turning it on the WiFi works like if nothing happened.

Since the laptop is getting old I don't mind considering a new one, but if the issue is a silly one I'd like to fix it to use it another couple of years maybe.

 

[Maxiride]

Well, shortly after posting the BSOD happened again
I've attached the new generate zip which has all the previous dump files plus the newly generated one.

 

[cwsink]

The 0x9F dump files show an IRP getting stuck when sent to a driver during a power command (probably a sleep/wake transition.) The driver having problems processing the command is FLxHCIc.sys and if that link is correct it's a USB 3 host controller driver. It would suggest something is going wrong with either the USB host controller or possibly a device connected to it.

Has anything changed recently involving USB 3 connections? (New devices added, problems with older devices, USB devices not working, etc.)

 

[Maxiride]

The 0x9F dump files show an IRP getting stuck when sent to a driver during a power command (probably a sleep/wake transition.) The driver having problems processing the command is FLxHCIc.sys and if that link is correct it's a USB 3 host controller driver. It would suggest something is going wrong with either the USB host controller or possibly a device connected to it.

Has anything changed recently involving USB 3 connections? (New devices added, problems with older devices, USB devices not working, etc.)

Woah that's really a lot of infos you managed to get!!

So, the laptop does have 1 USB 3.0 port that indeed is not working anymore since several months ago, at the beginning connected USB drives were "powered" meaning that leds on the USB would turn on but the device wasn't recognized by the system nor shown in the window explorer. Since three months or so any USB I try to connect to that port isn't getting powered at all.
Connecting a device does not trigger an immediate BSOD. I really don't need that port after all, might be helpful to somehow make the system ignore it?

Went to check in the device manager its properties and found out it is not recognized at all: http://prntscr.com/jn9o7i

 

[cwsink]

Power transitions are something every driver has to respond to when initiated by the operating system. Your system seems to be loading that driver I mentioned and it does seem to think it's part of a device stack involving a PCI bus and the ACPI subsystem - which is basically how the OS communicates with the motherboard. I'm hesitant to suggest disabling or deleting the driver because I'm not certain that's the device in question. Disabling the wrong USB driver could prevent any USB device from working on the system.

Can you check your other USB devices to see if that driver shows up in their driver list?

 

[cwsink]

Actually, it looks like the Fresco host controller is loading in the lower portion of your picture. I'd be tempted to just right click that Unknown device shown in the upper portion of the picture and delete it. Afterwards, reboot the system and see if the Unknown device reappears.

 

[Maxiride]

Actually, it looks like the Fresco host controller is loading in the lower portion of your picture. I'd be tempted to just right click that Unknown device shown in the upper portion of the picture and delete it. Afterwards, reboot the system and see if the Unknown device reappears.

I did it, the Unknown device didn't reappear. Can it be that such a silly issue cause such a dramatic error like the BSOD? :huh: I'll wait a couple of weeks before marking the thread as solved to see how the laptop goes.