I sit and wait/restart for 2+ HOURS every single day because of Stupidworks' instability. What about y'all? Do you lose much time?
Adding up the minutes now...
Notice that today I am in 2013...
Overall it costs me under 5 min / day.
Generally every afternoon I am alerted that my system resources are running dangerously low & then I restart. I may also decide to close other programs and live with the slow down if I don't expect much demand throughout the rest of my day. Feels like the drag build up throughout the day & restarting cleans things up. I also believe I am running a machine that could use more core processors so says my VAR. I believe him.
2015 SP4.0 on Win 7
I don't get too many crashes but I am constantly fighting Solidworks going into some kind of an infinite memory loop and just hanging ... I usually close everything else running and hope it comes back. 1 in 10 it does, 9 in 10 I give up and force close. Lately I have started just going straight to force close.
All in all I probably lose (including the work I have to redo since I didn't always save very recently) about 2 hours a day. Some days 3-4, some good days less than one.
I must clarify to everyone here. When I'm talking about "crashes" in 2015, I'm talking about mostly the "Freeze" type that never comes back no matter how long you wait. Yes you must then tell it to quit. This is why I was saying what I was about how long it realistically takes when a "crash" occurs. Because there is always some time initially waiting for it respond until you eventually give up and force quit. I estimate that as much as 90% of all "crashes" i experience are of the "freeze of death" variety, with the rest being some kind of instant dump. And usually the instant dump type can be traced to some specific sequence of steps. But the freeze type are the ones that are truly random and frustrating. In fact there is an entire thread here on the forum that I only just now discovered that relates to these freezes specifically: Solidworks constantly Freezing up
Agreed that is what happens. It hangs and then you get the win7 faded screen asking if you want to wait forever or kill it. When I get the chance to fill the SW crash report I am getting increasingly sarcastic...
my VAR just sent me access to SP5.0EV...about which I have heard better reports. Installing that now. Fingers crossed...
... I'm not sure if those "more stable" reports were from win10 users though...
As regards the autorecover actually causing the crash - I sometimes think that - but my colleague still had lots of crashes without that set up.
Questioning the autorecover - it seems some commands exit when autorecover fires. But I'm not totally certain of that. Support people say it "definitely doesn't affect your work" but I find I am occasionally restarting the odd command and select sequence....
18 minutes in, and SW 2015 crashed while saving a very simple assembly.
No wonder you don't want to get out of bed in the morning
I don't have near the amount of crashes that I had in earlier versions, it's just the little subtle things that pop up that makes life difficult, such as pack & go issues, opening up a file that was done months ago and errors pop up, or changes didn't stay.
But I still blame it on how they make me do it here, working on a server instead of local and saving a backup it on the server, luckily one afternoon I was working with our IT guy and the next morning when I opened up the assembly there were errors all over the place, some changes changed and others didn't, finally I could vindicate myself and it kept me from be sent to the asylum.
Technically, what's happening is neither a "crash" or a "freeze". The program is still running, it has just become unresponsive to external input. If you check the Resource Manager it is using every last bit of available memory and any you free up by closing something else immediately gets consumed as well. It is also using up cpu cycles, often 25% or more.
Unfortunately whatever it is that it's doing in the background never completes so the program remains unresponsive. I have actually left it sitting overnight as a test and in the morning it was still unresponsive (some 14 hours later). Thus I no longer bother with waiting for it to revive itself.
The best way I've found for avoiding this is constant stopping and restarting the program every 2-3 hours, which also helps minimise the loss of unsaved work.
You don't want to even know what I write in that box!
Yeah, IT had the same policy here too about working off of the server. It was especially bad when I first started. "No files should ever exist locally on your machine, EVER!" But I have since gotten them to loosen the reigns a lot. Plus the IT manager that was originally strictly enforcing that policy left years ago. I definitely find that working locally on files, especially big ones, helps dramatically both with crashing/freezing and just general overall performance.
Ha! Probably nobody at Dasseault reads it anyway...
LOL - I always Xed out of that box, never even dawned on me that you can type a note in there, Oh my, things flying through my mind..........
I have pretty much free reign with my workstation. I have the same tower my predecessor used from 2010 and hav only upgraded SW to 2012 SP5 from 2010. Win7, i5 760, FirePro 5800, upgraded RAM from 4 to 16 Gb.
I have the option at my disposal to upgrade my tower and SW (thinking we should probably go off maintenance at this point) but everything works well as it is. I know of no features/updates that would make my life easier so I am content. SW will crash out one a week or so(might be a bit more often) but usually when I am doing something that gives me that nagging feeling in the back of my head that it is about to crash. Often when switching between sketch in part to assembly the part is in or calling a server side block into a drawing.
Time lost is between 5min to restart (go grab coffee time) and rebuilding time can be immediate to an hour depending on my saving discipline. I do remember once I was working on parts and an assembly and forgot to save both after 2-3hrs of work. Its amazing how quickly you remember your last save point when Assembly1.sldasm whites out.
I lose between 5-10 minutes a day with Solidworks 2015. Worst release to date. Never had this kind of downtime with any other major release.
Bill Gates used to swear that Windoze was 'stable' because he rebooted between each and every task. True story. He considered the 'uptime' tool, ubiquitous to all linux users, to be a silly exercise of self gratification. Naturally he would feel that way. linux boxes were well-known to have uptimes, meaning time since last reboot in the 10,000 hours range (>1 year), and were frequently cut 'short' by failures of the Uninterruptible Power Supplies than the need to 'reread the boot sector'!
Also maybe a minute/day (2015 SP4.0).
I started working with SOLIDWORKS when it was still spelt SolidWorks (circa 1998) and later with Inventor from 2009 to 2015 (beginning of this year). I've been using SWX again since about March, using 2015 SP 5.0.
SWX has crashed more in the past 7 months than Inventor did in 6 years (I kept copies of all my Inventor crash reports). In fact, the previous company I worked for switched from SWX to Inventor because of stability issues.
Sure, SWX is a better modeller, but when it comes to stability, Inventor wins hands down. Don't know the reason, but I'm sure DirectX (Inventor) vs OpenGL (SWX) plays a part. With Inventor you only need to buy a proper gaming card that is WHQL certified, and you can be pretty sure you won't have issues.
I use a ZBook 15 with a Quadro K610M card and 16 Gig of RAM on Win 7, so can't blame the hardware.
I have to use SW2013 and SW 2014. SW2013 is my choice, It is rock solid and only crashes if I do something stupid, even with big assemblies is works great. I get 1 crash a month, if I am unlucky. Now SW 2014 has been a problem from the start. I am using SP2 and do not want to try any other SP.
It will crash on closing it will crash on opening something it crashes for no reason. I can push it hard and it's OK. I can save a small file and it crashes.
I don't like the way this is going, it's getting worse, imagine if I had to use SW2016? The good thing is I save a lot, I think the question should be how much time do you loose saving your work in case it crashes.
Our biggest headache has been crash upon crash especially during routing pipes etc.
SW2014 was bad for this however SW2015 is marginally better.
Our biggest pain now is SW freezing and awaiting to respond, it can be good for a few days then the next day you can be restarting regularly as waiting for it to respond can run for hours (left it while at a meeting and came back to see no change).
Unfortunately we feel we are now computing and not engineering as productivity some days is some way below what you expect or indeed demand.
i am using SW 15 SP 1.1. Last week,i lost a full assembly that was 1 full day work. all parts and sub assemblies were fine,but the main full assembly was not opening.Technical team said it cant recovered,so i had to start assembly from scratch.
Since January of this year (2015) I purchased 2 brand new Dell M6800 laptops. I set both of them up (that might be the problem right there ). The other person I gave one of them too has had next to no problems with his. However the one I kept was having issues all the time since the day I got it. I was losing a lot of work daily. A normal day for me had to consist of at least 4-5 crashes a day with a few hours of lost data. The Auto Backup would work part of the time, but if there was anything in the Auto Backup during the next crash all data I was working on that was the same name was lost. I spent a lot of time removing the old Auto Backup data. Sometimes that data so so far out of date it was easier to start over.
I started complaining to Dell since some of the problems I was having in SW was not repeatable by my VAR. Dell Support responded extremely well, but of course I paid for the Pro Support. They immediately sent out a USB reinstall drive. I reinstall the OS, and little to no change in the problems. Then they sent out a tech the next day to replace the Motherboard and the Video card. I tested it for a few days and still had issues and the performance was still very poor. So they escalated the issue and finally they sent me out a new Laptop and before it was made I requested a SSD in the new PC. Now after having it for a couple of weeks I have crashed all of 1 time. So I am very pleased to see most of my problems was due to the PC itself or the fact I had the old HDD... either way SW 2015 SP4 is running a lllllot better.
OBLT001 was my old PC and OBLT003 is the new PC. OBLT002 is the other Engineer here and you can see he rarely crashed since that one and 001 have been logging since January of this year. The CAD Admin Dashboard does capture all the crashes that actually occur unfortunately or that red would be a lot worse.
Not this is thread comment I am about to mention is about this thread but, if anyone ever gets any Dell products I highly recommend getting the Pro support. its more expensive at first, but when you have issues it pays for itself in the long run.
Sorry for being so long, but I just wanted to share the problems to the solution.... hope this helps someone.
Scott - thanks for taking the time to post this. I wish there were an explanation - with a new install of OS and a new MB and vid card... But it confirms a suspicion I have had that "the problem" - whatever the problem is - can be caused by anything.
I also am a proponent of the Pro Service offered by Dell. For a few hundred dollars per machine, it has paid for itself on three occasions over the last 5 or so machines I have had. Not a great track record for Dell now that I think about it, but maybe that's because I am cheap and go the refurb route...? And the service has always been quick and good...
Thanks Scott. That's very helpful info. After everything I've tried over the past year of troubleshooting these issues, I had started coming to the same conclusion that it's either something in the background that I'm not aware of, or that it's somehow related to the hardware. The reason I reached this conclusion was because of how the freezes increased on my new machine. Though I had been fighting with the issue quite a bit on the old machine as well. Also other people in the office don't seem to freeze quite as much as I do on different hardware. Though, it comes in waves for some reason just like it does with me, where there will be a very bad few hours of constant freezing (or even for days), and then all of a sudden it will clear up. So it's this behavior that led me to suspect that something runs on occasion in the background. It's just the weirdest, most frustrating thing I've ever had to try and troubleshoot.
Seems like these posts might still be relevant, 6 years later:
SolidWorks Crashes & Slowdowns: It's Your Fault - Jeff's Tool Shed - Jeff's Tool Shed
SolidWorks Crashes and Slowdowns, Part 2 - Jeff's Tool Shed - Jeff's Tool Shed
SolidWorks Crashes and Slowdowns, Part 3 - Jeff's Tool Shed - Jeff's Tool Shed
SolidWorks Crashes and Slowdowns, Part 4 - Jeff's Tool Shed - Jeff's Tool Shed
SolidWorks Crashes & Slowdowns - Part 5 - Jeff's Tool Shed - Jeff's Tool Shed
SolidWorks Crashes & Slowdowns - The End - Jeff's Tool Shed - Jeff's Tool Shed
Yes, this is a bit (a lot?) of shameless self promotion.
Retrieving data ...