Jump to content

Nvidia Driver 399.24 fixes bug on 32/64 c/t CPU's

ThePD
By ThePD
in General Discussion
 Share
Posted

In the patch notes for Nvidia Geforce driver 399.24. One of the notes included a patch for 32 core CPU's in which gaming performance was being dropped by 50%.
 

[3D games]: Game performance drops in half when moving from 16 core/32 thread CPU to 32 core/64 thread CPU. [2334312]


Following link brings you to PDF of the Nvidia Patch Notes. http://us.download.nvidia.com/Windows/399.24/399.24-win10-win8-win7-desktop-release-notes.pdf

It will be interesting to see how this patch really affects Threadripper CPU's all though they aren't truly gaming chips.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Not to be rude, but that driver is already outdated :P  we're at 411.70 now. And yes, it did help performance.

PC Specs - AMD Ryzen 7 5800X3D - MSI B550M Mortar - 32GB Corsair Vengeance RGB DDR4-3600 @ CL16 - ASRock RX7800XT - 660p 1TBGB & Crucial P5 1TB - Fractal Define Mini C - CM V750v2 - Windows 11 Pro

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
Just now, NelizMastr said:

Not to be rude, but that driver is already outdated :P  we're at 411.70 now. And yes, it did help performance.

True, but there are people like myself who do not follow Nvidia's driver updates as soon as they release. I had a bad experience with my 980Ti getting bricked by a Nvidia driver.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
4 minutes ago, ThePD said:

True, but there are people like myself who do not follow Nvidia's driver updates as soon as they release. I had a bad experience with my 980Ti getting bricked by a Nvidia driver.

A driver doesn't break a card, that's just a coincidence. At worst, a driver can cause instability, but the card actually becoming a brick, no.

PC Specs - AMD Ryzen 7 5800X3D - MSI B550M Mortar - 32GB Corsair Vengeance RGB DDR4-3600 @ CL16 - ASRock RX7800XT - 660p 1TBGB & Crucial P5 1TB - Fractal Define Mini C - CM V750v2 - Windows 11 Pro

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
8 minutes ago, NelizMastr said:

A driver doesn't break a card, that's just a coincidence. At worst, a driver can cause instability, but the card actually becoming a brick, no.

Their driver did broke some cards in the past though, twice. 

| Intel i7-3770@4.2Ghz | Asus Z77-V | Zotac 980 Ti Amp! Omega | DDR3 1800mhz 4GB x4 | 300GB Intel DC S3500 SSD | 512GB Plextor M5 Pro | 2x 1TB WD Blue HDD |
 | Enermax NAXN82+ 650W 80Plus Bronze | Fiio E07K | Grado SR80i | Cooler Master XB HAF EVO | Logitech G27 | Logitech G600 | CM Storm Quickfire TK | DualShock 4 |

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

My "clickbait" thread on this topic

PLEASE QUOTE ME IF YOU ARE REPLYING TO ME

Desktop Build: Ryzen 7 2700X @ 4.0GHz, AsRock Fatal1ty X370 Professional Gaming, 48GB Corsair DDR4 @ 3000MHz, RX5700 XT 8GB Sapphire Nitro+, Benq XL2730 1440p 144Hz FS

Retro Build: Intel Pentium III @ 500 MHz, Dell Optiplex G1 Full AT Tower, 768MB SDRAM @ 133MHz, Integrated Graphics, Generic 1024x768 60Hz Monitor


 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
14 minutes ago, xAcid9 said:

Their driver did broke some cards in the past though, twice. 

No.

What has happened in the past is that a driver causes issues with the OS, either crashing it or preventing it from booting.

That is not bricking.

Having windows crash can be fixed by clean installing windows or doing some workaround to uninstall the bad driver and install an older one.

 

Bricking is when you put a custom BIOS or firmware on a device that causes it to become unusable and it is not possible to re-flash the bios/firmware afterwards to fix it.

NEW PC build: Blank Heaven   minimalist white and black PC     Old S340 build log "White Heaven"        The "LIGHTCANON" flashlight build log        Project AntiRoll (prototype)        Custom speaker project

Spoiler

Ryzen 3950X | AMD Vega Frontier Edition | ASUS X570 Pro WS | Corsair Vengeance LPX 64GB | NZXT H500 | Seasonic Prime Fanless TX-700 | Custom loop | Coolermaster SK630 White | Logitech MX Master 2S | Samsung 980 Pro 1TB + 970 Pro 512GB | Samsung 58" 4k TV | Scarlett 2i4 | 2x AT2020

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
4 minutes ago, Enderman said:

No.

What has happened in the past is that a driver causes issues with the OS, either crashing it or preventing it from booting.

That is not bricking.

Having windows crash can be fixed by clean installing windows or doing some workaround to uninstall the bad driver and install an older one.

 

Bricking is when you put a custom BIOS or firmware on a device that causes it to become unusable and it is not possible to re-flash the bios/firmware afterwards to fix it.

Nah, these drivers i'm talking about was actually broken and killed some chips. 

| Intel i7-3770@4.2Ghz | Asus Z77-V | Zotac 980 Ti Amp! Omega | DDR3 1800mhz 4GB x4 | 300GB Intel DC S3500 SSD | 512GB Plextor M5 Pro | 2x 1TB WD Blue HDD |
 | Enermax NAXN82+ 650W 80Plus Bronze | Fiio E07K | Grado SR80i | Cooler Master XB HAF EVO | Logitech G27 | Logitech G600 | CM Storm Quickfire TK | DualShock 4 |

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
23 minutes ago, Enderman said:

No.

What has happened in the past is that a driver causes issues with the OS, either crashing it or preventing it from booting.

That is not bricking.

Having windows crash can be fixed by clean installing windows or doing some workaround to uninstall the bad driver and install an older one.

 

Bricking is when you put a custom BIOS or firmware on a device that causes it to become unusable and it is not possible to re-flash the bios/firmware afterwards to fix it.

You are correct. My use of Bricking was incorrect. Bricking was just the first word that popped into my head.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
20 minutes ago, xAcid9 said:

Nah, these drivers i'm talking about was actually broken and killed some chips. 

Source?

Pretty sure that's never happened, at least not in the past decade.

NEW PC build: Blank Heaven   minimalist white and black PC     Old S340 build log "White Heaven"        The "LIGHTCANON" flashlight build log        Project AntiRoll (prototype)        Custom speaker project

Spoiler

Ryzen 3950X | AMD Vega Frontier Edition | ASUS X570 Pro WS | Corsair Vengeance LPX 64GB | NZXT H500 | Seasonic Prime Fanless TX-700 | Custom loop | Coolermaster SK630 White | Logitech MX Master 2S | Samsung 980 Pro 1TB + 970 Pro 512GB | Samsung 58" 4k TV | Scarlett 2i4 | 2x AT2020

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
6 minutes ago, Enderman said:

Source?

Pretty sure that's never happened, at least not in the past decade.

Pretty old but not a decade old. 
https://www.anandtech.com/show/3605

https://www.engadget.com/2010/03/05/nvidia-pulls-196-75-driver-amid-reports-its-frying-graphics-car/

 

Another one is 32x.xx circa 2013. I forgot which specific version but for this one Nvidia simply close one eye i think because smaller audience was affected by it. No official announcement. 

| Intel i7-3770@4.2Ghz | Asus Z77-V | Zotac 980 Ti Amp! Omega | DDR3 1800mhz 4GB x4 | 300GB Intel DC S3500 SSD | 512GB Plextor M5 Pro | 2x 1TB WD Blue HDD |
 | Enermax NAXN82+ 650W 80Plus Bronze | Fiio E07K | Grado SR80i | Cooler Master XB HAF EVO | Logitech G27 | Logitech G600 | CM Storm Quickfire TK | DualShock 4 |

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing General Discussion

×