Since last week my old work desktop is having the same BSOD: starts very slowly, enters windows 10, and crashes with a power state failure, restarts again slowly, enters windows 10, and then everything seems to be ok... with the exception that one sata port is not recognized. I thought at first it was my old secondary hdd ending days, but i replaced it with a new ssd and the same thing happens.
nt!KeBugCheckEx:
fffff807
0: kd> !analyze -v
***
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: ffffbb8188eb8060, Physical Device Object of the stack
Arg3: fffff8077d86d990, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffbb818edb1c70, The blocked IRP
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 8155
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 18156
Key : Analysis.Init.CPU.mSec
Value: 812
Key : Analysis.Init.Elapsed.mSec
Value: 4876
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffbb8188eb8060
BUGCHECK_P3: fffff8077d86d990
BUGCHECK_P4: ffffbb818edb1c70
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffffbb8188e66830
IMAGE_NAME: atapi.sys
MODULE_NAME: atapi
FAULTING_MODULE: fffff8077c9d0000 atapi
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff807
fffff807
fffff807
fffff807
fffff807
fffff807
IMAGE_VERSION: 10.0.19041.1083
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {2e0d03b3-946c-de11-316d-86bb51b53b4f}
Followup: MachineOwner
---------
I tried to understand everywhere the main issue, but didn't find a proper answer. I already did a cleanup (didn't delete old windows updates though), did a drive verifier (nothing), restored it (nothing), updated it this morning with the kb5004945, changed all drives sata power connections (nothing), and i thought it could be like a damaged sata cable but probably is not. Any help?
nt!KeBugCheckEx:
fffff807
78ff6c20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff807
7d86d960=000000000000009f0: 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: ffffbb8188eb8060, Physical Device Object of the stack
Arg3: fffff8077d86d990, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffbb818edb1c70, The blocked IRP
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 8155
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 18156
Key : Analysis.Init.CPU.mSec
Value: 812
Key : Analysis.Init.Elapsed.mSec
Value: 4876
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffbb8188eb8060
BUGCHECK_P3: fffff8077d86d990
BUGCHECK_P4: ffffbb818edb1c70
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffffbb8188e66830
IMAGE_NAME: atapi.sys
MODULE_NAME: atapi
FAULTING_MODULE: fffff8077c9d0000 atapi
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff807
7d86d958 fffff807
79160017 : 000000000000009f 00000000
00000003 ffffbb8188eb8060 fffff807
7d86d990 : nt!KeBugCheckExfffff807
7d86d960 fffff807
7915ff31 : ffffbb8192221520 fffff807
7d86dab8 0000000000000000 ffffbb81
88ea8520 : nt!PopIrpWatchdogBugcheck+0xdffffff807
7d86d9d0 fffff807
78f0a5d2 : ffffbb8192221558 fffff807
74642180 fffff8077d86dc58 00000000
00000002 : nt!PopIrpWatchdog+0x31fffff807
7d86da20 fffff807
78f2279d : 0000000000000000 00000000
00000000 0000000000140001 00000000
002a2969 : nt!KiProcessExpiredTimerList+0x172fffff807
7d86db10 fffff807
78ffa78e : 0000000000000000 fffff807
74642180 fffff80779927a00 ffffbb81
93786080 : nt!KiRetireDpcList+0x5ddfffff807
7d86dda0 00000000
00000000 : fffff8077d86e000 fffff807
7d868000 0000000000000000 00000000
00000000 : nt!KiIdleLoop+0x9eIMAGE_VERSION: 10.0.19041.1083
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {2e0d03b3-946c-de11-316d-86bb51b53b4f}
Followup: MachineOwner
---------
I tried to understand everywhere the main issue, but didn't find a proper answer. I already did a cleanup (didn't delete old windows updates though), did a drive verifier (nothing), restored it (nothing), updated it this morning with the kb5004945, changed all drives sata power connections (nothing), and i thought it could be like a damaged sata cable but probably is not. Any help?