Vanguard Conflict with VT-d/IOMMU Causes DRIVER_VERIFIER_DMA_VIOLATION BSOD and Infinite Reboots
I've been constantly searching for a way to solve this problem, and thank God I saw this group. This means there's a possibility for a solution, especially with community players and engineers who I can discuss the issue with, rather than getting cold replies from support tickets (I submitted a ticket a long time ago and was hoping for some kind of daily response, but unfortunately, that didn't happen; the ticket seems to just submit the problem to Riot's official channels rather than helping me solve it). Besides wanting to solve this problem, I also hope to help other friends who have encountered the same issue—the spirit of the internet!
The problem my computer is facing is:
Vanguard prompts me that I need to initialize the IOMMU (VAN IOMMU: RESTRICTION - An IOMMU restriction has been applied, however a system restart is required to complete initialization).
After that, the situation became uncontrollable. After restarting, my computer couldn't enter the operating system and was stuck in an infinite loop of blue screens. The blue screen error code is (DRIVER_VERIFIER_DMA_VIOLATION).
After troubleshooting time and time again, I found that the problem comes from having VT-d enabled. As long as I disable VT-d, I can get into the system, but because VT-d is disabled, I can't play the game.
But none of this should be happening!
20 Replies
1- The first time this issue occurred was on September 3rd. Before that date, everything was normal. At the same time, that date was not when Vanguard updated its IOMMU detection, as far as I know. This means the problem that appeared on that date was not due to my IOMMU settings, because in the BIOS, my IOMMU was enabled, not disabled as the pop-up error claimed.
2- DRIVER_VERIFIER_DMA_VIOLATION Blue Screen Error: This issue (Vanguard) has caused a system-level problem on my computer. When I enable VT-d, my system will restart endlessly and I cannot get in, except in safe mode. Only by disabling VT-d can I enter the system.
To investigate the cause of this problem, I replaced the hard drive with a new one and reinstalled the operating system (to avoid losing data on the original drive and corruption of log files). This issue (DRIVER_VERIFIER_DMA_VIOLATION blue screen) did not reappear immediately after I reinstalled the OS, but rather after I downloaded and installed Valorant and Vanguard.
Specifically, after reinstalling the OS, this error (DRIVER_VERIFIER_DMA_VIOLATION) would not appear, regardless of whether VT-d was enabled or disabled. The error only started appearing when restarting the computer after I downloaded Vanguard. I have reinstalled the system four times to test this repeatedly (it's five times now), so the problem has been narrowed down very specifically.
I also want to provide the information that my problem is absolutely not a hardware-level driver issue related to the BIOS, graphics card, CPU, etc. I have upgraded the graphics card, BIOS, and CPU drivers all to the latest versions. For the BIOS especially, I have repeatedly installed new versions three times (this was, of course, a pointless action, but I did it just in case).
Last night, I spent four hours reinstalling the system once again and narrowed down the problem even further:
My computer will enter an infinite loop of restarts and blue screens at the exact moment Vanguard shows the following pop-up:
VAN IOMMU: RESTRICTION
An lOMMU restriction has been applied, however a system restart is required to complete initialization
Before this, regardless of any system updates or other factors, I could enable VT-d and enter the system normally. The one and only problem occurs after Vanguard makes changes to my IOMMU settings. And I have to say, this seems to have genuinely caused a hardware-level issue, because my minidump folder doesn't collect any blue screen log files. This means the blue screen is happening before the system can even load to the point of generating a log for it. In other words, the system seems to be getting stuck directly at the hardware level.
Drop your riot id(name and #)
💀
i can‘t, my id not only english, and only english can use in this dc
can i sent in chat to u?
@ItsGamerDoc IOMMU :Clove_Wave:
Dm it to him
Send it to gamerdoc in dms
ok ty
I've sent it, thanks for your help!
i have the same issue and still waiting
@Rachelhi, sry to bother u, he has same issue, and i was sent dms to @ItsGamerDocbut no reply
@momo and do u has any info for that? I'm sory to bother but I have no idea for that... I just wanna play my premier
You’d have to wait for him to be available, riot devs check dc related issues on their free time.
ok thank you very much
you can pass your riot id . and what windwos you are on . have you made any hardware changes ? ?
and Does the box persist even after reboot?
i can't pass my id bc is not in english, and if i open the VT-D, does its coming
hmmm
No hardware modifications have been made, as I said in the article
I replaced the hard drive with a new one and reinstalled the operating system . but you said this
@ItsGamerDoc
https://discord.com/channels/679875946597056683/1417833085310996481 can you look at this . he shared weird ban message 🫡
Hello, have you solved your problem? I have been having this problem for more than ten days.
Hello @秦腔古调 .
I'm facing the same issue.
Has this issue been resolved?
Make post
No, im still waiting da answer from itsgamerdoc