Question DRIVER_POWER_STATE_FAILURE (9f) ?

Jan 26, 2024
1
0
10
I am currently facing an issue where the GPU in my MSI GE66 10SFS laptop is not being detected.
Earlier, while loading a game, the system encountered a blue screen error during the shader cache loading process. Since that incident, the Nvidia RTX 2070 Super GPU is not being recognized at all, and only the integrated Intel graphics seems to be operational.


Below are the contents from the Event Viewer:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffd684e56e1630, 0xffff9c021c0ef6f8, 0xffffd684e8a6ba90). A dump was saved in: C:\WINDOWS\Minidump\012524-9375-01.dmp. Report Id: f4f9849a-049b-4f7b-b006-f12aeb4f5913.


and the dump file:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.047 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


Loading Dump File [C:\Users\felix\Desktop\012524-9375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`0f000000 PsLoadedModuleList = 0xfffff806`0fc13510
Debug session time: Thu Jan 25 09:31:59.309 2024 (UTC - 8:00)
System Uptime: 0 days 5:58:17.240
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................................
Loading User Symbols

Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`0f416bc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9c02`1c0ef6b0=000000000000009f
8: 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: ffffd684e56e1630, Physical Device Object of the stack
Arg3: ffff9c021c0ef6f8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd684e8a6ba90, The blocked IRP

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

Implicit thread is now ffffd684`e2eec0c0
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2217

Key : Analysis.Elapsed.mSec
Value: 12751

Key : Analysis.IO.Other.Mb
Value: 33

Key : Analysis.IO.Read.Mb
Value: 29

Key : Analysis.IO.Write.Mb
Value: 78

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x9f

Key : Dump.Attributes.AsUlong
Value: 1808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x9F_3_DXG_POWER_IRP_TIMEOUT_IMAGE_pci.sys

Key : Failure.Hash
Value: {52f87b6b-6f6d-7c24-f421-639ee8689be5}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 21631230

Key : Hypervisor.Flags.ValueHex
Value: 14a10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7


BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffd684e56e1630

BUGCHECK_P3: ffff9c021c0ef6f8

BUGCHECK_P4: ffffd684e8a6ba90

FILE_IN_CAB: 012524-9375-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

DRVPOWERSTATE_SUBCODE: 3

FAULTING_THREAD: ffffd684e2eec0c0

ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.

IRP_ADDRESS: ffffd684e8a6ba90

DEVICE_OBJECT: ffffd684e56e1630

DRIVER_OBJECT: ffffd684e55b4d50

IMAGE_NAME: pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff80613050000 pci

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9c02`1c01f050 fffff806`0f26c9d5 : ffffe781`e5156180 00000000`00000000 ffffd684`e2f84040 00000000`00000000 : nt!KiSwapContext+0x76
ffff9c02`1c01f190 fffff806`0f26ebb7 : ffff7d72`b1c66f38 fffff806`0f32b10a ffff7d72`b1c66f28 00000000`00000000 : nt!KiSwapThread+0xab5
ffff9c02`1c01f2e0 fffff806`0f270ad6 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x137
ffff9c02`1c01f390 fffff806`2b7eadf6 : 00000000`00000000 00000000`00000000 ffffd684`e8efca28 ffffd684`e8efca30 : nt!KeWaitForSingleObject+0x256
ffff9c02`1c01f730 fffff806`2b7ea761 : ffffd684`e9327030 00000000`00000000 ffffd684`e8cb3000 ffffd684`ef781000 : dxgkrnl!DpiFdoHandleDevicePower+0x1f6
ffff9c02`1c01f7d0 fffff806`2b7ec191 : ffffd684`e8a6ba90 ffffd684`e9327180 ffffd684`e9327030 ffff5ba1`ae43180a : dxgkrnl!DpiFdoDispatchPower+0x21
ffff9c02`1c01f800 fffff806`4060c4c2 : ffffd684`e8cb3000 ffffd684`e8a6bc80 00000000`00000001 ffffd684`e9327000 : dxgkrnl!DpiDispatchPower+0xe1
ffff9c02`1c01f920 ffffd684`e8cb3000 : ffffd684`e8a6bc80 00000000`00000001 ffffd684`e9327000 ffff9c02`1c01f978 : nvlddmkm+0x148c4c2
ffff9c02`1c01f928 ffffd684`e8a6bc80 : 00000000`00000001 ffffd684`e9327000 ffff9c02`1c01f978 00000000`00000004 : 0xffffd684`e8cb3000
ffff9c02`1c01f930 00000000`00000001 : ffffd684`e9327000 ffff9c02`1c01f978 00000000`00000004 ffffd684`00000001 : 0xffffd684`e8a6bc80
ffff9c02`1c01f938 ffffd684`e9327000 : ffff9c02`1c01f978 00000000`00000004 ffffd684`00000001 fffff806`00000000 : 0x1
ffff9c02`1c01f940 ffff9c02`1c01f978 : 00000000`00000004 ffffd684`00000001 fffff806`00000000 00000000`00000000 : 0xffffd684`e9327000
ffff9c02`1c01f948 00000000`00000004 : ffffd684`00000001 fffff806`00000000 00000000`00000000 ffffd684`e8a1e7d0 : 0xffff9c02`1c01f978
ffff9c02`1c01f950 ffffd684`00000001 : fffff806`00000000 00000000`00000000 ffffd684`e8a1e7d0 ffffd684`e8cb3000 : 0x4
ffff9c02`1c01f958 fffff806`00000000 : 00000000`00000000 ffffd684`e8a1e7d0 ffffd684`e8cb3000 ff030000`00000000 : 0xffffd684`00000001
ffff9c02`1c01f960 00000000`00000000 : ffffd684`e8a1e7d0 ffffd684`e8cb3000 ff030000`00000000 ffffd684`e5726de0 : 0xfffff806`00000000


IMAGE_VERSION: 10.0.22621.3073

STACK_COMMAND: .process /r /p 0xffffd684e2efe040; .thread 0xffffd684e2eec0c0 ; kb

FAILURE_BUCKET_ID: 0x9F_3_DXG_POWER_IRP_TIMEOUT_IMAGE_pci.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {52f87b6b-6f6d-7c24-f421-639ee8689be5}

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

I've tried various troubleshooting steps including an EC reset, running both the sfc /scannow and dism /restorehealth commands, and uninstalling the Nvidia drivers using DDU (in Safe Mode). Despite these efforts, the Nvidia graphics card is still not being detected, rendering me unable to install the Nvidia drivers.

All drivers are up to date, and the Device Manager does not indicate any issues.

Is there any way to resolve this issue?
 
Last edited: