There are a lot of nvlddmkm reports with TUF systems. I think it can be ASUS fault aswell.
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
2024-09-05T19:04:27+00:00 -
Anonymous
2024-09-05T18:53:15+00:00 I have Asus Tuf Gaming f15 2022. I have same issue, tried everything, even switching rams. didn't fix. starting to think it's a windows bug.
-
Anonymous
2024-09-05T18:50:45+00:00 I also have done the same things you said, Iam having the same issue in my laptop. Game shows black screen and buzz sound. I have to force shutdown and boot again. This may probably happened after a windows update, so cannot be 100% sure it's a hardware issue. I have also tried removing and replacing rams. The issue was still there and it is still there now. Sometime it doesn't happen at all. Some days i cannot even play for 10 minutes
-
Anonymous
2024-07-11T13:21:13+00:00 I've the same problem on my Asus TUF Dash F15 laptop. I alreadly tried:
- Clean Windows Install;
- Physical cleaning and changed thermal paste (so there's no overheating);
- Unnistaled nvidia graphs driver using DDU and installed version 537.58 and 512;
- Installed MSIAfterburner to "underclock" my GPU/RAM;
- Disabled all services on startup at msconfig;
- Changed some settings on NVidia Control Panel (as per @Mihai_B_PC suggestion)
- Disabled HAGS (@BitsGuy)
After all that, the error persisted. I've read here that changing the RAM sometimes solved it. I disassembled the laptop just to find out there was one 8Gb RAM stick and the other 8Gb was an onboard chip. So I tried my luck, bought a new stick (with the exact same specs) and... It did not work at all. I guess I have a spare RAM now. So it might be yet some random configuration I've not yet found or my onboard RAM is the problem (if that's the case, I'll just wait to buy a new pc in the future). But I'll tinker a little bit more to be sure. Any progress I found I'll update on this forum.
-
Anonymous
2024-03-07T01:01:57+00:00 I know you are trying to be helpful, but what you have said isn’t providing any guidance.
So far I have (not necessarily in this order):
1 Uninstalled drivers with DDU and reinstalled with drivers from laptop manufacturers website.
2 turned off windows hardware acceleration
3 reinstalled a clean install of windows
4 turned on Nvidia debug
5 run scanfc
So far, nothing has resolved it.