nvlddmkm Event ID 153 on RTX 50 Cards: Free Diagnoser With an Ordered Fix List
nvlddmkm Event ID 153 is an error logged in Windows Event Viewer when the NVIDIA graphics driver hits a fault it has to recover from. Owners of GeForce RTX 50 series cards see it alongside game crashes, a black screen for a few seconds, freezes after waking the PC, or stutter. This free diagnoser puts the known fixes in the best order for your symptom and setup.
There is no single confirmed cause. NVIDIA has not tied Event ID 153 to one driver bug, and the same event appears for driver faults, an unstable PCI Express link, power delivery problems and unstable overclocks. That is why a fix that works for one person does nothing for the next. The guide below explains how to read the event, then covers each cause with steps for the RTX 5090, 5080, 5070 Ti, 5070 and 5060 family.

Table of Contents
How to Use the nvlddmkm Event ID 153 Diagnoser
The diagnoser does not guess a single cause. It reorders seven groups of fixes so the most likely one for your setup comes first.
- What happens. A crash, a brief black screen, a fault on wake, a fault in video, or stutter.
- What changed. A new driver points at the driver. A newly installed card points at the slot and the power cable.
- Riser or vertical mount. Moves the PCIe checks to the top.
- Overclock or undervolt. Moves stability checks to the top.
- Power cable and card. Add notes specific to adapters and to high-power cards.

What nvlddmkm Event ID 153 Is
nvlddmkm.sys is the kernel-mode part of the NVIDIA display driver. When it loses contact with the graphics card or detects a fault, it writes an event to the Windows System log and tries to recover. Event ID 153 is one of those entries. It often sits beside Event ID 14 from the same source, or beside a “display driver stopped responding and has recovered” message.
How to find it
- Right-click the Start button and choose Event Viewer.
- Open Windows Logs, then System.
- In the right pane choose Filter Current Log.
- Under Event sources tick nvlddmkm and select OK.
- Compare the time of each entry with the time of each crash or black screen.
| What you see in the log | What it suggests |
|---|---|
| Entries at the exact moment of each crash | The event describes your problem. Work through the fixes |
| Entries at boot or wake only | A start-up or resume fault. Check Fast Startup, BIOS and the driver |
| A few entries, with no visible problem | The driver recovered silently. Low priority |
| No entries when the game crashes | The crash has another cause. Look at the game or memory |
| Bugcheck 116 alongside it | The driver failed to recover and Windows stopped. Treat as a hardware or driver fault |
NVIDIA has not published a statement linking Event ID 153 to a specific driver bug, and reports go back to the launch of the RTX 50 series in early 2025. Treat it as a symptom with several possible causes.
Fix 1: Clean-Install or Roll Back the Driver
Start here if the problem began after a driver update, or if you have never done a clean install on this card.
- Download the current GeForce driver from NVIDIA’s site or the NVIDIA app.
- Run the installer, choose Custom, and tick Perform a clean installation.
- Restart and test. If the error returns, install the previous driver version in the same way.
- For a deeper clean, use Display Driver Uninstaller in Safe Mode before installing. It removes every leftover driver file.
| Driver branch | Use it when |
|---|---|
| Latest Game Ready | You play new releases and the current version is stable for you |
| Previous Game Ready | The fault began with the latest version |
| Studio | You want the slower-moving branch. Some owners report fewer faults on it |
| Hotfix | NVIDIA has released one that names your symptom |
Read the release notes before installing. The “Fixed” and “Open Issues” lists say whether your symptom is known. One 2026 report says driver 595.97 addressed stutter and Event ID 153 after boot and wake on RTX 5080 Founders Edition cards. Check NVIDIA’s notes for that version before relying on it.
Fix 2: The PCIe Link, Risers and the Slot
Community troubleshooting points to the PCI Express connection more often than anything else on RTX 50 cards. These cards negotiate a PCIe 5.0 link, which is far less tolerant of a long or imperfect signal path than PCIe 4.0 or 3.0.
- If the card is on a riser cable or vertical mount, test it directly in the motherboard slot. Risers are the most often reported cause on RTX 50 cards.
- In the BIOS, set the PCIe slot speed from Auto to Gen 4. A Gen 5 link over a marginal connection produces exactly this error.
- Reseat the card: power off, unplug, remove it, check the slot for dust and press it back until the latch clicks.
- Update the motherboard BIOS. Several board makers released updates for RTX 50 compatibility.
Signal speed per PCIe lane
Higher speeds are less tolerant of risers and worn slots
Setting the slot to Gen 4 costs almost nothing in games. Frame rates are within a percent or two, because current graphics cards do not fill a Gen 4 x16 link. It is a safe test, and for many owners a permanent fix.

Fix 3: Power Cable and Power Supply
- Push the 12V-2×6 power connector in fully at both ends. There should be no gap between the plug and the socket.
- Use the power supply’s own 12V-2×6 cable if it has one, in place of the multi-plug adapter.
- Do not bend the cable sharply within 3 cm of the connector.
- Check the power supply meets the card’s requirement, with headroom. An undersized unit trips under load spikes.
| Card | Typical power draw | Power supply NVIDIA recommends |
|---|---|---|
| RTX 5090 | About 575 W | 1000 W |
| RTX 5080 | About 360 W | 850 W |
| RTX 5070 Ti | About 300 W | 750 W |
| RTX 5070 | About 250 W | 650 W |
| RTX 5060 Ti | About 180 W | 600 W |
| RTX 5060 | About 145 W | 550 W |
These are reference figures. Partner cards with factory overclocks draw more, so check the box or product page for yours. A power supply at the edge of its rating can pass every benchmark and still trip on the short load spikes games produce.
Fix 4: Overclocks, Undervolts and Memory
A driver timeout is what an unstable system looks like from Windows’ side. The graphics card is often blamed for a fault that starts in the memory or processor.
- Reset the GPU to stock settings in any tuning tool. Undervolts that pass benchmarks often fail in real games.
- Turn off XMP or EXPO for one test session. Unstable memory produces driver timeouts that look like GPU faults.
- Reset CPU overclocks and curve optimiser offsets.
- Retest. If the error stops, bring settings back one at a time.
Undervolting is the most common trap. A curve that is stable in a stress test can fail in a game that swings between low and high load, because the card passes through voltage points the test never held it at.
Fix 5: Faults After Sleep, at Boot or in Video
After boot or waking from sleep
- Turn off Fast Startup: Control Panel, Power Options, Choose what the power buttons do, untick Turn on fast startup.
- Update the motherboard BIOS and chipset drivers.
- Clean-install the graphics driver.
- If it only happens on wake, test with sleep disabled for a few days to confirm.
While playing video
- Update the graphics driver. Video decode faults on RTX 50 cards have been reported with specific driver branches.
- Turn off hardware acceleration in the browser or player as a test.
- If the fault stops, the cause is the driver’s video decoder. Stay on the workaround until a newer driver is released.
- Report it with NVIDIA’s driver feedback form, with the driver version and the file type.
Video playback uses the card’s hardware decoder, a different part of the driver from the one games use. A fault that appears only in video and never in games is almost always a driver issue, and the hardware acceleration switch is a reliable workaround.

When It Is the Card Itself
| Test | Result | Conclusion |
|---|---|---|
| Card in a second PC | Fault follows the card | Card is faulty. Ask for a replacement |
| Different card in your PC | Fault stays | Motherboard, power supply or memory |
| Stock settings, direct in slot, Gen 4, new cable | Fault continues | Likely hardware |
| Fault only in one game | Other games are fine | That game or its settings |
If stutter is your only symptom and the event is rare, the two may be unrelated. Work through how to fix FPS drops, and see the fix lag and FPS drops hub for game-specific guides.

About NVIDIA GeForce RTX
nvlddmkm.sys is the kernel-mode display driver for NVIDIA GeForce graphics cards on Windows. Faults it detects are written to the Windows System event log under the source nvlddmkm.
The GeForce RTX 50 series, launched in 2025, includes the RTX 5090, 5080, 5070 Ti, 5070, 5060 Ti and 5060. The cards use the PCI Express 5.0 interface and, on most models, the 12V-2×6 power connector.
The nvlddmkm Event ID 153 diagnoser on this page is free to use, and we update it when the game changes its numbers.
Official page: NVIDIA, official driver downloads.
Related Calculators
If this nvlddmkm Event ID 153 diagnoser helped, these free tools work the same way.
- How to fix FPS drops
- Fix lag and FPS drops hub
- DLSS vs FSR frame generation checker
- KB5132061 install error fixer
- Best anti aliasing setting picker
- All free gaming and tech calculators
New this month: KB5132061 install error fixer, 0xc000000d boot loop fixer, Windows 11 version checker, EmuDeck Ryujinx crash fixer.
Frequently Asked Questions
Quick answers about NVIDIA GeForce RTX and the nvlddmkm Event ID 153 diagnoser.
What is nvlddmkm Event ID 153?
An entry the NVIDIA display driver writes to the Windows System log when it detects a fault and tries to recover. It appears with crashes, black screens and freezes.
How do I fix nvlddmkm Event ID 153?
Clean-install the driver and try the previous version, remove any PCIe riser and set the slot to Gen 4, reseat the card and its power connector, and remove overclocks and undervolts.
Is nvlddmkm Event ID 153 a driver bug?
Not always. NVIDIA has not confirmed one cause. The same event is logged for driver faults, an unstable PCIe link, power problems and unstable overclocks.
Does setting PCIe to Gen 4 lower performance?
By one or two percent at most. Current graphics cards do not fill a Gen 4 x16 link.
Does Event ID 153 mean my RTX 50 card is faulty?
Only if the fault continues at stock settings, directly in the slot, with a good power cable, and follows the card into another PC.
Can a riser cable cause nvlddmkm errors?
Yes. Risers are the most often reported cause on RTX 50 cards, because a PCIe 5.0 link is sensitive to signal quality.
How do I see nvlddmkm events?
Open Event Viewer, Windows Logs, System, choose Filter Current Log and tick nvlddmkm under Event sources.
Is the nvlddmkm Event ID 153 diagnoser free?
Yes. It runs in your browser and needs no sign-up.
More Lag and FPS Fixes
Every guide starts with a free diagnoser. See them all on the fix lag and FPS drops hub.
Axee Davies is the founder of AxeeTech, publishing gaming guides, codes, and Windows how-tos since March 2013. A tech enthusiast for 13+ years — starting with smartphones and Android rooting — he now runs a site that puts out a new guide every day for Roblox players, traders, and Windows users. More about AxeeTech
More Games You May Like
Blue Lock Rivals 8v8 Update: New Modes, Codes, and Strategies for 2026
Halo Reach Mission List: All 11 Campaign Levels in Order
Best Anti Aliasing Setting: Free Picker for DLAA, TAA, FXAA, MSAA, SMAA and FSR Native
How to Fix Recording Lag in Minecraft: Free OBS Settings Generator by GPU
How to Fix Minecraft Server Lag: Free TPS and RAM Calculator With server.properties Values
How to Fix Discord Lag: Free Fixer for App, Voice, Stream and In-Game Lag (Step by Step)
How to Fix Marvel Rivals Lag: Free FPS vs Ping Diagnoser With the Right Fix List
How to Fix FPS Drops: Free Diagnoser Finds the Cause in 7 Answers (CPU, GPU, Heat or Windows)