Recent NVIDIA Drivers Causing Crashes (40 series cards only) - RESOLVED


CarrieS
 Share

Go to solution Solved by Taylor_B,

Recommended Posts

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. 

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

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).

Link to comment
Share on other sites

@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. 

 

image.thumb.png.44af984fc51cfebabd2904455992440f.png

 

Link to comment
Share on other sites

  • 2 weeks later...

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.

  • Upvote 2
Link to comment
Share on other sites

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.

  • Upvote 3
Link to comment
Share on other sites

  • 2 weeks later...
On 8/7/2026 at 7:58 AM, DrawingABlank said:

May I ask, what do you mean by deadlock?

 

I’m referring to a classic circular dependency of accountability — a sociotechnical wait state where progress permanently halts.

In a standard compute deadlock, Thread A waits on Thread B, and Thread B waits on Thread A.

Link to comment
Share on other sites

Got it. Don't understand entirely but understand it sounds different than what I thought. Thanks for the reply.

 

I experienced basically a loop installing driver where pc thinks it is the wrong GPU so it fails. GPu becomes useless. Dead.

The solution was to start install process and after the .exe performed the initial extracting and file prep you save those file contents elsewhere so you can get into the 'black box' contents and work with them manually.

 

Edited by DrawingABlank
Link to comment
Share on other sites

I don't use Cheif Architect applications, I'm just desperate to find a way to get my RTX 4050, a studio-ready NVIDIA driver, and some Python+CuDa packages to cooperate.

I am slightly relieved to see it's not just me. Sorry to be... Shadenfreude (one who takes joy in others' pains).

Link to comment
Share on other sites

  • 2 weeks later...
  • Solution
3 hours ago, josecarlos said:

UPDATE: Version 616.56 is now working.

 

Please see details for Studio Driver 616.56 here:

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

 

So far as we've seen, this new driver does appear to resolve the crashes we've been seeing with 40-series RTX cards.

If you continue to experience issues after installing this new driver, please contact Technical Support.

  • Like 2
Link to comment
Share on other sites

  • BrianBeck changed the title to Recent NVIDIA Drivers Causing Crashes (40 series cards only) - RESOLVED

Never had problems with this crash in my office....until today. One of my employees updated X18 to the latest and it now causes crashes. They have a 4070 ti Super. They were working on some plans just fine on X18 after the X18 update (I believe projects that were started in X18). They then brought an X16 plan forward and it crashes every time they open it. We updated to the latest Nvidia driver with no fix. Downgraded driver to the listed 596.36 and that fixes it. Opening the offending plan on my system with a 50 series card, the latest X18 update and the latest Nvidia driver has no issues.  So don't know if it's the plan, the software, the hardware, etc...but it is definitely related to the Nvidia driver and possibly the X18 update?? since the downgraded driver fixes the issue.

 

So apparently not out of the woods yet..??  Have not tested this further...needed them to get to work :)   so will keep them on the old driver until further notice.

 

PS: didn't see if other plans crashed before the driver downgrade or just that one, etc.

PSS: I just realized that I do have another 40 series computer in the office that I will test this and other plans on a bit later, along with the drivers

Link to comment
Share on other sites

@BenPalmerOur Technical Support Team has not encountered any problem with the new driver yet. If you have a plan that might interact with it please send it in to our Technical Support team. We would then be able to diagnose the problem and it will have a much higher chance of getting fixed. 

Link to comment
Share on other sites

@CarrieS I believe you are correct. After some time, the referenced computer and that specific plan on X18 began to crash, even with the rolled back driver. I will try to reproduce the problem and send to tech support and concede this is likely a different issue than the Nvidia crash referenced in this thread.

  • Upvote 1
Link to comment
Share on other sites

I installed 616.56 on my laptop (4060) and my desktop (4070).  When I'm using my laptop, the white background in chief architect randomly shifts back and forth from a warm white to a very bright, cold white, primarily in camera views.  Everything else seems fine, but the color shift is super annoying.

Link to comment
Share on other sites

I just used the Nvidia app to download the unified driver.  AFAIK, the unified driver functions for all cards on any computer on windows, but I will look into it later.

 

I'm guessing it's Nvidia, Windows, and MSI all fighting for control of color schemes.  Wasn't an issue prior to this driver version.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share