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-04-08T23:25:45+00:00

    Thank your soul bro omg!!!!! I have tried everything from uninstalling drivers with DDU, uninstalling windows, disabling my overclock, undervolting my system, reinstalling games, reseating my gpu and ram and it was all because of this setting lmao, my usage was stuck at 100% and would constantly crash my gpu, it now sits around 45% in PUBg lmao. This has caused me so much stress.

    Was this answer helpful?

    10 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-12-11T19:38:39+00:00

    I am glad someone posted this. I thought it was faulty video card, turns out it was a bad RAM stick. When i built my computer a year ago, I did long memtest, but i guess the issue only occurs when combined by playing or graphic intensive process (for example: RTX)

    Once i took out the bad one RAM stick, all the games i have ever had problem with random crashing started working great

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-11-01T20:31:10+00:00

    GPU: TUF Gaming RTX 3060

    CPU: Radeon 5700

    RAM: 16 Corsair Vengence (2x8)

    On a recent build, we started having this error appear after a few days of stable gaming. We did the entire NVidia "clean" install of drivers, DDU uninstall and reinstall of the latest drivers, and DDU uninstall and reinstall pre-4000 series drivers. All mainboard updates applied (except a Beta BIOS update...nope no beta tyvm). Installed MSI Afterburner/Kombuster/SPeccy/HM just to get any bit of information we could. Nothing was jumping out.

    We could reproduce to the exact level in Doom Eternal and after 3-4 matches in Halo Infinite. We started seeing additional errors as well, not related to GPU then it just would not post...

    Suffice it to say, it was a challenge to figure out. In the end, we went back to the shop for help (Memory Express for those in Canada) and had their tech take a look.

    TL;DR It was a bad DIMM. Replaced the set with another set and the system has been completely stable ever since (3+ weeks). Usual Doom and Halo points of failure are breezed by. Try your RAM?

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-03-20T14:14:23+00:00

    It may be you have faulty RAM.

    Try removing one of your RAM sticks (DIMM), and then swapping over to the other RAM stick

    I had this issue with same nvlddmkm error codes, and have posted a reply in this thread already stating that removing one of the DIMM resolved the issue, and using only the faulty DIMM resulted in system being unable to start.

    The GPU uses the RAM for some operations, so (in simple terms) it can lose communication with the driver if the RAM is not working correctly.

    Luckily, RAM is cheap and easy to replace.

    It worked for me, and I was struggling woth the problem for 3 years before finding out it was a RAM issue.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2022-09-18T13:19:12+00:00

    Im also facing similar issues like this. I have also searched through every possible solutions and unfortunately with no luck of fixing this errors. Im using ASUS TUF FX505GT, i bought this from year 2020 and i also thought that my gpu is failing. But i ran gpu stress test and my gpu seems to be okay. I think maybe its from an update or something. Because i recently updated my laptop to windows 11 and reverted back to windows 10 because it doesn't support armoury crate yet. And then i frequently getting errors. Hoping it will be resolved soon by an update or something..

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments No comments