There is no single fix for every Total War: WARHAMMER III crash or freeze. The quickest route is to identify when the failure occurs, then test the likely cause in order: mods, damaged files, overlays, drivers, user configuration, GPU selection, security software, and—only after those checks—a possible game-version regression.
Back up your saves before moving or resetting the game’s user folder. Start with the symptom that matches your problem instead of applying every workaround at once.
As an Amazon Associate I earn from qualifying purchases.
Before troubleshooting
Record your storefront, game version, Windows build, CPU, GPU, RAM, graphics-driver version, and whether mods are installed. Also note whether the issue began after a patch, driver update, mod change, display-setting change, or move to another drive.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →This guide is primarily for Windows PC players. Steam’s listing still shows Windows 7 64-bit as the game’s minimum operating system, but Steam Client support is limited to Windows 10 and later. The published minimum is an Intel i3/Ryzen 3-class processor, 6 GB RAM, GTX 900/RX 400-series or Intel Iris Xe graphics, DirectX 11, and 120 GB of storage. Recommended specifications are Windows 10 64-bit, an Intel i5/Ryzen 5-class processor, 8 GB RAM, a GTX 1660 Ti, RX 5600-XT or Intel Arc A750, DirectX 11, and 120 GB storage. Updates and downloadable content can raise the practical requirements. Check the current Steam requirements.
#1 Best Overall
- Empire Total War Complete Edition
Integrated graphics, limited memory, laptop power-saving modes, and large or heavily modded campaigns can still be unstable even when the minimum specification is met. macOS and Linux users should not apply Windows registry or Windows AppData instructions; use the support path for the platform and storefront you actually run.
First classify the failure
- Won’t launch: the launcher or game never appears.
- Startup crash: the game closes at the splash screen or during loading.
- Battle-loading crash: the campaign works but the game fails when entering a battle.
- Campaign freeze: the game becomes unresponsive during turns or after extended play.
- Whole-PC lockup: Windows, input, and possibly audio stop responding.
- Display problem: black screen, flicker, missing textures, invisible UI, stretched image, or incorrect resolution.
Also ask whether the problem occurs only with a particular save, only with mods, only after a specific patch, or on both a new vanilla campaign and an existing campaign. That distinction is more useful than repeatedly reinstalling the game.
The fastest repair sequence
- Restart Windows and Steam.
- Disable every mod, including manually installed files and external mod managers.
- Verify the game installation through your storefront.
- Disable Steam and third-party overlays.
- Update Windows and the graphics driver, or test the previous driver if the issue began immediately after an update.
- Confirm that a laptop is using its dedicated GPU and is connected to AC power.
- Reset the Warhammer III user folder after backing up saves.
- Test a new vanilla campaign or built-in test scenario.
- Repair the Visual C++ components.
- Check antivirus and firewall interference, then collect logs if the failure remains.
1. Disable mods completely
Mods are a primary troubleshooting variable. Disable all mods in the launcher, unsubscribe from recently installed or updated Workshop mods, and remove manually installed mod files or mod managers from the game directory. A mod that has not been updated for the current game version can prevent the game from functioning.
Then launch a new vanilla campaign. Do not use a save that depends on removed mods until the clean test is complete. If the vanilla game works, re-enable mods in small groups. Test the exact action that previously failed, leaving framework, UI, overhaul, graphics, and script-heavy mods until last. Keep a record of the working combination and game version.
Disabling a mod in the launcher is not always the same as removing files installed outside the Workshop. The Warhammer III support hub contains current mod-removal guidance.
2. Verify the game files
Steam
- Open Steam and select Library.
- Right-click Total War: WARHAMMER III and choose Properties.
- Open Installed Files.
- Select Verify integrity of game files.
- When it finishes, restart Steam and test the game without mods.
Verification repairs damaged or missing installation files, but it does not necessarily remove user-profile data, manually installed mods, or a broken save.
Epic Games Store
Use Epic’s own verification and launcher-cache steps rather than the Steam path. SEGA’s Epic Games troubleshooting guide covers verification, web-cache clearing, driver checks, and externally installed mods.
Recommended Free Tools
Microsoft Store or Xbox App
The repair and reset menus differ from both Steam and Epic. Use the current instructions in SEGA’s Warhammer III support hub instead of guessing the path.
Rank #2
- Games Workshop - Warhammer 40,000: Introductory Set (10 Edition - 2023)
- A great way to begin your journey into the Warhammer 40,000 hobby
- Includes basic rules for the game, plus dice, a gaming mat, reference sheets, and a range ruler
- 16 push-fit models make up two balanced starter forces - Space Marines and Tyranids, plus hobby supplies to build and paint them
3. Reset corrupted preferences and cached user files
A reinstall may leave a damaged configuration untouched because the relevant data is stored in your Windows user profile. SEGA’s default location is:
C:UsersYOURUSERNAMEAppDataRoamingThe Creative Assembly- Close the game and launcher.
- Open the folder above. You may need to enable hidden items in File Explorer.
- Back up the Warhammer3 folder to the desktop or another safe location.
- Preserve your save-related folders before changing anything.
- Move the entire Warhammer III user folder out of the Creative Assembly directory, or rename it rather than deleting it.
- Launch the game so it creates a fresh folder.
- Test a new vanilla campaign before restoring old preferences or mod-related data.
- If the clean profile works, copy back only the required saves—not the entire old folder.
Restoring the complete old folder can reintroduce the corrupted settings or cache that caused the problem. SEGA documents this backup-and-move procedure in its Steam troubleshooting guide.
4. Update or roll back the graphics driver
Install drivers from NVIDIA, AMD, Intel, or your PC manufacturer, then reboot. Do not use third-party driver-updater bundles or download individual DLL files from unofficial sites.
“Newest” is not always the correct answer. If the crash began immediately after a graphics-driver update, testing the previous stable driver is reasonable. On laptops, verify that the game is not being launched on the energy-saving integrated GPU. SEGA’s guide includes manufacturer-specific advice for selecting the high-performance GPU: SEGA troubleshooting.
5. Confirm the correct GPU and power profile
For a laptop test, connect the charger, select a performance-oriented Windows power mode, assign the game executable to the high-performance GPU in Windows Graphics settings, and check the GPU vendor control panel. Reboot before retesting.
On a desktop, check that the display cable is connected to the dedicated graphics card where applicable. A GPU upgrade can help a system below the recommended specification or one relying on integrated graphics, but it will not repair corrupted user data, incompatible mods, security-software interference, or a patch regression.
6. Fix a game that will not launch
Check the Steam branch
If you opted into a beta or old branch, open the game’s Steam Properties, choose Game Versions & Betas, and select Default Public Version unless you specifically need another branch. SEGA also lists administrator launch as a permissions diagnostic. Use it as a temporary test, not as a general performance fix or a permanent requirement.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Repair Visual C++ components
For a Steam installation, look in:
C:Program Files (x86)SteamsteamappscommonSteamworks Shared_CommonRedistvcredistRun the appropriate Microsoft Visual C++ redistributable installers from that directory, restart Windows, and test again. Never replace missing DLLs using random download sites.
Rank #3
- Warhammer 40,000
Test security software safely
Antivirus or firewall software can block a launch. Temporarily test with protection disabled only for a short, controlled interval, preferably while disconnected from untrusted networks. Re-enable it immediately afterward. If it is confirmed as the cause, use a narrowly scoped exclusion for Steam and the game rather than leaving all protection disabled. SEGA covers this diagnostic in its official guide.
7. Fix crashes while loading a battle
Prioritize mods affecting units, effects, battles, or scripts; a fresh user profile; a driver reinstall or rollback; and a test on a new vanilla campaign. A damaged campaign save can fail even when a new campaign works.
Intel integrated-graphics case
Intel documents a specific hang or crash when moving from the campaign map to a battle on systems using only integrated graphics. Its targeted workaround is to increase the Windows graphics timeout:
- Press Win + R, enter
regedit, and press Enter. - Back up the relevant registry key first using Registry Editor’s export function.
- Go to
HKEY_LOCAL_MACHINESystemCurrentControlSetControlGraphicsDrivers - Find a DWORD named
TdrDelay. If it does not exist, create a DWORD (32-bit) Value with that name. - Set its value to
10and ensure the value is interpreted as Decimal. - Restart Windows.
This is an Intel-documented workaround for the integrated-graphics battle-loading scenario—not a universal Warhammer III crash fix. Registry edits can affect Windows stability if entered incorrectly. Do not add unrelated values such as TdrLevel, use arbitrary timeout values, or install registry cleaners. A dedicated GPU may be the more durable solution for demanding campaigns, but do not buy one before isolating files, mods, configuration, and drivers. Read Intel’s support article.
8. Disable overlays and background conflicts
As a controlled test, disable Steam Overlay from the game’s Steam Properties, under General, then relaunch. Also close or disable one variable at a time:
- Discord overlay
- NVIDIA or AMD recording overlays
- Xbox Game Bar
- MSI Afterburner and RivaTuner overlays
- Peripheral-control suites
- Screen-capture software
- Citrix or other remote-work software
- Overclocking and undervolting utilities
These are diagnostic tests, not instructions to leave security or monitoring software disabled permanently.
9. Fix black screens, flickering and incorrect resolution
- Reset the user configuration as described above.
- Start with a conservative graphics preset.
- Try borderless or windowed mode if exclusive fullscreen produces a black screen.
- Temporarily disable HDR and unusual scaling configurations.
- Disconnect secondary monitors for one test.
- Match the game resolution to the primary display’s native resolution.
- Disable overlays and capture tools.
- Update or roll back the graphics driver according to when the problem began.
- Verify files again after removing or changing graphics-related mods.
If the game works with a fresh profile and basic display settings, restore changes one at a time so the conflicting option is identifiable. The configuration reset and driver steps are part of SEGA’s official troubleshooting guidance.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 1110. Diagnose freezing and “Not Responding” errors
A game freeze is different from a crash to desktop, and a whole-PC lockup may indicate a driver or hardware-stability problem. Check Windows Event Viewer:
- Press Win + X.
- Open Event Viewer.
- Go to Windows Logs → Application.
- Inspect entries around the time of the freeze.
Look for AppHangB1, AppHangXProcB1, Event ID 1002, Event ID 1001, display-driver resets, and WHEA hardware errors. Also check CPU and GPU temperatures, remove overclocks or undervolts, and confirm that memory pressure and paging-file space are not extreme.
A Creative Assembly community report describes random full-game freezes with AppHangB1/AppHangXProcB1 and Event IDs 1002/1001, associating the problem with versions 8.0.1/8.0.2 and some Intel 13th- and 14th-generation CPUs. This remains a player report, not a confirmed universal developer diagnosis. See the reported issue.
A game-version regression becomes plausible when the game worked before a particular patch, files are verified, mods are removed, the user profile is reset, drivers and Windows are current, other demanding games are stable, and Event Viewer records an application hang rather than a display-driver reset. In that case, reinstalling Windows or buying a GPU may not help. Record the exact game version and submit the hardware, driver, mod status, Event Viewer details, crash files, and reproduction steps to SEGA.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsDo not confuse a long end-turn calculation in a very large campaign with a crash unless the game remains unresponsive and the evidence supports it.
When reinstalling is justified
Reinstalling is reasonable after you have removed mods, verified files, tested a fresh user profile, checked drivers and overlays, and ruled out security software. It is not a substitute for resetting AppData: reinstalling the game may leave the damaged user configuration in place. Back up saves first, remove externally installed mods, and avoid restoring the entire old configuration immediately after reinstalling.
What to send SEGA support
If the problem persists, provide a concise reproducible report through SEGA Support:
- Storefront and exact game version
- CPU, GPU, RAM, Windows build, and graphics-driver version
- Whether the issue occurs without mods and on a new campaign
- The exact action that triggers the failure
- Event Viewer entries, including event IDs and AppHang names
- DXDIAG information
- Crash-report files requested by support
- Whether the issue began after a patch, driver update, mod change, or display change
A precise report helps distinguish a damaged installation or configuration from a reproducible game-side issue.
Quick Recap
Sources and storefront guidance
- SEGA: Total War troubleshooting for Steam
- SEGA: Total War troubleshooting for Epic Games
- SEGA: Total War: WARHAMMER III support hub
- Steam: published system requirements
- Intel: integrated-graphics battle-loading issue
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
