Amdkmdag.Sys Failed | Clean Driver Repair Steps

Guide / By

Most amdkmdag.sys failed crashes stop after a clean AMD graphics driver install plus quick Windows file checks.

If your PC freezes, restarts, or throws a blue screen tied to an AMD display driver, it can feel random. It usually isn’t. This error points to a graphics-driver file that Windows loads when the GPU is doing work, so problems show up during games, video playback, waking from sleep, or when the desktop is switching resolutions.

This guide walks you through a clean, safe repair path. You’ll start with quick checks that catch the easy wins, then move into a proper driver reset, Windows file repair, and a few stability checks. By the end, you’ll know whether the fix is a driver swap, a Windows repair step, or a deeper stability problem like heat, power, or memory.

What This File Error Usually Means

amdkmdag.sys is part of the AMD Radeon kernel-mode graphics driver. Windows talks to the GPU through this driver layer, and a crash can trigger a stop code, a black screen, or a full reboot. Many reports pair it with display timeout errors, where Windows resets the driver after the screen stops responding.

The tricky part is that the driver can be the victim, not the cause. A driver crash can come from a bad install, Windows updates swapping components, a buggy driver branch for your card, unstable GPU clocks, overheating, power delivery dips, corrupted system files, or even unstable RAM.

What You Notice Common Trigger First Move
Blue screen during games Driver crash under load Clean-install the AMD driver
Black screen after sleep Display wake handshake Update GPU + chipset drivers
Random reboot on desktop Power or unstable clocks Reset tuning to stock
Stutter then driver reset Timeout detection (TDR) Try a different driver version

Amdkmdag.Sys Failed On Windows 10 Or 11

When the screen goes blank or Windows throws a stop message that names this file, treat it like a driver install problem until proven otherwise. A clean reinstall removes broken pieces, clears leftover settings, and gives you a known baseline.

Before you start, grab two things. First, the AMD Adrenalin driver that matches your GPU and Windows version. Second, the AMD Cleanup Utility, which removes AMD graphics and audio driver pieces so the next install starts fresh.

Step 1 Collect A Bit Of Clue Data

These checks take a minute and can keep you from chasing the wrong thing.

  • Note the stop code — If you see VIDEO_TDR_FAILURE, it fits the driver-reset pattern.
  • Check Event Viewer — Look under System for display driver resets around the crash time.
  • List recent changes — A driver update, Windows update, new monitor cable, or GPU tuning change is often the spark.

Step 2 Do A True Clean Driver Install

  1. Disconnect the internet — This reduces the chance Windows pulls a driver mid-process.
  2. Run AMD Cleanup Utility — Choose Safe Mode when it offers it, then let it remove AMD driver files.
  3. Restart back to normal Windows — Let the PC boot normally after the cleanup finishes.
  4. Install the AMD driver you downloaded — Use the full installer, then reboot once more.
  5. Test your usual trigger — Launch the game, video app, or workload that caused the crash.

If the crash started right after a driver update, don’t force the newest build. Try one older driver version that was stable on your machine. If the crash started after Windows updated, a clean install often puts the Radeon stack back in order.

Step 3 Reset GPU Tuning And Overlays

Driver-level tuning is a common reason a system looks fine on the desktop and falls over in games.

  • Set GPU tuning to default — Undo undervolts, overclocks, custom fan curves, and power limits.
  • Turn off third-party overlays — Disable recording and overlay tools, then test again.
  • Reset shader cache — Clear cached shaders in the AMD software if stutter or glitches began after an update.
  • Disable browser hardware acceleration — If crashes happen during video playback, this can narrow the cause.

If you can’t stay in Windows long enough to run the cleanup tool, boot into Safe Mode first. Use the Windows recovery screen, pick Startup Settings, then choose Safe Mode. Once the desktop loads, run the cleanup utility, reboot, and install the driver.

Fix Windows Files That Can Trip The Driver

Even if the graphics driver is the name on the crash, Windows system files can be part of the mess. A broken system component can cause driver calls to fail, which then looks like a GPU problem.

Run these commands from an elevated Command Prompt. They are built into Windows and aim to repair the Windows image and protected system files.

  1. Run DISM RestoreHealth — Use DISM.exe /Online /Cleanup-image /Restorehealth and wait for it to finish.
  2. Run System File Checker — Use sfc /scannow after DISM completes.
  3. Restart the PC — A reboot lets repaired files load cleanly.

If DISM fails, rerun it after a reboot and try again. If SFC reports fixes, test your usual crash trigger right after the restart so you get a clean signal.

Also install pending Windows updates. Graphics stability fixes sometimes land in cumulative updates, and driver resets can calm down after the OS patch level catches up.

Windows Settings That Cut Down Driver Resets

Once you have a clean driver baseline, a few Windows settings can help keep the display stack steady. Start with the safe, reversible toggles. Leave registry edits for last.

Power And Display Tweaks

  • Turn off Fast Startup — Fast Startup can carry a messy driver state across boots on some PCs.
  • Set PCIe Link State Power Management to Off — On desktops, this can prevent link power dips during load changes.
  • Use a steady refresh setup — If you run two monitors with different refresh rates, test with one monitor to see if the crash stops.

TDR Delay For Heavy Workloads

TDR is Windows’ timeout system that resets the graphics driver if the GPU stops responding for too long. A longer delay can help with long compute tasks and some creation apps. It can also mask a crash that would have reset faster, so treat it as a diagnostic step, not a permanent patch.

  1. Create a restore point — Use System Protection so you can roll back if you make a mistake.
  2. Open Registry Editor — Run regedit as an admin.
  3. Go to GraphicsDrivers — Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers.
  4. Add TdrDelay — Create a DWORD named TdrDelay and set a decimal value like 10 or 15.
  5. Restart and test — Run the same workload and watch for a driver reset.

MPO Toggle For Desktop Flicker

If you see desktop flicker or black flashes, disabling MPO can calm some setups. It’s reversible.

  1. Create a restore point — Do this before any registry edit.
  2. Add OverlayTestMode — In HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm, create OverlayTestMode and set it to 5.
  3. Reboot and test — To undo, delete the value or set it to 0, then reboot.

Driver Version Choices That Reduce Crashes

AMD publishes new driver packages often, and not every release behaves the same on every GPU, motherboard, and monitor setup. If your issue began after an update, your goal is to land on a stable branch, not to chase the newest number.

Pick A Stable Target First

  • Start with the current recommended release — Install the driver that AMD lists for your GPU and OS.
  • Roll back one version — If the newest driver started the crash, step back one release and retest.
  • Try a driver-only install — If the full software stack is crashing, a lean install can narrow the trigger.
  • Avoid mixing installers — Don’t layer a vendor bundle on top of a full AMD package without a cleanup pass.

Watch For Windows Replacing The Driver

Windows Update can install display drivers. That can be fine, yet it can also overwrite pieces of a Radeon install and create mismatches. If your clean install holds for a day and then the crash returns, check update history for driver installs and pause driver updates while you test.

Hardware And Firmware Checks That Matter

If a clean driver install and Windows file repair don’t stop the crashes, check stability. A GPU driver is often the first component to crash when the system is on the edge.

Chipset Drivers And BIOS

On AMD systems, chipset drivers handle power, PCIe, and device communication. If those layers are old or corrupted, graphics can act flaky. Update your chipset driver from AMD, then reboot. If your motherboard vendor has a BIOS update that lists stability or compatibility fixes, apply it with care and follow the vendor steps.

On laptops with switchable graphics, start with the driver package from the laptop maker. If it’s stable, stay there. If not, try AMD’s package after cleanup once.

Heat And Airflow

  • Check GPU temperature under load — Use Radeon metrics or a trusted monitor tool while running a game.
  • Clean dust from the card and filters — Dust can raise temps and push the card into instability.
  • Confirm fans ramp up — A stuck fan can cause sudden black screens.

Power And Cables

  • Reseat the PCIe power plugs — A loose connector can cause a dip that the driver can’t recover from.
  • Use separate PSU cables when possible — Don’t daisy-chain a single cable to two GPU sockets if your supply includes two leads.
  • Swap the display cable — A bad HDMI or DisplayPort cable can mimic driver faults during mode changes.

Memory And Storage

  • Disable XMP or EXPO for a test — If your RAM overclock is unstable, GPU stress can expose it.
  • Check drive health — Corrupted driver files can come from storage errors.
  • Test with one RAM stick — If you suspect memory, a quick isolation test can save time.

When The PC Won’t Stay Up Long Enough

If your PC can’t stay up long enough to reinstall drivers, take the safe path first. Boot into the Windows recovery menu, then start Safe Mode. In Safe Mode, the display runs on a basic driver, so you can clean up the AMD stack without triggering the same crash.

After you regain a stable desktop, repeat the clean install steps. Keep your first test simple: one game, one benchmark, or one video workload you trust, with no overclocking and no overlays. If the system stays stable, add your tweaks back one by one.

If you still get amdkmdag.sys failed blue screens after clean installs, Windows file checks, and stock settings, it’s time to look at deeper causes. A flaky GPU, a weak power supply, or unstable RAM can all surface as graphics-driver crashes. At that point, logging temps, checking dump timestamps, and testing with a different GPU or PSU can narrow it down fast.