IOMMU Is Disabled in FACEIT: How to Enable DMA Protection
If FACEIT says IOMMU is disabled, enable IOMMU in the ASRock BIOS, turn on DMA protection and Memory Integrity, then restart Windows. The steps below show the exact BIOS path for an ASRock AMD motherboard.
FACEIT Anti-Cheat refuses to start with "IOMMU is disabled" or asks you to "please enable DMA protection" when the platform cannot see IOMMU and DMA protection active on your system. On ASRock AMD motherboards the fix is a short trip into the BIOS. The steps below show exactly where the settings live.
Step 1. Enable IOMMU in the BIOS
Head over to the BIOS by restarting your PC and spamming the DEL key on the keyboard.
As soon as you are in the BIOS, make sure you are on the advanced mode (F6). It should look like this.
Then, click on ADVANCED.
Then, AMD CBS.
Then, NBIO Common Options. Find IOMMU and enable it.
Enable the next 2 settings as well.
Then, press F10 and OK to save and reboot.
Step 2. Turn on Memory Integrity in Windows
It's good to make sure to have Memory Integrity on as well. As soon as you are on Windows, open CMD as admin and paste:
reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v Enabled /t REG_DWORD /d 1 /fReboot your system. That's it. FACEIT AC should now start without the IOMMU or DMA protection warning.
Frequently asked questions
Why does FACEIT say IOMMU is disabled?
FACEIT Anti-Cheat checks whether hardware-assisted DMA protection is available. On an ASRock AMD motherboard, IOMMU may need to be enabled manually under AMD CBS and NBIO Common Options in the BIOS.
How do I enable IOMMU for FACEIT on an ASRock motherboard?
Enter Advanced Mode in the BIOS, open Advanced, AMD CBS, then NBIO Common Options, and enable IOMMU and the related DMA-protection settings shown in the guide. Save with F10 and restart.
Does FACEIT also require Memory Integrity?
FACEIT may require Memory Integrity alongside IOMMU and DMA protection. The guide includes the Windows registry command used to enable Hypervisor-Enforced Code Integrity, followed by the required restart.