The computer has rebooted from a bugcheck. The bugcheck was: 0x00000113 (0x0000000000000019, 0x0000000000000001, 0x00000000000010de, 0x0000000000002216).

Anonymous
2025-03-19T17:12:44+00:00

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.

0 comments No comments

42 answers

Sort by: Most helpful
  1. Anonymous
    2025-03-25T20:04:50+00:00

    I’m fine with deleting every thing yeah but do I need to spend more money cause I’m not tryna get another windows key

    Was this answer helpful?

    0 comments No comments
  2. David-M 127.1K Reputation points Independent Advisor
    2025-03-25T19:54:47+00:00

    Thanks for the clarification.

    Are there any objections to performing a clean install of Windows?

    Clean Installing Windows will remove all data stored on the system. Therefore, you will need to back up your personal files on an external drive or cloud storage service.

    I'm considering suggesting you do this because instability problems don't survive a clean install unless the problem is caused by hardware.

    I await your reply. Click on the "Reply" button below my reply.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-03-25T19:29:20+00:00

    passed 4/4 memtest86 and my disk health is 99%

    Was this answer helpful?

    0 comments No comments
  4. David-M 127.1K Reputation points Independent Advisor
    2025-03-25T11:46:00+00:00

    Sorry for the delay in reply. I've been offline.

    This minidump also mentions the Nvidia driver as the cause of the crash. No other drivers are mentioned.

    In this case, I have 2 suspicions about the cause of this problem.

    1. A severe corruption of Windows.
    2. A hardware problem.

    It is possible to test some parts of the hardware using software, but unfortunately, not all of them.

    I suggest you use the free MemTest86 tool for a deep check of your RAM.

    https://www.memtest86.com/download.htm

    The deep scan can take a long time, depending on how much RAM you have. So do it at a time that suits you.

    Feel free to share a photo of the test result.

    Also, check the "health" of your HD/SSD using Crystal Disk Info.

    https://crystalmark.info/en/download/#CrystalDi...

    (On this same page, there is the download of another app. The "Crystal Disk Mark". Do not download Crystal Disk Mark. Download only the "Crystal Disk Info".)

    Download the "Standard Edition" by clicking on the "ZIP (XP-)" button.

    Extract the ZIP and run the file "DiskInfo64.exe".

    The health result of your HD/SSD will be displayed. See if there are any alerts.

    Feel free to share a screenshot if you want. Use the shortcut "Windows + Shift + S" to use the screenshot tool.

    Let me know the result. Click on the "Reply" button below my reply.

    Feel free to ask back any questions.

    ________________________________________________________

    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-03-24T21:32:47+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:
    ------------------
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 1250
    
        Key  : Analysis.Elapsed.mSec
        Value: 2172
    
        Key  : Analysis.IO.Other.Mb
        Value: 5
    
        Key  : Analysis.IO.Read.Mb
        Value: 1
    
        Key  : Analysis.IO.Write.Mb
        Value: 31
    
        Key  : Analysis.Init.CPU.mSec
        Value: 468
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 10946
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 97
    
        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_nvlddmkm!unknown_function
    
        Key  : Failure.Exception.IP.Address
        Value: 0xfffff8046429dc61
    
        Key  : Failure.Exception.IP.Module
        Value: nvlddmkm
    
        Key  : Failure.Exception.IP.Offset
        Value: 0x184dc61
    
        Key  : Failure.Hash
        Value: {fb504da1-90a7-64ec-e7aa-d0c04338976f}
    
    BUGCHECK_CODE:  113
    
    BUGCHECK_P1: 19
    
    BUGCHECK_P2: 1
    
    BUGCHECK_P3: 10de
    
    BUGCHECK_P4: 2216
    
    FILE_IN_CAB:  032425-9671-01.dmp
    
    DUMP_FILE_ATTRIBUTES: 0x21008
      Kernel Generated Triage Dump
    
    FAULTING_THREAD:  ffffe709e5c72040
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  System
    
    STACK_TEXT:  
    fffffd85`acaa7208 fffff804`52eb1316     : 00000000`00000113 00000000`00000019 00000000`00000001 00000000`000010de : nt!KeBugCheckEx
    fffffd85`acaa7210 fffff804`53113c37     : ffffe709`dcd90117 ffffe709`dcd90117 ffffe709`dcd90180 00000000`00000000 : watchdog!WdLogSingleEntry5+0x156
    fffffd85`acaa72a0 fffff804`531110d4     : ffffe709`e78ab000 ffffe709`dcf50000 ffffe709`dcd90117 fffff804`52f1fdd7 : dxgkrnl!DpiFdoHandleSurpriseRemoval+0x157
    fffffd85`acaa7300 fffff804`532a05c9     : ffffe709`dcd90030 ffffe709`eec41de0 ffffe709`dcd90030 ffffe709`e78ab000 : dxgkrnl!DpiFdoDispatchPnp+0xd4
    fffffd85`acaa73a0 fffff804`6429dc61     : 00000000`00000000 fffffd85`069c0000 ffffe709`dcf50000 00000000`00000000 : dxgkrnl!DpiDispatchPnp+0xe9
    fffffd85`acaa74c0 00000000`00000000     : fffffd85`069c0000 ffffe709`dcf50000 00000000`00000000 fffff804`6429df69 : nvlddmkm+0x184dc61
    
    SYMBOL_NAME:  nvlddmkm+184dc61
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    STACK_COMMAND:  .process /r /p 0xffffe709d36dd040; .thread 0xffffe709e5c72040 ; kb
    
    BUCKET_ID_FUNC_OFFSET:  184dc61
    
    FAILURE_BUCKET_ID:  0x113_19_nvlddmkm!unknown_function
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {fb504da1-90a7-64ec-e7aa-d0c04338976f}
    

    Was this answer helpful?

    0 comments No comments