One of our engineers is having a problem with Solidworks where he is getting a low memory/system resources warning.
His system specs are as follows:
SW 2011 64-bit SP 5.0
Windows 7 Pro 64-bit
Core i7-2600K CPU (not overclocked)
16GB Ram
ATI FirePro V4800
The thing is there is just no way he is using up all 16GB of RAM and the task manager confirms this. There are two other engineers with identical computers that don't have this problem. Any ideas? Thank you.
Tom,
Thanks for the help. We modified the registry and now I guess we'll just have to wait and see if that works or if the error reoccurs.
No problem. I haven't seen that message since I did the fix.
Samuel, sorry to hijack your thread, but how do you get on with this system? I am looking at getting pretty much the same soon. Do you do rendering?
No problem Greg.Yes, we do some rendering. It seems to perform pretty well. We have three machines, all identical, and they've all been very fast.
Cheers!
When you render, how many "blocks" do you have moving around the screen?
It looks to me like 8, but they move kind of fast, so it's a little hard to count.
Thanks!
I have been struggling with the "Low memory issue" for weeks, and I want to share the solution.
The problem is either the GDI objects, which reach the allowed limit, which is the default to be about 9000 in Windows registry. Just google for the way to edit it in registry - set it to 30, 40, 50 thousands or so. The limit is ~64k..
I have set this to 50k in my workstation - but I used to still receive messages when actually having 3k GDI objects at the moment of the warning.
The second issue is a virtual memory of Windows. If you have 16 GB RAM, you should set virtual memory to 16 to 32 GB, depending on different recommendations (that does not make a big difference, I often have assemblies with 10-15k components, and it takes overall about 8-10 GB RAM).
The problem is that if you set your virtual memory size to be "automatic", with minimum 1 GB and maximum say 24 GB, somehow Solidworks does not manage to "ask" Windows for more memory when it reaches the limit, leaving the virtual memory to pretty low amount. The point is this: SET THE MINIMAL VALUE EQUAL TO MAXIMUM VALUE (set minimum to 24 GB and maximum 24 GB). This will now affect any performance in any way, but Solidworks will always have plenty of virtual memory to use.
Use google to find the workflow to set the amount of virtual memory in you version of Windows.
Hope this helps
i had the same problem with a laptop today
so i made a batch file that wil update the registery key
i found out the hard way there that the fix dint work on 64bitX64 and it did on 32bitX86 Operating systems
since there is a differents i made 2 versions
both can be found in the link down below
File sharing and storage made simple
how this wil help people in the future
in case u dont trust me here is the actual code of the file
(title Running low on memory repair X64 )
set regkey="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows"
set value="GDIProcessHandleQuota"
REG ADD %regkey% /v %value% /d "262144" /t REG_DWORD /f
set regkey="HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows"
set value="GDIProcessHandleQuota"
REG ADD %regkey% /v %value% /d "262144" /t REG_DWORD /f
echo msgbox Replace ("You succesfully Reset the Regestry Key Regarding the low memory isue\nThank u for using this Batch file \nCompliments of ZUNDAPPCHEF :)", "\n", vbLf) > %tmp%\tmp.vbs
cscript /nologo %tmp%\tmp.vbs
del %tmp%\tmp.vbs
and here is a explanation of the lines:
1 line finds the proper map where the regestry key is located
2 line get the key that needs to be edited
3 line eddits/adds the new value , and sets it to the proper format
this proces repeats on 4-5 and line 6 but for the X64 version of windows
rest is just to display a message informing it was done
hi, i just experienced a similar issue and decided to tell you what i did as i never saw it on internet.
just build a new pc :
intel i7 8700K 6 Cores watercooled
16GB ram
250 SSD 950 EVO Samsung
3TB 7200RPM Drive
GTX 1060 GPU
normally this system is way enought to make a lot of things except heavy simulations, but at least open a layout file...
i was able to open the small drawing in 3D without any problems, but when opening the layout, it was freezing while opening, then error from ressource ressource monitor then crash and closed...
in task manager, was saying that solidworks was using 7GB, but in memory usage it was at 15.9...full ram usage... HOW POSSIBLE?? tried everything on google... virtual memory.. scripts... nothing working.. but wait !
virtual memory is done for a disk, you set up it for A specific disk, either for c or d drive... like everyone on an ssd bootable config, i installed solidworks on my D drive, not on the SSD ! so i decided to intall it to the ssd and worked !!!
I can't explain in detail why and how solidworks is controlled from the D drive but looks like it's not well used from D drive... now it using not even 1GB on stanby file and i can use it without problem ! Before, even clicking on the layout was freezing and crashing, now everythings works fine !
Hope it can help someone ! install solidworks on C drive, it handles better, or maybe i don't know if there's a specific parameter on solidwork to make it handle better on D drive but... Worked for me.
Thanks to all
Why did you install it on your D: drive to start with?
Dave.
Just fixed this for someone today. Add this to registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]
"GDIProcessHandleQuota"=dword:00004e20
(decimal value is 20000)
explanation:
S-048684
SolidWorks Professional 2010
6/28/2010 05:16:36 PM
Hardware / OS
Windows Vista -64
Question:
Why does a "system resources are running low" warning dispaly on Windows Vista® and Windows® 7 64-bit if not all of the Physical and Virtual Memory is used?
Answer:
Please see Solution S-048683 for the cause of the “SolidWorks has detected that your system resources are running low. It is recommended that you close some applications to free additional resources." warning message.
To find out the cause of the "system resources running low" warning message, first open the Performance tab in the Windows Task Manager and make sure that free Physical an Virtual Memory is available. If it is, then go to the Processes tab of the Task Manager and add the GDI Objects columns. (See attached screen shot). The default windows limits are 10,000 GDI Objects for each process. If SolidWorks has created more than 9,000 GDI Objects, the "system resources running low" message will be displayed. The following entry will also appear in the SolidWorks Performance logs, GDI_HANDLES_DEPLETED. If a lot of files are not open please report the issue to your SolidWorks Technical Support Professional and include a SolidWorks Rx.
A possible workaround to the problem is to increase the windows limit of 10,000 GDI Objects. The maximum number of allowed objects in Windows is 65,535. However, this should be done only if no other cause is found for the large number of Objects. This can be done by editing the following registry keys. Please edit the registry at your own risk.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota
The warning "system resources running low" warning is a sign that SolidWorks is unstable and should be closed and restarted to clear up resources.