System Resource Notification

[JMesz]

This error message popped up in Solidworks telling me that I am running low on system resources, and while I have closed it several times it keeps coming back.

This is baffling to me: I run a Win 7 X64 system with 12G of RAM, plenty of hard drive space, Quadro FX 3800 graphics card with 4G of total Memory (1G dedicated), and Intel Xeon W3520 Quad Core CPU (2.67GHz/Core).

I don`t think at any one time I have ever used more that 6 of my 12 gigs of RAM up. Occasionally I will use up 25% of my CPU (which would be one entire core as Solidworks is only capable of using one core) with no problems. I have never really monitored the usage of the graphics card.

I have no ideas what may be causing this...perhaps network problems as I save all my parts here?...(like I said I`m grasping at straws)

 

[ctopher]

I have seen this with too much stuff running on the computer.

Check your processes, what programs are running?

One option:
1. Open your Start menu.
2. Click Run.
3. In the command screen type "msconfig.exe".
4. In the "system configuration utility",click either "service" or "startup" tab.
5. Uncheck all programs that your are no longer using.
6. Click "OK".

Chris
SolidWorks 10 SP4.0
ctopher's home
SolidWorks Legion

 

[JMirisola]

You can also download ccleaner to help manage what programs automatically start running when you start windows. It's also a great tool to delete your temp files and clean up your registry files.

Jeff Mirisola, CSWP
Design Manager/Senior Designer
M9 Defense
My Blog

 

[steinmini]

I had a lot of those, most of them popping up after I had been working for long time in SW, opening, editing files, but not restarting the application. I have a 4 core CPU but I think it's the memory that never gets released from SW. the simplest method to see if it's the memory occupied is to go to task manager and se how much SW took from resources (memory) Open several files and then close them. Open some more, close them again. If it behaves in a similar fashion, it will take a lot of memory. I also found that using RealView all of the time increases the amount of system memory that SW chews... but doesn't spit out...