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

90 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-08-04T17:44:58+00:00

    Post back if it works. I have been fighting this for about a year, but it seems like it go WAY worse with the new drivers. I don't play Multi-Player so I would just pause the game, wait for a bit, and unpause and it I could get it to run for a while. Frustrating but I could get it to work for a while. With the newest drivers I would get 4-5 minutes at most before getting the error. Good luck!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-08-04T17:26:53+00:00

    Thanks Man. I'll try this settings and will let you know if it fixed my problem. Been facing this problem since December 2022. Asked Asus for services but they just told me to RMA. It's out of warranty so it would cost me around 740 US dollars. Better to buy and new laptop.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-08-04T17:16:39+00:00

    I dropped the Core clock by 52. I didn't mess with the Memory clock at all. So far I have not had a crash and have played for 2 hours.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-08-04T17:03:24+00:00

    Can you tell me the at what speed you set it in the msi afterburner. Since we got the same laptop, it might work with mine too.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-08-04T16:51:14+00:00

    I underclocked my GPU with MSI Afterburner and so it is working perfectly! I have been battling this for over a week and this is the only thing that has worked.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments