Runtime error atibtmon.exe: what it is and how to stop it

The dialog reads “Runtime Error! Program: C:\Windows\System32\atibtmon.exe” (the path varies slightly). Atibtmon is a small AMD/ATI utility that adjusts screen brightness when a laptop switches between battery and plugged-in power. On Windows 10 and 11 it frequently crashes — the utility is old, and the operating system moved on without it. The error is annoying, not dangerous.

What atibtmon.exe actually does

It watches power changes and varies display brightness according to AMD's Vari-Bright settings. If it crashes at login, on unplugging the charger, or when brightness changes — that's this known mismatch, not a failing screen and not malware (the genuine file lives in System32 or the AMD driver folder and is signed by AMD).

The fix, in order

  1. Update the AMD graphics driver from AMD's site (or the laptop maker's support page for your model). Newer driver packages replace or retire the utility. Restart and test through a plug/unplug cycle.
  2. Turn off Vari-Bright. Open AMD Software → Settings → Display → disable Vari-Bright. Without the feature, the utility has nothing to do and usually stops launching.
  3. If the error persists, disable atibtmon itself. It is a helper, not a driver — the display works without it:
    1. Open File Explorer to C:\Windows\System32 (on some installs it's in the AMD folder under C:\Program Files).
    2. Find atibtmon.exe, right-click → Rename, and change it to atibtmon.exe.bak (administrator permission required).
    3. Restart. The error is gone; brightness keys and Windows brightness settings still work normally. Renaming — rather than deleting — keeps the change reversible.
  4. Laptop-specific alternative: some makers (Dell, HP, Lenovo) ship their own power utilities that conflict — updating the chipset and power drivers from the maker's page settles those.
Only rename the file in its real location, and only the AMD one. A file named atibtmon.exe in a random folder (Downloads, Temp) is not this utility — leave it alone and run a Microsoft Defender scan instead. And skip any “atibtmon fixer” download; the fix above is the whole job.

If it still happens

If the renamed file reappears after a driver update reinstalled it, that's expected — repeat the Vari-Bright step, since driver packages respect that setting. If brightness itself misbehaves (stuck dim, flickering on battery), that's a separate display-driver issue: reinstall the current AMD driver cleanly using AMD's cleanup utility, then the latest package.

Common questions

Is atibtmon.exe a virus? The genuine AMD file is not. It's a legitimate, signed brightness utility that simply doesn't get along with modern Windows. Files with its name in strange locations are a different story — scan those.

Will disabling it break brightness control? No. Windows' own brightness controls and the keyboard keys keep working. Only AMD's automatic battery/AC brightness switching stops.

Related errors

Visual C++ Runtime Library error · Runtime Error 217 · Runtime Error 216