Driver Download Failed Nvidia Geforce Experience

0 views

Skip to first unread message

Malene Mederios

unread,

Aug 3, 2024, 4:14:12 PM8/3/24

to karansdete

To fix this do a custom install without GeForce Experience and drivers, I have 3 Windows 10 machines with various OS releases on them (general and developer releases) and it works on each one of them.

I had newer or equivalent versions of these at the time of installation, so I did not include them in the installation. I felt that I should include this information just in case it does actually matter and help someone.

I have disabled-
GeForce Experience Software (had already installed newer version)
GeForce Drivers (had already installed newer version)
PhysX (had already installed newer version)
Visual Studio Integration.

I had a problem installing CUDA 11 with similar symptoms. (Also, nvidia-smi showed Cuda v10, and deviceQuery failed.) I needed to update Windows 10, update VisualStudio to 2019 then repeatedly uninstall all Nvidia programs. An older DLL NVCUDA64.dll (from an earlier CUDA v10 install) was particularly stubborn, but finally was able to remove it, reboot, then installing CUDA v11 worked ok.

I never had an issue until yesterday. Granted, I haven't started the program up in a few weeks, so it could have started earlier. Anyway, I got into an online chat with Adobe with a rep named Devendra, and they had me roll back graphic drivers, still failed. They had me delete the 11.0 file in AE, still failed. I killed the firewall, still failed. I uninstalled and reinstalled, still failed. Not sure what else to do.

That's clearly your graphics driver crashing, but figuring out as to why is still a mystery. Generally one would boot into safe mode/ simplified mode, uninstall the graphics driver completely and then on rebood let Windows Update look for the latest certified one to be installed automatically. and of course do the usual troubleshooting - unplug seconfddary monitors, reset you themes/ appearance, try different screen resolutions, reset any specific configurations that may have been introduced by games or application specific driver settings, reset your color adjustments and look for flakey color profiles... Also uninstall your Wacom stuff and/ or reset its configuration. Perhaps it has created an oversized virtual screen area for drawing and the graphics driver ends up in a balck hole trying to serve it...

Ok, I uninstalled the Wacom stuff, no change, still failed. I uninstalled graphics driver, geforce experience and all the nvidia stuff. rebooted, it updated my graphics card and downloaded correct drivers and all. I did not download the geforce experience program and it still fails. i was able to laod it up without any graphics installed other than onboard. As soon as I installed nvidia drivers, it fails....becoming angry. I can't be the only one?

I'll check back tomorrow. Right now I just backed up my hard drive. I have an new SSD here I bought a few weeks back. Just haven't had the time, so this is making that time. that I'm going to put in it, I have a more powerful comp at home with nvidia as well and have no issues. so I think I will start fresh.

Anyways, I installed a new SSD anyway, and reinstalled everything. It works fine now. So thanks to everyone for your help. But from what I can determine, it was nVidia's OpenGL. When I first installed everything my nVidia drivers were on a 311.## install. I left it on that for a while, whilst I installed AFX and a few other programs, essential to the pc running smoothly. It started fine, ran smooth, updated to 11.0.2 and it still worked wonderfully. SO I created a restore point at that time and went ahead and updated the drivers. I did a custom install and selected for graphics driver, audio hd, physx, and 3d something-or-other. I opted out of the GEFORCE Experience gaming optimization program(which is what I think was the original issue to begin with). Once updates were ran, I restarted the pc and once it came back on, I loaded up AFX, I got a fail immediately. This one was different though, it was somthing about OpenGL not being correct and there was an issue loading it. Sorry I could not get a screen shot. But once I clicked ok, it loaded up fine. It loads up fine now when I load it up. Haven't had an issue. So either I got lucky, or the OpenGL was just a warning and it disabled, I don't know. Thanks again, for your help. I've read a lot of Mylenium help threads to get my answers, so thank you.

Hi!

I just posted a potential solve for stutter, audio crackeling and shimmering that seem to plauge pcvr. The reason i'm mentioning it is because of that tedious adventure i've found that some things fail to initialize when starting the oculus services and i have questions. I'm refering WINUSB in perticular, but there are more things that seem to fail if you want to look into it. (debug tool > services > make console visible)

So, my thought process at the time was that winusb might be the reason for why the usb 3.1 gen 2 port only show up as 3.0 and only deliver 1.5 Gbit/s. This is obviously not the case for me as there seem to be some sort of bios problem and i don't think others achive higher speeds than around 2.2 gbit/s to the quest.

Anyway, WINUSB failed to initialize because of lack of memory. I have plenty of RAM so it probably has to do with the memory windows allocates to the process. So i doubled the maximum allowed heap allocation in regedit, as you do, to no effect.

So my questions are: What is WINUSB respossible for? And is there a benifit to getting it working? also, is there a way to globaly change OpenXR settings or can i only do it on an app per app basis?

TEMPORARY FIX

But yes, can confirm. I have found a solution that should help people who use Nvidia GPUs at least. If you go to Msconfig and then to services and uncheck Nvidia display container, most if not all, the stutter goes away. Nvidia container seems to be the biggest problem but you might also need to uncheck all non microsoft services and load starting items if this doesn't work.

Final Edit: Yes, for me it's the Nvidia Container LS that needs to be unchecked. Keep in mind that if you restart your computer it seems like it enables itself again. This should have to be the only thing you need to do if you are suffering from the same problem. If anyone has any more ideas of how to make this more permanent please share. Otherwise i hope this worked for you!

WinUSB seems like it cant be used by the quest 3. To many interfaces and the WINUSB driver is not good with that sort of thing it seems. It's not that it lacks memory per say but that it cant interface with the quest properly.
What things have you tried in the debug tool?

If you try to press Win + R and type msconfig. select "selective startup" and uncheck "load startup items". Then go to the services tab, check "hide all microsoft services" and then uncheck all. Does this help?

This helps my stutter problem temporarily. But something, somewhare decides that the apps should run at a fixed 60 fps after a while and i think that is the reason for the stutter.

Please report back as I'm trying to get to the bottom of this. Disabling the Nvidia container LS service seems to be one of the things that temporarily elevates the stutter. but maybe our two problems are connected. Also, how does the quest act when it stops?

EDIT: I am trying to learn C and am currently playing around with LIBUSB open source USBDrivers. If i get that to work and it helps i'll upload it to GITHUB or somewhere else.

You can probably save yourself the trouble of shutting down services here.

If terminating NVDisplay.Container.exe causes the stutter to disappear, this is most likely due to the GeForce Experience overlay.
Deactivate the overlay in GeForce Experience Settings.

Step 1: Right click on the Nvidia system tray icon and select NVIDIA GeForce Experience.
Step 2: Log into your NVIDIA account.
Step 3: Click the Settings icon (gear) on top right.
Step 4: In the GENERAL tab, turn off IN-GAME OVERLAY and exit.

It's quite possible that VSync might lock onto your connected 60 Hz monitor. If you have not already done so, switch off vertical synchronization system-wide in the 3D settings of the NVIDIA Control Panel, at least as a test.

Step 1: Access the NVIDIA control panel by entering NVIDIA control panel into your Windows search bar.
Step 2: Select Manage 3D Settings.
Step 3: Under the Global Setting tab you should find a list of features.
Setp 4: Go to Vertical sync.
Step 4: Using the dropdown menu to the right, select Force off.

In the same list of features, set "Power management mode" to "Prefer maximum performance" as a test.

If you are running any RGB software (CORSAIR iCUE, OpenRGB, Mystic Light etc.), close the software. The software will continue to run in the background, so also kill the respective process via the task manager.

If your CPU has integrated graphics, then deactivate them, either in the device manager, if possible via BIOS/UEFI.

Thank you but all these have been tried. Don't have Geforce experience and reinstalled windows with nothing but oculus client and drivers. The Nvidia Container LS seem to play a role but there is something more. The displays i have are 120 and 240 so can't be that either.

If you run your console window while starting up the Oculus services do you get any errors like in the pictures shown?

ADDITION: I should also add that the app-trk to mid-photon latency becomes higher even without the device locking to 60 hz for some reason. It's starting to feel personal xD. But yeah, the tracking latency becomes worse after a while. Don't know the reason yet, it is not thermal, most likely software.

From what i can tell right now, The issue (atleast for me) might be that my USB-C Port is not supplying sufficient power and at some point during use it stops due to too much demand. I just ordered a powered USB-C Hub that should help amplify the power of the cable/port, I'll update here once it arrives and i test it for a couple of hours.