Soldato
Not everyone updates their drivers bet there are 1000's still on the same driver when the card was installed.
-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
**THE NVIDIA DRIVERS THREAD**
- Thread starter Boomstick777
- Start date
Soldato
I wonder if this applies to AMD too. My sister's PC has a 4350 in it with an ancient driver. Haven't tried the update on it yet tho.
Soldato
Updated to 2004 and it gave me three BSOD in three days...more than I've had in three years.
Reverted back to 1909, I've read 2004 has issues and MS are working on them.
Wouldn't recommend updating to it yet.
Reverted back to 1909, I've read 2004 has issues and MS are working on them.
Wouldn't recommend updating to it yet.
Caporegime
Not even getting it offered here, it just does a check and comes back, 'You're up to date'
Soldato
The update screen originally informed me that my PC was "not ready yet" for 2004, so I updated it manually.
Guess the software is smarter than me!
The update screen originally informed me that my PC was "not ready yet" for 2004, so I updated it manually.
Guess the software is smarter than me!
I updated manually too last week and haven't had any issues. Guess you were unlucky.
Soldato
Think I will hold off it advises against updating manually too.
Caporegime
Same, just don't wont to be sitting here just getting the same, this time next year.
Soldato
@Neil79 what does that change actually do?
Caporegime
Got no issues with the 446.14s.
Soldato
Been on the insider 2004 for donkeys and the beta drivers listed on here without issue. Those with bsods have you parsed the dump files to see what is causing the issue?
Soldato
Didn't do any dump inspections. After three BSOD's I couldn't reverse the update quick enough.
However, the last BSOD error message was Watchdog Timeout which Google told me is something to do with the CPU getting confused.
Have not had that error before and I've been running this build for a few years now.
Caporegime
There's a few BSOD reports over on the guru3d forum as well for this driver on 2004. Haven't had any issues myself but there does appear to be some conflict there with certain types of hardware or software.
All the problems I've heard about the new Win 10 2004 update are due to not having the latest Nvidia or AMD GPU drivers.
I'm running the latest Win 10 update that I manually installed, then installed 450.99 as that's the latest GFE driver, or least it will be in a week or two. Not had a single problem so far.
I'm running the latest Win 10 update that I manually installed, then installed 450.99 as that's the latest GFE driver, or least it will be in a week or two. Not had a single problem so far.
Caporegime
The update screen originally informed me that my PC was "not ready yet" for 2004, so I updated it manually.
Guess the software is smarter than me!
If you have...
The Latest Windows 2004 release
If you have a 10Xx or higher GPU
Then go for the 450.99 and enable Hardware Scheduling for ultimate DX 12 fun
(Also enable Low Latency Mode - ULTRA in Nvidia Control Panel )
What does Low Latency Mode add something extra with Hardware Scheduling? FWIW i have found 450.99 more stable than the 445.XXs - i was getting all sorts of crashes with them.
1 thing. i did do a run on timespy - and smashed/a bit better my previous score with lower clocks - but it did say the score was invalid as the driver had changed the LOD...make of that what you will...