I worked without issue also for years until did an update in Nvidia drivers, so anything is possible, some change can easily cause this unfortunately.
I noticed also same issue, the frame rate when i got the issue was very high as 60fps steady, so for sure is more of a bug or huge hardware limitation in latest GPUs and drivers than an actual stall.
I have currently wasted 4 days on addressing this issue. I was suppose to finish the produce for Friday last week, but am currently doing everytning I can to test so I can isolate the issue. I looked into how swapchains work, and it’s bizarre how anything I have found so far could cause it to happen. however, I need to isolate the issue before I can release, and I am fearing this will take the rest of the week given just how many have this problem and how many parts are potentially involved, and how frail the whole system seems to be.
Swapchains were made to handle tearing issues, so why does Unity crash with this on .Paint?
I found a swapchain crash could be 100% reproduced if “Asyncronous Shader Compilation” was disabled. This was added in Unity 2022, so projects migrating from 2021 (or earlier) will not have that option enabled by default.
Haven’t seen a crash since I enabled that, no matter which driver versions I use.
So it’s starting to look like the DX11 Swapchain issue is not caused by me, but by Unity. I have spent a few hours now doing nothing related to compute shaders, and still it crashes. It looks like it’s a GUI-issue, as it always happens on .Paint and .Repaint.
This is mad sad as so far I have lost 4 days on this so far, and I still haven’t been able to get to a release. By tomorrow it’s been a full working week. I really feel the stress caused by the missed release deadline due to this. I need to release as a lot of people were interested in trying it. I cannot let them down.
[edit] I now got this error randomly when entering playmode:

Why would a window need a connection for something that is unrelated to the testing I am doing, and why would this prevent the testing from running? This was immediately followed by a DX11 Swapchain error upon exiting the playmode.
One more update on my issue:
It seems to be isolated to .Paint and .Repaint on the Unity GUI when I have ranged sliders and Headers and Spaces, and switch between the editor and vscode/browser upon writing code and checking for API-help online. This gets called when I make an update to the C#-code as it has to rebuild the inspector view of the code, and this causes the DX11 Swapchain error to happen. I am able to do this relatively consistently now.
It really destroys my pace as I have to restart Unity a billion times daily…
I can work around it by not having the scene open which has the scripture with all the fancy and elaborate styling in it, and switch back to that scene when I need to test, but this is also a hassle.
Hello!
In my case there was a problem with integrated Intel graphics (got laptop with Intel CPU + Nvidia GPU setup) - there was just very old Intel drivers installed and it created such problems for Unity windows. After installing “Intel® Driver & Support Assistant” and updating everything Intel-related problem gone.
Good luck everyone!