Windows 10: Even id 14 nvlddmkm errors

Hello , My pc reboots or freezes all of a sudden . When I check event logs I see these type of errors and a lot of them .Here is the full description of errors.Log Name: System Source: nvlddmkm Date: 10-05-2022 19:13:00 Event ID: 14 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DESKTOP-VN4OTRQ Description: The description for Event ID 14 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

:)

 

nvlddmkm errors event id 13 and 14 when activating drivers after clean install

Hello,

I've had a very frustrating bug for a bit. I've tried to troubleshoot and can't seem to resolve this. I've got it narrowed down to the graphics card drivers. I have the newest Nvidia drivers. I've booted in Safe Mode, deleted the device in Device Manager,
restarted, reinstalled newest drivers. System works fine when I only have Intel(R) HD Graphics 530 active (I've got an Optimus system). But as soon as I activate my 970M card, I get errors 13 and 14 from nvlddmkm.

I haven't messed with the system at all since clean OS reinstall about two months ago. I've got the Asus GL502VT system with no overclocking/custom tuning.

****

The description for Event ID 13 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\UVMLiteController0x1

Graphics Exception: ESR 0x404490=0x80000001

The message resource is present but the message was not found in the message table

***********

The description for Event ID 14 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\UVMLiteController0x1

13604(2ed0) 8401359d 003aa70d

The message resource is present but the message was not found in the message table

 

Error 14 & 4101 nvlddmkm

I have build a new pc with the following components:

CPU: AMD Ryzen 9 3900X
Motherboard: Gigabyte Aorus X570 ULTRA
GPU: Gigabyte Aorus GeForce RTX 2080 Ti Xtreme 11G
CPU cooler: Corsair Hydro H150i Pro
Memory: Corsair Vengeance RGB Pro CMW32GX4M4C3200C16
Power supply: EVGA SuperNOVA 850 G2

If I play a game (league of legends) the computer completely freezes on a random moment. After I unfreeze in the event viewer I got the following errors (printscreen:
Screenshot)

last part of this post I have posted the XML view of the errors.

• 22:31 Error 14: nvlddmkm
• 22:31 - 22:32 error 4101 & 4109: display

I have monitored and logged the GPU during the times that the errors and freezed computer happened. Here the link to the file. (monitored with GPU-Z)

https://github.com/l/GPU-Z/blob/master/GPU-Z log.txt

I tried last couple week allot to solve the problem, but without succes. I tried the followed things:

• Install and double check if I have all drivers
  
• Installed nvidia drivers on different versions (uninstall drivers with DDU and new nvidia drivers)(use now newest version 436.02 because older versions like 319, 416.94, 419.67, 430.86, diddn' t work
  for me)
• I plugged ram out and in to make sure its good.
  
• I also did memtest where he had no errors after completed.
  
• I tried to do GPU vol +5% diddn't help also
  
• Power options: High Performance
  
• Power options hard disk turn off never
  
• Power options PCI Express -> Link state -> Settings: OFF
  
• Power options Display-> Turn off display after: Never
  
• Regedit GraphicsDrivers set TdrDelay to 20
  

GPU-Z screen Screenshot

I hope someone can help me.

XML view of the errors

Code:

  <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">- <System>  <Provider Name="nvlddmkm" />   <EventID Qualifiers="49322">14</EventID>   <Level>2</Level>   <Task>0</Task>   <Keywords>0x80000000000000</Keywords>   <TimeCreated SystemTime="2019-08-24T20:31:17.989470600Z" />   <EventRecordID>6899</EventRecordID>   <Channel>System</Channel>   <Computer>DESKTOP-EFVPIJU</Computer>   <Security />   </System>- <EventData>  <Data>\Device\Video3</Data>   <Data>0cde(308c) 00000000 00000000</Data>   <Binary>0000000002003000000000000E00AAC0000000000000000000000000000000000000000000000000</Binary>   </EventData>  </Event>

Code:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">- <System>  <Provider Name="Display" />   <EventID Qualifiers="0">4101</EventID>   <Level>3</Level>   <Task>0</Task>   <Keywords>0x80000000000000</Keywords>   <TimeCreated SystemTime="2019-08-24T20:32:51.529245200Z" />   <EventRecordID>6900</EventRecordID>   <Channel>System</Channel>   <Computer>DESKTOP-EFVPIJU</Computer>   <Security />   </System>- <EventData>  <Data>nvlddmkm</Data>   <Data />   </EventData>  </Event>Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">- <System>  <Provider Name="Display" />   <EventID Qualifiers="0">4109</EventID>   <Level>3</Level>   <Task>0</Task>   <Keywords>0x80000000000000</Keywords>   <TimeCreated SystemTime="2019-08-24T20:33:04.189805800Z" />   <EventRecordID>6901</EventRecordID>   <Channel>System</Channel>   <Computer>DESKTOP-EFVPIJU</Computer>   <Security />   </System>- <EventData>  <Data>League of Lege</Data>   <Data />   </EventData>  </Event>

 

Event ID 14 from source nvlddmkm cannot be found.

Hi MrPepka, thanks for your reply. Actually done this a couple of hours after posting this thread and currently observing if there would be another BDOD caused by nvlddmkm error.

Though earlier, got 2 event ID 41 caused by PAGE_FAULT_IN_NONPAGED_AREA. Minidump shows USBXHCI.sys and ntoskrnl.exe as the culprit. This was after doing the 3 updates above. Minidump from V2 log collector attached.

Attachment 310892