VIDEO_DXGKRNL_FATAL_ERROR (113) - dxgkrnl!DpiFdoHandleDevicePower+b2e3c

Question

Microsoft Surface Laptop Studio 2 crashes and displays BSOD screen with error message that reads VIDEO_DXGKRNL_FATAL_ERROR.

The minidump files indicate issue with dxgkrnl!DpiFdoHandleDevicePower+b2e3c.

Machine is running Windows 11

VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress.  By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 0000000000000019, The subtype of the BugCheck:
Arg2: 0000000000000002
Arg3: 0000000000008086
Arg4: 0000000000006240

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2889

    Key  : Analysis.Elapsed.mSec
    Value: 6648

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x113

    Key  : Bugcheck.Code.TargetModel
    Value: 0x113

    Key  : DirectX.FatalError.Code
    Value: 19

    Key  : DirectX.FatalError.Desc
    Value: UNEXPECTED_DEFERRED_DESTRUCTION

    Key  : Failure.Bucket
    Value: 0x113_19_dxgkrnl!DpiFdoHandleDevicePower

    Key  : Failure.Hash
    Value: {56f08134-df9b-8892-49c3-80dcb44337ee}

    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

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  113

BUGCHECK_P1: 19

BUGCHECK_P2: 2

BUGCHECK_P3: 8086

BUGCHECK_P4: 6240

FILE_IN_CAB:  071224-20562-01.dmp

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


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff8381`13e177c8 fffff803`84ec5745     : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`00008086 : nt!KeBugCheckEx
ffff8381`13e177d0 fffff803`84cc48ac     : ffffe601`4f88d100 ffffe601`4ebfb530 ffffe601`4ebfb538 ffffe601`4ebfb540 : watchdog!WdLogSingleEntry5+0x3c05
ffff8381`13e17880 fffff803`84c11a56     : ffffe601`4f88d030 fffff803`7d453300 ffff9a81`9d860000 ffffe601`00000000 : dxgkrnl!DpiFdoHandleDevicePower+0xb2e3c
ffff8381`13e17930 fffff803`84c134e1     : ffffe601`4f454380 ffffe601`4f88d180 ffffe601`4f88d030 ffffe601`4e0ba9a0 : dxgkrnl!DpiFdoDispatchPower+0x16
ffff8381`13e17960 fffff803`7d452efa     : ffffe601`472de080 ffffe601`472de080 ffffe601`472de080 fffff803`00000000 : dxgkrnl!DpiDispatchPower+0xe1
ffff8381`13e17a80 fffff803`7d479ca7     : ffffe601`472de080 00000000`00000000 fffff803`7d452ca0 97a056d3`20913a9e : nt!PopIrpWorker+0x25a
ffff8381`13e17b30 fffff803`7d61af64     : ffff9a81`9d851180 ffffe601`472de080 fffff803`7d479c50 49e7595d`b8c63321 : nt!PspSystemThreadStartup+0x57
ffff8381`13e17b80 00000000`00000000     : ffff8381`13e18000 ffff8381`13e11000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgkrnl!DpiFdoHandleDevicePower+b2e3c

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.22621.1390

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  b2e3c

FAILURE_BUCKET_ID:  0x113_19_dxgkrnl!DpiFdoHandleDevicePower

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {56f08134-df9b-8892-49c3-80dcb44337ee}

Followup:     MachineOwner

Answer 1

I too have been having this EXACT same issue with my Microsoft Surface Laptop Studio 2 since buying it brand new 3 months ago. Tried multiple factory resets or Windows reinstallations with no luck. Zero help from multiple attempts contacting "support". Will never buy another surface device.

Answer 2

we have similar problem on four computers. does microsoft support have a solution to the problem? thanks

The minidump files indicate issue with

VIDEO_DXGKRNL_FATAL_ERROR (113) - 0x113_19_nvlddmkm!unknown_function

Machine is running Windows 11.