Thursday, June 29th 2023

NVIDIA GeForce 536.40 WHQL Drivers Released

by
btarunr
 Discuss (21 Comments)
NVIDIA today released the latest version of the GeForce Game Ready drivers. Version 536.40 WHQL introduces support for the latest GeForce RTX 4060 graphics card that went on sale today. The drivers also fix a handful of issues. Display corruption noticed with Street Fighter 6 with MFAA enabled during the fight start cutscene, has been fixed. NVIDIA also fixed a bug with OptiX de-noiser that caused vignette effect to disappear in border pixels. A bug that caused the driver to not be able to detect external HDMI displays from NVIDIA Control Panel after driver re-installation has also been fixed.

DOWNLOAD: NVIDIA GeForce 536.40 WHQL Drivers
Gaming Technology
  • Introduces support for the GeForce RTX 4060.
Fixed
  • [Street Fighter 6] Corruption during the fight start cutscene when MFAA is applied [4147907]
  • [Optix Denoiser] Addresses vignette effect that could appear on image border pixels
  • Not able to detect external HDMI display from NVCPL after driver re-installed [4085941]
Known Issues
  • Increase in DPC latency observed in Latencymon [3952556]
  • Applying GeForce Experience Freestyle filters cause games to crash [4008945]

Related News

Add your own comment

21 Comments on NVIDIA GeForce 536.40 WHQL Drivers Released

#1
igralec84
Hope they fix the Diablo 4 crashing that started with the previous ones, but wasn't there in the 40 hours of playing before :rolleyes:
Posted on Reply
#2
LukeHjo
Very nice, I still want them to prioritize the DPC latency issue. Why're you using Latencymon to measure it anyways? Xperf is better.
Posted on Reply
#3
Sp33d Junki3
igralec84Hope they fix the Diablo 4 crashing that started with the previous ones, but wasn't there in the 40 hours of playing before :rolleyes:
seen no crash running 535.98 which is stable with D4
Posted on Reply
#4
LukeHjo
Sp33d Junki3seen no crash running 535.98 which is stable with D4
Me neither.
Posted on Reply
#5
igralec84
Sp33d Junki3seen no crash running 535.98 which is stable with D4
LukeHjoMe neither.
Must not like DLSS3 then or Reflex. Can barely finish a dungeon without crashing, haven't tried the today's drivers yet. Maybe it's a problem on the game's side though.
Posted on Reply
#6
THU31
LukeHjoVery nice, I still want them to prioritize the DPC latency issue. Why're you using Latencymon to measure it anyways? Xperf is better.
What exactly is this issue?

I've seen huge spikes with adaptive power management when power states change.

With prefer max performance, I'm always under 500 us, usually under 300.
Posted on Reply
#7
trparky
btarunrKnown Issues
  • Increase in DPC latency observed in Latencymon [3952556]
OK, this is far... far past stupid already.
Posted on Reply
#8
R-T-B
trparkyOK, this is far... far past stupid already.
It's supposedly fixed in next release according to their blog.
Posted on Reply
#10
RAJOD1
igralec84Must not like DLSS3 then or Reflex. Can barely finish a dungeon without crashing, haven't tried the today's drivers yet. Maybe it's a problem on the game's side though.
Really do you have AMD or Intel system?

I have a 4070 + 536.23 + Old hex core xeon and windows 10 never had a crash in D4. I just use the settings that experience recommends which is maxed out.
Posted on Reply
#11
igralec84
RAJOD1Really do you have AMD or Intel system?

I have a 4070 + 536.23 + Old hex core xeon and windows 10 never had a crash in D4. I just use the settings that experience recommends which is maxed out.
7950X + 4090 on win 11, it's been fine for the first couple of weeks, then started crashing. I also run undervolted and FPS limited to 144. Either crash to desktop, hard reset or freeze. Really annoying if it happens while you've almost cleared a dungeon. But it also does like to happen in town, when opening inventory.
Posted on Reply
#12
RAJOD1
igralec847950X + 4090 on win 11, it's been fine for the first couple of weeks, then started crashing. I also run undervolted and FPS limited to 144. Either crash to desktop, hard reset or freeze. Really annoying if it happens while you've almost cleared a dungeon. But it also does like to happen in town, when opening inventory.
Well you have a very nice cpu. Were you over clocking the ram or cpu? Mines is stock no OC, and ECC ram. Did you do a mem test just to make sure its not a hardware ram issue?
Posted on Reply
#13
igralec84
RAJOD1Well you have a very nice cpu. Were you over clocking the ram or cpu? Mines is stock no OC, and ECC ram. Did you do a mem test just to make sure its not a hardware ram issue?
The CPU is undervolted with CO and i think i have +50mhz or even 0, forgot. RAM is a different story, i bought it according to the QVL list for the mobo but 6400 doesn't work at all, so i'm using a custom 6200 setting. Spent hours refining it and testing it, so should be stable as i've probably played 200 hours on the current settings. Also none of the Diablo 4 betas crashed not even once, so no sure what the problem is.
Posted on Reply
#14
RAJOD1
Does it crash the entire computer or just the game? Blue screen, reboot? Can you reload the game right after a crash or do you reboot the entire pc? Maybe run your ram slower like underclock it and see if any diff. could be just a driver issue. Do you have cpu z, or any new monitoring programs running at the same time? I've had cpuz cause a lock up on me before.
Posted on Reply
#15
igralec84
Yesterday the game crashed like 3 times in a row, before a hard reboot. The RAM actually is underclocked as for some reason ASrock gave QVL to an intel kit, so no way to make it run at it's original speed. It's interesting that just game crashes were usually too much GPU undervolt (i've recently gone from 2730mhz @0.95v to 2700mhz), but is also crashed without the UV. The hard reboots were usually unstable RAM or too much CPU undervolt, but it's very rare and it has to be one specific core that causes it. Not running any monitoring software except for NZXT CAM for the AIO. Yesterday i was running HWinfo before the hard reboot, to see if maybe the RAM is overheating, but didn't log it, so no idea.

But still, i haven't had a single crash during all the betas and i haven't changed anything, other than updated GPU drivers as soon as they're available. Well maybe the room temp has gone up since March/April by around 4°C.
Posted on Reply
#16
Chomiq
igralec84Yesterday the game crashed like 3 times in a row, before a hard reboot. The RAM actually is underclocked as for some reason ASrock gave QVL to an intel kit, so no way to make it run at it's original speed. It's interesting that just game crashes were usually too much GPU undervolt (i've recently gone from 2730mhz @0.95v to 2700mhz), but is also crashed without the UV. The hard reboots were usually unstable RAM or too much CPU undervolt, but it's very rare and it has to be one specific core that causes it. Not running any monitoring software except for NZXT CAM for the AIO. Yesterday i was running HWinfo before the hard reboot, to see if maybe the RAM is overheating, but didn't log it, so no idea.

But still, i haven't had a single crash during all the betas and i haven't changed anything, other than updated GPU drivers as soon as they're available. Well maybe the room temp has gone up since March/April by around 4°C.
If event viewer shows WHEA errors it's most likely due to unstable RAM or CO.
Posted on Reply
#17
igralec84
ChomiqIf event viewer shows WHEA errors it's most likely due to unstable RAM or CO.
I think i've only seen a WHEA error once and it said which core it was, but that was using core cycler or OCCT iirc, when i was doing the CO manually for each core. Need to check yesterday's events as there should be 4 crashes between 8.30 PM and 10PM in there. Really annoying if a quest takes long enough to crash, but at least i keep the XP and loot lol.

EDIT: the only event is that display driver has crashed and recovered, but that was only the first crash i think. Maybe i'll try to disable DLSS 3 and Reflex, probably don't need them for 4K 144fps anyway.
Posted on Reply
#18
RAJOD1
igralec84Yesterday the game crashed like 3 times in a row, before a hard reboot. The RAM actually is underclocked as for some reason ASrock gave QVL to an intel kit, so no way to make it run at it's original speed. It's interesting that just game crashes were usually too much GPU undervolt (i've recently gone from 2730mhz @0.95v to 2700mhz), but is also crashed without the UV. The hard reboots were usually unstable RAM or too much CPU undervolt, but it's very rare and it has to be one specific core that causes it. Not running any monitoring software except for NZXT CAM for the AIO. Yesterday i was running HWinfo before the hard reboot, to see if maybe the RAM is overheating, but didn't log it, so no idea.

But still, i haven't had a single crash during all the betas and i haven't changed anything, other than updated GPU drivers as soon as they're available. Well maybe the room temp has gone up since March/April by around 4°C.
Run everything at stock and turn off ALL monitoring software. No HWinfo NZXT CAM etc. Clean out the game cache in case of corruption.

Something changed since the beta. Did you remove the beta files and install the game fresh? As in a retail installation with the gpu drivers you were using? Could be a conflict with the snooping software like HW info and the game. Do you have the Max fps set to a fixed number like 120fps or is it unlimited fps? I would like to think my 32 gigs of ECC is the reason I get no crashes but I doubt it.

Does it pass mem test? You have to create a boot USB or CD for mem test.
Posted on Reply
#19
igralec84
RAJOD1Run everything at stock and turn off ALL monitoring software. No HWinfo NZXT CAM etc. Clean out the game cache in case of corruption.

Something changed since the beta. Did you remove the beta files and install the game fresh? As in a retail installation with the gpu drivers you were using? Could be a conflict with the snooping software like HW info and the game. Do you have the Max fps set to a fixed number like 120fps or is it unlimited fps? I would like to think my 32 gigs of ECC is the reason I get no crashes but I doubt it.

Does it pass mem test? You have to create a boot USB or CD for mem test.
I'll do a BIOS update as i haven't done it for almost half a year and try leaving everything standard, RAM at 4800 or whatever the JEDEC speed is. I did have a good Wednesday with 1.5h of no crashes and yesterday around 3 hours with only one crash while playing. Seems like not running +500 memory OC on the 4090 helps a bit, or it's just random. But 2 mins after closing the game, i had a BSOD faulty hardware corrupted page while browsing reddit, so hmm :confused:

I did a fresh install after beta, maybe a reinstall could be a good idea. I don't really run HWinfo, but NZXT CAM needs to run to have a custom fan and pump curve sadly. I have max foreground FPS limited to 144 as the display is 144hz, background to 30fps. It does seem that most of the crashes, freezes or reboots happen in town the moment i open inventory.

I haven't tried the outside of windows mem test, only the ones testers here use for their overclocks, but you can only test like 25/32GB of it. Does pass 12000% and 3+ hours without errors though, or it did back in winter.

Oddly, i haven't had any crashes in 50+ hours of Cyberpunk 2077, The Witcher 3 (well that one had some DLSS problems) or Forza Horizon 5 this year on the current setup.
Posted on Reply
#20
igralec84
Happy to report, after updating BIOS, setting the CPU CO to -10 all core and leaving RAM at 4800, and also not running any memory OC on the 4090 with the UV, it hasn't crashed since. Not sure how much of a performance hit the RAM caused, but i can try +500 or 1000 memory OC on the GPU to probably get it back :D
Posted on Reply
#21
RAJOD1
igralec84Happy to report, after updating BIOS, setting the CPU CO to -10 all core and leaving RAM at 4800, and also not running any memory OC on the 4090 with the UV, it hasn't crashed since. Not sure how much of a performance hit the RAM caused, but i can try +500 or 1000 memory OC on the GPU to probably get it back :D
Nice job!!!
I stopped overclocking years ago, just a fad not worth it unless you just like to fiddle and create work debugging.
Posted on Reply
Add your own comment
May 21st, 2024 16:45 EDT change timezone

Latest GPU Drivers

New Forum Posts

Popular Reviews

Controversial News Posts