A Windows 11 update completes, and the NVIDIA driver that was rock-solid for months starts crashing: games die to the desktop, the display flickers black for seconds at a time, and the Event Viewer fills with nvlddmkm errors. The GPU hardware did not change overnight — the driver did. Windows replaced your working NVIDIA driver with a migrated version during the update, and that version is either incompatible, corrupted, or fighting with the new OS build.

This is one of the most common post-update complaints on gaming laptops, and it has a clear signature: stability before the update, crashes after, with no hardware changes in between. The fix is equally clear in concept — get the bad migrated driver off the machine and install a known-good NVIDIA release cleanly — but the details matter, because Windows Update will happily reinstall the bad driver if you let it.

The sequence below removes the bad driver thoroughly, installs the right replacement, blocks the bad version from returning, and addresses the thermal and clock factors that turn a marginal driver into a crashing one.

Why this happens

  • Corrupted driver migration: The update’s driver migration can complete with damaged files. The driver loads but crashes under any real GPU workload.
  • Incompatible driver version pushed by Windows Update: Microsoft’s catalog version may lag NVIDIA’s releases or mismatch your GPU, producing a driver that installs cleanly and crashes constantly.
  • Remnants of the old driver conflicting: The migration can leave pieces of the previous driver behind. Mixed old and new components destabilize the whole stack.
  • GeForce Experience overlay and filters: The update can re-enable overlays and filters that hook the driver. These hooks are a known crash source, especially the in-game overlay.
  • GPU thermals degraded: Unrelated to the update but unmasked by it: a GPU that was borderline on heat crashes more under the new driver’s different power behavior.
  • Unstable overclock carried over: Driver updates reset some settings but not external overclock tools. An overclock stable on the old driver may crash on the new one.
  • Windows Update re-replacing the driver: The cruelest loop: you fix the driver manually, and Windows Update silently reinstalls the bad version days later.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm the crashes track the update

Verify the diagnosis before rebuilding the driver stack. Timing is evidence.

  1. Open Settings, then Windows Update, then Update history, and note the most recent feature or cumulative update date.
  2. Check Event Viewer under Windows Logs, then System, for nvlddmkm errors and their timestamps.
  3. Crashes beginning within days of the update confirm the migration as the trigger.

Fix 2: Remove the bad driver completely with DDU

A standard uninstall leaves the remnants that cause repeat crashes. DDU from Safe Mode is the thorough option.

  1. Download the newest NVIDIA notebook driver for your GPU from NVIDIA’s download page before starting.
  2. Boot into Safe Mode and run Display Driver Uninstaller with Clean and restart.
  3. Install the fresh NVIDIA driver immediately in normal Windows, choosing the clean installation option in the installer.

Fix 3: Disable overlays and GeForce Experience hooks

Overlays inject into the driver’s rendering path and are a disproportionate crash source after updates re-enable them.

  1. Open GeForce Experience settings and turn off the in-game overlay.
  2. Disable filters and instant replay if enabled.
  3. Also disable other overlays — Discord, Xbox Game Bar — while testing stability.

Fix 4: Block Windows Update from reinstalling the bad driver

Protect the fix. An unprotected manual install is temporary.

  1. Pause driver updates or use the show-or-hide updates troubleshooter to block the specific bad version.
  2. Verify after the next Patch Tuesday that your NVIDIA driver version is unchanged.
  3. If crashes ever return after an update, check the driver version first — it is the fastest diagnostic you have. The 24H2 installer notes cover related version-pinning scenarios.

Fix 5: Stabilize thermals and clocks

A marginal driver crashes sooner on a hot or overclocked GPU. Remove those multipliers.

  1. Monitor GPU temperatures under load and clean vents if they run hot.
  2. Reset any overclock to stock clocks in Afterburner or the vendor utility.
  3. Test the previously crashing games for an extended session. For persistent keep-crashing patterns beyond updates, the NVIDIA crashing driver guide goes deeper.

Fix 6: Test with a clean boot

Isolate third-party software interference with a minimal startup.

  1. Open msconfig and choose a clean boot with non-Microsoft services disabled.
  2. Test GPU stability in this minimal state.
  3. If crashes stop, re-enable services in groups to identify the conflicting software. Microsoft’s Windows support pages document the clean-boot procedure.

Fix 7: Roll back to the last stable driver as a bridge

While you work on a permanent fix, rolling back to the pre-update NVIDIA driver restores stability immediately. This is triage, not surrender: it gets the machine usable today while you prepare the clean install of the current release. Keep the rolled-back version only until the clean install is done, since old drivers accumulate game and security issues over time. Note the stable version number so you have a known-good fallback if future updates misbehave again.

  1. In Device Manager, open the NVIDIA adapter’s Properties and choose Roll Back Driver on the Driver tab.
  2. If rollback is unavailable, download the previous release from NVIDIA’s driver archive and install it.
  3. Verify stability with the previously crashing games or workloads.
  4. Schedule the DDU clean install of the current driver, treating the rollback as a bridge rather than a destination.

Closing

An NVIDIA driver that crashes after a Windows 11 update is telling you the migration went wrong, not that the GPU is dying. DDU the bad driver, install the current NVIDIA release cleanly, strip the overlays, and block Windows Update from resurrecting the bad version. Stability returns with the right driver — and stays, as long as the update channel is not allowed to swap it behind your back again.

Frequently asked questions

Why does my NVIDIA driver keep crashing after the Windows 11 update?
The update migrates the graphics driver during installation, and the migrated driver is frequently a version that is incompatible with your GPU or corrupted mid-migration. Games crash to desktop, the screen flickers, or the driver restarts repeatedly. Replacing the migrated driver with a clean install of the current NVIDIA release resolves it.
How is a crashing driver different from the installer failing?
A crashing driver installed successfully but cannot run stably — the software is present and malfunctioning. An installer failure means the software never got installed at all. They need different fixes: crashes need driver replacement and stability work, while installer failures need the blockers cleared first, as covered in the installer failure guide .
Should I roll back to the previous NVIDIA driver?
Rolling back is reasonable as an immediate workaround if the previous version was stable — it gets you working today. But treat it as temporary: install the newest NVIDIA release cleanly afterward, since staying on old drivers accumulates game incompatibilities and security gaps. If the newest also crashes, the cause is deeper than version choice.
Can Windows Update replace my fixed driver with the bad one again?
Yes, and it does. Windows Update may reinstall its preferred driver version over your manual install, resurrecting the crashes weeks later. After stabilizing, pause driver delivery or block that specific driver version so your working driver survives future update cycles.