I have an ASUS PRIME B760-PLUS D4 system with an Intel Core i7-14700KF. Valorant's Vanguard requires VT-d/IOMMU to be enabled, but turning it on in the BIOS causes Windows to crash during startup. Depending on the configuration, I see either DRIVER_VERIFIER_DMA_VIOLATION or INACCESSIBLE_BOOT_DEVICE. With VT-d disabled, Windows boots immediately and the system works normally in other games.
I have already tried reinstalling Windows, updating BIOS and drivers, and using Intel's Default settings for the processor. The Intel Default profile did not resolve the problem and prevented manual voltage or power adjustments. Intel's diagnostic tool also reported that the processor passed. There are no minidump files because the crashes occur very early in the boot process.
Has anyone encountered this combination of ASUS B760, a 14th-generation Intel CPU, and VT-d? Could a BIOS option, storage/chipset driver, or Windows configuration fix the conflict, or is this more likely a hardware stability problem requiring an RMA?
3 Answers
The 13th- and 14th-generation desktop Intel CPUs have a well-documented history of instability, and some games require dedicated troubleshooting guidance for them. Passing a basic diagnostic does not necessarily rule out intermittent degradation. I would update to the newest BIOS, load Intel’s recommended default profile, and test at completely stock settings. If VT-d still triggers crashes while the machine is stable with it disabled, an Intel warranty replacement may be the most practical next step.
If Windows can stay running long enough, crash dumps from C:WindowsMinidump could help identify whether a storage or chipset driver is involved. Since these failures happen immediately during boot and the system has been reformatted several times, an empty folder is understandable. In that case, test with the latest motherboard BIOS, Intel chipset and storage drivers, and a minimal hardware configuration. Also verify that the boot drive is detected consistently with VT-d enabled.
The fact that disabling VT-d makes the computer completely stable points toward an interaction with firmware, DMA protection, or hardware rather than Vanguard itself. There usually is not a registry tweak that safely bypasses this requirement. Try clearing CMOS and reconfiguring UEFI settings from scratch, using UEFI boot with the current storage-controller mode, and removing unnecessary PCIe or USB devices. If the issue remains on a clean Windows installation at Intel defaults, test another boot drive or CPU if possible; otherwise, pursue a board or processor warranty claim.
I tried the Intel Default profile, but VT-d still caused the same early-boot crashes even with the processor locked to Intel’s stock limits. I’m hoping there is another firmware or driver setting to test before starting an RMA.