NVIDIA GeForce GAME READY DRIVER v531.79 WHQL

[stage]

Release Date: May 2, 2023
https://us.download.nvidia.com/Windows/531.79/531.79-win11-win10-release-notes.pdf

Changes and Fixed Issues in Version 531.79

The following sections list the important changes and the most common issues resolved in this version. This list is only a subset of the total number of changes made in this driver version. The NVIDIA bug number is provided for reference.

Fixed Issues in this Release
[RTX 30 series] Application crash may be observed while playing Battlefield 2042/The Last of Us/Unreal Editor [4013983]
[Asus VG27WQ][Acer XV253Q] Highest monitor refresh rate is missing from the NVIDIA Control Panel after updating to NVIDIA display driver 531.41 [4072741]

Open Issues in Version 531.79 WHQL

As with every released driver, version 531.79 WHQL of the Release 530 driver has open issues and enhancement requests associated with it. This section includes lists of issues that are either not fixed or not implemented in this version. Some problems listed may not have been thoroughly investigated and, in fact, may not be NVIDIA issues. Others may have workaround solutions.

You may encounter issues installing the NVIDIA Control Panel from the Windows Store. See “Issues Installing the NVIDIA Control Panel from the Windows Store” for more information.

desktop download:
https://us.download.nvidia.com/Windows/531.79/531.79-desktop-win10-win11-64bit-international-dch-whql.exe
notebook download:
https://us.download.nvidia.com/Windows/531.79/531.79-notebook-win10-win11-64bit-international-dch-whql.exe

[Vox Maximus]

And still no fix for a huge DPC latency caused by the driver...

[Vox Maximus]

Better detailed info about the driver:
https://www.reddit.com/r/nvidia/comments/135l80f/game_ready_driver_53179_faqdiscussion/

And (unofficial) additional info in comments:
https://www.reddit.com/r/nvidia/comments/135l80f/comment/jik7in7/?utm_source=reddit&utm_medium=web2x&context=3

[Arc]

Originally posted by MaxL:

And still no fix for a huge DPC latency caused by the driver...

I'm still waiting for the fix where turning off HDMI 2.1 TV and rebooting PC will disable all other secondary screens for some reason.

[Mexicola9302]

I had this crash yesterday in BF 2042, thanks i didn't think it's a driver issue. Gonna DDU that new driver now.

[Maskrider]

Upgraded, on 1.0.4.1, crashed while building shaders at around 25% and 4x%, not yet finished building shaders, have to try again.

edit: crashed again, aaaahhhh!

edit: 5 times in a roll, damn!

edit: 6 times in a roll, still building shaders, no more words. I think ND is seriously incompetent on PC games, no next purchase will be made.

edit: Finally able to finish building shaders, toke 40min counting all the crashes.

edit: crawling under water for a while, crashed. You've gotta be admiring their competence on PC games. Gotta stop "PLAYING" by them.

[Lince_SPAIN]

Originally posted by Maskrider:

Upgraded, on 1.0.4.1, crashed while building shaders at around 25% and 4x%, not yet finished building shaders, have to try again.

edit: crashed again, aaaahhhh!

edit: 5 times in a roll, damn!

edit: 6 times in a roll, still building shaders, no more words. I think ND is seriously incompetent on PC games, no next purchase will be made.

edit: Finally able to finish building shaders, toke 40min counting all the crashes.

edit: crawling under water for a while, crashed. You've gotta be admiring their competence on PC games. Gotta stop "PLAYING" by them.

it's like a super intensive hardware stress test (compiling shaders the way Iron Galaxy does it) so whatever is wrong with your PC (thermals, overclocking/ underclocking, bad blocks in storage drives, DIMMs mismatch, OS config... etc, etc) it will show during this crazy process they're doing with libraries taken straight away from a PS5 devkit instead of PC APIs.

[em_t_hed]

ive written off the game ready drivers because of their instabilities for their studio drivers and haven't looked back... much better overall experience

[Seibzehn]

This new driver crashes the shader process every time!

This never happens before.

Verify game files and delete the shade folder does not help.

Edit: Nvidia 531.61 studio driver solve the problem.

[Vox Maximus]

Originally posted by em_t_hed:

ive written off the game ready drivers because of their instabilities for their studio drivers and haven't looked back... much better overall experience

Studio ones aren't any better here tbh

[Maskrider]

Originally posted by Lince_SPAIN:

it's like a super intensive hardware stress test (compiling shaders the way Iron Galaxy does it) so whatever is wrong with your PC (thermals, overclocking/ underclocking, bad blocks in storage drives, DIMMs mismatch, OS config... etc, etc) it will show during this crazy process they're doing with libraries taken straight away from a PS5 devkit instead of PC APIs.

My PC works fine under stress, Windows memtest passed without an error, 100% CPU for tens of minutes when bulk converting images or encoding video.

It is ND, everything else works fine (games, applications, etc). May be also NVIDIA, not many crashes for the previous version of driver.

[em_t_hed]

the game ready drivers for several generations of the drivers were causing OS problems ever since i got my current card...

i dont really care how they're updated so often for games like it's a phone app getting updated on the daily... if it's causing issues outside of games themselves as in OS problems they shouldnt be published

the studio drivers do nothing of the sort, albiet not updated nearly as often, they are WAY MORE STABLE

the kicker here is... NVIDIA themselves state this same issue themselves when choosing between game ready drivers and studio drivers... they briefly (VERY BRIEFLY) discuss stability problems may occur with the game ready drivers... they don't lie

[_APA [~sudo]]

Make sure ya'all rebuild the shaders

[kgkong]

Originally posted by Maskrider:

Originally posted by Lince_SPAIN:

it's like a super intensive hardware stress test (compiling shaders the way Iron Galaxy does it) so whatever is wrong with your PC (thermals, overclocking/ underclocking, bad blocks in storage drives, DIMMs mismatch, OS config... etc, etc) it will show during this crazy process they're doing with libraries taken straight away from a PS5 devkit instead of PC APIs.

My PC works fine under stress, Windows memtest passed without an error, 100% CPU for tens of minutes when bulk converting images or encoding video.

It is ND, everything else works fine (games, applications, etc). May be also NVIDIA, not many crashes for the previous version of driver.

Memtest and benchmark stress tests are all synthetic. They are not true real world situations and as a result may not accurately represent some real world use situations. So you may not always noticed some of these issues.

If you haven't tried to manually set your XMP/EXPO profile settings for your memory, that would be a good place to check to help ensure that memory is stable. If the game continues to crash, set the CL timing value up from the XMP/EXPO value (DDR4 CL16 goes to CL18 and DDR5 CL36 goes to CL38 for examples). The game should stop crashing. If it doesn't, it's probably an issue then with drivers (nVidia drivers have been sucking lately), high thermals, or too much system multitasking processes. Ideally, you don't wanna alt+tab out of the game while it compiles shaders, nor do you really wanna run other apps or run a web browser during this, and all of this puts more workload on the CPU and since shader comp takes up to 100% usage, it will take longer as tasks have to switch back and forth more while compiling shaders and multitasking.

[Maskrider]

Originally posted by KingGorillaKong:

Originally posted by Maskrider:

My PC works fine under stress, Windows memtest passed without an error, 100% CPU for tens of minutes when bulk converting images or encoding video.

It is ND, everything else works fine (games, applications, etc). May be also NVIDIA, not many crashes for the previous version of driver.

Memtest and benchmark stress tests are all synthetic. They are not true real world situations and as a result may not accurately represent some real world use situations. So you may not always noticed some of these issues.

If you haven't tried to manually set your XMP/EXPO profile settings for your memory, that would be a good place to check to help ensure that memory is stable. If the game continues to crash, set the CL timing value up from the XMP/EXPO value (DDR4 CL16 goes to CL18 and DDR5 CL36 goes to CL38 for examples). The game should stop crashing. If it doesn't, it's probably an issue then with drivers (nVidia drivers have been sucking lately), high thermals, or too much system multitasking processes. Ideally, you don't wanna alt+tab out of the game while it compiles shaders, nor do you really wanna run other apps or run a web browser during this, and all of this puts more workload on the CPU and since shader comp takes up to 100% usage, it will take longer as tasks have to switch back and forth more while compiling shaders and multitasking.

That does not happen with anything else. I frequently encode video and converts a bulk of images. Have also generated images with stable diffusion with many steps, and local AI chat bot like Alpaca, nothing crash my OS, not even the app.

[kgkong]

Originally posted by Maskrider:

Originally posted by KingGorillaKong:

Memtest and benchmark stress tests are all synthetic. They are not true real world situations and as a result may not accurately represent some real world use situations. So you may not always noticed some of these issues.

If you haven't tried to manually set your XMP/EXPO profile settings for your memory, that would be a good place to check to help ensure that memory is stable. If the game continues to crash, set the CL timing value up from the XMP/EXPO value (DDR4 CL16 goes to CL18 and DDR5 CL36 goes to CL38 for examples). The game should stop crashing. If it doesn't, it's probably an issue then with drivers (nVidia drivers have been sucking lately), high thermals, or too much system multitasking processes. Ideally, you don't wanna alt+tab out of the game while it compiles shaders, nor do you really wanna run other apps or run a web browser during this, and all of this puts more workload on the CPU and since shader comp takes up to 100% usage, it will take longer as tasks have to switch back and forth more while compiling shaders and multitasking.

That does not happen with anything else. I frequently encode video and converts a bulk of images. Have also generated images with stable diffusion with many steps, and local AI chat bot like Alpaca, nothing crash my OS, not even the app.

None of those things are actually as intensive as shader compilation through AVX process tasks with heavy memory usage, with the amount of shaders that TLOU is compiling.