Yes. Facing this issue for over 2 years on my Asus TUF, don't game that much now but still very annoying when you're casually gaming too.
Game crash with "The description for Event ID 0 from source nvlddmkm cannot be found"
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.
90 answers
Sort by: Oldest
-
Anonymous
2024-09-05T19:33:39+00:00 -
Anonymous
2024-09-06T21:35:38+00:00 Have this problem bad right now on an asus MB and a 4090. literally cant play any game more than 30 minutes without getting this crash and error. All relatively new parts and the problem just started out of nowhere. Even did a full OS clean install, wiped whole SSD and still no luck.
-
Anonymous
2024-09-07T21:25:23+00:00 So i did a clean windows installation, i already had a usb drive with windows 11 64 bit setup. This time i created a folder named "drivers" in my mobile phone. Then downloaded every driver including gpu and chipset drivers from my laptop manufacturer website which is asus. I did this with providing my laptop serial number in the website so that i get correct drivers for my laptop. Then when doing WINDOWS INSTALLATION, I chose not to connect to internet and bypassed the process. Then after windows installation i connected my phone to laptop using usb cable. After that i installed every driver 1 by 1 which i previously stored in my phone. Then before connecting to internet i disabled automatic driver updates from "System properties > Hardware > Device installation settings" and paused windows updates. Then i installed the game i played and crashed when i first raised this complaint to nvidia. I played for more than a hour, no issues till now. Will check again without changing any settings or installing any other programs.
-
Anonymous
2024-09-18T01:13:12+00:00 Hey Rahul, have you had any success with this? Did manually installing the Drives solve the problem at last?
-
Anonymous
2024-11-03T19:23:10+00:00 I want to share my case too cause I used too many hours to this. (solution is bolded)
I did all the same things as everyone else. I updated the bios version, windows version, tried different nvidia drivers (clean install with ddu), changed the ram memory and so on.
The thing that fixed the problem was to once again uninstall the nvidia drivers with DDU and download the drivers from the manufacturer's site. (in my case from Asus, right dirver was Driver Version: 560.94 )Not directly from Nvidia or via Geforce experience.
So neither the newer nor the older driver worked. Only the driver on the Asus website worked.
Nvidia seems to be making a complete fool of itself these days and I will never install Geforce experience again. I'm also considering on my next graphics card purchase whether I will even get an Nvidia card because this was such a **** bug.