Critically low. But how can that be. I open one part do what I need then save and close that part. Never having more than on part open at a time. After opening about 10 My system thinks its running out of memory. Running 16 sp4.
Have to add 16gb ram
Dell Precision T3600
We have seen this caused by a low GDI object limit in Windows. Check out the information at the link below and let me know if you have any better luck.
Yes, It's really annoying ....
In addition to what Benjamin Modic said, errors with memory don’t generally differentiate between RAM and VRAM (the memory on your video card). It will give low memory/resource warnings if GDI Objects, RAM or VRAM are low.
Windows also does not have a built in way to measure how much of your VRAM is in use at any given time. There is a tool that you can download and use to observe this though called GPU-Z (https://www.techpowerup.com/gpuz/). Try downloading this and see how much of the VRAM is in use when these warnings come up.
Have to add this just started yesterday. before I could have several items open at once.
When was the last time you did a full power off reboot?
That is the only way to fully clear the memory.
These resources are shared across all programs on your machine and would be used up by any other program you have open at the time. Those programs don't tend to have built in resource warnings though like SolidWorks does. If you run GPU-Z on your machine it will be able to tell you if you are running out of VRAM across the entire machine though.
This is a very annoying problem, I don't even have a huge assembly open but halfway through my work I start getting popups telling me
"warning solidworks is running critically low on windows resources"
Only way to fix it is to close solidworks, and open the exact same thing I am working on with no problem. This tells me Solidworks doesn't know how to let go of resources. This has to be the GDI (whole new meaning thanks to SW) objects because I at the most use 6 gigs out of my 16 gigs of ram.
I mentioned this above but since you are seeing the same sort of behavior, Windows also does not have a built in way to measure how much of your VRAM is in use at any given time. There is a tool that you can download and use to observe this though called GPU-Z (GPU-Z Video card GPU Information Utility). Try downloading this and see how much of the VRAM is in use when these warnings come up. I believe you will find you are at or near the limit of your graphics card VRAM.
Also, if you think you are reaching the GDI Object cap then you can raise it by running this .REG on your system (GoEngineer - Raise GDI Object Limit Cap). That would certainly alleviate any issues with reaching the GDI Object limit.
I feel your pain. I recently opened a support case about this issue. SolidWorks 2016 didn't have this issue but we are seeing it with 2017. With the same workstations.
If I hit the GDI warning limit and close all open SolidWorks documents (not the application) it doesn't release all of these objects. It keeps my system at about 4,000 GDI objects out of an allowable 10,000. Sounds like something wrong in the software to me.
Since I can't necessarily create a workflow to recreate the error, I seem to be hitting a dead end on the support side. So far the answer has been to just be in the practice of closing out of SolidWorks a couple of times throughout the day.
IT is a bit wary of changing the Reg settings so we haven't gone that route yet.
The 10,000 GDI Object limit is a somewhat arbitrary softcap imposed by the operating system. I have had my own cap increased to the theoretical max (65536) for more than a decade with no ill effects from it. Have you tried having your IT talk to your VAR on this? It seems like that would be the simplest fix.
uncheck toolbox and check if the performance is back to normal?
Tim, that is exactly my problem, 2016 on the same work station, 0 issues. 2017 BAM I have issues. I was almost at 10k GDI objects, I closed Solidworks, open the exact same project and I am at 2k, it's not releasing those object.
I was having this issue with my system at home running Windows 10 with 24GB of memory. Set the GDI limit in the registry to the max but was still having problems. Finally found where to turn on the GDI objects in the task manager & found that the zz3DxLCD50RSSReader.exe program which is the RSS reader for the 3D Connecion Space Pilot driver was at 10,000 GDI at startup and wasn't even displaying the RSS feed. Went in to the program manager in the 3DConnexion software and made sure that the RSS reader was turned off. Now I haven't had any problems so far.
Went away for a long time But today I'm fixing a lot of models Just open fix a couple of mates and close. After about 15 of those I go a warning that if I do anything else Solidworks will shut down. Did it anyway and completed what I was doing then did a complete system shut down and reboot.
Will see how long this lasts.
Tool box was shut down we have to check it out to use it and that can be a pain.
I've opened and closed 20 so far and not one problem.
I don't know if anyone has solved this yet?
I've been having this issue for ages and have tried upping the GDI limit in the registry to 65,000 and increasing VRam to 24GB, both to no avail.
I'm thinking it is related to a 6GB RAM limit somewhere as it always happens when I tip over 6GB. Then i get the critical error when it gets to about 6.5GB RAM, however my system has 12GB available.
I currently have a ticket open with my VAR on this and am hoping to get it escalated to solidworks.
Chances are good that this forum post will be sent back to your VAR for follow-up. Are you having trouble escalating this through them?
Also, it might be beneficial if you went into the "System Information" utility on your machine (search "msinfo32.exe" in your Windows Start Menu) and posted screen shots of these categories:
I think they're escalating it now, but i've had 4 long screen share calls troubleshooting it and i'm getting a bit bored with it flashing up every 5 seconds! See screen info below:
Thanks for your help.
like many of you, we started experiencing this more under v2016 then previous versions. With v2017 it went into overdrive. Some of the below is covered above, but here is what we have put in place and it has drastically cut down on the annoying messages.
With SWX running, in the Task Bar > right click SW Resource Monitor > check the Dismiss options. Occasionally the graphics option gets turned back on... not sure what is overwriting it.
We increase the GDI objects and the Process Handle. After digging and digging, and several calls / complaints to our VAR (who went to SW Corp) came up with another couple of settings on messages. We have a REG file that is pushed along with the SW install, but it can be added at any time.
; set GDI object from default 10000 to 30000
; set Process Handle from default 10000 to 18000
; this shuts off resource messages > maybe
"Don't show messages"="TRUE"
; This sets the Hungtime setting to help SWX keep from appearing to crash
I am excited to see what the ultimate cause ends up being. If you would come back and let us know it would probably help some people in the future.
One thing of note, your amount of installed RAM (12 GB) is lower then I might expect for a modern machine that is also running an NVidia Quadro P4000. I would expect that resource warnings would start coming up ~9.5 GB RAM usage on this machine which is pretty easily gobbled up in the last few years.
I think the problem was VRAM related. I had increased my VRAM to 2 x my installed 12GB ram, however i'd set the MIN to 1GB and MAX to 24GB. For some reason I don't think it was allocating any VRAM above 1GB and hence going straight to physical RAM.
I've since set both MIN and MAX to 24GB and the problem seems to have disappeared. I've not pressure tested it yet but certainly not seen any errors since. I'll update this thread if the problem comes back. I'm pretty confident i was never coming up against any GDI object limits but have also increased them as part of the trouble shooting process (but this didn't solve my issue).
Regarding physical RAM, I agree 12GB is a little low but I've only just purchased the P4000 and the system is working like a dream so i'll only install more RAM if I start bumping up against the limit. Currently i seem to be running around 6GB for most of what I do (which is why the error message was so frustrating!).
Ah, yeah... I forgot about the Virtual Memory change. We have played around with that over the years and what we are running is below. For a while we set the MIN and MAX to the same amount, but discovered that when the 'warning' threshold is crossed by the time the system realized it, it was too late and hit the maximum. At which point it has no room and crashes. Again, this is what we use... and there are many, many opinions out there on this subject.
I'll probably pull it down a bit to give a small difference. However, what i 'appeared' to be experiencing was that SW was throwing the error message without using anything above the min threashold, so pulling it down will just mean that i'll get warnings sooner. I think i'll keep them quite close and evaluate next steps if/when I hit the limit.
Now the system is working better, the next step may be to install more physical RAM...
Retrieving data ...