Windows 10 and ram

[Young Enthousiast]

Hello clever people of the interwebz, 

 

I am getting a lot of errors in Windows 10 regarding ram.

When I use a program like the latest Adobe Premiere Pro CC or Photoshop CC Windows just seems to give up if I go past using about 6GB of ram. Windows first gives a message which says that the program I am using is using too much ram (which I have 12GB of while it only uses about 6-7GB) after this error the program becomes unresponsive and my wallpaper disappears. I used multiple memtest programs in and out of Windows, I have also used Asus realbench with no errors. My Windows 10 installation is a fresh one on my Asus N56JN-CN035H laptop, upgraded with a Samsung 840 evo ssd and 8GB of Kingston ValueRAM KVR16LS11/8 (combined with the 4GB of Kingston 1600mhz ram that was pre-installed). 

 

At this point I have no idea what causes the issue. The pagefile is set to automatic, the ram is at 50-60% and the ram doesn't seem to generate any problems in a bench/test program. Still Photoshop and Premiere often crash with the error that there is too little ram.

 

Does anybody know what might cause this issue and how to solve it?  

 

 

[Tedster]

-postsnip-

 

Does anybody know what might cause this issue and how to solve it?  

I believe that Windows 10 likes to use RAM more than other Windows versions for caching more stuff but if that's causing you problems, I'd suggest trying to disable stuff like SuperFetch if your storage setup is fast enough.

https://www.youtube.com/watch?v=RPvOMlxLQAI

[OSBK]

this ram issue is a very known problem in windows 10 until now there is no final solution. so you'd better do if you go back to windows 7 or 8.1

[The Official Czex]

Disable SuperFetch like @Tedster said.

[Grrizz]

IDK if these are the same problems as what you are having but with SolidWorks there are two causes for that error, one is the GDI object limit in windows which SolidWorks seems happy to fill up sometimes, you can check if this is the cause by going to 'task manager', right clicking on a column title and going to 'select columns' in there you can turn on 'GDI objects' and see how many you are using, I think the default limit is 10K but you'll get warnings at about 7K IIRC, if that's the cause you can fix it by upping the limit in the registry (google for the process). The other cause I found was SolidWorks wouldn't request virtual memory correctly so I manually set it with the 'initial size' as equal to my memory (16GB) and the max double that, its a bit wasteful but 16GB of storage space really isn't worth worrying about these days unless your stuck on a 128GB or smaller SSD and its all about the end result of getting rid of that error anyway

Hope that helps you, unfortunately I don't have much experience with Adobe CC specifically.

[Young Enthousiast]

@Tedster @The Official Czex  SuperFetch was already disabled 

[Tedster]

@Tedster @The Official Czex  SuperFetch was already disabled 

Okay, you've left me clueless for now (:

[Young Enthousiast]

this ram issue is a very known problem in windows 10 until now there is no final solution. so you'd better do if you go back to windows 7 or 8.1

The weird thing to me is that it already crashes at only 50% usage of the ram 

[Tedster]

The weird thing to me is that it already crashes at only 50% usage of the ram 

Have you run a memtest to verify that all of your RAM is working fine?

[Young Enthousiast]

Also in the taskmanager I can see Premiere Pro running and using 4GB of memory now while it doesn't appear to be running while looking at the taskbar. 

[Young Enthousiast]

Have you run a memtest to verify that all of your RAM is working fine?

Yes, on a usb stick to eliminate Windows as a variable and in Windows, both with no crashes. 

[Young Enthousiast]

IDK if these are the same problems as what you are having but with SolidWorks there are two causes for that error, one is the GDI object limit in windows which SolidWorks seems happy to fill up sometimes, you can check if this is the cause by going to 'task manager', right clicking on a column title and going to 'select columns' in there you can turn on 'GDI objects' and see how many you are using, I think the default limit is 10K but you'll get warnings at about 7K IIRC, if that's the cause you can fix it by upping the limit in the registry (google for the process). The other cause I found was SolidWorks wouldn't request virtual memory correctly so I manually set it with the 'initial size' as equal to my memory (16GB) and the max double that, its a bit wasteful but 16GB of storage space really isn't worth worrying about these days unless your stuck on a 128GB or smaller SSD and its all about the end result of getting rid of that error anyway

Hope that helps you, unfortunately I don't have much experience with Adobe CC specifically.

I'll try that now

[Young Enthousiast]

After having changed things like the pagefile I can't get it to crash at about 6GB but I can get it to crash at about 18GB (about 11GB ram and 7GB pagefile). The GDI was about 200 max so thats not the problem. Just before it crashed I did get a message that the nvidia driver had crashed and had been restored.

[GoodBytes]

Did you touch the pagefile? That sounds like previously touched the pagefile, and hence why you have these issues.

[Young Enthousiast]

Did you touch the pagefile? That sounds like previously touched the pagefile, and hence why you have these issues.

Windows 10 originally set the pagefile to 1GB and I have just changed it to automatic.

[Young Enthousiast]

Okay, it seems to be solved by setting the pagefile size to automatic. I find it weird that the stock setting only allows the pagefile to be 1GB but changing it to automatic worked. 

[BrightCandle]

As a programmer of a Windows application its possible to assign memory to different purposes. Software that uses a lot and especially software designed before the 64 bit era (which is most of it) tends to be designed to have a 2GB working set and then use the page file explictly. Its possible in the Windows API to put parts in the pagefile because while you want to access it like its RAM in practice you know its not going to really be read randomly as its video or such. So what happens it gets set to be paged out. So what happens is if your page file isn't big enough you run out of RAM even though you have physical RAM.

 

This happens with a few games as well like Arma 3 that uses the page file pretty heavily. Its one of the reasons why the very old advice of setting the page file to something small is actually quite bad, because many programs will use the page file quite heavily for basic work even when RAM is available.