Gamers launching EA titles on Windows 11 are increasingly hitting a hard stop: an “EA AntiCheat has detected an incompatible driver” message that bars the game from starting. The popup may name a driver file like gdrv.sys, mhyprot2.sys, or glckio2.sys, or it may just refuse to load with no further explanation. After digging through official EA guidance, Microsoft’s kernel-mode documentation, and thousands of community reports, one thing becomes clear: the fix is rarely a single magic setting, but a structured cleanup that avoids permanently weakening Windows’ defenses.

EA’s anti-cheat (EAAC, often called EAC or Javelin) operates at the kernel level to intercept cheats before they touch the game. When it encounters a driver that is unsigned, outdated, deny-listed, or incompatible with modern kernel mitigations like Hypervisor-protected Code Integrity (HVCI), it slams the door. The block is deliberate, not a bug. But the collateral damage hits gamers running perfectly legitimate hardware utilities—RGB controllers, monitoring tools, or even leftover anti-cheat remnants from other titles—that install low-level kernel-mode drivers for features that have nothing to do with cheating.

The Three Root Causes Behind Every ‘Incompatible Driver’ Error

EA AntiCheat flags drivers for three broad reasons, and each demands a different fix path.

  1. Third-party kernel drivers from system utilities. Apps like Gigabyte’s RGB Fusion, MSI Afterburner, HWiNFO, and EVGA Precision install kernel components (gdrv.sys, glckio2.sys, hwinfo64a.sys) that hook into the OS at the same low level cheats would use. EA’s denylist includes many of these by name.
  2. Unsigned or non-WHQL drivers. A driver that lacks a valid digital signature from a trusted certificate authority—either because it’s a leftover from an old anti-cheat install, a homebrew tool, or simply an out-of-date vendor driver—will fail signature checks that EAAC enforces.
  3. Windows security settings that clash with the driver. Features like Memory Integrity (HVCI), Test Mode (TESTSIGNING), or Secure Boot policies can prevent a kernel driver from loading at all, even if the driver itself is benign.

Microsoft’s own documentation on test-signed code loading spells out that Test Mode allows unsigned drivers to load, but it also disables critical signature checks that anti-cheat relies on. Enabling Test Mode is a death sentence for EAAC compatibility—and for your system’s security posture. The moment the desktop shows the test mode watermark, EAAC will refuse to run.

Start Here: The Fastest Path to Diagnosis

Before you touch any settings, gather evidence. Every fix hinges on identifying the exact driver EAAC is upset about.

1. Note the Popup’s Driver Name

The error often cites a filename. Copy it exactly. Common offenders:
- gdrv.sys – Gigabyte App Center / RGB Fusion
- glckio2.sys – Another Gigabyte RGB driver variant
- mhyprot2.sys – HoYoverse anti-cheat remnant (Genshin Impact)
- hwinfo64a.sys – HWiNFO monitoring driver
- Anything from MSI Afterburner or RivaTuner overlay

If the popup is blank, open Event Viewer (Win+X → Event Viewer) → Windows Logs → System. Filter for errors around the time of the launch. You’ll often find a driver load failure logged there with the exact filename.

2. Cross-Check Against the EA Denylist

EA’s support articles explicitly call out RGB tools, overclocking utilities, and kernel-level monitoring software. If your driver appears on that list, uninstalling the parent application is the first—and usually last—step.

Step-by-Step Fix Order (From Safest to Most Invasive)

Follow these steps sequentially. Each one is designed to fix the most common cases without sacrificing security or stability.

1. Uninstall Known Culprit Utilities

Open appwiz.cpl and get rid of:
- Gigabyte App Center / RGB Fusion / Xtreme Engine
- MSI Afterburner + RivaTuner Statistics Server
- HWiNFO (if it installs a kernel driver)
- EVGA Precision, Galaxy RGB tools
- Voicemod, Process Explorer (use Autoruns to disable kernel hooks if needed)
- Any OEM GPU overlay or “game boost” app

Reboot and test. This alone clears roughly 60% of community-reported blocks.

2. Clean Up GPU and Chipset Drivers

An outdated or mismatched GPU driver frequently trips EAAC’s integrity checks. Use Display Driver Uninstaller (DDU) in Safe Mode to purge all remnants, then install the latest WHQL-certified driver from NVIDIA, AMD, or Intel. Do the same for chipset and network drivers obtained directly from your motherboard or laptop vendor. Never download drivers from aggregator sites.

Windows Update occasionally overwrites a clean vendor driver with an older version. Use the ExcludeWUDriversInQualityUpdate registry key (carefully) or Group Policy to block automatic driver pushes while you troubleshoot. Re-enable updates once the issue is resolved.

3. Reinstall EA AntiCheat Completely

Navigate to the game’s installation folder (e.g., C:\Program Files\EA\AC or inside the game directory) and run EAAntiCheat.Installer.exe as Administrator. Uninstall the anti-cheat for your title, then reinstall it. This rebuilds the local configuration and fixes many driver validation failures. If the installer is missing, verify game files via the launcher or download the EAAC installer package from the publisher’s support page.

4. Disable Windows Test Mode (if Active)

Open an elevated Command Prompt and run:

bcdedit /set TESTSIGNING OFF
bcdedit /deletevalue TESTSIGNING   # if the set command fails

Reboot. Test Mode must be off. Any “Test Mode” watermark in the desktop corner means certain anti-cheat services will refuse to start. Microsoft’s TESTSIGNING documentation warns that this setting is incompatible with Secure Boot, and on newer Windows builds it may be impossible to enable without also disabling Secure Boot—if you see the “value is protected by Secure Boot policy” message, you’ll need to enter the UEFI/BIOS and temporarily turn off Secure Boot to toggle Test Mode. This is for diagnostics only; re-enable Secure Boot and leave Test Mode off permanently.

5. Run EAAC and the Game with Admin Rights

Right-click both EAAntiCheat.Installer.exe and the game’s executable → Properties → Compatibility → check “Run this program as an administrator.” Some permission-restricted environments block EAAC’s kernel communication.

6. Repair Windows System Files

From an elevated Command Prompt:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Reboot. Corrupted system files can cause driver load failures; SFC and DISM are the standard first-aid.

Advanced Diagnostic Arsenal for Persistent Blocks

If the simple steps fail, you’ll need to peer deeper into the kernel.

Hunt Down Hidden Drivers with Driverquery and Autoruns

Export the loaded driver list:

driverquery /v /fo list > %USERPROFILE%\Desktop\drivers.txt

Open drivers.txt and scan for non-Microsoft drivers. Then launch Sysinternals Autoruns and examine the “Drivers” tab. Disable suspicious entries one at a time, rebooting between tests. Look for remnants of old anti-cheats (e.g., mhyprot2.sys from Genshin Impact) or vendor utilities you thought you’d removed. Only delete a driver file manually from C:\Windows\System32\drivers after you have uninstalled the owning application and confirmed the driver is no longer in use. Create a system restore point first.

Check Memory Integrity (Hypervisor-protected Code Integrity)

Windows 11’s Memory Integrity feature uses virtualization to enforce that only signed, trusted kernel-code runs. If a driver isn’t compatible, enabling Memory Integrity can block it silently—but EAAC may interpret the block as a threat. Open Windows Security → Device Security → Core isolation details. If Memory Integrity is on, toggle it off temporarily, reboot, and test. Do not leave it off. If the game now works, the incompatible driver needs an updated, signed version from its vendor.

Microsoft’s test-signing guide clarifies that starting with Windows 10 version 1507, test-signed drivers must be explicitly signed with a test certificate when HVCI is active—an unsigned driver won’t load. EAAC registers this as a violation.

Secure Boot Interactions

Test Mode and Secure Boot work like a seesaw. If you’re seeing “value is protected by Secure Boot policy” when running bcdedit, Secure Boot is preventing the change. To toggle Test Mode, you must first disable Secure Boot in the UEFI firmware, make the change, reboot, and then re-enable Secure Boot. BitLocker may also force recovery key entry during this process. Document every step.

The Trade-Off: Security vs. Convenience

EA’s strict kernel-level checks are a double-edged sword. They genuinely raise the bar for cheat developers by denying them easy kernel access vectors. But they also penalize enthusiasts who use legitimate hardware control software. Disabling Memory Integrity or leaving Test Mode on is not a solution—it’s a security downgrade that opens the door to rootkits and advanced malware. Microsoft’s own guidance explicitly states that Test Mode should only be used for development.

The better path: push hardware vendors to release HVCI-compatible, WHQL-signed drivers, and vote with your wallet by choosing peripherals that don’t require kernel-level background processes. For the here and now, follow the structured cleanup order above before dialing down protections.

When All Else Fails: Escalation Kit

Collect these artifacts and contact EA Help:
- The exact driver filename from the popup or Event Viewer.
- EAAntiCheat.Log from the game installation directory.
- The drivers.txt export from driverquery.
- DxDiag output or your full hardware/software list.

EA’s support can cross-reference denylist entries and sometimes whitelist a specific driver version or provide a one-off fix. In stubborn cases, the game’s publisher (not EA) may need to coordinate with the anti-cheat vendor.

Prevention Instead of Panic

  • Keep drivers current, but stick to WHQL releases. Auto-update tools from GPU vendors are fine; shady driver updater utilities are not.
  • Skip kernel-level tweaking tools when playing EAC-protected games. RGB control panels often work in user-mode if you close the background service; check your motherboard’s UEFI for hardware-level RGB controls instead.
  • Never enable Test Mode for routine use. If a tutorial tells you to run bcdedit /set testsigning on to fix a game, close that browser tab.
  • Make a habit of exporting your driver list (driverquery /v) before installing new hardware utilities. It makes removing them later trivial.

EA AntiCheat’s driver checks aren’t going away, and as Windows 11 tightens kernel security with every feature update, more legacy utilities will break. The smart gamer’s playbook is clear: whittle down your kernel-mode footprint, keep signed drivers current, and leave Windows’ security features intact. The game will launch—and your system will stay safer for it.