Simplify3D User Forum

it's not the machine, problems started for me with 3.1.1 update. I found that it was always crashing on 2 profiles and no other. if I used petg or pla and any profile I setupped for them it would work ok but 2 (out of maybe 7-8) profiles for abs were crashing on almost any change .. changing something in profile or clicking update profile or trying to slice... I deleted those two profiles and 3.1.1 was working without crashes till 4.0 update ... then it started to crash again, I was removing profiles as it was crashing but it didn't help, then I did a virgin installation and it works ok since then (I had maybe total 2 or 3 crashes in some weird situations like my nvidia driver restarted or I loaded some huge part ..)... so now it works properly... win7 64bit on some i7 with 32G ram 1080 nvidia with 3 screens with 2560x1440 and 1 screen 2560x1600 ..

so, I'd say there's def. a bug with profiles upgraded from 3.x, but I can't say that's the only bug... weird beh. was reported with 4k screens, with win10...

arhi wrote:..I had maybe total 2 or 3 crashes in some weird situations like my nvidia driver restarted or I loaded some huge part ...

Thank you for posting this snippet - I think in my case, you might have found the cause.

Like you I have four screens. I had noticed the occasional screen redraw on icons I could see on bare portions of the Desktop, and just thought, "Pah. Typical Windows can't keep up..." As nothing else seemed to be going wrong, no virii, etc., I just shrugged it off.

You may be onto something here -
On examining the Event Viewer log - there was the Nividia driver (nvlddmkm) doing it's now-famous bucket-kicking routine. Looking at the dates and times that S3D has crashed-out and corrupted the in-use profile (and the subsequent panicked exporting of any profiles that might not be affected) - the exporting usually follows directly after one of these events. [Sometimes I walk off in disgust for a few hours though so the times are only approximate...]

In Safe Mode, I used DDU many multiples of times to remove any residual bits of Intel, AMD, and Nvidia video drivers that might be lurking around, then installed the Nvidia driver v347.88 (apparently this is considered one of the most stable versions). My video card is currently an EVGA GTX 770.

Well, it's been 3 days of heavy S3D use so far, and no crashes yet of either the Nvidia driver or S3D. It's too early to say, but I am hopeful (and desperately grasping at any straw now!)...

Ah well. It was nice while it lasted.

No more graphics crashes, but had an S3D one this afternoon while updating a profile. So...

...back to exporting every single fff before and after modifying a profile. Rats!!

Since fixing the Nvidia driver issue on the 5th Nov, no crashes of any sort other this one from S3D.

Something still isn't right with this program. ;(


From Event Viewer -

Faulting application name: Simplify3D.exe, version: 4.0.0.0, time stamp: 0x597095a0
Faulting module name: Simplify3D.exe, version: 4.0.0.0, time stamp: 0x597095a0
Exception code: 0xc0000005
Fault offset: 0x00000000000c9480
Faulting process id: 0x2bbc
Faulting application start time: 0x01d35875d241002a
Faulting application path: C:\Program Files\Simplify3D-4.0.0\Simplify3D.exe
Faulting module path: C:\Program Files\Simplify3D-4.0.0\Simplify3D.exe
Report Id: 7b405dc8-c498-11e7-8b64-bcee7bda86df

So, on the advice of S3D TechSupp, I reset v4.0 and uninstalled it.
I then deleted everything on the C: drive that had anything to do with S3D - including stuff buried in the AppData folders.
I then manually cleared out every reference to S3D in the registry.
Rebooted.
Reinstalled v4.0, and created any profiles from scratch. Never used anything from anywhere else, just in case.

Everything has been absolutely great for 4 weeks - until today.

What was different about today?

I had noticed that if Fusion 360 was running on my computer, I had more of these crashes when saving profiles - so I stoped using both at the same time, just in case. Coincidentally, no more crashes.

Today, I was desperately drawing stuff on F360, then printing it (via SDCard) to various printers. Crash.

I know I am grabbing at straws once more, but I have had trouble in the distant past with the way Autodesk programs birdshots different versions of QT5Core.dll all over the place - almost every program of theirs uses a different version of it!

As the crash is QT5Core.dll-related, could this be the cause?
Fusion 360 and S3D together make for random profile corruptions?

It does not always happen immediately if I use both together, but after a couple of dozen or so saved profiles (used for material testing purposes) - pow!

I'd like to test this further, but I actually have to work and don't get time.
So, if any of you folks notice your crashes start when running Autodesk progs, specifically Fusion 360 alongside Simplify3D, please post here and let Tech Support know.

Thanks, and good luck.
Susi xx

I see 2 huge problems here
1. when app crashes it can mess up the profile
2. messed up profile will crash the app

both 1 and 2 should not happen! neither the crash of the app should mess up the profile (unless app crash during the millisecond profile is being updated there's no reason for profile to be crashed if app is killed / crashed during editing, printing etc..) and also if profile is messed up app should not crash but figure out the profile is corrupted and offer to fix the corruption... not crash... this is kinda very basic behavior of the app designed by junior developer

that app crash from time to time for other reasons (nvidia driver, qt being messed up by autodesk, instability of the widows, poor hardware...) is ok, every app crash from time to time... but those 2 huge problems create a magic circle app can't get out of.

I don't know what corrupted my profiles the first time, but since I fixed them I never had a crash... I don't keep fusion on my computer for a while now (don't like it, I use either solidworks, openscad, art of illusion or onshape for my designs and in rare cases I use freeCad and thinkercad) so can't say if fusion help crash it or not, not having fusion360 def. helps ... not sure why would fusion360 mess with QT libs since it just opens a browser in it's window, the whole thing works in browser it's not a desktop app...