onnoj
onnoj
Hi, In the mean time, it seems that it's actually a device hang, and the aforementioned deadlock is just collateral damage. * The issue seems to happen less often when...
~It's a mediocre workaround, but the issue no longer seems to occur with 1ms sleep added before a present call.~ ~That version is v0.3.16~ ~The version with the original issue...
I noticed that when the deadlock occurs, there are various messages written to the windows event log: * System (source: nvlddmkm) > The description for Event ID 153 from source...
[nvkernelcrashes.zip](https://github.com/user-attachments/files/19395346/nvkernelcrashes.zip)