Hi Zoltan ... this did the trick on my Factory OC GTX 1080ti consistently randomly crashing issue. I was going crazy troubleshooting this and completely forgot HIDEvolutions installed an OC version. Thanks a bunch !
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: Most helpful
-
Anonymous
2023-11-23T02:27:56+00:00 -
Anonymous
2023-08-30T22:47:41+00:00 Turns out I was wrong lol. It must of been some coincidence that the issues stopped. I have however found a solution albeit it completley random, The crashes continue, only when playing what you would consider a low res game. The crashes happen now within seconds of loading any type of that game up. The fix; I have found, is to load up a high res game in the background then they run as smooth as silk, as soon as i terminate the high res game then it crashes. I have no idea why, but a way forward I have.
-
Anonymous
2023-08-12T23:28:15+00:00 Possible Fix
We got two computers in the house, same parts but running 2 different gpus.
AMD Ryzen 7 770X
MSI PRO B650P WiFi
32G Ram
GPUs are 950gtx 2gb mem and a 1060ti 3gb mem neither are overclocked.
Both Windows 11
I do weekly updates on videocard, windows and any other software. Also physical cleanup every 3 weeks.This happened on the 1060 pc and after trying everything incl windows reinstall, I managed to fix it by updating BIOS. Been ok ever since.
However the 950 been having same driver error specifically on Diablo IV Seasonal, apparently when playing on eternal realm is all good despite the bios update (there is a new one out but is beta so im holding off for now)
The forum for that game are littered with people having crashes, they seemed to happen around 20 min or so, once my husband portalled around that time frame, I took off cross platform play and communication and the time extended to 1 hour.
the 1060 is fine. Other people with more powerful cards complain about the same issue in the same game. Im unsure how to circumvent this issue atm. But if your videocard isnt too old, try the bios update would be my recommendation once the update/clean reinstall process didnt work.
That driver crash was at least in the 1060 case resulting from memory leaks, the bios update fixed the mobo handling of the memory process and worked out. Hope this helps!
Cheers
-
Anonymous
2023-08-07T17:53:57+00:00 This post has been a life saver, I tried to find an answer to this issue 12 minths ago and found nothing. This issue flared up again for me and ive run into this post which has saved me! it was the debug mode in Nvidia Control panel that fixed it, uninstalling Alienware Command Centre was what originally seemed to fix it, saved me buying some new memory too hopefully.
Thanks.
-
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!