This means FACEIT's kernel driver or the Secure Boot and UEFI changes it needs are causing blue screens or a PC that will not boot. Correcting the boot setup and drivers fixes it. Jump to your situation below or work through the methods in order.
Blue screens naming FACEIT_AC.sys, or a PC that will not boot after enabling Secure Boot or UEFI for FACEIT, come from two things: FACEIT's kernel driver hitting a conflict, or a mismatched boot setup from the requirement changes. The most common boot failure is a UEFI with MBR mismatch: if you switched to UEFI but your system drive is still MBR, Windows will not boot. Convert the drive to GPT with mbr2gpt, then set UEFI and Secure Boot. If the system still will not boot, revert the change (disable Secure Boot), update your BIOS, and try again. For blue screens once Windows is running, treat it as a kernel-driver conflict: update your GPU and chipset drivers, disable any overclock (including XMP or EXPO), and remove old or incompatible anti-cheat software that conflicts with FACEIT's driver, plus add FACEIT to your antivirus exclusions. If a minidump names FACEIT_AC.sys or another driver, that pinpoints the conflict. Because these are boot and driver conflicts rather than a ban, correcting the setup restores stable boots.
Enabling FACEIT's Secure Boot and UEFI requirements can expose a mismatched boot setup, and its kernel driver, FACEIT_AC.sys, can conflict with other drivers. A boot failure is usually a UEFI with MBR mismatch, while an in-Windows blue screen is a driver conflict or an unstable overclock.
Converting the drive to GPT fixes the UEFI mismatch, and reverting Secure Boot plus a BIOS update recovers a system that still will not boot. For blue screens, updating GPU and chipset drivers, disabling overclocks, and removing conflicting anti-cheat software clears the conflict.
“Two different problems wear the same badge here. If the PC will not boot after you turned on UEFI, that is nearly always a UEFI-with-MBR mismatch, so convert the drive to GPT with mbr2gpt. If it still will not come up, back the change out, disable Secure Boot, update the BIOS and try again. The blue screens once Windows is up are a driver conflict, FACEIT_AC.sys bumping into something, so update GPU and chipset drivers, kill any overclock including XMP, and pull any old anti-cheat. A minidump naming the driver seals it.”
mbr2gpt /validate mbr2gpt /convert /allowfullOS
FACEIT_AC.sys blue screens and boot issues come from a mismatched boot setup or a kernel-driver conflict. For a PC that will not boot after enabling UEFI, convert the drive to GPT with mbr2gpt; if it still fails, disable Secure Boot, update the BIOS, and retry. For blue screens in Windows, update GPU and chipset drivers, disable overclocks (XMP or EXPO), remove old anti-cheat, and add FACEIT to antivirus exclusions.
If blue screens continue after a GPT conversion, driver updates and stock clocks, capture the minidump and test your RAM with a memory test, since Memory Integrity and TPM requirements can expose marginal memory. You can also submit your error to us for a tailored fix.
