AoE4 Crashes | Fix Dx12 Driver And Mod Conflicts

Guide / By

Most aoe4 crashes trace back to drivers, overlays, or damaged files, so update the GPU driver, verify files, and disable overlays first.

A crash in Age of Empires IV feels random, but it usually is not. The game drops when something it relies on fails under load. That could be the GPU driver timing out, a file that will not read, an overlay injecting into graphics, or a Windows feature that clashes with your setup.

This guide is built for the moment you just crashed and want the fastest path back into a match. Start with the quick checks, then move down the list. Change one thing, test again, then keep the change only if it proves itself across a full session.

What To Do In The First Five Minutes

Before you start changing deep settings, grab an easy win. These steps fix a big share of crash loops without touching your saves, your mods folder, or your Windows install.

Also check the simple stuff that gets missed. Reboot the PC, then launch the game once with no other game running. If you use a second monitor, unplug it for one test. If you run antivirus scanning on the game folder, add an exception for AoE4 during your next match.

Quick Triage Table

Crash Moment Likely Trigger First Move
Before intro video DX12 or driver mismatch Update GPU driver, check DX12
Main menu Overlay or bad config Disable overlays, reset config
Loading a match Damaged files or mod clash Verify files, disable mods
Mid-match Driver timeout, heat, VRAM Cap FPS, drop shadows

Do These Three Steps First

  1. Restart The Game And Steam — Close the game, exit Steam from the tray, then reopen Steam and relaunch.
  2. Disable Overlays — Turn off Steam overlay and Discord overlay for one test run so nothing hooks into graphics.
  3. Verify Game Files — Run Steam’s built-in file check to replace missing or damaged files.

If you want the official step list for Steam file repair, Steam documents the verify process in its help article. If you see a spike in crashes right after a patch, the Age of Empires IV Known Issues page can confirm whether a widespread bug is active. It was updated on December 8, 2025. Steam File Verification Steps and Age Of Empires IV Known Issues.

AoE4 Crashes On Launch Or Loading Screen

Launch crashes feel brutal because you cannot even reach settings. The upside is that the fix list is shorter. The official Age of Empires article for crashing before the intro video calls out DirectX 12 and GPU compatibility as a top checkpoint. Crash Before Intro Video Checklist.

Confirm DirectX 12 Is Available

  1. Run Dxdiag — Press the Windows logo, type dxdiag, open it, then read the DirectX Version line.
  2. Update Windows — Install pending Windows updates, then restart once so graphics components reload.
  3. Check Your GPU — If your GPU does not meet DirectX 12 needs, the game can crash at the grey screen stage.

Repair Files And Remove Mod Variables

A reinstall can still leave a bad file in place if the installer pulls from a cached source. A verify step forces a clean comparison against what the game expects.

  1. Run Steam Verification — In Steam, open Properties, Installed Files, then click Verify integrity of game files.
  2. Turn Off Mods — Disable all mods, launch once, then add mods back one at a time after stability returns.
  3. Clear Cached Downloads — In Steam settings, clear download cache, then sign back in and retry.

Reset The Game Config Safely

If the game reaches the menu and then drops, the config and shader cache are common suspects. A reset gives you a clean baseline without a full reinstall.

  • Back Up The Settings Folder — Copy the Age of Empires IV settings folder to your desktop first.
  • Remove The Graphics Config — Delete the graphics config files so the game rebuilds them on the next launch.
  • Start With Default Settings — Launch, load a skirmish, then change one setting at a time.

Fix Crashes That Happen Mid-Match

Crashes that happen ten minutes into a match often point to stability under load. Big fights raise draw calls, VRAM use, and CPU spikes. If a driver or an overclock is on the edge, this is when it fails.

Cap Frame Rate And Reduce Spike Load

  1. Set A Frame Cap — Try 60 or 90 FPS. A cap smooths spikes that can trigger a driver reset.
  2. Lower Shadows One Step — Shadows are a common stress point. Drop them first, then test again.
  3. Reduce Effects In Big Battles — Lower effects quality and reflections if you crash during large fights.

Remove Overlay And Capture Hooks

Overlays are a repeat crash trigger because they inject into the render path. They can be stable in one game and unstable in another after a patch or driver change.

  • Disable Steam Overlay — Turn it off for Age of Empires IV, then test a full match.
  • Disable Discord Overlay — Switch it off, then retry ranked or a custom lobby.
  • Pause Background Recording — Turn off Xbox Game Bar recording and GPU app capture for one test run.

Return CPU And GPU To Stock Clocks

Even a mild overclock can be fine in short tests, then fail in long sessions. Resetting to stock is a clean way to rule it out fast.

  1. Reset GPU Tuning — In your GPU app, return core and memory clocks to default.
  2. Reset CPU Overclock — In BIOS or your tuning app, return the CPU to default settings.
  3. Test For One Hour — Run a skirmish with bots for a long session and watch for a crash.

Multiplayer And Lobby Crashes

If you can play skirmish fine but crash in a lobby, treat it like a service or network fault until it is ruled out. Age of Empires IV uses Microsoft account services for multiplayer flows even when you launch the game from Steam.

Refresh Sign-In And Gaming Services

  • Sign Out And Back In — Log out of the Xbox app, then log in again before you queue.
  • Repair Gaming Services — In Windows Apps settings, select Gaming Services, then run Repair and Reset.
  • Test A Short Custom Match — Play a quick match with a friend before you run ranked.

Reduce Connection Jitter

RTS netcode is sensitive to spikes. A bad drop at the wrong time can desync, freeze, then crash. A simple cleanup can steady the line.

  1. Use Ethernet — A cable removes Wi-Fi interference and random drops.
  2. Pause Downloads — Stop Steam downloads and cloud sync while you play.
  3. Restart Your Router — Power cycle it, wait one minute, then retry the lobby.

Check For Patch-Related Crash Clusters

Sometimes the crash is not on your side. When a patch ships, a bug can hit a chunk of players at once. The Known Issues page is the fastest official cross-check when crashes spike after an update.

  • Read The Latest Known Issues Entry — Check for notes tied to your crash pattern and platform.
  • Test After A Hotfix — If a hotfix lands, run the game with mods off first.
  • Keep A Simple Log — Write the date, patch number, and crash moment so you can spot patterns.

Windows Settings That Can Trigger Game Crashes

Windows 11 adds graphics toggles that can help some PCs and hurt others. Hardware-accelerated GPU scheduling is a common one tied to game instability in some setups. Microsoft Answers threads often point to switching it off when games crash often. Windows 11 Crash Thread With HAGS Steps.

Disable Hardware-Accelerated GPU Scheduling

  1. Open Graphics Settings — Go to Settings, System, Display, then Graphics.
  2. Open Default Settings — Click Default graphics settings.
  3. Switch Off HAGS — Turn off Hardware-accelerated GPU scheduling, then restart.

Turn Off Fullscreen Optimizations For The Game

Fullscreen optimizations can cause odd behavior with some games, drivers, and overlays. Turning it off for one test run is quick and reversible.

  1. Open The Game Folder — In Steam, use Browse to open the installed files folder.
  2. Open Compatibility Settings — Right-click the game exe, open Properties, then Compatibility.
  3. Disable Fullscreen Optimizations — Check the box, apply, then test a match.

Give The Game A Clean Power Profile

Laptop power saving can starve the GPU during spikes. Desktop power plans can also throttle in odd ways. A stable plan helps with long sessions.

  • Set A High Performance Plan — In Windows Power settings, pick a plan that favors performance.
  • Plug In Laptops — Run the game on AC power, not battery, during testing.
  • Close Battery Tools — Exit third-party battery managers while you test.

A Clean Routine That Keeps The Game Stable

Once you stop the crash loop, keep the setup steady. That does not mean never updating. It means making updates in a controlled way, then testing before you stack more changes.

After Every Big Patch Or Driver Update

  1. Verify Files Once — Run Steam verification after a large patch to catch partial updates.
  2. Launch With Mods Off — Run one match without mods first, then re-enable mods one at a time.
  3. Test One Full Session — Play for an hour before you add new overlays or capture tools back in.

If You Still Get A Crash After All Fixes

At this stage, stop changing random switches. Grab a small clue from Windows, then match it to a fix. This saves time and prevents new problems.

  • Check Reliability Monitor — Search for Reliability Monitor, then check the crash timestamp for reliccardinal.exe or a driver reset.
  • Check Event Viewer — Open Windows Logs, Application, then find the error that matches the crash time.
  • Search The Exact Error Text — Use the module name or error code to find a targeted fix tied to that component.

Keep A Simple Do-Not-Stack Rule

If you change five things at once, you never learn what worked. That is how aoe4 crashes come back and waste your time later. Make one change, test one match, then move on.

If you want a reliable set of reference pages, stick to these three. The Known Issues page for patch-related problems, the official launch crash checklist for DirectX and startup failures, and Steam’s file verify steps for damaged files. They are short, concrete, and updated when issues shift. Known Issues Page, Launch Crash Checklist, Steam Verify Steps.