Recent NVIDIA Drivers Causing Crashes (40 series cards only)

[CarrieS]

We are currently seeing reports that recent NVIDIA drivers are causing crashes on RTX 40-series GPUs (4060, 4070, etc). If you are using one of these cards, we recommend using the April Studio driver or earlier for now. 

https://www.nvidia.com/en-us/drivers/details/267262/

 

We are in contact with NVIDIA as it seems the problem is within the driver and not Chief Architect. We'll update this post as soon as we have more information or a confirmed fix. 

[ChiefExperts]

I had to revert back to the April 23 driver and then in worked again. 

 

Go here to get the older driver and istall it:

https://www.nvidia.com/en-us/drivers/

[KacyRSC]

Yep, can confirm. This crash has been plaguing me for weeks now on both my RTX 4070 Super desktop and 4070 work laptop. Driver 569.49 from May 12 is stable (for me).

[josecarlos]

This issue persists across three consecutive Nvidia driver updates. Currently, neither Nvidia nor Chief Architect support has provided a timeline for a fix.

[joselyn_ren]

I reverted back to the April driver and its still crashing sometimes every few minutes! Hope there is a solution soon. 

[CarrieS]

@joselyn_renWhen you install the the driver I recommend using the "Custom (Advanced)" option and choose the option for Clean Install. Sometimes remnants from previous drivers can interact and still cause crashing. Technical Support has had consistent success with this approach. Feel free to contact Support if you'd like help with the process. 

 

 

[DRAWZILLA]

has anyone tried the latest new release (today 7-28-26), is it working?

[josecarlos]

Don't update to 610.88 driver; as an end user, it’s the ultimate deadlock: the software is a closed 'Black Box' you can't fix, and neither company wants to take the blame.

[DRAWZILLA]

thanks for the info

[Smn842]

On 7/28/2026 at 8:35 PM, josecarlos said:

Don't update to 610.88 driver; as an end user, it’s the ultimate deadlock: the software is a closed 'Black Box' you can't fix, and neither company wants to take the blame.

 

As as life long software developer and architect, I can say that the big companies like Nvidia, Apply et al will never make any statements about when issues get fixed or often even acknowledge them. Even larger enterprises cannot make statements for future release due to accounting legal requirements.  CA, as a smaller company just have to wait for a fix where they have no safe workaround they can add to their code or any third party rendering code they incorporate.

 

One thing I learned many years ago was GPU drivers are one if not the biggest source of issues for graphical software and these days many applications that aren't graphical also use accelerated GPU rendering for their pretty interfaces and text rendering.  At home I run 4 desktops, 3 laptops and 8 virtualised Windows installs  (4 of which use GPU passthrough so the same as physical machines) and only do 1 or 2 GPU driver updates per year just to keep them in a fairly recent range.   Unless you're running a game or newly released hardware you're unlikely to get any benefit from the frequent GPU releases so I choose a studio driver that's been out for quite some time (and check later release notes) before upgrading and apply that to all my Windows VMs/machines in stages and considering GPU generations/models. 

 

Doing this has meant I struggle to remember my last GPU driver issue and the I similarly don't upgrade other device drivers unless there's a good reason for it.  Sadly many devices come with lots of add-on software beyond their core drivers and I always recommend to never install that unless its absolutely required for functionality (such as the Stream Decks I use).   For Nvidia I only install the core driver not the optional GeForce app software that loves to auto upgrade or nag to do it.