I can say that I ran into the same problem recently. I also have a 1060 6GB, and I got well reproducible crashes with D3D12 with certain games.
I checked it out and it revealed that the NV driver returns an error under unknown(?) circustances to the DXGI rutime inside IDXGISwapChain::Present method (when presenting a frame).
In response the DX12 runtime transitions the DX12 device into DEVICE_REMOVED state at once, which is a straight way to a crash with dgVoodoo. The DX debug layer did not report any error or warning.

So, nothing that I could handle in dgVoodoo, it's driver internals so I don't know the reason of the error either. NV should be asked about it but I don't think they'd bother with it.
The solution for me was going back to an older driver, I chosed the newest one (from 2021 december or so) from the available older ones from the NV page.
And all the crashes was gone.
Oh, and I had no problems with AMD and Intel.

My everlasting experience with NV drivers that new ones just don't fit to old hardware, no matter if they are officially supported, I always run into bugs with them.
The newest one is the D3D12 resource transition bug which I had to workaround in the latest WIP.

Thank you for your reply. How running record with OBS Studio eliminates CTD? This could be the key to fix.

But with https://github.com/elishacloud/dxwrapper/ and ForceDirect3D9On12 option no CTD in U2. BUT! With dxwrapper in Space Rangers 2 game with option ForceDirect3D9On12 i have CTD with error.

I remember reading posts on nvidia forum about bugs being fixed based on reports. There are two ways for it:

Feedback form: https://forms.gle/kJ9Bqcaicvjb82SdA
Developer bug report (need nvidia account): https://forums.developer.nvidia.com/t/how-to- … rt-a-bug/160853

https://forums.developer.nvidia.com/t/if-you- … his-first/27131

It's worth a try.

https://github.com/elishacloud/dxwrapper/issues/253

Dege what version of driver are you using? My old driver was 528.02 (2023.1.5). I try find version where good work d3d12 wrappers.

536.23

But it's strange, I'm pretty sure I installed an older one. Maybe it's been upgraded by an update.
Anyway, I get no crashes with this.

I did some research and found out the latest working version for NFS Underground 2 is 537.58. Next 545.84 version have CTD.

as far as I understand the owners 20**\30**\40** don't have this problem? I mean surely this isn't a common driver problem? Otherwise, this can be considered sabotage against wrappers.

i send report to NV. PLS ALL SEND REPORT WHO HAVE THIS PROBLEM!

Thanks!

I don't know if only the 10xx series is affected. But it can easily be the case because I guess only the driver pack is the same for all series not the drivers themselves.
And even drivers can run on different paths depending on the underlying hw.

Raven Shield still crashed even on 528.02. Apparently I didn't know about this because I didn't run the second level (Swiss Alps). Apparently these problems started a long time ago. I won't check very old drivers, there's no point in that.

Please don't stop supporting d3d11! After all, I think this is the most stable (fail-safe and working) mode.

What you thinking about OBS Studio? Why if running record no crashes?

I don't know. For me, the driver error came from presenting the scene, which could be caused by an internal scheduler (falsely) detecting too many frames or sg like that. If it is hooked and the load is less then it might alter the detection and no error code generated. Or sg like that, but it's only pure speculation from me.

in v2.82.3 CTD in R6 Raven Shield still happen, U2 didnt check (delete this game, this game uses too much deception). Iam back to latest 551.23 and toggle all games to d3d11* mode.