BthPS3.sys DRIVER_POWER_STATE_FAILURE restoring from hibernate - Windows 10/11

[dxgldotorg]

BthPS3 version v2.0.144
Windows 11 version 22000.100
Had a DRIVER_POWER_STATE_FAILURE after restoring from Hibernate

WinDBG log as follows:

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


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


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\Symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 22000 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff806`7da00000 PsLoadedModuleList = 0xfffff806`7e629600
Debug session time: Sat Jul 24 21:13:06.253 2021 (UTC - 4:00)
System Uptime: 0 days 2:58:38.079
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`7de129b0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffb70f`58a8f6a0=000000000000009f
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffb88a95fe5a70, Physical Device Object of the stack
Arg3: ffffb70f58a8f6d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffb88abb075010, The blocked IRP

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for BthPS3.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3999

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 14693

    Key  : Analysis.Init.CPU.mSec
    Value: 983

    Key  : Analysis.Init.Elapsed.mSec
    Value: 603378

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 90

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffb88a95fe5a70

BUGCHECK_P3: ffffb70f58a8f6d0

BUGCHECK_P4: ffffb88abb075010

DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: ffffb88a80632e10

IMAGE_NAME:  BthPS3.sys

MODULE_NAME: BthPS3

FAULTING_MODULE: fffff8069a6f0000 BthPS3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffb70f`58a8f698 fffff806`7dfc2ca7     : 00000000`0000009f 00000000`00000003 ffffb88a`95fe5a70 ffffb70f`58a8f6d0 : nt!KeBugCheckEx
ffffb70f`58a8f6a0 fffff806`7dfc2bc1     : ffffb88a`89eac208 00000000`00000080 ffffb70f`58a8f9f8 ffffb70f`58a8f9f0 : nt!PopIrpWatchdogBugcheck+0xdf
ffffb70f`58a8f710 fffff806`7dc12824     : 00000000`00000000 ffffb88a`00000001 ffffb70f`00000000 ffffb88a`00000002 : nt!PopIrpWatchdog+0x31
ffffb70f`58a8f760 fffff806`7dc10e14     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`7aa52648 : nt!KiProcessExpiredTimerList+0x204
ffffb70f`58a8f890 fffff806`7de168fe     : 00000000`00000000 ffff8101`9fdd6180 ffff8101`9fde2240 ffffb88a`86bbd080 : nt!KiRetireDpcList+0x714
ffffb70f`58a8fb40 00000000`00000000     : ffffb70f`58a90000 ffffb70f`58a89000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x9F_3_IMAGE_BthPS3.sys

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {328a30da-bacc-a428-20ed-22a427c03a3c}

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

[nefarius]

Aw sh... It's back 😭

[IsaacGHoward]

Just had this too

[Ehren1337]

Just had this too

yup same lol hopefully they can fix it. i think it happens when you leave controller plugged in then turn on pc to desktop then wait maybe around 5-20 mins then it happened. not really sure if it happens consistent, ill test it later.

[nefarius]

Just had this too

yup same lol hopefully they can fix it. i think it happens when you leave controller plugged in then turn on pc to desktop then wait maybe around 5-20 mins then it happened. not really sure if it happens consistent, ill test it later.

Yes, it's a known issue. As a workaround make sure to disconnect your controllers before you send the machine to sleep.

The behaviour is pretty consistent to reproduce, connect controller, send PC to sleep, wake it up, almost exactly 10 minutes later (Windows Kernel Watchdog Timer) the BSOD happens.

I haven't had the time to look into it yet so simply watch this issue's progress and I don't need anymore "happens to me too" comments for the time being, thank you 😛

[Ehren1337]

Yes, it's a known issue. As a workaround make sure to disconnect your controllers before you send the machine to sleep.

The behaviour is pretty consistent to reproduce, connect controller, send PC to sleep, wake it up, almost exactly 10 minutes later (Windows Kernel Watchdog Timer) the BSOD happens.

I haven't had the time to look into it yet so simply watch this issue's progress and I don't need anymore "happens to me too" comments for the time being, thank you 😛

Still happens while controller is disconnected hope this helps you to find those lines. Sorry if im bothering you.

[nefarius]

Yes, it's a known issue. As a workaround make sure to disconnect your controllers before you send the machine to sleep.
The behaviour is pretty consistent to reproduce, connect controller, send PC to sleep, wake it up, almost exactly 10 minutes later (Windows Kernel Watchdog Timer) the BSOD happens.
I haven't had the time to look into it yet so simply watch this issue's progress and I don't need anymore "happens to me too" comments for the time being, thank you 😛

Still happens while controller is disconnected hope this helps you to find those lines. Sorry if im bothering you.

No worries, mate, I just need a time slot to dig into this and will update my progress on GitHub, if there is any 😜

[dxgldotorg]

Yes, it's a known issue. As a workaround make sure to disconnect your controllers before you send the machine to sleep.
The behaviour is pretty consistent to reproduce, connect controller, send PC to sleep, wake it up, almost exactly 10 minutes later (Windows Kernel Watchdog Timer) the BSOD happens.
I haven't had the time to look into it yet so simply watch this issue's progress and I don't need anymore "happens to me too" comments for the time being, thank you 😛

Still happens while controller is disconnected hope this helps you to find those lines. Sorry if im bothering you.

Maybe I'm just getting lazy; I had two of these crashes this week.

[nefarius]

Yes, it's a known issue. As a workaround make sure to disconnect your controllers before you send the machine to sleep.
The behaviour is pretty consistent to reproduce, connect controller, send PC to sleep, wake it up, almost exactly 10 minutes later (Windows Kernel Watchdog Timer) the BSOD happens.
I haven't had the time to look into it yet so simply watch this issue's progress and I don't need anymore "happens to me too" comments for the time being, thank you 😛

Still happens while controller is disconnected hope this helps you to find those lines. Sorry if im bothering you.

Maybe I'm just getting lazy; I had two of these crashes this week.

That sucks but the status is still unchanged so that shouldn't come as a surprise 😛

[dxgldotorg]

On my last GSOD (they are green on Insider Preview instead of blue or black) I noticed a DS3 HID device with an error in Device Manager before the system crashed. So yes it appears to be due to having the controller connected to Bluetooth when the system goes to sleep.

[nefarius]

I. Know. 🙂

[Fukeung]

I'm now also getting this on Windows 10 21H1 with latest patches as of writing.

[dust0vich]

Yes, I will confirm on 21H1/2 as well. Usually happens about :30-1 minute after resuming from sleep. Subscribed.

It tricks you as you get going with what you were doing upon resume as there is no issue then you get the bluescreen haha.

[youarentdoneyet]

I'll double this
Edition: Windows 10 Education
Os Build: 19043.1348
Windows Feature Experience Pack 120.2212.3920.0

Same bsod

https://pastebin.com/raw/XjMsYHgb

[nefarius]

I am aware 🙂 It's an issue independent from OS (version) and I'll look into it when there's time, I kindly don't need more notifications about this thread 😉

[nefarius]

Found the issue. Will need a bit of rework to address it fully but we're getting there 😌

[nefarius]

Work to tackle this has started on the branch nefarius/issue/DRIVER_POWER_STATE_FAILURE-fix

The plan is to remove chunks of legacy verbose sections with DMF, especially the child device creation and lifetime handling. The underlying issue is, that currently upon power down for sleep/hibernation the controller gets disconnected, but it also destroys the WDFDEVICE of the PDO, which then is not available after wake-up and the request sent to it is orphaned and triggers the crash when the kernel watchdog runs and finds it.

The plan is to rewrite the child handling code with modern substitutes and change the behaviour on power down to keep the device and resume it when the user wakes up the machine and connects the controller again.

This sounds simple on paper but will require a fair bit of work and testing, but it's the way to go, so stay tuned 😉

[Jessseee]

How is this fix coming along? Just ran in to this problem on win11 as well.

[nefarius]

How is this fix coming along? Just ran in to this problem on win11 as well.

I was buried in company work last couple weeks so not much progress, as can be seen by the commits messages.

[Jessseee]

Ah, understandable sorry to bother you. Hadn't read the thread. I wish I could help, but unfortunately I am not very familiar with developing for windows.

[nefarius]

Oof, looking at the code again with a few months break is an experience... Like "who wrote this... oh, right, it was me..."

[MrRocketFX]

Sorry for making a Duplicate was tired while looking into this but I just realised this morning that it was caused by Fastboot (still technically hibernate issue) as I turned my pc off with the controller also off then booting it back up later in the day

[nefarius]

Aye, it's on the Roadmap. For 2022. I hope. 😬 So much to do lately it's crazy.

[wooxie2407]

still waiting for the fix, my laptop bsod a couple of times:) i thought my windows/other devices on my laptop making the bsod happen.

[kinglouie]

Can you guys that add nothing to the issue stop spamming/whining? Its annoying when you‘re subscribed here.

[nefarius]

It's the social media generation. Gotta post something even if it adds nothing whatsoever.

[nefarius]

Seriously, people, what do you expect posting the same thing over and over again? That I magically get more time to work on the fix? If anything, now it will take longer 😒

[drujd]

I am ocassionally getting a STATUS_DEVICE_POWER_FAILURE error in device manager for the Nefarius Bluetooth PS Enumerator device. No *SOD, though, just the device and thus the PS3 controller (over BT, USB is fine) doesn't work until restart. I didn't hibernate/sleep, just turned bluetooth on/off a few times. DsHidMini claims everything is fine, even though it's not. Restart fixes this. Windows 11, Intel BT v22.130.0.2

Not a big deal to me, just here to comment that I am not using sleep/hibernate at all.

[nefarius]

And locked until further notice.

[nefarius]

Found and reported a bug in DMF that currently keeps this on hold, hopefully MS' guys soon have an update, then a huge chunk of legacy code is ready to be replaced with Dmf_Pdo 🎉

[nefarius]

Nice! Continuing...

[nefarius]

Alright, the DMF bug was squashed, replacement code works a treat, now fixing and testing the power-related issues.

[nefarius]

The issue is resolved 🥳 a few more things are left to do, then a new release will be published.

[nefarius]

Here we go, have fun testing!