Can SW crashing be a user problem instead of computer problem?

[MDGroup]

I was wondering if SW crashing and having to re-start can be a user problem rather than a Computer problem.

One of the guys working here has the same computer I have (actually got it about a year later so it could be slightly better) and it also has 1G more RAM.
Graphics cards are the same with latest drivers/updates. He does have Windows 7, while I have XP.

We work with most of the same parts and assemblies.
He compains that SW is crashing several times a day. Yet, SW very rarely crashes for me (maybe twice a month).

Can SW crashing be a function of the user and how they operate the program, or is it really just a CPU issue.
Sure some complex features may demand more resources, but most of what he is doing is very basic.

Any thoughts? Thanks.

 

[SteveMartin]

Crashes can most definitely be a function of user practices. Basic computer maintenance (defrag, cleaning temp folders, proper installation/upgrade procedures, system options/settings, among other items) can make a lot of difference in the stability of any program. It can be very hard to trouble-shoot this type of thing too, as it's rarely one thing to point at and say 'this is the difference', but rather a combination of relatively minor factors.

 

[EEnd]

It is a bit of a stretch to refer to them as the same computer when one is a year newer and running an OS which is 8 years newer. I admit that user style can affect crash frequency, but given the differences in the systems, I would suspect the system first. You could switch systems for a couple of days. If it really is crashing on him several times a day, he might be happy to switch.

Eric

 

[CorBlimeyLimey]

It could very easily be a user-created problem, but it is far more likely to be an installation error or hardware/software conflict.

I agree with EEnd, exchanging computers for a day or two should quickly determine where the fault lays. Even a few hours may be sufficient.

 

[Eltron]

Also, Jeff Mirisola did a presentation at SWW called SolidWorks Crashes and Slowdowns this year that might be helpful. A quick Google search should find it.

Dan

http://www.eltronresearch.com

Dan's Blog

 

[NomLaser]

Just a note, same PC's built at the same time can easily suffer from different issues. Not all PC's are the same, especially ones built a year apart with different OS's.

 

[gwubs]

Agree with above posts that it is probably more machine related, however some users do suffer more crashes. Impatience is the problem here. Clicking way ahead definately can be the last straw that brings your machine down in flames. I find also that even when the Task Manager says "SolidWorks is not Responding", that it is not always true. Windows takes a hasty look and sees no imediate activity, and delivers the bad news. Usually if you give it time, it will finish (not always of course). Patience is a virtue with SW.