Running a Dell Precision 7710 (Xeon E3-1505M and Quadro M4000 GPU with 32GB DDR4 RAM)
I upgraded to SW 2016 SP5 last week and HOLY COW! I've probably had 20 crashes in the past 4 days. I have lost hours of work. I'm going to hit up my last restore point now and hope to salvage the last couple hours of the day...
Anybody else seeing horrible crashes on SP5? I have been extremely unimpressed with Solidworks 2016 as a whole, ironic that the last service pack should be this unstable...
when u say that you've lost hours of work, is that because you don't save often ?
I now save more often! When you crash 20 times, it's not hard at all to rack up hours of lost work...
About 10 of the crashes were just doing the normal stuff (parts, assemblies, drawings, etc.), but I now have a single (very important) part file that crashes non-stop when I try to edit the tree, a few weird things happen to this file:
A CTRL+Q Forced Regen was required to use the Freeze Bar, but caused a crash when I performed it every time.
I was able to back the EOF bar up the tree to a point where I could run a CTRL+Q and not crash, however it broke a bunch of features in the tree (not too uncommon for complex parts).
Now however, when I try to edit any of those features it's an immediate crash. It looks like I'm going to have to revert back to an older version of this file which has hours upon hours of surfacing work that will have to be redone... Really bummed about this one.
I don't know if Dropbox Links are appropiate, but this is the file (2016 SW format) with the freeze bar and EOF bar retracted as shown in the screenshot above.
I've got about 18 years of CAD work under my belt and never saw this before. If I could recover this file that would be amazing.
Apparently the part has numerous issues, unfortunately user input still rules, so somewhere you have a sketch that isn't rebuilding properly or there are dangling dimensions, meaning there are references that have been deleted and changed, either in the part file or on another part in another assembly, or you have circular rebuilds.... ok so now I threw the book at ya, how do we fix it...
Best way to fix it would be to upload the part and if someone has time they'll check it out for ya. Where I would start is to suppress the entire feature tree and then starting at the top un-suppress each feature one by one and if the part is made in context of another assembly or off another part then those areas need to be checked out as well, these can be fun to trouble shoot but if you can seriously find it on your own, that's the best feeling....
Thanks for all your help! See attached file...
BTW: I'm very familiar with broken sketches and other errors, however to have an error that crashes SW when you edit any feature is what I haven't seen before. Makes diagnosis very difficult...
I sent this file to my VAR who is really good with this sort of thing and he spent an hour on it before saying it's going to Corporate to attempt a recovery. I think I might have something weird here...
..opened/saved it multiple times... crashed multiple times..that was nasty!
good luck!
BTW,.. does the same thing in 2017 sp1... so, yeah, you got yourself a live one!
Yup, I even installed 2017 just to find out!
Thanks for the confirmation.
Solidworks Corporate has had the file for days now...
2016 SP5 is very stable here.... Would love to see your workflow and what you're trying to do...
I'm with Wojciech Paterski (hours of work???)
I have found over the years that many of the instability problems are due to corrupted user settings. The best indicator of corrupt user settings is when one user can perform an operation that the other user cannot without crashing. The fastest way to resolve stability problems is to clear your current user registry key for that version of SolidWorks, or even the user registry key for all of SolidWorks (INSERT STANDARD REGISTRY EDITING WARNING HERE). Simply reloading or re-applying settings from a saved file doesn't work - you must delete the current settings first.
The safe way to do this is to rename the key (folder) by adding "OLD" to the end. If it works better, you can delete the old key. If it is worse or there is no change, then you at least have the option of restoring your settings by renaming back (after deleting the new key that was created when you launched SolidWorks).
I hope that helps.
After a few weeks of having the file at my VAR, it's been confirmed on many systems that the file itself is corrupt, something to do with how SW translates lines and faces. It has been forwarded to SW Headquarters for an attempt at corruption recovery. In the meantime it looks like I'll be work with a step-ed out file to prevent these constant crashes. This individual part file is the heart of a much larger assembly which must have had 100 crashes by now. Really disappointed in this instability, it has caused a severe disruption in my workflow.
Bummer. Sure would be nice if we had ways to repair the files ourselves, wouldn't it?
Hi Michael:
Did you turn on this option once a while to check the feature integrity?
It is not necessary to turn this on all the time, but it is recommended to turn this on after some new features added, rebuild the model and then turn it off.
I've not had more than 2 crash since I had it install. So please use Rx tool and send the log files to your VAR.