Here’s the counterintuitive truth: your game isn’t crashing because of a corrupted file, an outdated driver, or bad RAM. It’s crashing because a single CPU instruction set—Advanced Encryption Standard New Instructions (AES-NI)—is turned off in your BIOS. And toggling it on takes 90 seconds. No reinstalls. No Windows reinstall. No third‑party tools. Just one setting hidden inside a menu most gamers never open.
Let’s reframe the entire troubleshooting process. Before you spend an hour verifying files, wiping shader caches, or arguing with anti‑cheat errors, check this one thing. If it’s off, turning it on fixes the majority of WARDOGS startup crashes, random desktop crashes, and even hard system restarts. The fix is free, safe, and permanent.
Why AES-NI Matters for WARDOGS
WARDOGS runs on Unreal Engine 5. The Easy Anti‑Cheat (EAC) layer inside the game relies on hardware‑level AES‑NI instructions to verify that your executable hasn’t been tampered with. When AES‑NI is disabled in BIOS, every attempt to launch the game triggers a conflict. The result? A crash before the main menu appears, often with no error message—or worse, a blue screen of death (BSOD) with SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDcodecodecodecode.
Many motherboards ship with AES‑NI enabled. But a surprising number of pre‑built PCs, especially from smaller system integrators, ship with it disabled. If you ever ran an overclocking utility, reset BIOS to “safe defaults,” or updated your BIOS, you may have accidentally flipped this switch off without knowing. And because AES‑NI is rarely listed in Windows‑side performance tools, players waste hours chasing the wrong root cause.
The fix doesn’t require any technical expertise. You just need to know where to look and what key to press.
Step 1: Enter Your BIOS
Shut down your PC completely. Turn it back on, and as soon as the screen lights up, repeatedly tap the Deletecodecodecodecode or F2codecodecodecode key—sometimes F1codecodecodecode or F10codecodecodecode on older boards. The system will boot into the BIOS/UEFI interface instead of Windows.
If you miss it: Don’t panic. Restart and try again. Most modern boards show a brief splash screen telling you which key to press. If yours doesn’t, consult your motherboard manual or manufacturer website.
Expected outcome: You see a menu with tabs like Main, Advanced, Boot, or Tweaker. If it looks simplified (Easy Mode), switch to Advanced Mode by pressing F7codecodecodecode (ASUS, MSI, ASRock) or F2codecodecodecode (Gigabyte). That’s where AES‑NI lives.
Step 2: Locate the AES‑NI Setting by Brand
The exact path varies by motherboard manufacturer. Use the table below to find your board’s entry.
| Motherboard Brand | BIOS Path to AES‑NI | Key to Press |
|---|---|---|
| ASUS | Advanced → CPU Configuration → Intel AES‑NI (or AMD AES‑NI) → Enabled | F7codecodecodecode for Advanced Mode |
| MSI | OC (Overclocking Settings) / Advanced → CPU Features → CPU AES Instruction (or AES‑NI) → Enabled | F7codecodecodecode for Advanced Mode |
| Gigabyte / AORUS | Tweaker (or MIT) → Advanced CPU Settings → Advanced CPU Core Settings → AES‑NI → Enabled | F2codecodecodecode for Advanced Mode |
| ASRock | Advanced → CPU Configuration → AES‑NI Support → Enabled | F7codecodecodecode for Advanced Mode |
If you don’t see any of these labels, search for “AES‑NI,” “CPU AES,” or simply “AES” inside the Advanced menu. Some boards, especially laptops, hide the setting under “Intel Advanced Menu” or “Security.” If you cannot find it at all, your motherboard likely has AES‑NI permanently enabled—skip to Step 4.
Step 3: Enable and Save
Once you locate AES‑NI, toggle it to Enabled. Press F10codecodecodecode (the universal save‑and‑exit hotkey). Confirm the change by selecting Yes or pressing Enter. Your PC will reboot automatically.
Expected outcome: Windows loads normally. WARDOGS should now launch without crashing. If it still crashes, move to the verification steps below.
Step 4: Verify AES‑NI Is Active
You can check inside Windows that the instruction set is working correctly.
- Press
Windows + Rcodecodecodecode, typemsinfo32codecodecodecode, and press Enter. - In System Information, look for Processor. It will list your CPU model.
- Download a free tool like CPU‑Z or HWiNFO64. Under the CPU tab, check that “Instructions” includes “AES.” If it does, AES‑NI is enabled and visible.
If WARDOGS still crashes after enabling AES‑NI, your issue lies elsewhere. But for the vast majority of players who hit startup crashes or BSODs with error codes like KMODE_EXCEPTION_NOT_HANDLEDcodecodecodecode, this single toggle resolves it.
Why This Works When Everything Else Fails
Most crash guides ask you to update drivers, verify files, or run Windows SFC scans. Those fixes address surface‑level file corruption or software conflicts. AES‑NI operates at the hardware‑instruction level—below the OS, below the game, below every overlay and service. When it’s missing, no amount of driver reinstalls will compensate. The anti‑cheat simply refuses to trust the CPU.
WARDOGS’ Easy Anti‑Cheat is particularly sensitive to this. Other UE5 titles (The Finals, for example) had the same requirement. The kernel‑level AC needs a deterministic path to execute cryptographic抯 checks. Without AES‑NI, that path breaks, and the AC kills the process.
One More Thing: BSOD After Enabling AES‑NI
If you enable AES‑NI and still get a blue screen—especially with the error SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDcodecodecodecode—the culprit is usually a conflicting kernel‑level driver, not the BIOS setting itself. Check your Windows Event Viewer (Windows logs → System) right after a crash. Look for a red exclamation mark. If it points to a file named inpoutx64.syscodecodecodecode, that’s an RGB‑lighting driver from software like SignalRGB, OpenRGB, or a fan/motherboard utility.
Disabling that driver via command prompt fixes the crashes without removing your lighting software forever. Open an elevated command prompt (run as administrator) and run:
“`
sc stop inpoutx64
sc config inpoutx64 start=disabled
“`
Restart your PC. WARDOGS should now run stable. This is a known conflict introduced by a Windows security update in August 2024, and it affects multiple UE5 games. Enabling AES‑NI and disabling this one driver together produce a crash‑free experience even on high‑end rigs.
The beauty of this two‑step fix is that it touches only hardware‑level or system‑level settings. It doesn’t alter any game files, Windows performance, or personal configurations. If you ever need to revert, just re‑enable the driver and disable AES‑NI in BIOS. No harm done.
Most WARDOGS players will never need this. But for the unlucky few whose boards shipped with AES‑NI off, or who toggled it accidentally, this is the fastest and most definitive solution. Try it before you refund.
