Game crash with "The description for Event ID 0 from source nvlddmkm cannot be found"

Anonymous
2022-07-18T19:19:37+00:00

Hello!

A few games are crashed after a few minutes of gaming. The mouse got stuck for a few seconds after I'm able to alt+tab but the game process is not responding.

I found the following errors and warnings in the Windows event logs:

**-the first one:**Warning 7/18/2022 8:46:11 PM WHEA-Logger 17 None
A corrected hardware error has occurred.

Component: PCI Express Root Port

Error Source: Advanced Error Reporting (PCI Express)

Primary Bus:Device:Function: 0x0:0x6:0x0

Secondary Bus:Device:Function: 0x0:0x0:0x0

Primary Device Name:PCI\VEN_8086&DEV_464D&SUBSYS_00000000&REV_02

Secondary Device Name:

  • <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
  • <System> <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" /><EventID>17</EventID><Version>1</Version><Level>3</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime="2022-07-18T18:46:11.0571189Z" /><EventRecordID>46864</EventRecordID><Correlation ActivityID="{dc219ba3-296d-4681-b18b-d8d04ce3064c}" /><Execution ProcessID="3928" ThreadID="17568" /><Channel>System</Channel><Computer>DESKTOP-067IHFL</Computer><Security UserID="S-1-5-19" /></System>
  • <EventData> <Data Name="ErrorSource">4</Data><Data Name="FRUId">{00000000-0000-0000-0000-000000000000}</Data><Data Name="FRUText" /><Data Name="ValidBits">0xdf</Data><Data Name="PortType">4</Data><Data Name="Version">0x101</Data><Data Name="Command">0x10</Data><Data Name="Status">0x406</Data><Data Name="Bus">0x0</Data><Data Name="Device">0x6</Data><Data Name="Function">0x0</Data><Data Name="Segment">0x0</Data><Data Name="SecondaryBus">0x0</Data><Data Name="SecondaryDevice">0x0</Data><Data Name="SecondaryFunction">0x0</Data><Data Name="VendorID">0x8086</Data><Data Name="DeviceID">0x464d</Data><Data Name="ClassCode">0x30400</Data><Data Name="DeviceSerialNumber">0x0</Data><Data Name="BridgeControl">0x0</Data><Data Name="BridgeStatus">0x0</Data><Data Name="UncorrectableErrorStatus">0x0</Data><Data Name="CorrectableErrorStatus">0x1000</Data><Data Name="HeaderLog">00000000000000000000000000000000</Data><Data Name="PrimaryDeviceName">PCI\VEN_8086&DEV_464D&SUBSYS_00000000&REV_02</Data><Data Name="SecondaryDeviceName" /></EventData> </Event>

-the second one:
Error 7/18/2022 8:47:22 PM nvlddmkm 0 None
The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

\Device\Video3

Error occurred on GPUID: 100

The message resource is present but the message was not found in the message table

  • <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
  • <System> <Provider Name="nvlddmkm" /><EventID Qualifiers="0">0</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2022-07-18T18:47:22.1833449Z" /><EventRecordID>46865</EventRecordID><Correlation /><Execution ProcessID="4" ThreadID="13464" /><Channel>System</Channel><Computer>DESKTOP-067IHFL</Computer><Security /></System>
  • <EventData> <Data>\Device\Video3</Data><Data>Error occurred on GPUID: 100</Data><Binary>00000000020030000000000000000000000000000000000000000000000000000000000000000000</Binary></EventData> </Event>

-the third one:
Warning 7/18/2022 8:47:27 PM Display 4101 None
Display driver nvlddmkm stopped responding and has successfully recovered.

  • <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
  • <System> <Provider Name="Display" /><EventID Qualifiers="0">4101</EventID><Version>0</Version><Level>3</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2022-07-18T18:47:27.3366478Z" /><EventRecordID>46866</EventRecordID><Correlation /><Execution ProcessID="0" ThreadID="0" /><Channel>System</Channel><Computer>DESKTOP-067IHFL</Computer><Security /></System>
  • <EventData> <Data>nvlddmkm</Data><Data /></EventData> </Event>

Also, I see the first one all the time.

Could you please help me?

Windows for home | Windows 10 | Gaming

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

90 answers

Sort by: Most helpful
  1. Anonymous
    2023-06-22T16:59:46+00:00

    I have the same error. And I checked my ram completely and it certainly healthy. The amazing thing that i understood is that When I plug in my 3 power cables of 3 hdd hards to PSU and turn on the computer it crashes after a few seconds of working. and it usually occurs after make computer out from sleep. Memory dump file analyze result:************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false AllowNugetExeUpdate : false AllowNugetMSCredentialProviderInstall : false AllowParallelInitializationOfLocalRepositories : true

    -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true

    >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

    ************* Waiting for Debugger Extensions Gallery to Initialize **************

    >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

    Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [L:\flash\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

    Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff80758a00000 PsLoadedModuleList = 0xfffff8075962a2d0 Debug session time: Thu Jun 22 09:26:05.609 2023 (UTC - 7:00) System Uptime: 0 days 0:11:16.263 Loading Kernel Symbols ............................................................... ...Page 300c0b not present in the dump file. Type ".hh dbgerr004" for details ............................................................. .................................................... Loading User Symbols

    Loading unloaded module list ......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff80758dfc030 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8b08c4e5aa20=0000000000000116 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

    VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: ffffbe8df2a5b010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff807771cad40, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000004, Optional internal context dependent data.

    Debugging Details:

    Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_777742171a918a50\nvlddmkm.sys, Win32 error 0n2 Page 25dd67 not present in the dump file. Type ".hh dbgerr004" for details *** WARNING: Check Image - Checksum mismatch - Dump: 0x3aff59, File: 0x3ab4c9 - C:\ProgramData\Dbg\sym\dxgkrnl.sys\0F2DDF593aa000\dxgkrnl.sys

    KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3000
    
    Key  : Analysis.Elapsed.mSec
    Value: 7965
    
    Key  : Analysis.IO.Other.Mb
    Value: 5
    
    Key  : Analysis.IO.Read.Mb
    Value: 0
    
    Key  : Analysis.IO.Write.Mb
    Value: 6
    
    Key  : Analysis.Init.CPU.mSec
    Value: 577
    
    Key  : Analysis.Init.Elapsed.mSec
    Value: 280054
    
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 104
    
    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x116
    
    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x116
    
    Key  : Failure.Bucket
    Value: 0x116\_IMAGE\_nvlddmkm.sys
    
    Key  : Failure.Hash
    Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
    
    Key  : Hypervisor.Enlightenments.Value
    Value: 0
    
    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0
    
    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0
    
    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0
    
    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0
    
    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0
    
    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0
    
    Key  : Hypervisor.Flags.CpuManager
    Value: 0
    
    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0
    
    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0
    
    Key  : Hypervisor.Flags.Epf
    Value: 0
    
    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0
    
    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 0
    
    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0
    
    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0
    
    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0
    
    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0
    
    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 0
    
    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0
    
    Key  : Hypervisor.Flags.RootScheduler
    Value: 0
    
    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0
    
    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0
    
    Key  : Hypervisor.Flags.Value
    Value: 0
    
    Key  : Hypervisor.Flags.ValueHex
    Value: 0
    
    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0
    
    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0
    
    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0
    
    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0
    
    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0
    
    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0
    
    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0
    
    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0
    
    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0
    
    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0
    
    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0
    
    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0
    
    Key  : Hypervisor.RootFlags.Nested
    Value: 0
    
    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0
    
    Key  : Hypervisor.RootFlags.Value
    Value: 0
    
    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0
    
    Key  : SecureKernel.HalpHvciEnabled
    Value: 0
    
    Key  : WER.OS.Branch
    Value: vb\_release
    
    Key  : WER.OS.Version
    Value: 10.0.19041.1
    

    BUGCHECK_CODE: 116

    BUGCHECK_P1: ffffbe8df2a5b010

    BUGCHECK_P2: fffff807771cad40

    BUGCHECK_P3: ffffffffc000009a

    BUGCHECK_P4: 4

    FILE_IN_CAB: MEMORY.DMP

    VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffbe8df2a5b010 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

    PROCESS_OBJECT: 0000000000000004

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)

    BLACKBOXWINLOGON: 1

    PROCESS_NAME: System

    STACK_TEXT:
    ffff8b08c4e5aa18 fffff80763cb65be : 0000000000000116 ffffbe8df2a5b010 fffff807771cad40 ffffffffc000009a : nt!KeBugCheckEx ffff8b08c4e5aa20 fffff80763c66b64 : fffff807771cad40 ffffbe8defa3c010 0000000000002000 ffffbe8defa3c0d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe ffff8b08c4e5aa60 fffff80763c5f69c : ffffbe8defa34000 0000000001000000 0000000000000004 0000000000000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174 ffff8b08c4e5aa90 fffff80763cb5ce5 : 0000000000000100 ffffbe8defa34a70 00000000f167b040 0000000000000000 : dxgkrnl!DXGADAPTER::Reset+0x4dc ffff8b08c4e5ab10 fffff80763cb5e57 : fffff80759725440 0000000000000000 0000000000000000 0000000000000300 : dxgkrnl!TdrResetFromTimeout+0x15 ffff8b08c4e5ab40 fffff80758c8e5c5 : ffffbe8df3519040 fffff80763cb5e30 ffffbe8deb2a1010 ffffbe8d00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27 ffff8b08c4e5ab70 fffff80758d268f5 : ffffbe8df3519040 0000000000000080 ffffbe8deb28e040 000fa425bd9bbfff : nt!ExpWorkerThread+0x105 ffff8b08c4e5ac10 fffff80758e04c68 : fffff80754f15180 ffffbe8df3519040 fffff80758d268a0 0000000000000000 : nt!PspSystemThreadStartup+0x55 ffff8b08c4e5ac60 0000000000000000 : ffff8b08c4e5b000 ffff8b08c4e55000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

    SYMBOL_NAME: nvlddmkm+108ad40

    MODULE_NAME: nvlddmkm

    IMAGE_NAME: nvlddmkm.sys

    STACK_COMMAND: .cxr; .ecxr ; kb

    FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

    Followup: MachineOwner

    Was this answer helpful?

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Anonymous
    2023-05-13T09:00:25+00:00

    so how does it go? i also got the same impact and the same error code

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Anonymous
    2023-04-27T21:34:44+00:00

    Blind Monk, my friend.

    I have had issues with this error code but only with the game Modern Warfare two. I don't get it. I tried lots of things including the most recent which was the end all be all fix, I replaced my ram.

    I went from 4 sticks of 8 to 2 sticks of 16. I figured if it was my RAM, I will just replace it all. I ran great for a week, no crashes on Call of Duty MW2.

    I was like wow, we did it boys I cant believe it.

    Butttt then last night I crashed again and as well as today. Activision Support has given me absolutely no help. I work in IT so this one is frustrating, I've done a lot of research myself and haven't really gotten anywhere.

    I just don't get it anymore. I've had crashing issues with this game since it came out in October have tried to rollback drivers. Switch drives that the game was installed on, played with settings etc. This is the only game that crashes for me, I am truly stuck.

    Do you have any ideas? If it was truly my RAM, why doesn't it happen with other games?

    Was this answer helpful?

    0 comments No comments