NVIDIA GeForce 496.13 WHQL driver download & Discussion

Goes it bit both ways, as there are some legit issues there are also issues caused by ignorance, even you can't deny that.
Common logic when the driver works for specific games for you and you friends on similar systems would be to state that the systems with issues are not driver related, especially when a detail being both different and important to a specific system is left out.

Apart from that, undervolting your GPU can be an issue on it's own, everything not within reference spec is on own account.
Ran into and issue myself with a factory overclocked card, solved it with a BIOS for the "better" model, but have to be careful with such, so not generally recommended, especially considering that most people bitch about the driver than look at what they messed around with.

@tty8k Can you show the man your findings regarding under/overvolt with driver changes especially regarding these newer drivers?
Can't recall in which driver release post we got in on the differences with powerlimit, voltage and frequency settings used between that driver and the one before it.

EDIT:
I might be wrong, but as I got it, when undervolting powerlimit can drive GPU frequency higher as long as temperatures are fine, meaning frequency can get up where the supplied voltage stagnates the GPU and therefor resulting with a failure (crash).

 

Had 3 system crashes with this driver in Elder Scrolls Online. Bluescreenview shows afd.sys as driver, and bugcheck 0a. No crashes with previous driver.

 

Turned out it wasn't the driver after all. Something strange going on with my ql instead. My bad!

 

Ive noticed on my 2 monitor setup sometimes windows will send some windows to the far right of the 2nd monitor when I open something on it. This usually happens when something is in full screen on the main monitor. Im constantly losing steam windows to it and even win + arrow keys dont bring it back. Its as if theres another screen space beyond the monitor.
As a result with the fact I can now run games in 4k on the main 8k tv, I cannot watch stuff in full screen on the 2nd monitor.

 

Pretty good driver for Tombraider benchmarking
Windows 11 Retail

 

I have also been having crashes with Call Of Duty Black Ops Cold War 0xC0000005 on 493.13, however it was working fine for a bit before the error came about (Before anyone says about hardware including system ram its DDR4 2133mhz non XMP which has been MemTested stable, no WHEA's nothing), I rolled back to 471.12 the game runs fine after.

I went to look for crash dumps and even event logs however found no event log reports and no crash dumps.

Do i think the driver is full 100% to blame no, do i think its the game update yes, however still can not understand why reverting back to 471.12 sorts the issue.

My system has no Overclocks on it during game play and fan curve is set aggressive.

Now the only difference i see is that 493.13 has a shader cache setting compared to 472.12 so it could be the game fills that and it just kills itself after maxing that out.

System Specs

Main Laptop: PCS Recoil 17.3" (Clevo X170KM-G)
{CPU:} Intel i5 11400 {RAM:} 4x 8GB DDR4 2133 {GPU:} Nvidia RTX 3070 Mobile
{Screen:} LG Philips LP173WFG-SPB3 144hz 1080p {Storage:} 2x M.2 SATA 1TB and 2TB Respectively
1x NVME M.2 WD SN750 Black. {OS:} Windows 10 Pro

Benchmarks: {TimeSpy}: Normal Extreme {Firestrike}: Normal Extreme {Port Royle}: Result

 

i wish i was paid to interact with the computer engineering ignorant masses, you'll be blaming drivers until the OS is out of support and your hardware has long started telling you the issue is in cache or memory directly

It seems it involves the shader baking stage generating corrupt shaders for some devices when it is performed with certain overlays enabled, GFE especially, when the faulty shader is executed a device hung occurs and the 0xC00005 is thrown because the driver reset invalidates device handles. The driver is behaving as it should in this scenario, the cause of the faulty shader is likely a defect in the latest game update.

you might be lucky and get a clean shader cache built by deleting the files under C:\ProgramData\Activision\Call Of Duty Black Ops Cold War\shadercache and restarting the game with nothing else running overlaying, and then not experience the crash again at all with 496.13

I'm afraid that the ancillary function driver cannot be 0a (Kmode Exception) bsodded by a change in the display driver, this is only interacted with by the network stack and windows kernel.

you're not using cFosSpeed at all? (its installed by Dragoncenter, among others), or game booster perhaps?

 

Its been acknowledged already so STOP misleading ppl in this case, sometimes your right sometimes your wrong thats life deal with it.

Best regards

 

so far no problems with this new driver, the cache I assigned 10gb really do not know if I will notice any difference with the default one

 

this one hard crashed my pc while playing destiny 2 - blackscreen with white elements of the hud

 

I have 10GB for the cache and it's already is 1GB
IMhO 10GB is minimum for ppl that play not only one game...

Really good release

Note:
I need to point out that im often Playing games & listen to YT Music using F.Fox (especially for Forza H4 & NFS Heat).

 

You're*

 

Mine is at default and is clocking at 866 MB rn after a clean install and me launching and shortly playing ~15 games or so.
I'd say that if you're not playing extensively more than 5 games at once then you don't need to do anything with the setting.

I also kinda wonder if driver default is even size limited? Seems like a better idea would be to limit it by time a compiled shader spent in cache than cache size really - or at least a combination of both.

 

Deleting the cache for that particular COD title has solved the issue for some that reported the issue, so unless it has been tried it's not wrong to ask someone to.

TESO works without issues when using 496.13, just ran an update on my install and checked it out last night, even did a full 496.13 driver install just to make sure.

 

Getting one random screen flicker with these drivers could be monitor or driver but never had it before ?

 

I have unlimited set as I have an 8TB drive, a 2TB drive and two SSDs that are all full of installed games Love that we finally have this feature and choice. I love to drop into a multitude of games on the fly so this is exactly how I always wanted it running.

Also, no problems as of yet so these could be a long term install for me until I get some newer games in the future.

 

Really nice drivers. I see an improvement in a few games (RDR2, Days Gone and Fallout 4 for now). And what is more important (to me), this drivers finally fixed my p-states issue. The one forcing P0 in borderless/DX12. My card is no longer stucked at max load after 9 min. Whatever was causing the memory leak it's gone with this ones.

 

It hasn't been acknowledged until the driver notes have it included in the fixed issues, the forum list of open issues are just those reported and not necessarily in the driver.

 

I'm afraid you may be out of luck.

 

Why are you going off on me about this? I simply answered your question.

Nvidia has discontinued regular driver support for Windows 7, 8 and 8.1. That's just how it is. DCH drivers aren't compatible with Windows 7 as well.

By the way, if you're that concerned about your privacy and security, using Windows 7 may not be such the best idea either. I'd recommend moving to a security/privacy oriented distro of Linux instead. But even that won't be entirely safe unless you remain disconnected from the internet (and even then NSA, FSB or whatever other spies might sneak into your house while you're asleep and access your computer physically! ).