Download: NVIDIA GeForce 442.50 WHQL drivers

loracle

2020-02-28 15:17

desmonds99:

Only a negligible difference for me but the results are replicable: 441.87, score: 8 435 https://www.3dmark.com/spy/10286264 442.19, score: 8 441 https://www.3dmark.com/spy/10762364 442.50, score: 8 301 https://www.3dmark.com/spy/10783185 Rolled back to 442.19, Score: 8 480 https://www.3dmark.com/spy/10783301 DDU and installed 442.50 again, 1st run score: 8 288 https://www.3dmark.com/spy/10783595 Restarted PC and 2nd run, score: 8 304 https://www.3dmark.com/spy/10783665 I haven't noticed much difference in games but this is the first time a driver update results in a consistent drop in score for me.

thank you for posting this, it's confirming that's something wrong with the last drivers ( at least the performance drops down), also 442.19 gives better score than 441.87, but 441.87 is more stable, thanks again dude.

#5764326

EDK-Rise

2020-02-28 15:33

support wddm 2.7?

#5764335

Party Poison

2020-02-28 16:00

To those who don't have dx12 crashes in Div2 you guys are the minority. For most people it ctd after an hour or so, always has, still does. Its even such a known issue internally that Massive considered patching the choice out and locking it to dx12. I'll give this driver a try and see how it goes.

#5764405

-Tj-

2020-02-28 18:18

I noticed bigger fps drop by loading transitions in D2 vs older 442.01. I'll just stay at this driver until newer main branch comes out. What this r450?..

#5764642

Robbo9999

2020-02-29 09:55

desmonds99:

Only a negligible difference for me but the results are replicable: 441.87, score: 8 435 https://www.3dmark.com/spy/10286264 442.19, score: 8 441 https://www.3dmark.com/spy/10762364 442.50, score: 8 301 https://www.3dmark.com/spy/10783185 Rolled back to 442.19, Score: 8 480 https://www.3dmark.com/spy/10783301 DDU and installed 442.50 again, 1st run score: 8 288 https://www.3dmark.com/spy/10783595 Restarted PC and 2nd run, score: 8 304 https://www.3dmark.com/spy/10783665 I haven't noticed much difference in games but this is the first time a driver update results in a consistent drop in score for me.

3DMark Timespy scoring identically with my system vs past recent drivers. BF1 gameplay seems fine, can't notice any differences in framerate.

#5764671

Morris

2020-02-29 12:33

Hi, test firestrike dx11 : 442.19: 29349 442.50: 28754 https://www.3dmark.com/compare/fs/21936941/fs/21936711# Timespy dx 12 442.19: 15013 442.50: 15082 https://www.3dmark.com/compare/spy/10798247/spy/10796745# I'm playng game in dx 11 Roll back to 442.19

#5764675

lukas_1987_dion

2020-02-29 13:10

LOL o_O

#5764701

Dagda

2020-02-29 14:59

ShadowDuke:

Wow, so Seasons are now considered a full/different game, which needs a game ready driver!? Ridiculous..

well the game still uses the old source engine, just updated to dx11, so yes adding stuff to an engine like that is practically making a new game every time btw the game still crashes with the dxdiag error when alt-tab, is less often but still happens

#5764745

IchimA

2020-02-29 18:36

Rdr2 can't start with MSAA activated ! Can anyone confirm ?

#5764747

Astyanax

2020-02-29 18:40

IchimA:

Rdr2 can't start with MSAA activated ! Can anyone confirm ?

MSAA or MFAA? MFAA can only break dx12. MSAA doesn't apply to Vulkan or DX12 from the driver. Or are you talking in game?

#5764751

IchimA

2020-02-29 19:11

Setting MSAA x2, x4 in game - in setting ! If I try to start the game I get GFX_Error crash

#5764755

Dan Longman

2020-02-29 19:17

Driver seems fine for me. Regarding Division 2 DX12 crashes, I switched my 2700x for a 3700x yesterday. Up till then I never had any crashes in div2 using dx12. Same settings and same driver and now getting crashes. So wonder if it's exacerbated by Zen2?

#5764761

TachiFoxy

2020-02-29 20:01

Giving my feedback on The Division 2 DX12-crashes: Got them with the old driver (442.37 Hotfix-Driver) only occassionally while browsing the inventory. With 442.50 it would crash during normal gameplay - in the midst of combat - way more often. At least once per hour, basically. Reverted back and the game runs as before, though without those pesky inventory-crashes yet. System-info: Ryzen 7 3700X 32 GB DDR4-3200 RAM GTX 1080 Win10 Version 1909 Build 18363.657

#5764767

Astyanax

2020-02-29 20:20

Purge the (disk cleanup) shader caches, and nvidia's shader caches.

IchimA:

Setting MSAA x2, x4 in game - in setting ! If I try to start the game I get GFX_Error crash

You need to delete the games pipeline cache after a driver update. delete "sga_" Vulkan cache files in the RDR2 documents settings folder

#5764783

IchimA

2020-02-29 21:38

Astyanax:

Purge the (disk cleanup) shader caches, and nvidia's shader caches. You need to delete the games pipeline cache after a driver update. delete "sga_" Vulkan cache files in the RDR2 documents settings folder

Thanks man !

#5764785

Dan Longman

2020-02-29 22:02

AsiJu:

Are all your CPU settings at default? Would you mind checking what is your actual SOC voltage?

Running PBO with AOC, (Boost/PPT 200, EDC/TDC 230) I have SOC set to 1.05 on my motherboard but ryzen master is showing 1.1v I have vcore set to Auto with no offset https://i.imgur.com/Xp2kIyA.png

#5764795

sean8102

2020-02-29 22:28

EDK-Rise:

support wddm 2.7?

Nope. WDDM 2.6. I'm running the Windows 10 Insider 20H1 build (latest slow ring build) and was getting WDDM 2.7 with the 450.12 driver. https://i.imgur.com/1xP0h6O.png Also no longer have the "Hardware-accelerated GPU scheduling" option in Settings>System>Graphics Settings that I did with 450.12 (no surprise I guess since it requires WDDM 2.7). https://i.imgur.com/H9rGP89.png

#5764823

TachiFoxy

2020-03-01 01:06

AsiJu:

Do you have Depth of Field enabled in gfx settings?

Yup, I have DoF turned on.

#5764841

Party Poison

2020-03-01 02:45

HeavyHemi:

If you say so. However, I'd like to point out that, the vast majority of the time those who do NOT have issues do not REPORT NOT HAVING ISSUES. Whereas those WITH ISSUES are FAR MORE LIKELY TO REPORT THEM. I have about 20 people I know that play the game. Only one of them had issues in DX12 and that was resolved by reducing his GPU overclock. So out of 20, that I know personally, only one had issues and we resolved it. I have nearly 300 hours in game. So, I think I can speak just a bit on how it performs.

Ok but WHY are you SHOUTING at RANDOM. I have about 1200 hours+ over my personal accounts and testing accounts. Both the Leamington Spa and Stockholm teams acknowledged the issue and could not find a fix, it got passed back as an Nvidia driver issue and was never fixed. But if it can't be replicated it can't be fixed. 20 people I know that play the game. Only one of them had issues in DX12 and that was resolved by reducing his GPU overclock. So out of 20, that I know personally, only one had issues and we resolved it. I have nearly 300 hours in game. So, I think I can speak just a bit on how it performs. So because you have no issues in that play time or in the circle of users you know there is no issues? Riiiight. Example: I know 20 people who had zero issues with RDR2 does that mean there are no issues? No. That's not how it works. Even if those with issues are more likely to report it ( those that bother that is ) that does not discredit those reports. If anything having constant reports of the same error across such a large sample of users and hardware variations indicates a software fault.

#5764848

Cyberdyne

2020-03-01 03:58

@Party Poison Don't take it personally, he's toxic, doesn't know how to talk civil. He has thrown a fit when someone asked another user to prove there was sharper textures in a driver. He said one person reporting is not always a placebo effect, defended him. Now, he's yelling at you for being one person with an issue, if anything he should be defending you.