F5F Stay Refreshed Hardware Desktop Ram, page files, and out-of-memory issues

Ram, page files, and out-of-memory issues

Ram, page files, and out-of-memory issues

J
Jihf_Jr
Member
87
06-12-2018, 12:34 PM
#1
I have ample RAM, yet I frequently encounter "Out of memory / Not enough memory" warnings. Key system details: OS version 64-Bit Windows 10 Pro; CPU Intel 14900k; 64GB DDR5 memory from MSI ACE Z790; 3080 GPU from MSI 3080. Despite this, utilization stays below 32GB even though the RAM isn’t fully used. I’ve learned that the CPU’s integrated graphics can allocate some system memory for VRAM, but no monitors are drawing power from it. I expect it won’t consume the full 32GB, as most reports suggest only 2-4GB in use. I’m puzzled by what Windows is actually doing with RAM behind the scenes. Could the problem also stem from paging or virtual memory? The pagefile size looks substantial—about 93GB committed out of 95GB—yet it still appears to use most of the available physical memory, leaving roughly 32GB free. Some suggestions I’ve had: add more RAM (possibly up to 128GB), though that might strain performance and speed requirements; consider mismatched kits; or invest in a dedicated SSD for paging. Transfer the pagefile to a smaller drive, expand its size, and see if virtual memory usage drops. Another option is to keep the current setup but monitor how Windows manages RAM under load.
J
Jihf_Jr
06-12-2018, 12:34 PM #1

I have ample RAM, yet I frequently encounter "Out of memory / Not enough memory" warnings. Key system details: OS version 64-Bit Windows 10 Pro; CPU Intel 14900k; 64GB DDR5 memory from MSI ACE Z790; 3080 GPU from MSI 3080. Despite this, utilization stays below 32GB even though the RAM isn’t fully used. I’ve learned that the CPU’s integrated graphics can allocate some system memory for VRAM, but no monitors are drawing power from it. I expect it won’t consume the full 32GB, as most reports suggest only 2-4GB in use. I’m puzzled by what Windows is actually doing with RAM behind the scenes. Could the problem also stem from paging or virtual memory? The pagefile size looks substantial—about 93GB committed out of 95GB—yet it still appears to use most of the available physical memory, leaving roughly 32GB free. Some suggestions I’ve had: add more RAM (possibly up to 128GB), though that might strain performance and speed requirements; consider mismatched kits; or invest in a dedicated SSD for paging. Transfer the pagefile to a smaller drive, expand its size, and see if virtual memory usage drops. Another option is to keep the current setup but monitor how Windows manages RAM under load.

R
RS_elizabeth
Member
79
06-12-2018, 12:34 PM
#2
The mistakes appear in specific formats and are linked to certain software tools.
R
RS_elizabeth
06-12-2018, 12:34 PM #2

The mistakes appear in specific formats and are linked to certain software tools.

P
PersieO
Posting Freak
786
06-12-2018, 12:34 PM
#3
Specifically which program? It might be a known problem with the software you're using. For 32-bit systems, the limit is 4GB RAM, so that shouldn't be a problem. However, it can still appear as if the RAM is reserved for the graphics card. That doesn’t seem likely here. This suggests a software-related issue—possibly a memory leak or malware. At this stage, reinstalling Windows might be the best approach. It looks like something is broken during installation, and fixing Windows setups usually causes more trouble than it solves.
P
PersieO
06-12-2018, 12:34 PM #3

Specifically which program? It might be a known problem with the software you're using. For 32-bit systems, the limit is 4GB RAM, so that shouldn't be a problem. However, it can still appear as if the RAM is reserved for the graphics card. That doesn’t seem likely here. This suggests a software-related issue—possibly a memory leak or malware. At this stage, reinstalling Windows might be the best approach. It looks like something is broken during installation, and fixing Windows setups usually causes more trouble than it solves.

P
primemaster77
Junior Member
9
06-12-2018, 12:34 PM
#4
You can still avoid memory issues with 32-bit applications. These programs are common and work well on x64 systems. They are restricted to about 3.5GB of RAM, which is a reasonable limit. Some other programs, like Java, also have flexible memory settings, allowing developers to manage their usage effectively.
P
primemaster77
06-12-2018, 12:34 PM #4

You can still avoid memory issues with 32-bit applications. These programs are common and work well on x64 systems. They are restricted to about 3.5GB of RAM, which is a reasonable limit. Some other programs, like Java, also have flexible memory settings, allowing developers to manage their usage effectively.

W
Wilson1
Member
178
06-12-2018, 12:34 PM
#5
It usually indicates a malfunctioning application or driver. The Task Manager sorted by memory usage will typically display a program consuming an unusually large amount of resources—often exceeding the standard 64GB threshold, especially under typical conditions.
W
Wilson1
06-12-2018, 12:34 PM #5

It usually indicates a malfunctioning application or driver. The Task Manager sorted by memory usage will typically display a program consuming an unusually large amount of resources—often exceeding the standard 64GB threshold, especially under typical conditions.

D
DRGNdragsYT
Senior Member
723
06-12-2018, 12:34 PM
#6
It seems like a software project with a significant memory issue. I just upgraded my media/homelab server to 64 GB, but it's not consuming much space. It's running Windows 10 Pro, with three virtual machines on Hyper-V, and overall memory usage is around: The host machine under Windows 10 is also handling XAMPP, Filezilla SFTP Server, Kodi, and a few other applications. Try to identify the memory consumer using Task Manager... otherwise what RONOTHAN## has already inquired about. Cheers Ang
D
DRGNdragsYT
06-12-2018, 12:34 PM #6

It seems like a software project with a significant memory issue. I just upgraded my media/homelab server to 64 GB, but it's not consuming much space. It's running Windows 10 Pro, with three virtual machines on Hyper-V, and overall memory usage is around: The host machine under Windows 10 is also handling XAMPP, Filezilla SFTP Server, Kodi, and a few other applications. Try to identify the memory consumer using Task Manager... otherwise what RONOTHAN## has already inquired about. Cheers Ang

N
NoahWraith
Member
199
06-12-2018, 12:34 PM
#7
The issue mainly involves Chrome, which tends to consume a lot of memory. I've enabled the memory saver but still face errors like "Not enough memory to load page" when refreshing pages. Similar problems appear with Firefox, Solidworks, and several JetBrains IDEs. The error messages often mention insufficient RAM, though it's unclear if Task Manager shows the correct usage stats. It seems the paged RAM plus physical RAM adds up, but the available free space is low—around half used and nearly half in standby. In the RamMap view, the top program is a JetBrains application using about 4GB, followed by browser and background tasks consuming a few MBs each. Overall, around 45-50% of resources are active.
N
NoahWraith
06-12-2018, 12:34 PM #7

The issue mainly involves Chrome, which tends to consume a lot of memory. I've enabled the memory saver but still face errors like "Not enough memory to load page" when refreshing pages. Similar problems appear with Firefox, Solidworks, and several JetBrains IDEs. The error messages often mention insufficient RAM, though it's unclear if Task Manager shows the correct usage stats. It seems the paged RAM plus physical RAM adds up, but the available free space is low—around half used and nearly half in standby. In the RamMap view, the top program is a JetBrains application using about 4GB, followed by browser and background tasks consuming a few MBs each. Overall, around 45-50% of resources are active.

A
AraxSpielt
Member
57
06-12-2018, 12:34 PM
#8
Yeah, it's about using committed paging plus physical RAM. "Standby" files are cached by Windows for often used data. You might want to clear them when you're not actively using things. All the problems you mentioned seem like memory leaks in a driver, which are tough to find. A fresh install should likely solve the issue.
A
AraxSpielt
06-12-2018, 12:34 PM #8

Yeah, it's about using committed paging plus physical RAM. "Standby" files are cached by Windows for often used data. You might want to clear them when you're not actively using things. All the problems you mentioned seem like memory leaks in a driver, which are tough to find. A fresh install should likely solve the issue.

A
Alsacecoser
Junior Member
44
06-12-2018, 12:34 PM
#9
I'll likely attempt to reinstall Windows and upgrade to Windows 11 soon. For the memory leak question, I'm not sure why it wouldn't appear as a program consuming memory. As a developer, I know what memory leaks are and how they occur, but I'd expect them to still show up as programs using memory. I'd appreciate seeing high memory usage in Task Manager, like "Hey, you're using all your RAM and running low, fix it or close some apps." But since the manager only shows 50% used, it's confusing to get error messages about being out of memory when there seems to be plenty of free space.
A
Alsacecoser
06-12-2018, 12:34 PM #9

I'll likely attempt to reinstall Windows and upgrade to Windows 11 soon. For the memory leak question, I'm not sure why it wouldn't appear as a program consuming memory. As a developer, I know what memory leaks are and how they occur, but I'd expect them to still show up as programs using memory. I'd appreciate seeing high memory usage in Task Manager, like "Hey, you're using all your RAM and running low, fix it or close some apps." But since the manager only shows 50% used, it's confusing to get error messages about being out of memory when there seems to be plenty of free space.

O
oisin100
Junior Member
14
06-12-2018, 12:34 PM
#10
I've noticed this a few times before. It usually happens in the non-paged pool area in Rammap where drivers are present, implying a driver might be the issue. However, nothing seems out of place, so it likely means something is seriously damaged. Good luck tracking it down (pagefile is disabled).
O
oisin100
06-12-2018, 12:34 PM #10

I've noticed this a few times before. It usually happens in the non-paged pool area in Rammap where drivers are present, implying a driver might be the issue. However, nothing seems out of place, so it likely means something is seriously damaged. Good luck tracking it down (pagefile is disabled).