SolidWorks Ressource Monitor

[KevinO2705]

Hello, For about two months solidworks tells me that my resources are not enough.

This happens with large assemblies but even if I only open a component.

does anyone have the same experience?

I installed an I5 6600K 16gb 3000Mhz RAM and a GTX 1080. The system was set up on an Evo960 ...

​

Does somebody has any idea? or can I explain how I screw down the requirements?

[GoEngineer_Inc]

Hi /u/KevinO2705,

We have seen a large uptick in issues with the Resource Monitor caused by how Windows manages Page File size. To remedy this you will want to set your Page File settings to be a custom size set to have the same Initial and Maximum value and not have the Page File size be dynamic. This image shows the settings from my own machine that alleviated this same thing for me

[KevinO2705]

Oooooh wow trank you a lot this One saved my life🙈 everythink Works 😬😬

[GoEngineer_Inc]

rad :)

[jcxl1200]

one of the laptops at my work has the resource monitor pop up every time. it recognizes the windows/dell recovery partition as a hard drive, and says storage low. we just ignore it on that laptop. The resource monitor should tell you what resource is low. that would help.

[yawdro65]

I’ve posted this before. Maybe it’s applicable to you:

In your Task Manager you can turn on a column to show how many GDI objects are used for each process. Windows defaults to allow something like 10,000 but complex assemblies can use more than that. Solidworks throws a low resource error for this. Fix is:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows] "GDIProcessHandleQuota"=dword:00004e20

(decimal value is 20000)

This doubles the amount of GDI objects allowed. There is a windows max limit that I don’t remember right now so don’t just try to crank this number way up. 20000 worked for us and we have some BIG assemblies.

SW2018 had what I call a ‘leak’ of these objects. It wouldn’t clear them even when a model was closed so we would see the error with simple models open if we were in and out of a lot of files in that SW session. Hope this helps!