Need help with event id 153 nvlddmkm

Question

Hi, for the past year my Acer Predator Helios 16 has been crashing when under load (gaming) everytime i boot up a game it crashes after 30mins to 1 hour, the game freezes then crashes. I have tried literally everything ranging from updating drivers, fiddling with the graphics settings in windows, using DDU to install new and older stabler drivers and still everytime it crashes i check event viewer and event id 153 and event id 13 pops up. I've even has the laptop serviced but there were no hardware issues on my end. Can anybody help me?

Here's the error

Log Name: System

Source: nvlddmkm

Date: 3/17/2026 11:47:46 PM

Event ID: 153

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: Dan

Description:

The description for Event ID 153 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\000000e3

Error occurred on GPUID: 100

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

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="nvlddmkm" />

<EventID Qualifiers="0">153</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2026-03-17T16:47:46.4339276Z" />

<EventRecordID>29950</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="13244" />

<Channel>System</Channel>

<Computer>Dan</Computer>

<Security />
```  </System>

  <EventData>

```sql
<Data>\Device\000000e3</Data>

<Data>Error occurred on GPUID: 100</Data>

<Binary>00000000020030000000000099000000000000000000000000000000000000000000000000000000</Binary>
```  </EventData>

</Event>  
  
  
Log Name:      System

Source:        nvlddmkm

Date:          3/17/2026 11:47:46 PM

Event ID:      13

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Dan

Description:

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\000000e3

Graphics SM Global Exception on (GPC 2, TPC 4, SM 1): Multiple Warp Errors

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

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

```xml
<Provider Name="nvlddmkm" />

<EventID Qualifiers="49322">13</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2026-03-17T16:47:46.4329275Z" />

<EventRecordID>29942</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="13244" />

<Channel>System</Channel>

<Computer>Dan</Computer>

<Security />
```  </System>

  <EventData>

```sql
<Data>\Device\000000e3</Data>

<Data>Graphics SM Global Exception on (GPC 2, TPC 4, SM 1): Multiple Warp Errors</Data>

<Binary>0000000002003000000000000D00AAC0000000000000000000000000000000000000000000000000</Binary>
```  </EventData>

</Event>  
  
![User's image](/api/attachments/dbb16d4e-bab8-4f84-9e17-bf2c88f8119e?platform=QnA)

Answer 1

Hi,

Is the problem occurring with a specific game?

Did you try updating the BIOS?

If possible, access msinfo32.exe in the search bar, take a screenshot and post it here.

Based on the information, it's almost certainly a hardware failure in the external GPU module.

Thanks

Answer 2

Event IDs 13 and 153 from nvlddmkm during gaming indicate that the NVIDIA display driver is repeatedly encountering GPU execution errors under load. On Windows this typically surfaces as a Timeout Detection and Recovery (TDR) problem: the GPU takes too long to complete work, the driver resets, and the game freezes or crashes.

On Windows, these conditions are what lead to VIDEO_TDR bug checks such as:

• 0x116 VIDEO_TDR_FAILURE
• 0x117 VIDEO_TDR_TIMEOUT_DETECTED

The documented root causes and mitigations for these TDR-related failures apply directly to the symptoms shown in the logs:

1. Ensure the display driver fully supports TDR and is not corrupted
   • Install the latest NVIDIA driver that is approved for the specific GPU and Windows version.
   • If a specific driver version is repeatedly named in crash dumps, disable that driver or replace it with an updated one from the GPU or system manufacturer.
2. Check for hardware and configuration issues that affect GPU stability The GPU taking longer than allowed to respond can be caused by:
   • Over‑clocked components (GPU, CPU, or motherboard settings).
   • Incorrect memory configuration or timings.
   • Insufficient system cooling causing thermal throttling or protection shutdowns.
   • Insufficient system power delivery under load.
   • Defective parts such as memory modules or motherboard components.
   For a gaming laptop, this means verifying in firmware/BIOS and vendor tools that:
   • No overclock is applied to GPU or CPU beyond factory settings.
   • Thermal profiles and fans are working correctly and vents are not obstructed.
   • Any vendor “turbo” or “OC” profiles can be temporarily disabled to test stability.
3. Verify graphics software stack and games are current
   • Confirm DirectX and any other graphics components (such as OpenGL runtime used by games) are up to date.
   • Make sure each affected game is fully patched.
4. Check Windows logs and, if possible, crash dumps
   • Use Event Viewer’s System log to correlate nvlddmkm errors with any bug checks like 0x116 or 0x117.
   • If kernel dumps are available, analyze them with WinDbg and the !analyze extension to confirm whether VIDEO_TDR failures are occurring and which module is faulting.
5. Run platform diagnostics
   • Use Windows Memory Diagnostics to rule out RAM issues. After the test, review the MemoryDiagnostics-Results entry in the System log.
   • Run any hardware diagnostics provided by the laptop manufacturer to stress‑test GPU, memory, and power delivery.
6. Use Safe Mode for isolation
   • Boot into Safe Mode (via Settings → Update & Security → Recovery → Advanced startup → Troubleshoot → Advanced options → Startup Settings → Restart, then choose option 4/5/6) and verify that the system is stable there. Safe Mode loads only minimal drivers; stability in Safe Mode and failures only under GPU load further implicate the graphics stack or hardware.

If, after clean driver installation, up‑to‑date graphics components, and passing memory and vendor diagnostics, the nvlddmkm errors and TDR‑like crashes continue only under GPU load, the remaining likely causes are marginal GPU hardware, power, or cooling that only fails under sustained gaming workloads. In that case, continued work with the system manufacturer’s support and their diagnostics is required, as the issue aligns with the documented VIDEO_TDR failure patterns.

---

References:

• Bug Check 0x116: VIDEO_TDR_FAILURE
• Bug Check 0x117: VIDEO_TDR_TIMEOUT_DETECTED