Good morning. I am fairly new to SW, using it for justover ayear. The company I work for currently hasapproximately 12seats of SW 2007....all are having SERIOUSperformanceissues...often seeing 4-6 crashes per day.
Most of our workstations are 64bit....some are higher end32bit. We are seeing similar crashes on both platforms.
My 64 bit machine is currently being looked at by ourITdepartment....the 32 bit machine I am now using actuallyfunctionsbetter BUT I still get the same errors. Thismachinesspecifications are as follows:
Microsoft WIndows XP 2002 SP2
HPxw4400 workstation
Intel Core 2pc
6600@2.4ghz
2.00GB ram
Pagefile size is maxed out at 4092
NVIDA quadro Fx 1500
This is a small machine...I don't have the specifications onthe64bit machines currently.
Types of crashes we are seeing are:
opening a single part
opening a assembly
starting solidworks
when creating a sheetmetal edge flange
starting Cosomosworks
creating a mesh in Cosmos on a single part or multiple parts
opening the toolbox
creating a new sketch
editing a sketch
opening the "add-ins" options box
using the measure feature in a model
Runtime Errors
starting Cosmos Express
Checking in files to the vault
creating drawing views
switching from one drawing layout to another
"WARNING: FAILED TO SAVE DOCUMENT"
drawing views disappearing when adding or editing dimensions
adding centerlines to drawings - crashes
performing a cut sweep - crash
I think you now understand, SW will crash at any moment,under mostany circumstances....without warning. Itdoesn't matterif we have a single simple part open, or a largeassembly.
I have contacted our IT department, and our SW distributorand havetried to work with both with no results.
"the computers are fine".....
"the software is fine"....

Is anyone else seeing such poor stability ???
SolidworksAdministration







Most of our workstations are 64bit....some are higher end32bit. We are seeing similar crashes on both platforms.
My 64 bit machine is currently being looked at by ourITdepartment....the 32 bit machine I am now using actuallyfunctionsbetter BUT I still get the same errors. Thismachinesspecifications are as follows:
Microsoft WIndows XP 2002 SP2
HPxw4400 workstation
Intel Core 2pc
6600@2.4ghz
2.00GB ram
Pagefile size is maxed out at 4092
NVIDA quadro Fx 1500
This is a small machine...I don't have the specifications onthe64bit machines currently.
Types of crashes we are seeing are:
opening a single part
opening a assembly
starting solidworks
when creating a sheetmetal edge flange
starting Cosomosworks
creating a mesh in Cosmos on a single part or multiple parts
opening the toolbox
creating a new sketch
editing a sketch
opening the "add-ins" options box
using the measure feature in a model
Runtime Errors
starting Cosmos Express
Checking in files to the vault
creating drawing views
switching from one drawing layout to another
"WARNING: FAILED TO SAVE DOCUMENT"
drawing views disappearing when adding or editing dimensions
adding centerlines to drawings - crashes
performing a cut sweep - crash
I think you now understand, SW will crash at any moment,under mostany circumstances....without warning. Itdoesn't matterif we have a single simple part open, or a largeassembly.
I have contacted our IT department, and our SW distributorand havetried to work with both with no results.
"the computers are fine".....
"the software is fine"....
Is anyone else seeing such poor stability ???
SolidworksAdministration

This sounds like a case of AV software running during theinstallation. Having the server AV software scanning SolidWorksfiles could also be contributing to the proglem.
Disable all AV software and reinstall.
Other than that, check for...
Clean out temp files
Check graphics card driver
Enable "Use Software OpenGL" to see if graphics card is the problem
Check for faulty memory, unseated DIMM
etc etc etc
Other things like what software is running in addition to SW,things like music CD's, internet streaming etc cause a huge hit onperformance that SW does not like.
With XP-64, you should have a minimum of 4GB RAM. With only 2GB,XP-64 can actually be slower than 32-bit.
Also, many 32-bit programs and utilities frequently installed by ITdepts can wreak havoc with 64-bit systems. They can "hang" thesystem for quite some time. It appears that SolidWorks has crashed,but it is actually just waiting for access. Scype and Audit32 aretwo examples of such programs.
Try disabling programs in your startup menu one by one to see ifany are causing the system to hang.
You're experiencing an unusual number of problems. It is likelythat there are several culprits.
For those problems that you can recreate on demand, use SwRx tocapture the problem and then send the problem report package toyour VAR.
I don't see which version of SW you're using. I've had joy withSW07 SP5.0.
On the workstations that are most unstable and random, try runningSW with Software OpenGL. This will bypass the video driver. You'llsee a bit of a performance hit, but if the stability improves, thenyou know that the video driver is a problem. ONLY use video driversfrom the approved list provided athttp://www.solidworks.com.
Power supplies can contribute an insidious problem if they are toosmall. Any workstation with a 350 watt (or smaller) power supply issuspect. A 550W+ won't cost that much and can do wonders. Ofcourse, use UPS power conditioners and blow the dust off of the CPUheatsink.
Good housekeeping is important - I'm talking about disk storage.The temp backup directory that SolidWorks might be using should beemptied at least monthly. I say "might" because its use is anoption setting.
Working with files over a network can be problematic. It is bestpractice to copy the files to a local hard drive for editing. Whenthe files are ready, transfer them back to the network for sharing.
There are times when the registry gets mungled (particularly onworkstations that have had several software installations added /removed). There are some tricks for deleting registry keys (searchthis forum for suggestions) however it may be best to start with afresh installation of XP and completely rebuild the workstationsoftware installation. Avoid installing "goodies" and stick withbrand name security software.
A couple of years ago I had a frustratingly unstable workstation. Iended up hauling it to my VAR's office and we set it up there towork through the problem. Some of it was hardware (mismatchedDIMMs). Some was OS related (3gb switch and too much freeware).Some was my fault (poor design practice). There was one SPRgenerated because of flawed functionality in SW.
Moral of the story: troubleshoot each workstation on an individualbasis.
also, have you checked the system's event logs? sometimes these canpoint you in the right direction. watching the 'performance' tab intask manager may be helpful, too. launch it (Ctrl+Shift+Esc) andtry leaving it up while you are working in SW; it may show that youare getting cpu or memory usage spikes immediately before or aftera crash. while this does not point to the exact problem, it maygive you a better idea as to where to focus your attention.
in the meantime, as Gerald has already suggested, be sure to runSwRx & forward the report to your VAR.
I have a similar system and I only crash when I open a file thatis larger than my available memory,
when my document properties effect or override what my views areset at.
When I do run solidworks, I only run that program and nothing elseon my computer, I exit out of my email, windows search, andanything else that is running in the background. I will also not beable to run solidworks efficiently if a scan is taking place on mycomputer.
That is pretty much all I can remember, from when I have issues.Good luck.
There are some excellent suggestions already mentioned here, but Iwould run MEMtest 86+ on that machine as well.
When you are having these problems, what else is running on themachine? Try turning off everything non-essential to see if thathelps. If this improves things it may give a clue as to what isgoing on.