I have been using the Software dince 1998 and on average it crashes about 5-10 times per week.
I have gotten used to the fact that it crashes by saving my work every ten minutes.
No more than 1 time every 2 to 3 weeks. Mark - you have a lot more patience than I. What have you tried to improve the time between crashes?
On average, about 5 times a week, but saying that it is really dependent on the size of the job and the current state of my work station.
once every 3 to 4 months.
Unless I develop a recurring problem (attempting to create a specific feature in a specific model causes a crash 100% of the time), I typically only crash SW maybe 2x a year.
(But I only recently updated from 2007 so hopefully that statistic gets better, not worse.)
I would say only once or twice a month and then it's sometimes something I've done like running multiple sessions. I used to have once a day or more but a few months ago we upgraded to SW2012 64 bit and new work stations with 16 gb ram. I am not sure which aspect brought the improvement, maybe both, but crashes are fairly rare.
Maybe 3-4 times a year..... Not enough to worry about.
I go weeks without a crash. See here: http://www.dezignstuff.com/blog/?p=261.
wow.....I wish I had you guys' systems. If mine doesn't crash everyday I think I'm doing something wrong.
Is it because I have an AMD/ATI Video Card?
Should I plead with my IT Dept to go way over budget and spend £300 on an Nvidia Card?
What are your system specs Mark?
What type of work do you do?
How big or feature rich are your models?
It looks like I only have 4GB of RAM. Think it would run better if I tricked my IT guy into adding more?
Mark - From the discussions about system specs on here nVidia often isn't the best option. I took the 2013 System suggestions from Charles Culp and went with the AMD Firepro v4900 and have been quite satisfied.
Eric - it shouldn't take much to convince them with how cheap memory is. I just built a system and spec'd 16 thinking they'd negotiate me back to 12 and they went ahead and populated it with 32 just to avoid me complaining in the future. Do you ever run a system monitor to see how much memory you are using to determine that is the reason for your crashes? Do you have extra programs running in the background chewing up resources?
When I don't use it, it doesn't crash at all . The weeks that I am primarily using SW I think I am down to approx. 2-3 crashes now. It was a couple times a day, but I'm getting better about how I organize my work. Also by being patient. Bigger assemblies and drawings lock up a lot for me. I get the little windows spinning circle icon that lasts minutes to many hours. I have found that if I don't try hitting esc.or anything else it will usually recover. Although that has been later the next day.
We are in the process of moving to EPDM software so hopefully that will help, and learning more about SW should help a lot. I should be taking a class this fall .
I'm beginning to think SW is a somewhat sensitive female software. If you don't do things exactly how she wants them done she will make you regret it. She won't tell you what you did wrong, because you should just know.
Joe Kuzich wrote: I'm beginning to think SW is a somewhat sensitive female software. If you don't do things exactly how she wants them done she will make you regret it. She won't tell you what you did wrong, because you should just know.
Joe Kuzich wrote:
Thank you, I got a good laugh from that. It sounds like my wife isn't the only one that expects me to read her mind. And I guess you're right about the similarities. I know my life has gotten smoother with experience, both working with SolidWorks (4 years) and being married (25 years).
Well Joe, at least in German "software" is a female word.
And with how non-descript some of dialog boxes posted in the Favorite Error Messages discussion are it makes you wonder if the software coders even know what goes wrong at times.
Sometimes it's like the old days of a re-draw in Autocad, get a cup of coffee and talk to your colleagues, it could be a while.
OK, rememember this site is mixed company and some of the engineers pulling us out of the fire are women.
I'm running SW2011 with 12Gb of RAM and nVidia Quadro 2000 card. SolidWorks crash about 10 times per week on the average. Somedays SW crash 3 or 4 times.
Depends upon what I'm doing. Sometimes I'll go several days without a crash. Today, probably a dozen times already.
"Crash" is an ambiguous term. Here's how I classify things:
All three happen about 2-3 times a month each. In most cases, it's something I can recreate. For example, for crashes and shut downs, recently I did something in a sketch that SW didn't like, and it shut down. I restarted SolidWorks, did exactly the same thing, and it shut down again. I learned after that to try a different approach.
Similarly, when the software freezes, it's something I've anticipated - accidentally rolling over the "All Edges" selection pop up when filleting a part with 6000 edges for example.
In all cases it's a pain in the behind, but I try and save every 10 minutes anyway as force of habit, and that way, regardless of how many niggles, I haven't really LOST much time since I've been in my current position.
It's so variable that I can't really put a number on it. Sometimes I go for months without crashes, even if I am using SW several hours a day. Other times I will have multiple crashes per day. These are usually in the periods when I am using SW almost all day, every day, for days on end. Often crashes are pretty clearly related to what I am doing, as when I am working on a very complex part or a large (for us) assembly. Other times they just come out of the blue when doing the simplest thing. Working a long time on a number of parts and assemblies seems to increase the likelihood of crashing. But I have also crashed immediately after a reboot.
I like Kieran's method of classifying crashes. The ones that get me the most are the freezes when I have been working a long time on something without saving (because it has been months since the last crash and I am getting cocky and/or forgetful). I've let it run for hours sometimes, only to give up and kill it. Other times I have been rewarded after several hours wait with a chance to save my work.
There are also two types of freezes. Sometimes it is unresponsive and the SolidWorks process is not showing any activity at all. Other times it will show that it is using one core pretty heavily. I have had SolidWorks recover from both types and have also given up and killed both types many times.
Retrieving data ...