- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
System: Intel NUC12SNKi72
OS: Windows 11 22621.1485
Arc driver: gfx_win_101.4255
Issue: PC randomly run into blue screen with VIDEO_DXGKRNL_FATAL_ERROR.
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Primary dump contents written successfully Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (20 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22621.1.amd64fre.ni_release.220506-1250 Machine Name: Kernel base = 0xfffff803`41200000 PsLoadedModuleList = 0xfffff803`41e133c0 Debug session time: Sun Apr 2 06:08:04.972 2023 (UTC - 5:00) System Uptime: 1 days 4:21:17.920 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........................................... Loading User Symbols Loading unloaded module list .................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`416292a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd184`c5c177f0=0000000000000113 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 0000000000000001 Arg3: 0000000000008086 Arg4: 0000000000005690 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 703 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 1041 Key : Analysis.IO.Other.Mb Value: 8 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 38 Key : Analysis.Init.CPU.mSec Value: 687 Key : Analysis.Init.Elapsed.mSec Value: 8929 Key : Analysis.Memory.CommitPeak.Mb Value: 118 Key : Bugcheck.Code.DumpHeader Value: 0x113 Key : Bugcheck.Code.KiBugCheckData Value: 0x113 Key : Bugcheck.Code.Register Value: 0x113 Key : DirectX.FatalError.Code Value: 19 Key : DirectX.FatalError.Desc Value: UNEXPECTED_DEFERRED_DESTRUCTION Key : Dump.Attributes.AsUlong Value: 1800 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 100 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Timestamp Value: 2022-05-06T12:50:00Z Key : WER.OS.Version Value: 10.0.22621.1 FILE_IN_CAB: MEMORY.DMP TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x1800 BUGCHECK_CODE: 113 BUGCHECK_P1: 19 BUGCHECK_P2: 1 BUGCHECK_P3: 8086 BUGCHECK_P4: 5690 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: ffffd184`c5c177e8 fffff803`605b5685 : 00000000`00000113 00000000`00000019 00000000`00000001 00000000`00008086 : nt!KeBugCheckEx ffffd184`c5c177f0 fffff803`603b4df1 : ffffa886`35e7c100 ffffa886`352a93f0 ffffa886`352a93f8 ffffa886`352a9400 : watchdog!WdLogSingleEntry5+0x3b45 ffffd184`c5c178a0 fffff803`6030c1b1 : ffffa886`35e7c030 00000000`00000000 ffffe680`b99eb000 ffffa886`00000000 : dxgkrnl!DpiFdoHandleDevicePower+0xa87a1 ffffd184`c5c17940 fffff803`6030dbe1 : ffffa886`3ecb55a0 ffffa886`35e7c180 ffffa886`35e7c030 00000000`00000000 : dxgkrnl!DpiFdoDispatchPower+0x21 ffffd184`c5c17970 fffff803`415d57e1 : ffffa886`00000000 ffffa886`2b0c2280 ffffa886`2b0c2280 fffff803`00000000 : dxgkrnl!DpiDispatchPower+0xe1 ffffd184`c5c17a90 fffff803`414db7d7 : 00000000`00000000 fffff803`415d5580 00000000`00000000 00000000`000001b4 : nt!PopIrpWorker+0x261 ffffd184`c5c17b30 fffff803`4162e204 : ffffe680`b99dc180 ffffa886`2b0c2280 fffff803`414db780 fa58386f`24a74f41 : nt!PspSystemThreadStartup+0x57 ffffd184`c5c17b80 00000000`00000000 : ffffd184`c5c18000 ffffd184`c5c11000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: dxgkrnl!DpiFdoHandleDevicePower+a87a1 MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys IMAGE_VERSION: 10.0.22621.1485 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: a87a1 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 ---------
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Cysh,
Thank you for posting on the Intel
To have a better understanding of the situation, please answer the following questions:
- Does the issue happen when disabling Intel® Arc™ A770M Graphics or Intel® Iris® Xe Graphics eligible?
- Download, run, save and attach the report for the following tools:
- Report for Intel® Graphics Drivers, find the installation steps on How to Install the Intel® Graphics Command Center From the Microsoft Store.
- Intel® System Support Utility for Windows (SSU), you can find the steps on the link How to get the Intel® System Support Utility Logs on Windows.
Regards,
Andres P.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Cysh,
Were you able to check the previous post?
Let us know if you still need assistance.
Best regards,
Andres P.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Cysh,
We have not heard back from you, so we will close this thread. If you need any additional information, please submit a new question as this thread will no longer be monitored.
Best regards,
Andres P.
Intel Customer Support Technician

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page