I get crashes on 2023.11880 (W11); usually when updating operators, but I also got one when I’ve clicked escape to come back from perform mode.
Can’t replicate anything, or narrow down the crash cases
Here are couple of .dmp’s
TouchDesignerCrash.2023.11880_2.dmp (326.2 KB)
TouchDesignerCrash.2023.11880_1.dmp (296.7 KB)
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.
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 can also make sure that your integrated GPU is running on the latest version available via Intel Driver Assistant.
You can use the AMD Adrenalin if you have an AMD Integrated GPU, in minimal install mode, via https://www.amd.com/en/products/software/adrenalin.html
If your machine comes with a proprietary power management software (From Asus, Dell / Alienware… etc), make sure that it’s setup properly to run TouchDesigner on the Nvidia / AMD DEDICATED GPU when plugged to power. Otherwise, it’s likely that TouchDesigner would run on the integrated graphics, hence it is important to also make sure your integrated graphics are up to date.
If the issue persists, try to generate a dump using Using WinDbg to Debug Crashes - Derivative
I’m actually running a pretty fresh windows install, without integrated graphics (“KF” intel processor), and my AMD drivers are definitely fresh.
Trying out WinDbg… I might. Hard to predict the crashes, but maybe I’ll manage to catch one.
Will windbg dump be much more useful the the dumps that touchdesigner produces?
Thanks for the extra information. Both of your dump files are crashing in the same place when it is trying to update the image onscreen, but unfortunately there’s not a lot in the file to say why it is happening.
We’ve seen one case like this before, but the user was never able to repeat it, so there wasn’t really enough information to find a fix.
If you’re already getting crash dumps, WinDbg won’t make much of a difference. That is usually only helpful when touchdesigner can’t catch the crash.
One extra thing you can try is to set the environment variable TOUCH_FULL_MEM_DUMP to 1. This will create a much larger dump file, but it may give us a little more information on the full state of things when it crashed. The larger dump files compress pretty well and can be posted to any common file sharing site.
Thanks for the help.