Frequent random hangs with RTX5080 and 2025.32460

[flogiston]

Hello!

Unfortunately I have a recurring issue with TD hangs on my RTX5080 laptop (Lenovo Legion).

My project runs fine for a random amount of time (it could be anything between 30 minutes to 2 hours), but eventually freezes and I can’t see any specific pattern (like content, UI interaction/parameter changes or extreme load). Obviously this is a deal breaker for a live show and I can’t find a solution. My project uses two Engine COMPs running with independent clocks (though this setting doesn’t help), loading different scenes and blending them (it’s a VJ deck). The problem occurs both in perform mode and without it. GPU is not pushed to the limit at all with at least 50-60% of headroom with the most intense scenes and post-fx. I’m not using any NVidia OPs. I’ve never encountered a hang running a single tox that I’m loading into the Engine COMPs.

Based on the stack trace, the deadlock happens between the OS and NVidia (win32u!NtDxgkSubmitPresentToHwQueue+0x14).

I’m runnning both the latest Studio Driver (596.36) and TD (32460). It also used to freeze with the previous NVidia driver (595.79) and I waited for the update hoping for the best.

Can anybody help with troubleshooting or tell me what tweaks to try? Downgrading drivers, TD? I tried super-conservative NVidia settings, reinstalling drivers and Touch, etc. Maybe somebody solved a similar problem?

Here’s the stack trace:

win32u!NtDxgkSubmitPresentToHwQueue+0x14
nvoglv64!DrvPresentBuffers+0x2ae4f
nvoglv64!DrvPresentBuffers+0x191e
nvoglv64!DrvPresentBuffers+0x575
nvoglv64!DrvPresentBuffers+0x21e4
nvoglv64!DrvPresentBuffers+0x16ac2
nvoglv64!DrvPresentBuffers+0x349fb
nvoglv64!DrvPresentBuffers+0x13b125
nvoglv64!DrvPresentBuffers+0x148c88
nvoglv64!DrvPresentBuffers+0x1615e9
nvoglv64!DrvValidateVersion+0x6ee6
nvoglv64!DrvPresentBuffers+0x122aa1
nvoglv64!DrvPresentBuffers+0xfe7f2
nvoglv64!DrvPresentBuffers+0xfdeb9
nvoglv64!vk_gr2608GetInstanceProcAddr+0x409a3
nvoglv64!vk_gr2608GetInstanceProcAddr+0x4a140
nvoglv64!vk_gr2608GetInstanceProcAddr+0x3a379
nvoglv64!vkGetInstanceProcAddr+0x15024a
libTD!TiXmlNode::FirstChild+0x5d2f1b
libTD!TiXmlNode::NextSibling+0x2e7079
libTD!TiXmlNode::NextSibling+0x2d3576
libTD!TiXmlNode::NextSibling+0x24d76b
libTD!TiXmlNode::NextSibling+0x154aa5
libTD!TiXmlNode::NextSibling+0x155983
libTD!TER_TouchExeBase::runMain+0xc
TouchDesigner+0x107a
TouchDesigner+0x12ea
kernel32!BaseThreadInitThunk+0x17
ntdll!RtlUserThreadStart+0x2c

Thanks,
Pawel

[flogiston]

Okay, so after many multi-hour tests I can confirm this doesn’t happen when running 2025.32280 with the exact same setup.

Lenovo Legion Pro 7 Gen 10
Windows11 Home, 25H2 build 26200.8246
NVIDIA GeForce RTX 5080 Laptop GPU
NVidia driver: 32.0.15.9636 (NVIDIA 596.36) DCH / Win11 64

Hangs also happened with NVidia driver 595.79, my impression is that they were less frequent.

I ran the project on a desktop PC with 5070Ti (only 2025.32280) and it was also flawless.

I can provide the DMP file if need be.

[flogiston]

Unfortunately the problem is also present in 2025.32820 both with NVidia Studio Driver 596.36 and 610.47. Hangs within minutes. Stable under 2025.32280 with only one hang over a 8h period with high load (multiple complex scenes loaded/unloaded into two Engine COMPs and live mixed), but this one hiccup happened during quick NDI source switching operations and might have been related to that.

When I was asking around before choosing a performance laptop everybody said “get the best gear you can afford”, but now when I bought an RTX 5080 I hear “your hardware is too new”, so it’s a bit frustrating… I hope this gets some attention one day , until then I’m locked to version 32280 and can’t use any new features.

[nettoyeur]

Not sure if you tried already, but especially on a laptop, the first step is getting rid of the hidden bloatware running in the background. If you search this forum you see that bloatware has been the cause of by far the largest part of laptop TD issues. See this post from @jetxs for a tool for cleaning that up:

TouchDesigner.exe - Application Error (0xc0000142)

Hello, As a first step, make sure that all your drivers, including integrated graphic drivers, are up to date and that your machine is free of bloatware. Make sure that TouchDesigner is fully up to date to the latest stable build available. The Bulk Crap Uninstaller helps in identifying unwanted or unneeded software: https://www.bcuninstaller.com/ Find the latest driver for your GPU at Official Drivers | NVIDIA or use Nvidia Geforce Experience Update Drivers & Optimal Playable Settings You…

[flogiston]

Yes, I removed most of preinstalled crap and it didn’t help. Besides, this is obviously tied to TD version. Works with 32280, all later versions hang pretty quickly. And only when two scenes are loaded to two engines in parallel and mixed. Individual scenes never make TD freeze, so it’s some kind of synchronization issue (they are running with independent clocks).

[nettoyeur]

I recommend to email a download link to the dumpfile to support@derivative.ca together with the smallest possible network that has the reproducible crash.

[bangnoise]

Hi @flogiston - yep if you can do exactly what @nettoyeur suggests (and reference this forum thread in your e-mail), we can take a look.

[flogiston]

@bangnoise, thanks! I was able to reproduce in a simplified network, will send the report today.

[malcolm]

Thanks for the sample, we were able to reproduce the issue and plan to fix it before the next release we post.

[bangnoise]

Thanks for the report - this is fixed in the next release we post.

[ben]

@flogiston We posted 2025.30070 a couple of weeks ago, this build has a fix for the reported issue. We’d love to get confirmation its working for you now.
Thanks

[flogiston]

Hi all, sorry for the delay, confirming that the problem is gone. Awesome!