Nope it still crashes after like 3 minutes that was a fluke
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000113 (0x0000000000000019, 0x0000000000000001, 0x00000000000010de, 0x0000000000002216).
Computer keeps crashing i just fixed the hyper x issue on event 10110 and 10111 now this is my last problem after playing a game for one minute exactly it crashes and gives me the errors in the title
Windows for home | Windows 11 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
42 answers
Sort by: Oldest
-
Anonymous
2025-03-26T02:36:00+00:00 -
Anonymous
2025-03-26T03:04:53+00:00 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: 00000000000010de Arg4: 0000000000002216
Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** WARNING: Check Image - Checksum mismatch - Dump: 0xc2ed94, File: 0xc31fe0 - C:\ProgramData\Dbg\sym\ntkrnlmp.exe\783A7A83144f000\ntkrnlmp.exe KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1281 Key : Analysis.Elapsed.mSec Value: 3925 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 2 Key : Analysis.Init.CPU.mSec Value: 312 Key : Analysis.Init.Elapsed.mSec Value: 3570 Key : Analysis.Memory.CommitPeak.Mb Value: 88 Key : Analysis.Version.DbgEng Value: 10.0.27793.1000 Key : Analysis.Version.Description Value: 10.2410.02.02 amd64fre Key : Analysis.Version.Ext Value: 1.2410.2.2 Key : Bugcheck.Code.LegacyAPI Value: 0x113 Key : Bugcheck.Code.TargetModel Value: 0x113 Key : DirectX.FatalError.Code Value: 0x19 Key : DirectX.FatalError.Desc Value: UNEXPECTED_DEFERRED_DESTRUCTION Key : Dump.Attributes.AsUlong Value: 0x21008 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0x0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: 0x113_19_dxgkrnl!unknown_function Key : Failure.Hash Value: {af8e85f4-5e29-1c44-d9f6-cdaa6f2ad79a} BUGCHECK_CODE: 113 BUGCHECK_P1: 19 BUGCHECK_P2: 1 BUGCHECK_P3: 10de BUGCHECK_P4: 2216 FILE_IN_CAB: 032525-7140-01.dmp DUMP_FILE_ATTRIBUTES: 0x21008 Kernel Generated Triage Dump FAULTING_THREAD: ffffdc8f97c64040 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffee8b`995d71f8 fffff800`44271316 : 00000000`00000113 00000000`00000019 00000000`00000001 00000000`000010de : nt!KeBugCheckEx ffffee8b`995d7200 fffff800`444d3c37 : ffffdc8f`93e0d117 ffffdc8f`93e0d117 ffffdc8f`93e0d180 00000000`00000000 : watchdog!WdLogSingleEntry5+0x156 ffffee8b`995d7290 ffffdc8f`93e0d117 : ffffdc8f`93e0d117 ffffdc8f`93e0d180 00000000`00000000 00000000`000010de : dxgkrnl+0x233c37 ffffee8b`995d7298 ffffdc8f`93e0d117 : ffffdc8f`93e0d180 00000000`00000000 00000000`000010de 00000000`00002216 : 0xffffdc8f`93e0d117 ffffee8b`995d72a0 ffffdc8f`93e0d180 : 00000000`00000000 00000000`000010de 00000000`00002216 ffffdc8f`93e0d1c0 : 0xffffdc8f`93e0d117 ffffee8b`995d72a8 00000000`00000000 : 00000000`000010de 00000000`00002216 ffffdc8f`93e0d1c0 ffffdc8f`9c0db001 : 0xffffdc8f`93e0d180 SYMBOL_NAME: dxgkrnl+233c37 MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys STACK_COMMAND: .process /r /p 0xffffdc8f846b2040; .thread 0xffffdc8f97c64040 ; kb BUCKET_ID_FUNC_OFFSET: 233c37 FAILURE_BUCKET_ID: 0x113_19_dxgkrnl!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {af8e85f4-5e29-1c44-d9f6-cdaa6f2ad79a} Followup: MachineOwner --------- -
David-M 127.1K Reputation points Independent Advisor2025-03-26T11:56:19+00:00 Sorry for the delay in reply. I've been offline.
The last minidumps you shared only mention graphics-related drivers as the cause of the crashes.
I want to confirm the procedure you did.
Did you first perform a clean installation of Windows 10 and then proceed to upgrade to Windows 11?
I await your reply. Click on the "Reply" button below my reply.
-
Anonymous
2025-03-26T14:10:37+00:00 Yes I did
-
David-M 127.1K Reputation points Independent Advisor2025-03-26T14:20:28+00:00 Thanks for the clarification.
In this case, it is clear that there is a hardware problem with your PC. However, it is not clear whether the problem is actually with the GPU, as it could also be a problem with the motherboard, CPU, or power supply.
You have already checked for problems with the RAM and disk. Unfortunately, there is no reliable software to test the other parts.
I suggest you consult a technician you trust or the manufacturer's authorized support.
Sorry for the bad news.
If you have any questions, don't hesitate to ask. Click on the "Reply" button below my reply.