I/O driver is not responding or not loaded.

[irusanov]

I/O driver is not responding or not loaded.

[rexbinary]

I found my issue. I had installed the game Valorant which installs Riot Vanguard anti-cheat. Vanguard was blocking inpoutx64.sys from loading which I presume is ZenTimings's i/o driver. Uninstalling Riot Vanguard resolved the issue.

[eddie-LA]

I have the same issue...
Any updates on this? :)

Maybe there is a way to circumvent using the inpoutx64.sys driver by replacing it with this WinRing0? It's much newer, still supported and used in the very popular app ThrottleStop.

I have tried and can confirm that ThrottleStop doesn't trigger a response from Vanguard.

Other applications that work are Ryzen Master (although I can see why this shouldn't use that SDK), HWInfo, AIDA64 and Thaiphoon Burner (those 3 show only SPD, the active timings shown are only the main timings, but this is likely by design, rather than inability.)

@irusanov

Ако мога да помогна с тестови билдове, разработка на нов драйвър или нещо друго по ZenTimings, gimme a shout :)
Питам, за да разбера кое е приоритетно или блокиращо.

[irusanov]

Unfortunately, the widely available WinRing driver has the physcial memory functionality flag disabled when it was compiled, so it can't replace the inpoutx64. There are other libs that can be used (some ati ones), but I won't be able to distribute them freely. These drivers need to be digitally signed in order to work in modern OS.

It would be good to find another solution and get rid of this driver.

@eddie-LA The current priority is to find how to read VDDG voltages on Zen4.

[irusanov]

@sanyer Most probably the anti-cheat, it blocks the driver.

[rexbinary]

Debug_Report_27157968.8538381.txt
I am having the same issue here. It was working yesterday so I am trying to backtrack to see what I might have changed or installed. It's a bit tough to track down as this build is just two days old so a lot was done yesterday.

[frostvoid83]

I found my issue. I had installed the game Valorant which installs Riot Vanguard anti-cheat. Vanguard was blocking inpoutx64.sys from loading which I presume is ZenTimings's i/o driver. Uninstalling Riot Vanguard resolved the issue.

Vanguard? I think that's installed in my PC too since I play Valorant but why would it think ZenTimings is a cheating software?

[rexbinary]

From what I understand that driver has been used in cheats before so they just block it regardless of what software installs it or uses it. I read it was a problem also for folks using Corsair's iCUE software as iCUE used that driver to control radiator fans.

[frostvoid83]

This is a pain because Vanguard is needed in order to play Valorant.

[andrei-cb]

Same issue on Windows 11 with memory integrity disabled, vulnerable driver block list disabled, no faceit ac, no valorant ac

[irusanov]

I will have to install Windows 11 latest build to check myself.

• Any specific BIOS options?
• Have you tried with BIOS defaults?
• What board and bios version?

Thanks!

[unr3al1089]

Can't get it to load either, Fresh install of Win 11 / Ryzen 7 5800x / MSI MAG B550 Tomahawk

[irusanov]

@unr3al1089 Ok, that's a board I have, can you tell me which bios is that?

[sanyer]

@irusanov I've had this problem also, but it works now. I'm not sure, though, what exactly is the fix. Is it disabling SVM Mode or uninstalling FACEIT Anti-cheat. I will enable SVM and check again.
I have 5800X3D and MSI B550M Mortar and Win 11.

[msimic]

I have this problem as well.
Windows 11 latest updates.
No anti cheats.
Tried disabling SVM in BIOS.
Trying disabling Core Isolation (which disables vulnerable driver block list as well).

Nothing helps. I think it is just windows that does not like the io driver... which TBH does circumvent the windows driver model.

Never worked on this system. Just installed and updated everything.

[msimic]

I have this problem as well. Windows 11 latest updates. No anti cheats. Tried disabling SVM in BIOS. Trying disabling Core Isolation (which disables vulnerable driver block list as well).

Nothing helps. I think it is just windows that does not like the io driver... which TBH does circumvent the windows driver model.

Never worked on this system. Just installed and updated everything.

Nevermind.
The bug is in ZenTimings.
It cannot start the I/O driver only at first load.
Perhaps it does not wait enough or does something weird.
To fix it: after each reboot start ZenTimings and close it after it errors about the I/O driver, then start again, and it works.

[msimic]

Nevermind. The bug is in ZenTimings. It cannot start the I/O driver only at first load in WIn11. Perhaps it does not wait enough or does something weird. To fix it: after each reboot start ZenTimings and close it after it errors about the I/O driver, then start again, and it works.

@irusanov