Help! how to bug hunt slicer crashing...
Help! slicer 2.5.0 crashes after 15 seconds or so, every time I open it. Occasionally I get a blue screen and the whole machine restarts. (I have seen this occasionally doing other things in the last 6 months... so suspect a driver issue, but am at a loss as to what, though my NVidia drivers feel the most likely culprit-I should say I don't run any games, though have been running stable diffusion which uses the GPU and seems unstable at times).
My laptop (a gigabyte p57v7 with 2.80 gigahertz Intel Core i7-7700HQ Intel(R) HD Graphics 630 Display adapter, NVIDIA GeForce GTX 1070 GPU) is running windows 10 home edition x64. I have installed all Microsoft updates, used intel's driver updater to update all drivers, installed the latest nvidia "studio" drivers (released December), and updated my 3dConnexion mouse (which used to work fine with it, and still does until it crashes!)). I had earlier versions of slicer working, but have had 9 months or so away from 3d printing, and thought I'd update slicer to the latest version, prior to doing more work with it. I've uninstalled and reinstalled slicer...and uninstalled/ installed v 2.3.1 2.3.3 and 2.4.2 and they all have this crashing behaviour, so I’m fresh out of ideas what to try next.
Any suggestions on how to bug hunt this?
thank you hive mind!
RE: Help! how to bug hunt slicer crashing...
Usually is the nvidia drivers. You can start PS from a modified shortcut to use software rendering. Not as quick as using a graphics card but if it keeps crashing then slower is better than never. Also it would then tend to confirm its the nvidia drivers.
RE: Help! how to bug hunt slicer crashing...
Thank you ! Looking at the windows error logs, indeed there are a number of Nvidia openGL driver Errors logged, requiring an application close. mmm. eg
A TDR has been detected.The application must close.
Error code: 7 (pid=14316 tid=5484 prusa-slicer.exe 64bit)
Some googling tells me : What is TDR in Windows?
TDR is an abbreviation for Timeout, Detection, and Recovery. It's a windows component. Whenever you receive this error, the Graphics card stops responding and Windows will stop to fix the driver error.
so your hunch I think is right. How do I force from a shortcut software rendering? I've had a look at the shortcut options, and although there are compatibility modes, none o them offer software rendering....? meanwhile I'll see if I can track down how to fix the underlying recurring TDR error ... and try and post an update if this helps someone in the future...
RE:
Mmmm so I changed i.e. added the TdrDelay registry setting to 60, which stopped it crashing swiftly : but now, after perhaps 30 seconds of using it (during which there can be period of a few seconds of it apparently being frozen, but it comes back, then a different message : "application has been blocked from accessing graphics hardware" even more perplexing ! apparently google tells me to check the graphics drivers, and I have the latest stable nvidia ones. Irritating : as the card must be 5 years old, so its not like this should be bleeding edge hardware/software !
RE: Help! how to bug hunt slicer crashing...
You add the switch --sw-render to the start shortcut. That tells PS to use software rendering.
You can also launch in console mode to capture the log from PS using prusa-slicer-console.exe --sw-render --loglevel=5 (or it might be 9) but thats only usually used when sending stuff to the devs on github.
RE: Help! how to bug hunt slicer crashing...
ahhh thank you so much ! I was unaware of that switch. that will probably be a good work around for me till I can get the graphics card/ drivers properly working, really helpful. Thank you.
RE: Help! how to bug hunt slicer crashing...
Has this issue been resolved yet? I've been forced to stay on 2.5.2 if I want hardware rendering. I can run 2.6.x with the --sw-render switch, but it way slow.
I have the current drivers for my nvida graphics card, Asus 3060 Ti
The 2.6.x installs, removes any previous version and then I get this error if I try to run without the switch, and then it closes.
Anyone sort out how to make this work with hardware rendering?
RE: Help! how to bug hunt slicer crashing...
Correction, after installing the latest nvidia drivers, I cannot even use the switch --sw-render to run 2.6.0 or 2.6.1
With the switch, it does nothing when I try to open it. As already mentioned, without the switch, I get the error and it closes.
Any ideas?