Framework Desktop Crashes

Had a new hard crash, this time, DRIVER_POWER_STATE_FAILURE

WhoCrashed

Crash dump file: C:\WINDOWS\FULLMEMORY.DMP (Full memory dump)
Bugcheck code: 0x9F(0x3, 0xFFFF888D22AF0060, 0xFFFFF800ADB99000, 0xFFFF888D2B426C10)
Bugcheck name: DRIVER_POWER_STATE_FAILURE
Driver or module in which error occurred: fffff8011a4fc38c : 0000000000000000 fffff800adb993f0 ffff888d4e80f498 fffff800adb99189 : nt.sys (fffff8011a4fc38c : 0000000000000000 fffff800adb993f0 ffff888d4e80f498 fffff800adb99189 : nt!KeStallWhileFrozen+0xb81d)
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
Analysis: A device object has been blocking an IRP for too long a time. This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues

Google query: fffff8011a4fc38c : 0000000000000000 fffff800adb993f0 ffff888d4e80f498 fffff800`adb99189 : nt DRIVER_POWER_STATE_FAILURE

Was trying to play Tom Clancy’s Rainbow Six Siege where it crashed upon loading into the game. The first time loading, the game froze for a few seconds and gave an AMD Timeout Screen, had reported it, second time, was the hard crash above.

After the restart, Windows Update was probably working on an update, but my AMD drivers looks like they were entirely removed, the GPU not even appearing in the task manager and trying to use the Adrenalin tool just says version mismatch…

Just went ahead and tried to reinstall AMD again through their website tool, then the irony..

Unsure if one of the recent Windows Update has caused this, but a screenshot of my Update history incase it’s related to one of these updates for others to compare.

Here would be a WinDbg !analyze -v of the full memory dump,

WinDbg !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: ffff888d22af0060, Physical Device Object of the stack
Arg3: fffff800adb99000, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff888d2b426c10, The blocked IRP

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

Implicit thread is now ffff888d`186ea040

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1734

    Key  : Analysis.Elapsed.mSec
    Value: 7937

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.2

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x9f

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x9f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x9f

    Key  : Dump.Attributes.AsUlong
    Value: 0x21800

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 100

    Key  : Failure.Bucket
    Value: 0x9F_VRF_3_DXG_POWER_IRP_TIMEOUT_IMAGE_ACPI.sys

    Key  : Failure.Hash
    Value: {4450b202-fb03-b620-ae4a-e3d5e61fa358}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    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: 1

    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: 38670575

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24e10ef

    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: 0x3f7

    Key  : SecureKernel.HalpHvciEnabled
    Value: 1

    Key  : Stack.Pointer
    Value: NMI

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.System.BIOSRevision
    Value: 3.4.0.0


BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffff888d22af0060

BUGCHECK_P3: fffff800adb99000

BUGCHECK_P4: ffff888d2b426c10

FILE_IN_CAB:  FULLMEMORY.DMP

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


DUMP_FILE_ATTRIBUTES: 0x21800

FAULTING_THREAD:  ffff888d186ea040

DRVPOWERSTATE_SUBCODE:  3

ADDITIONAL_DEBUG_TEXT:  DXG Power IRP timeout.

IRP_ADDRESS: ffff888d2b426c10

DEVICE_OBJECT: ffff888d186ca040

DRIVER_OBJECT: ffff888d18ed3da0

IMAGE_NAME:  ACPI.sys

MODULE_NAME: ACPI

FAULTING_MODULE: fffff800ac230000 ACPI

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


PROCESS_NAME:  System

DPC_STACK_BASE:  FFFFF800ADBA1FB0

STACK_TEXT:  
fffff185`1e01efa0 fffff801`1a258204     : ffffdd01`c8ea2180 ffffdd01`c8ea2198 00000000`00000000 ffff888d`18819040 : nt!KiSwapContext+0x76
fffff185`1e01f0e0 fffff801`1a221eed     : 00000000`00000000 00000000`00000000 fffff185`1e01f270 fffff801`1a18c369 : nt!KiSwapThread+0x6d4
fffff185`1e01f170 fffff801`1a2200e9     : 00000000`00000000 00000000`00000000 ffffe776`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x39d
fffff185`1e01f200 fffff800`abd4923b     : fffff185`1e01f318 ffff888d`00000000 00000000`00000000 ffff888d`2b75c000 : nt!KeWaitForSingleObject+0x859
fffff185`1e01f2e0 fffff800`abd48f4c     : fffff185`1e01f300 00000000`00000004 ffffe552`d1b9c1ec 00000000`00000000 : dxgkrnl!DpiFdoHandleDevicePower+0x2cb
fffff185`1e01f370 fffff800`abd28990     : ffff888d`2b426c10 ffff888d`2b426c10 ffff888d`2b75c180 ffff888d`2b75c030 : dxgkrnl!DpiFdoDispatchPower+0x1c
fffff185`1e01f3a0 fffff801`1a41a557     : fffff185`00000001 ffff888d`4e80f420 ffff888d`4e80f400 ffff888d`00000000 : dxgkrnl!DpiDispatchPower+0xe0
fffff185`1e01f4c0 fffff801`1a3b782a     : 00000000`00000000 ffff888d`186ea040 fffff801`1a41a180 00000000`00000000 : nt!PopIrpWorker+0x3d7
fffff185`1e01f570 fffff801`1a5db324     : ffffdd01`c8c64180 ffff888d`186ea040 fffff801`1a3b77d0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff185`1e01f5c0 00000000`00000000     : fffff185`1e020000 fffff185`1e019000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


STACK_COMMAND: .process /r /p 0xffff888d186b4040; .thread /r /p 0xffff888d186ea040 ; kb

FAILURE_BUCKET_ID:  0x9F_VRF_3_DXG_POWER_IRP_TIMEOUT_IMAGE_ACPI.sys
OS_VERSION:  10.0.26100.1
BUILDLAB_STR:  ge_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {4450b202-fb03-b620-ae4a-e3d5e61fa358}
Followup:     MachineOwner
---------

Going to probably be risky, but since this looks to be a ACPI issue, the latest beta bios may help, probably going to give this a try, even though the update info for this bios update doesn’t show anything regarding ACPI, it’s still best to be on the latest to report further bugs.