-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I/O driver is not responding or not loaded. #27
Comments
Debug_Report_27157968.8538381.txt |
Vanguard? I think that's installed in my PC too since I play Valorant but why would it think ZenTimings is a cheating software? |
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. |
This is a pain because Vanguard is needed in order to play Valorant. |
I have the same issue... 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 :) |
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. |
Same issue on Windows 11 with memory integrity disabled, vulnerable driver block list disabled, no faceit ac, no valorant ac |
I will have to install Windows 11 latest build to check myself.
Thanks! |
|
@unr3al1089 Ok, that's a board I have, can you tell me which bios is that? |
@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. |
@sanyer Most probably the anti-cheat, it blocks the driver. |
I have this problem 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. |
|
Valorant is installed on my pc too. I was using it as vanguard tray icon disabled so, I enabled it again and it immediately gave me this notification: I disabled vanguard as it says and deleted the io driver. Then, launched zentimings again and it worked without any error: |
Yes. It was fixed with version 1.2.6 back Aug 15th 2022. This issue should be closed. |
I'm using 1.3.1 and it still happens. And I don't think it can be fixed. Vanguard just blocks it everytime. |
also have the issue on 1.3.1, probably vanguard or faceit ac blocking it (i have both installed) |
can confirm that the bug is related to vanguard |
The issue persists in version 1.32, but I don't blame the developer. |
Confirming issue still exists in 1.35 with Faceit Anti-cheat and also Akros Anti-cheat. |
Every time I try running ZenTimings 1.2.5 and older, it stays on "waiting for power table" and then I get the "I/O driver is not responding or not loaded" error which omits a few sections. If anyone has a fix for this then please let me know because I can't get it to display those omitted sections.
![ZenTimings_Screenshot](https://user-images.githubusercontent.com/88593802/128609799-5ff8b77e-c4b4-452e-9f79-85315b5080fc.png)
The text was updated successfully, but these errors were encountered: