Watch out... Win10 forces nvidia update

Samsara

S
I have not had any problems with the latest Nvidia driver 388.31 from November 15th. I just downloaded the driver from Nvidia and ran it after Windows was finished with the update.

The Windows Fall update did break my Rift drivers until I ran the occulus-driver.exe driver installer.
 

Bosie

Bosie
I've a copy of 382.53 on my drive and I noticed this update at the weekend whilst playing iRacing and my head tracking went to .
 

o'moylan

o'moylan
My system ground to a crawl. ED wasn't even playable. I uninstalled NVIDIA and when it reinstalled I think I told it not to do its own updates and I've been good for a few months now. I didn't do anything in windows 10 I told NVIDIA to shut up which is to bad because I liked the record/play update it came with.
 
Last edited:

Jon flint

Jon flint
Same here, windows forcibly installed a driver that just wasn't playing nice with my system, frequent drops to 30fps in Elite.

Going to the Nvidia site and manually installing a newer driver version fixed it, although there's no guarantees windows won't pull that again when it decides my drivers are out of date.
 

loribee

loribee
PiggyPiggyPig said:
Strange, I've experienced serious frame drop on galaxy view when enabling star names. Smooth as butter until now.
Click to expand...

I did actually notice frame drops after moving to the Fall Creators Update . it would drop to 20's FPS on the main menu screen with my headset static.

Rolled back the update (and fixed a few of the C++ libraries rolling back broke) and it's back to normal.
 

Worminator

W
Same problem here. Fall update pushed new NVIDIA driver and it wrecked everything in VR for me. It was almost like there was intermittent lag between the right eye and left eye. Wiped drivers with DDU and rolled back to 388.0 fixed it for me.
 

loribee

loribee
Worminator said:
Same problem here. Fall update pushed new NVIDIA driver and it wrecked everything in VR for me. It was almost like there was intermittent lag between the right eye and left eye. Wiped drivers with DDU and rolled back to 388.0 fixed it for me.
Click to expand...

Ahh that's interesting.. I did not check the version of Nvidia after the update - its back on 387.92 now -- do you recommend I go back even further to 388.0?

~L
 

TorTorden_VR

T
Y2K said:
goto settings, update. look for Defer updates. It stops windows updating any drivers.
Click to expand...
I'm not 100%.

But I suspect that is a function only found in the pro version of win 10, on home we are have to reg hack all these settings.

The fall creators update didn't come with 388.13 but with 385.69, but sometime during last week it got silently updated.

Well, done the reg hack from ASkVG now, here's hoping.
 

loribee

loribee
Y2K said:
goto settings, update. look for Defer updates. It stops windows updating any drivers.
Click to expand...

Already doing that .. and I used GPedit to defer the major feature updates for a year .. I manually installed Fall Creators using their tool to check out the Samsung - which I subsequently returned .. I would have been happy to keep the PC on the Fall Creators, but the frame drops were annoying ..
 

Worminator

W
loribee said:
Ahh that's interesting.. I did not check the version of Nvidia after the update - its back on 387.92 now -- do you recommend I go back even further to 388.0?

~L
Click to expand...
After the fall/windows update I was on 388.13. If it is working fine I would just leave it.
 

TorTorden_VR

T
Worminator said:
After the fall/windows update I was on 388.13. If it is working fine I would just leave it.
Click to expand...

loribee said:
Ahh that's interesting.. I did not check the version of Nvidia after the update - its back on 387.92 now -- do you recommend I go back even further to 388.0?

~L
Click to expand...

As with most things no point in fixing stuff that's not broken.

My experience with 388.13 however was complete rendering freezes for up to 2-3 seconds on every instance change, hourglass showing in the rift (meaning complete VR system overload).
Believe the steamvr equivalent is the image going grey, and sometimes as many as four of them consecutively.
 

Gunner Deckard

G
Same thing happened here. It tried to update me to 388.13 and crashed my computer while I was playing D2. Windows doesn't need to be updating my Nvivia drivers automatically I need to turn it off somehow.
 

NW3

NW3
Samsara said:
I have not had any problems with the latest Nvidia driver 388.31 from November 15th.
Click to expand...

The 388.31 driver is working fine for me too, but I'm not running VR (yet). For now I'm using a 3D monitor and NVidia LCD shutter glasses.
 

PiggyPiggyPig

PiggyPiggyPig
Just to confuse things further. I've now forced a Nvidia update, to the latest version. Now my problems are cured. However, I remember turning updates off a while back, so no automatic updates for me, although some updates were being performed on shutdown.
So what went wrong? As I mentioned previously, I had serious lockups on galaxy view. This thread then prompted me to check on my Windows Geforce experience but I noticed that it had gone missing!
 

TorTorden_VR

T
Geforce experience was ok. two years ago.

Now it's a pile of nagging bloatware and should never be installed on any computer.

For recording get OBS instead.
yeah if take a little more to setup but you also have so much options on tailoring.
And they have sorted their version of shadowplay as well.
If you want it.
 

NW3

NW3
Interestingly, the 388.31 driver appears to be 10-20% faster than the (fairly recent) drivers I was running. I also upgraded Voice Attack tonight, so that might be part of the framerate improvement. It's most noticeable when I'm in deep space, which doesn't really matter (120 fps vs. 150 fps), but it's also apparent while in a station ~50 fps -> 60 fps, which is still a nice framerate increase.
 
You must log in or register to reply here.
Back
Top Bottom