BSOD - - - -> "Driver Power State Failure" ?
BSOD - - - -> "Driver Power State Failure" ?
Hello. I have been getting weird driver and PC crashes on startup and if it doesn't crash on startup, everything is fine afterwards. I would appreciate any help. Thank you! Computer Type: Desktop GPU: RX 7900 XT CPU: RYZEN 5 7600X Motherboard: B650 AORUS Elite AX BIOS Version: F8 RAM: 32GB G.Skill Trident Z5 Neo RGB DDR5-6000 PSU: Corsair RM850x 80 PLUS GPU Drivers: 23.11.1 Description of Original Problem: Receiving high voltages, cpu temps, and frequencies while idle according to hwinfo64. IDLE CPU TEMPS: 45-65c IDLE VOLTAGES: 1.475. IDLE FREQUENCIES: 3.4GHz-4.3GHz. AMD Ryzen Master shows regular temp in the 40s as well as regular voltages of 1.00-1.2. I don't know what program to believe. Troubleshooting: I've tried setting Ryzen balanced and Ryzen high performance as well as windows balanced and performance yet hwinfo still shows high temps. When I disable both Core performance boost and Percision boost overdrive, temps drop to the low 40s in hwinfo. I still want my CPU to boost but not when idle. Here is the info from minidump: 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: ffffa10a592430a0, Physical Device Object of the stack Arg3: ffffb287b9447178, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffa10a59d159a0, The blocked IRP Debugging Details: Implicit thread is now ffffa10a`718df040 *** WARNING: Unable to verify timestamp for AtihdWT6.sys *** WARNING: Check Image - Checksum mismatch - Dump: 0x35a22, File: 0x35c3c - C:\ProgramData\Dbg\sym\HDAudBus.sys\D38B55132f000\HDAudBus.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1499 Key : Analysis.Elapsed.mSec Value: 20541 Key : Analysis.IO.Other.Mb Value: 22 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 37 Key : Analysis.Init.CPU.mSec Value: 124 Key : Analysis.Init.Elapsed.mSec Value: 34150 Key : Analysis.Memory.CommitPeak.Mb Value: 106 Key : Bugcheck.Code.LegacyAPI Value: 0x9f Key : Failure.Bucket Value: 0x9F_3_HDAudBus!HdaController::TransferCodecVerbs Key : Failure.Hash Value: {d537d977-4d49-4313-8130-09cc882bd617} Key : WER.OS.Branch Value: ni_release Key : WER.OS.Version Value: 10.0.22621.1 BUGCHECK_CODE: 9f BUGCHECK_P1: 3 BUGCHECK_P2: ffffa10a592430a0 BUGCHECK_P3: ffffb287b9447178 BUGCHECK_P4: ffffa10a59d159a0 FILE_IN_CAB: 112823-13000-01.dmp DRVPOWERSTATE_SUBCODE: 3 FAULTING_THREAD: ffffa10a718df040 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffb287bc8b6270 fffff80112e6d645 : ffffd7007be61180 0000000000000000 ffffa10a50bce080 0000000000000000 : nt!KiSwapContext+0x76 ffffb287bc8b63b0 fffff80112e6f827 : ffffa10a718df1c6 0000000000000000 0000000000000000 0000000000000000 : nt!KiSwapThread+0xab5 ffffb287bc8b6500 fffff80112e71746 : ffffa10a00000000 ffffb28700000001 ffffb28700000000 0000000000000000 : nt!KiCommitThreadWait+0x137 ffffb287bc8b65b0 fffff8018de429bd : ffffa10a58e90000 ffffa10a58e90000 0000000000000001 ffffa10a79996120 : nt!KeWaitForSingleObject+0x256 ffffb287bc8b6950 fffff8018de427c2 : ffffa10a58e90000 ffffa10a58e90000 00000000ffffffff fffff801136ac2b0 : HDAudBus!HdaController::TransferCodecVerbs+0x17d ffffb287bc8b69f0 fffff8018711ae87 : 0000000067447a41 ffffa10a59b98a90 ffffa10a7aa7de70 0000000000000100 : HDAudBus!HdaBusInterface::TransferCodecVerbs+0x202 ffffb287bc8b6aa0 0000000067447a41 : ffffa10a59b98a90 ffffa10a7aa7de70 0000000000000100 0000000000000000 : AtihdWT6+0xae87 ffffb287bc8b6aa8 ffffa10a59b98a90 : ffffa10a7aa7de70 0000000000000100 0000000000000000 ffffa10a59b98a90 : 0x67447a41 ffffb287bc8b6ab0 ffffa10a7aa7de70 : 0000000000000100 0000000000000000 ffffa10a59b98a90 0000000000377a00 : 0xffffa10a59b98a90 ffffb287bc8b6ab8 0000000000000100 : 0000000000000000 ffffa10a59b98a90 0000000000377a00 8000000000000000 : 0xffffa10a7aa7de70 ffffb287bc8b6ac0 0000000000000000 : ffffa10a59b98a90 0000000000377a00 8000000000000000 ffffa10a5878ed50 : 0x100 SYMBOL_NAME: HDAudBus!HdaController::TransferCodecVerbs+17d MODULE_NAME: HDAudBus IMAGE_NAME: HDAudBus.sys IMAGE_VERSION: 10.0.22621.2771 STACK_COMMAND: .process /r /p 0xffffa10a50b84040; .thread 0xffffa10a718df040 ; kb BUCKET_ID_FUNC_OFFSET: 17d FAILURE_BUCKET_ID: 0x9F_3_HDAudBus!HdaController::TransferCodecVerbs OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {d537d977-4d49-4313-8130-09cc882bd617} Followup: MachineOwner
Please upload the dump file to the cloud using that link I gave you. There is much more to do with the dump analysis other than running "analyze-v".
No big deal, I'll get this done when I can. By the way, that bugcheck says a piece of hardware didn't react quickly enough after turning off and on again. The dump file will show exactly which part is broken, but looking at what you pasted from the analyze -v output, it looks like an audio device might be the problem.