2.5.0 error on startup I receive "Unhandled unknown exception; terminating the application" #9370

MiFixIt87 · 2023-01-07T17:28:45Z

Description of the bug

At startup I receive the following error

when I click OK to that I receive the following:

I have searched for information on this error and one thread indicated that it was related to an NVIDIA graphics setting. I checked my NVIDIA settings and mine are correct.

My system is:

Prusa Slicer 2.5.0+Win
Dell Precision 7760
Intel UHD Graphics (only using the built-in display)
NVIDIA RTX A6000 graphics (No external displays connected)
32GB RAM
1TB NVMe SSD

I had this same issue with Prusa Slicer 2.4.0 and upgraded to 2.5.0 hoping it would cure the issue.
It never proceeds to a point where I can export the configuration or configure printers.

Any ideas?

Project file & How to reproduce

Start Prusa Slicer or try to 3d print from Fusion 360 with Prusa Slicer set as the application to print to.

Checklist of files included above

Project file
Screenshot

Version of PrusaSlicer

2.5.0 Windows

Operating system

Windows 11 pro

Printer model

never gets that far before crashing

kubispe1 · 2023-01-08T15:53:31Z

Hi, there is quite similar issue #9178.

MiFixIt87 · 2023-01-08T18:12:59Z

I saw that before I posted and I tried the solution that worked for the OP ( see the NVIDIA setting screenshot in my post) and it did not resolve my issue.

MiFixIt87 · 2023-01-08T18:13:47Z

Closed accidentally, issue is not resolved.

jrwaters2 · 2023-01-12T04:17:53Z

I'm having the same issue with PrusaSlicer 2.5.0 and my Nvidia settings are to allow the application to decide.

I did have an unexpected Windows shutdown earlier that I suspect is the trigger. PrusaSlicer 2.5.0 has been working fine for weeks before the event today.

My PrusaSlicer.ini file does not look corrupted - I didn't try to manually compare the MD5 but there is no garbage in the ini file. Also the .ini.bak file matches the main .ini file. There are 7 other ini files in my PrusaSlicer roaming profile and none of them have any garbage / apparent corruption.

I also tried removing my .ini and .ini.bak file temporarily and that made no difference.
I've also tried repairing my installation which didn't help.
I've tried other NVIDIA settings which had no impact.
I booted my system with 3rd party services disabled and that had no impact.
I don't see anything in the Windows Event Viewer logs but not certain what events I might look for.

Interestingly, if I run prusa-slicer-console.exe --sw-renderer, the error does not happen

This may be a workaround for me in the coming days - not yet sure. I have to see if all the functionality still works.

I ran prusa-slicer-console .exe normally (i.e. not using sw rendering) with loglevel 5 and got the following output

C:\Program Files\Prusa3D\PrusaSlicer>prusa-slicer-console.exe --loglevel 5
[2023-01-11 21:15:18.500842] [0x00000c0c] [trace] Initializing StaticPrintConfigs
[2023-01-11 21:15:18.510474] [0x00000c0c] [debug] full path: 17328539711037480854
[2023-01-11 21:15:18.511476] [0x00000c0c] [debug] single instance: undefined. other params: prusa-slicer-console.exe;--loglevel;5
[2023-01-11 21:15:18.511476] [0x00000c0c] [debug] init wx instance checker 17328539711037480854.lock C:\Users\myusername\AppData\Roaming\PrusaSlicer\cache
[2023-01-11 21:15:18.517696] [0x00000c0c] [info] Instance check: Another instance not found or single-instance not set.
[2023-01-11 21:15:18.518714] [0x00000c0c] [trace] System language detected (user locales and such): en_US
[2023-01-11 21:15:18.519707] [0x00000c0c] [trace] Best translation language detected (may be different from user locales): en_GB
[2023-01-11 21:15:18.519707] [0x00000c0c] [trace] Switching wxLocales to en_GB
[2023-01-11 21:15:18.543707] [0x00000c0c] [debug] boost::filesystem::permisions before copy error message (this could be irrelevant message based on file system): The system cannot find the file specified
[2023-01-11 21:15:18.595706] [0x00000c0c] [info] Checking if indices need to be installed from resources...
[2023-01-11 21:15:19.114479] [0x00000c0c] [trace] No 3DConnexion device detected
[2023-01-11 21:15:19.116479] [0x00000c0c] [info] Undo / Redo snapshot taken: New Project, Undo / Redo stack memory: 0MB WorkingSet: 87MB; PrivateBytes: 73MB; Pagefile(peak): 73MB(75MB)
[2023-01-11 21:15:19.182938] [0x00000c0c] [debug] BuildVolume bed_shape clasified as: Rectangle
[2023-01-11 21:15:19.234929] [0x00000c0c] [debug] boost::filesystem::permisions before copy error message (this could be irrelevant message based on file system): The system cannot find the file specified
[2023-01-11 21:15:19.247929] [0x00000c0c] [debug] boost::filesystem::permisions before copy error message (this could be irrelevant message based on file system): The system cannot find the file specified
[2023-01-11 21:15:19.264732] [0x00000c0c] [debug] boost::filesystem::permisions before copy error message (this could be irrelevant message based on file system): The system cannot find the file specified
[2023-01-11 21:15:19.275743] [0x00000c0c] [debug] boost::filesystem::permisions before copy error message (this could be irrelevant message based on file system): The system cannot find the file specified
[2023-01-11 21:15:19.284743] [0x00000c0c] [debug] boost::filesystem::permisions before copy error message (this could be irrelevant message based on file system): The system cannot find the file specified
[2023-01-11 21:15:19.294886] [0x00000c0c] [debug] boost::filesystem::permisions before copy error message (this could be irrelevant message based on file system): The system cannot find the file specified
[2023-01-11 21:15:19.411919] [0x00000c0c] [error] Unable to parse version of AMD driver.
[2023-01-11 21:15:19.571093] [0x00000c0c] [info] Checking for cached configuration updates...
[2023-01-11 21:15:19.572092] [0x00000c0c] [info] Confing bundle not installed for vendor Anycubic, skipping:
[2023-01-11 21:15:19.573093] [0x00000c0c] [info] Confing bundle not installed for vendor Artillery, skipping:
[2023-01-11 21:15:19.574103] [0x00000c0c] [info] Confing bundle not installed for vendor BIBO, skipping:
[2023-01-11 21:15:19.576092] [0x00000c0c] [info] Confing bundle not installed for vendor Creality, skipping:
[2023-01-11 21:15:19.577093] [0x00000c0c] [info] Confing bundle not installed for vendor Elegoo, skipping:
[2023-01-11 21:15:19.578105] [0x00000c0c] [info] Confing bundle not installed for vendor FLSun, skipping:
[2023-01-11 21:15:19.579101] [0x00000c0c] [info] Confing bundle not installed for vendor gCreate, skipping:
[2023-01-11 21:15:19.580092] [0x00000c0c] [info] Confing bundle not installed for vendor INAT, skipping:
[2023-01-11 21:15:19.581094] [0x00000c0c] [info] Confing bundle not installed for vendor Infinity3D, skipping:
[2023-01-11 21:15:19.582092] [0x00000c0c] [info] Confing bundle not installed for vendor Jubilee, skipping:
[2023-01-11 21:15:19.583092] [0x00000c0c] [info] Confing bundle not installed for vendor LulzBot, skipping:
[2023-01-11 21:15:19.606142] [0x00000c0c] [debug] Vendor: Prusa Research, version installed: 1.5.1, version cached: 1.5.5
[2023-01-11 21:15:19.635153] [0x00000c0c] [debug] PresetUpdater: Copying "C:\Users\myusername\AppData\Roaming\PrusaSlicer\cache\PrusaResearch.idx" -> "C:\Users\myusername\AppData\Roaming\PrusaSlicer\vendor\PrusaResearch.idx"
[2023-01-11 21:15:19.639152] [0x00000c0c] [debug] boost::filesystem::permisions before copy error message (this could be irrelevant message based on file system): The system cannot find the file specified
[2023-01-11 21:15:19.650152] [0x00000c0c] [info] Confing bundle not installed for vendor RatRig, skipping:
[2023-01-11 21:15:19.651153] [0x00000c0c] [info] Confing bundle not installed for vendor Snapmaker, skipping:
[2023-01-11 21:15:19.653153] [0x00000c0c] [info] Confing bundle not installed for vendor TriLAB, skipping:
[2023-01-11 21:15:19.654152] [0x00000c0c] [info] Confing bundle not installed for vendor Ultimaker, skipping:
[2023-01-11 21:15:19.655153] [0x00000c0c] [info] Confing bundle not installed for vendor Voron, skipping:
[2023-01-11 21:15:19.659153] [0x00000c0c] [info] Confing bundle not installed for vendor Zonestar, skipping:
[2023-01-11 21:15:19.660152] [0x00000c0c] [error] Uncaught exception: Calling AppConfig::save() from a worker thread!

My system is an HP Laptop - ZBook Firefly with Windows 10.

I'd be happy to run a diagnostic build if that helps.

jrwaters2 · 2023-01-15T04:02:24Z

The normal PrusaSlicer.exe also accepts the parameter --sw-renderer. For now, I've just created a shortcut and all is working fine. Of course would love to get back to normal rendering at some point, but for the desperate:

MiFixIt87 · 2023-01-15T14:14:31Z

I tried your workaround for my issue, and it works on my system as well.
If you do find a solution that allows for hardware graphics, please post it here or DM me if possible.
Thank you very much!!!!!

Tux0Topo · 2023-01-17T21:44:47Z

Also having the same issue.
Notebook, with Windows 11, intel i7 11th gen + RTX 3080.
--sw-renderer is a bypass.
Any one knows if the lack of HW renderer will be that bad?

jrwaters2 · 2023-01-18T05:58:47Z

Also having the same issue. Notebook, with Windows 11, intel i7 11th gen + RTX 3080. --sw-renderer is a bypass. Any one knows if the lack of HW renderer will be that bad?

Its been fine for me. Not saying I like the idea but performance-wise I don't notice a difference for what I'm doing.

kubispe1 · 2023-02-03T14:30:28Z

Have you tried also 2.6.0? alfa 2? Please? Can you check ?

Tux0Topo · 2023-02-03T15:48:41Z

Same error with Versión 2.6.0-alpha2+win64.

Tux0Topo · 2023-02-03T19:43:57Z

alpha3 also having the same problem!

jrwaters2 · 2023-02-04T14:52:51Z

Of course - will definitely let you know. Been experimenting with driver upgrades. So far no luck.

…

On Sun, Jan 15, 2023 at 6:14 AM MiFixIt87 ***@***.***> wrote: I tried your workaround for my issue, and it works on my system as well. If you do find a solution that allows for hardware graphics, please post it here or DM me if possible. Thank you very much!!!!! — Reply to this email directly, view it on GitHub <#9370 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQBXO33JN6OQPIU2HJ22JXDWSQA5DANCNFSM6AAAAAATUB6VVA> . You are receiving this because you commented.Message ID: ***@***.***>

Jeroen6 · 2023-02-06T08:03:23Z

Can confirm this issue on Dell 3571, Windows 11 Pro (10.0.22621 Build 22621) and NVIDIA T600 driver 517.66 for prusaslicer 2.5.0 and alpha3.

Dell pushed driver updates for video in january. Maybe those are of help.
NVIDIA Txx0/Txx00/RTX Ax00/RTX Ax000/GeForce MXx50 Graphics Driver - A04
Intel UHD/Iris Xe Graphics Driver and Intel Graphics Command Center Application - A09

--sw-rendered does help

bubnikv · 2023-02-07T15:18:58Z

Hopefully fixed with 8472287
Implementing a test whether the current thread is the main (UI) thread
and using it on AppConfig::save() to assert if save is called
from a worker thread.
The old assert was using thread names, which did not always work
on Windows.

MichalBuzek · 2023-02-10T08:44:44Z

I have the same error with PrusaSlicer-2.6.0-alpha3+win64-202302031521_signed
on
Dell Precision 5570
Windows 11 10.0.22621 N/A Build 22621
Nvidia RTX A1000 Driver version: 31.0.15.1766
12th gen Intel i7-12800H
NVMe PC801
32GB ram

lukasmatena · 2023-02-10T10:44:25Z

@MichalBuzek That is expected. @bubnikv's fix was done after alpha3, so the first version to test the fix will be 2.6.0-alpha4.

Renbrant · 2023-02-14T15:16:03Z

--sw-renderer

This resource did not work for me.

and using it on AppConfig::save() to assert if save is called from a worker thread. The old assert was using thread names, which did not always work on Windows. Fixes #7839 #9178 #9370 #9420

Tux0Topo · 2023-02-20T17:43:52Z

ITS FIXED ON ALPHA 4!!!
Great!!! Thanks!!

lukasmatena · 2023-02-20T19:06:32Z

@Tux0Topo Thanks for the update. Closing.

MiFixIt87 closed this as completed Jan 8, 2023

MiFixIt87 reopened this Jan 8, 2023

kubispe1 added the 2.6.0 label Jan 20, 2023

kubispe1 mentioned this issue Jan 23, 2023

Internal error: Calling AppConfig::save() from a worker thread! Nvidia GPU error new driver. #9420

Closed

2 tasks

kubispe1 added the awaiting response label Feb 3, 2023

kubispe1 removed the awaiting response label Feb 3, 2023

kubispe1 removed the 2.6.0 label Feb 7, 2023

lukasmatena closed this as completed Feb 20, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

2.5.0 error on startup I receive "Unhandled unknown exception; terminating the application" #9370

2.5.0 error on startup I receive "Unhandled unknown exception; terminating the application" #9370

MiFixIt87 commented Jan 7, 2023 •

edited

Loading

kubispe1 commented Jan 8, 2023 •

edited

Loading

MiFixIt87 commented Jan 8, 2023

MiFixIt87 commented Jan 8, 2023

jrwaters2 commented Jan 12, 2023 •

edited

Loading

jrwaters2 commented Jan 15, 2023

MiFixIt87 commented Jan 15, 2023

Tux0Topo commented Jan 17, 2023

jrwaters2 commented Jan 18, 2023

kubispe1 commented Feb 3, 2023

Tux0Topo commented Feb 3, 2023

Tux0Topo commented Feb 3, 2023

jrwaters2 commented Feb 4, 2023 via email

Jeroen6 commented Feb 6, 2023

bubnikv commented Feb 7, 2023

MichalBuzek commented Feb 10, 2023

lukasmatena commented Feb 10, 2023 •

edited

Loading

Renbrant commented Feb 14, 2023

Tux0Topo commented Feb 20, 2023

lukasmatena commented Feb 20, 2023

2.5.0 error on startup I receive "Unhandled unknown exception; terminating the application" #9370

2.5.0 error on startup I receive "Unhandled unknown exception; terminating the application" #9370

Comments

MiFixIt87 commented Jan 7, 2023 • edited Loading

Description of the bug

Project file & How to reproduce

Checklist of files included above

Version of PrusaSlicer

Operating system

Printer model

kubispe1 commented Jan 8, 2023 • edited Loading

MiFixIt87 commented Jan 8, 2023

MiFixIt87 commented Jan 8, 2023

jrwaters2 commented Jan 12, 2023 • edited Loading

jrwaters2 commented Jan 15, 2023

MiFixIt87 commented Jan 15, 2023

Tux0Topo commented Jan 17, 2023

jrwaters2 commented Jan 18, 2023

kubispe1 commented Feb 3, 2023

Tux0Topo commented Feb 3, 2023

Tux0Topo commented Feb 3, 2023

jrwaters2 commented Feb 4, 2023 via email

Jeroen6 commented Feb 6, 2023

bubnikv commented Feb 7, 2023

MichalBuzek commented Feb 10, 2023

lukasmatena commented Feb 10, 2023 • edited Loading

Renbrant commented Feb 14, 2023

Tux0Topo commented Feb 20, 2023

lukasmatena commented Feb 20, 2023

MiFixIt87 commented Jan 7, 2023 •

edited

Loading

kubispe1 commented Jan 8, 2023 •

edited

Loading

jrwaters2 commented Jan 12, 2023 •

edited

Loading

lukasmatena commented Feb 10, 2023 •

edited

Loading