If I understand well, you did upgrade nvidia drivers then your station did not boot after that ? And motherboard bios as been corrupted ? Is that what happenned ?
And starting in safe mode (shortcuts when computer is booting) is no longer avalaible ?
I have the opposite view. If I can upgrade, I will do it. As a rule, it makes your PC or software better and your PC more secure. But of course, not if I’m doing an important job. Then I wait.
Intel I7 - RTX 5060 8GB, and I had exactly the same issue, after installing the latest Studio Driver 616.56. Reverting back to the previous Studio Driver 610.88, resolved the issue.
Not always. Sometime it is good for your software, often it does nothing sensible, and sometime (very rare) it creates glitches that need to be debugged.
My fear us it was caused by their update but do you see them doing a fix? With PL 10 due its not going to get a good start relying on Nvidia doing a fix and I suspect its going to be DXO having to work round ut again
If there’s a real bug on a driver release, better to DxO to say not to use these version and wait the next one than make tricky things to get around the problem. If it is some change in handling things, then DxO will have to make the move anyway.
This is now worse for me. All was better than partly cloudy using compatibility mode, but now that does not work either. I’m running Windows, and after the August update immediately noticed issues, as did many using Nvidia. It is more fun to blame Microsoft, and in this case it is likely accurate.
Keeping Windows, and probably also MAC OS, and other programs updated secure your computer from many known vulnerabilities used by with bad intent. And normally other problems in the apps you run on your computer are improved for the better.
I even downgraded to version 610.88, but with no success—the export still hangs without throwing any error whenever I use the denoising feature.
It would be highly beneficial if DxO implemented a built-in diagnostic or troubleshooting tool under the ‘Help’ menu. Right now, it takes hours of trial and error with different drivers just to figure out what is wrong. A quick automated check to flag known driver issues would be a massive help for the community.
There’s a general problem with 616.56 but if you have problems with 610.88 there’s a specific(to you) problem. I’ve not upgraded yet and 610.88 works without problems(RTX 4090).