WOW! I can confirm that the Nvidia Studio Driver 431.70 is stable, FASTER and uses both the GPU and CPU on my GTX 1080 Ti in iRay. Thanks again for the tip!



https://www.artstation.com/pascalcomics
https://www.renderosity.com/users/Pascal_Comics/gallery
https://www.deviantart.com/pascalcomics/gallery

Tried the latest Nvidia Studio Driver 431.86, release date 09/04/2019.   iClone 7.6 and CC 3.1 appear OK.

CyberpowerPC, 64 GB Ram, 64bit Windows 10 Pro, Intel Core i9-10980XE 18 Core CPU,  ASUS TUF X299 Mark 1 Motherboard, ROG-STRIX-RTX2080TI-O11G-GAMING graphics card, Toshiba 3TB hard drive, 3 x Seagate 3TB hard drives, RAGNAROK 801 Full Tower, LEPA G1600 1600W power supply, Killer WI-FI 6,  ASUS PA329Q 32" 4K/UHD IPS Monitor.

Has anyone else tried out the Nvidia Studio Driver 431.86, Geforce Experience wants to download it but I do not want a repeat of what happened last time?


75% of original size (was 667x19) - Click to enlarge
Greco Arts
www.grecoarts.com

So where are we with the fix?

Nvidia usually release new drivers when big games are released; the next ones are probably Gear 5 and Borderlands 3, so a new driver should be on its way.

What I do not understand is "who is at fault"; did Nvidia driver break CC3? Did CC3 broke with the new drivers? (they sound the same, but they are very different); because I can't really be bothered do wait for Nvidia to fix a problem, if the problem is affecting only your application.

Can you please formulate in technical terms, what is causing this issue with CC3? I used to work in Nvidia in their drivers division; so I think I can send a message or 2 on their way; to get this sorted out.
If the issue is in your application, a patch that fix the issue would be not only appreciated, but probably expected in a short timeframe. I was not able to open the app for a month now;it is not a matter of few days; and I expect that people here depending from this software for working, are quite disappointed.

Hopefully this will be resolved soon; with the rate at which we update drivers these days, if apps stop working for a month every few months; we won't get anything done anymore.

So I was able to run iC7.6 and CC3.1 with the most recent studio driver that was released on September 4th. It is 431.86. Note that the studio drivers do not have matching version numbers to the game drivers.

Make sure you do a custom install and check the box for a clean install, so it completely removes your old driver.

Just incase this may help,    i had same problem iClone 7.6 would not open after uodating driver (nvidia)  BUT C.C3 would open so i had a character ready and i thought lets see wha happens if i try to export the character to iClone.

So i exported …  send to iclone and it worked…….iclone opened and had opened ever since ok.  wierd but it worked.

Hi, which driver # are you running on now?

I upgraded to latest 436.15 knowing I would run into issues, but just wanted to see.   
CC3 and iC7 indeed do crash following "Please Wait" (never loads).
I also tried iC7 Morph Creator, and this also crashes (basically never loads.)

Interesting, however-
3DXchange and Iray Standalone Batch Renderer load and work.

Then every time I try an .mi file in Iray Batch, I get errors that look like file referencing fails, but also mentions potential error during import itself.

431.86 studio drivers works; probably because studio drivers are usually behind the gaming drivers by a release or 2 (game drivers are the "bleeding edge" version after all).

From the log you posted, seems that some API has changed or a module is missing; which is why the app is failing. Other apps may run because they do not use the API call that is affected by the changes

This topic looked like the were discussing API and new drivers, in some context...

https://devtalk.nvidia.com/default/topic/522598/what-is-the-difference-between-runtime-and-driver-api-/

this post, in above link, looked narratively like scenarios we have been imagining:


How could a newer driver make a difference for an existing CUDA application? Here is what I can think of oo the op of my head:

[1] The application uses JIT compilation, either on purpose or inadvertently (missing SASS for the GPU architecture in use). The driver will frequently contain a newer version of PTXAS then ships with the offline compiler.

[2] There was a functional change to an existing CUDA API. This is extremely unlikely at this point and any occurrence would presumably be well communicated by NVIDIA.

[3] The application inadvertently relies on undefined behavior, and the driver artifacts in older drivers that made the code work by chance no longer exist. That is a fairly frequent scenario in my experience, as programmers have a tendency to consider whatever works with current software as specified and guaranteed behavior, even if the specification actually disagrees.

[4] A driver bug was introduced with the newer driver. It is likely that a couple of instances of this occur with every new driver release. Mostly these would be minor issues, or issues affecting infrequently occurring corner cases, as these are easiest to miss during QA.