pcman
Posts: 43
Joined: Sun Dec 27, 2015 10:50 pm

Re: S3D crash error on startup

Ah, OK. The three processes were left over from the registry because you didn't completely clear it the first time. The FFFWindow key that I suggested to delete was just to reset your profiles. So, that's not unexpected.

Try again by running the uninstaller for S3D, then deleting the registry key HKCU/Software/Simplify3D and all its subkeys, then reinstalling. If it crashes again, right click on the Simplify3D key and select export then post the file here and I will take a look.
pcman
Posts: 43
Joined: Sun Dec 27, 2015 10:50 pm

Re: S3D crash error on startup

Please disregard the last request. Do not post your entire S3D registry key here as it would include your login credentials.
singhm29
Posts: 41
Joined: Thu Feb 12, 2015 11:52 pm

Re: S3D crash error on startup

Hmm dont seem to see anything in the log file about my credentials but ill refrain. Ive been talking to S3D tech support and sent them the log file, hopefully they can resolve it quickly and I can throw up the solution.
singhm29
Posts: 41
Joined: Thu Feb 12, 2015 11:52 pm

Re: S3D crash error on startup

So turns out the crashes had todo with a fourth monitor I connected that couldn't support the same resolution as my other monitors which caused my video card togo a bit wonky. I ended up switching out the monitor to one that could be consistent with the others and reinstalled. All is good!

Thanks for the input!
pcman
Posts: 43
Joined: Sun Dec 27, 2015 10:50 pm

Re: [ Solved ] Windows 10 S3D crash error on startup

Thanks for completing the thread. It might help someone else in future. Of course, I never would have guessed you were using four monitors! I use 3x27" @ 1920x1200 without problems but S3D is only ever on one and I sometimes have the control panel on another. It seems odd that yours would work when the registry entries were deleted though.
Javanator
Posts: 1
Joined: Sun Jul 16, 2017 11:57 pm

Re: [Solved] Windows 10 S3D crash error on startup

Thank you! I'd like to add my experience: I have 2 3840x2160 monitors and had this exact same issue. Support was unable to solve it. After reading this thread, I tried disabling one monitor, and it worked! Now I am asking support if they can reproduce this and fix it.

Return to “Troubleshooting and Bug Reports”