NVIDIA Hotfix GeForce 511.72 driver download & Discussion

I've never seen this during my 500+ hrs of playtime...

 

I play regularly and this hasn't happened for me at all.

 

Thanks for the reports. I'm aware it doesn't happen to everyone but it's in fact an issue to a certain % of the users. With a quick search i easily found other (recent) posts talking about it such as:

• https://www.reddit.com/r/apexlegends/comments/sj94bh/loading_issue/
• https://www.reddit.com/r/apexlegends/comments/q7xnhe/shaders_compiling/
• https://www.reddit.com/r/apexlegend..._keeps_freezing_during_loading_and_compiling/
• https://www.reddit.com/r/apexlegends/comments/rcpzsb/shader_compiling_everytime/

It seems that there's still an issue with shader caching and this game despite it not affecting all the players.

 

For me shader compilation happens only on driver updates or when the new big patch drops.
I always thought this was a normal thing. Doesn't take that long too, about a minute or less.

 

Begin a GPU it's the driver and the lack of it. Sound strange I know . yet, the CPU score sometime I'm seeing is compatible with a disabled PCI-EX graphics adapter.
Since there are also other correlated issue and deficiency ( even when the driver improperly work the CPU is still impacted by traceable performance loss ) mine suggestion is to NOT deploy any recently released driver past the 47X.XX that actually make the GPU goes hi-wire until the issue is identified or rectified by NVIDIA.
[DDNINJED] for sanity.

 

Looks like the new Vulkan 1.3 driver is an improvement for RDR2, I haven't encountered black flashing so far, no crashes and far less (VRAM management related?) slow downs when riding through Saint Denis. Let's hope it sticks.

 

And this cpu issue with dwm also not present?

 

This is the 1.3 driver.

 

Is anyone able to help please.

I have not been able to update my driver past 472.12. If I update after an hour of playing I get a hard lock in game, then it’s ok for a few moments, then it will hard lock again and usually close to desktop.

discord starts to connect and disconnect during this time and the temperatures on my NZXT display hard lock, everything becomes very unresponsive for a short period of time.

this mainly happens in COD Warzone, but has happened in Dying light 2.

it has happened with every driver since 472.12, the only resolution I find is to revert back to this driver.

Surely this can not be right, everything is up to date including bios. I’m on windows 11.

thanks

 

replace the cpu.

your system is practically timing out interrupts because of error correction.

 

Did you try a clean uninstall with DDU?

 

I had 2 Bsod’s in Vanguard during last 2 days with 511.65.
Will try this fix.

 

I had occasional crashes with latest drivers last two month in warzone and vanguard. Only thing that helped me is, someone earlier mentioned in this thread to use 472.84 studio driver. That driver fixed all the issues I had.

 

I have unfortunately, anytime i install a new driver i do it this way due to issues i have had in the past. I have also used Nvidia "Clean" tool which their support provided. Both end in the same scenario.

I don't get any crashes with 472.12 so all good there, but thanks for the suggestion of the older driver, this seems crazy that i can not upgrade my GPU to anything past Sept time last year without having crashes.

 

its not crazy because you have a hardware issue.

 

Did you update the chipset drivers?
What version of windows are you using?
What is your CPU and motherboard?
Did you run any memory test?

 

And? Thats not what i asked.

 

Really sounds like you have another issue(s) with your machine

Software conflict or hardware issue, have you tried reinstalling the os fully with format?

 

Except for a quick benchmark with Horizon Zero Dawn, which gave me the same result pretty much of any other driver, duo the driver borderline state (probably more in polling saturation context) and the GPU temperature increase on desktop I didn't run any extensive games on those DCH to risk the GPU electronics.
What you can do is to check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceMigration for [Classes] [Devices] and [Location] and delete the whole sub key of it to clear latent installation issue that could cause unpredictable behavior and reboot before making an in place upgrade of the OS and stick to the older driver.

 

Maybe because Vulkan 1.3 hasn't anything todo with the dwm requests?

As for the dwm spam, did you notice any performance regres caused by it?