[NVIDIA API intermittent issue] No NVIDIA driver was found for your system configuration / API returning Studio drivers when GRD is chosen
ksbrar opened this issue · comments
Moving discussion from the other issue here.
--
Hey Guys, is this the same issue? I recently updated my game ready drivers through nvidia (through the standard installer), but now Tiny thinks I don't have an nvidia driver after restart? I also tried reinstalling the same driver as a 'Clean Install' option in the nvidia installer...still no luck unfortunately.
Originally posted by @LukeDuring in #163 (comment)
Super weird as the NVIDIA API returns found driver. This is not the first time this is happening I am starting to suspect my code possibly breaking..?
Here is something strange....When i got back from work today and turned my pc on... it started working perfectly again. I have done nothing to the pc since my last post, it just randomly started working again haha
When it originally wasn't working, I restarted several times after the nvidia update to try and get it to work....no luck..... i always fully shut down my pc as it is my gaming rig, so it never stays on for no reason.
But today its working....so thats a win haha
@LukeDuring I just tried again and its working for me as well 😅 . So @ElPumpo perhaps it was just an intermittent failure for a few days?
FWIW this is still not working for me. I'm running the latest release on Windows 11.
So to recap quick as I previously said this is not a new issue in any way. I have seen reports from 2023-02-11 #169, #167
The bug report at #169 shows this issue and how it lies in NVIDIAs end. The author of the bug report had opened the NVIDIA AJAX API on their web browser and got success 0 response. But hours later when I opened the link he shared I got success 1.
This proves that this is on NVIDIAs API intermediately not working
I cannot do much about it. Unless I move away from it but I just started using it lol.. I will keep this bug report open for people who get this error.
The solution for now is to just wait some time til NVIDIA API gives the correct response.
1.16.4 worked for me on latest win10 today
Still happening? Have not heared anything in a while..
Still happening? Have not heared anything in a while..
Hey Mate, Its working perfectly again for me 👍🏻 Thank you for any fix you applied !
@ElPumpo It happened to me last week for 1 day. After that it started working again without issues.
Okay good then i will keep the bug report open for now
Any news on this intermittent issue? Perhaps it's time for a close?
I haven't seen it since my original report.
I can confirm that there are sometimes outages until today. I reported this in february. I can remember around 4 -5 days where i got this error again. The next pc boot on the next day and the tool worked again.
I have tracked the bug to Windows 11. The issue is can be tracked to os-data.json which has the following:
{ "id": "56", "code": "10.0", "name": "Windows 10 32-bit" }, { "id": "57", "code": "10.0", "name": "Windows 10 64-bit" }, { "id": "135", "code": "10.0", "name": "Windows 11" },
This has interaction with this line of code in OS identifying loop (match code and name contains architecture) that causes it to be misidentified as Windows 10 64-bit. Windows 11 does not have an x86 version.
I believe the common practice fix is to also check build number, >=22000 should be Windows 11
#184 edit: made a pull request
Hi Jessie.
How can you confirm that you have tracked this bug to Windows 11? For me it makes no sense. As we already discussed the NVIDIA API gives out faulty responses, at random.
What osID you have should not make a difference. And even if it does then how would your solution magically fix it for Windows 10 users?
Furthermore there is currently no difference between parsing osID for Windows 10 or 11, as they are the same drivers. At least for RTX>X cards.
For the record I am Windows 11 with a GTX 970.
gpuId: 756
osId: 57
isDchDriver: 1
I got this issue after I upgraded to Windows 11. I investigated that the ajax call being made is:
https://gfwsl.geforce.com/services_toolkit/services/com/nvidia/services/AjaxDriverService.php?func=DriverManualLookup&pfid=756&osID=57&dch=1
Notice that osID=57 is corresponding to Windows 10 64-bit. As of now, this fails. Replacing with osID=135 for Windows 11 will give a successful ajax call for "v536.23"
Now, another modification you can make to get a successful ajax call is to remove dch=1 and you will get a "success" but it will give you a completely different driver, "v472.12". My suspicion is that Nvidia is focusing more on DCH drivers due to Microsoft's requirements, and is dropping off support for legacy/standard drivers, especially for older graphics cards like mine.
Now for what is causing this issue for Windows 10 users, I have no idea, I agree with you it is probably Nvidia's API being a few days behind. However the OP's screenshot appears to be a Windows 11 terminal. Their debug output shows osId 57.
That is super strange I will continue to investigate this further.
Perhaps they changed the Windows 10 OS ID? Perhaps it's not 57 anymore..
Yes DCH drivers are discontinued since long time ago now. It will give you a very old driver. My code attempts to lookup DCH driver if your system currently is not on one. So it searches for true and false and compares which one is the latest.
Two hours later the same URL you sent works again. Super strange but it's NVIDIA
Perhaps they changed the Windows 10 OS ID? Perhaps it's not 57 anymore
Windows 10's ID is still 57. I have a script that periodically updates the nvidia-data repo if there are any. Though I noticed there's no 4060 yet which is maybe weird.
The URL jesseclvrt provided seems to show the correct driver at the time I'm writing this (as ElPumpo stated above). Windows 10 and 11 shouldn't have different driver versions available (at least not yet).
Will have more time to investigate this over the weekend; life and work is quite busy for me right now. Improving the OS identification code is a good thing to do for the time being but as you said it won't fix the issue for Windows 10 users if it comes up again.
i updated my drivers approx 2 weeks ago, no problems (running windows 11). used the update checker again today and i can confirm that the error ("No NVIDIA driver...") is still there.
I have exact same behavior and pinned it down to 1.17.0 update. Running both side by side gives me success on 1.16 and following on latest version:
TinyNvidiaUpdateChecker v1.17.0
Verifying internet connection . . . OK!
Searching for Updates . . . OK!
Retrieving GPU information . . . ERROR!
No NVIDIA driver was found for your system configuration.
Debugging information:
gpuId: 995
osId: 135
isDchDriver: 1
driverType: grd
It seems that it has gotten worse since v1.17.0 when using as it now uses the &upCRD= parameter to choose GRD/SD driver.. but reverting this change is not a good idea people will get studio drivers if they are more up to date.
I would have to get latest 10 drivers and filter grd/sd...
Hello @ElPumpo
I'm also having the same issue. It was working when I first set it up which I hadn't changed my drivers, today 1/17/24 I noticed that there are new drivers. I have the checker run on startup with command line but it doesn't error on "no Nvidia Driver was found" and completes the check. I just installed the newest drivers from today and still the checker things I don't have any installed.
Debugging information:
gpuId: 995 (4090)
osId: 135 (Windows 11 22H2 build 22621.3007)
isDchDriver: 1
driverType: grd
Program gets an error retrieving GPU information - hopefully this can be resolved by the time the card gets newer drivers.
gpuName: GeForce RTX 4070 Ti SUPER
isNotebook: False
Should be fixed now; my automation for updating the data repo broke again...
@Dramion82 this issue report is for the intermittent issue we're facing with the NVIDIA API. Do you still have a problem with this? If so open a seperate bug report, thanks.
@Dramion82 this issue report is for the intermittent issue we're facing with the NVIDIA API. Do you still have a problem with this? If so open a seperate bug report, thanks.
Hi @ElPumpo , It started working a few weeks ago. I didn't do anything to resolve it, it automagically fixed itself.
Update 2024: I think the solution is to query the API multiple times if success 0 is returned with some time waits inbetween. As for issue #202 the API also returned a SD driver when the query was asking for GRD driver, so it should also be something to check on the API response and validate.
- API response arrive
- verify response success
- if response success is 0 then retry API query 1-3 times more
- validate response driver type (SD, GRD). if not correct then retry API query 1-3 times more (#202)
- if API query fails then fail and explain in console log that it might be API intermittent issue