SW2004 memory problem

[Duds66]

Hello,

I've got a problem with Solidworks 2004 opening a large assembly (abt 3500 parts) with the large assembly mode.
I got a message "not enough space memory for SW application" and then it crashes.
I have 1GB RAM, and 10GB virtual memory, and nothing else runing at the same time. When it crashes, only 500MB of the total memory are used.
I have a graphic card Nvidia Gforce FX 5300 with 128MB RAM. So I don't think it's a performance problem. But maybe a WinXP pro config problem.


Maybe you have an idea abt that...

Thanx

Cédric, FRANCE

 

[SBaugh]

That card is not a certified card - the GF 5200, 5600, and 5900 shows as "passes with limitations". I'm willing to bet that means the 5300 as well.

Try restarting in VGA mode and see if that helps - If so, it's a graphics card problem.

Try it on another machine to see if you or they get the same result.

Try a new driver or maybe an older one might help.

Otherwise:

I would try reinstalling SW.

Did you have your AV turned off when installing? If you did and upgrade than un-install & re-install per my faq559-488

Turn off all other apps when installing.

Don't do an upgrade do a new installation. If you did and upgrade than un-install & re-install per my faq559-488

Turn off all other programs when running SW, and see if that helps.

Try making a new login account and see if that helps.

Regards,

Scott Baugh, CSWP
3DVision Technologies

http://www.3dvisiontech.com

http://www.scottjbaugh.com

faq731-376
When in doubt, always check the help

 

[Duds66]

Actually the problem was an incompatibility between PhotoWorks release 2 and SW2004. If you want to open a large assembly, you must unload photoworks release2. I think this probleme will be corrected in the SP1.

 

[Arlin]

>I have 1GB RAM, and 10GB virtual memory

Why so much virtual memory??

Try reducing your virtual memory to 1.5 or 2GB. Windows cannot allocote any more than 2GB to any single process anyway (3GB with some special tweaks), so there is no need for such large amounts of virtual memory.

I have tested this in the past and it stopped 'out of memory' errors for me.

 

[CorBlimeyLimey]

I agree with Arlin. Rule of thumb is 2 to 3 times amount of RAM for Virtual Memory size. Any more is a waste of space.

 

[BBJT]

No only a waste of space but it could also slow you dwon because of the large space that it has to search.

BBJT CSWP

 

[kcarpenter]

I don't see it mentioned in any other replies, but you should set the virtual memory so it's static not dynamic. This means that you should set the min. and max. to be say 2048MB which equals 2GB. Don't make it something screwy like 1500MB which doesn't actually mean 1.5GB to the system....1536MB would be 1.5GB to the system. What this will do is keep the system from having to allocate virtual memory on the fly thusly taking away some system performance. I also wasn't aware that Windows could allocate more than 4096MB of memory for swap unless your tweaking the registry to accomplish this.

Kevin Carpenter
CAD Systems Specialist
Invacare Corp.