F5F Stay Refreshed Software Operating Systems Prevent the operating system from terminating applications due to insufficient memory.

Prevent the operating system from terminating applications due to insufficient memory.

Prevent the operating system from terminating applications due to insufficient memory.

I
Ikbennietflof
Junior Member
4
08-22-2016, 04:56 PM
#1
I turned off my pagefile because it wasn’t doing anything useful. As soon as my PC reached 4.0GB of RAM, Windows showed the 'Close programs and save now' alert and ended the program I was using—FALLOUT FREAKING 4. What a surprise! With only half of my 8GB being used, Windows shouldn’t be warning me about low RAM. After re-enabling it, the issue disappeared but remained bothersome. Even on my server with 16GB of RAM, this happens. How can I stop Windows from closing things like this? My Chromebook doesn’t do this on Windows 10 and has just 2GB of RAM. I’m trying to stay calm but it’s really frustrating.
I
Ikbennietflof
08-22-2016, 04:56 PM #1

I turned off my pagefile because it wasn’t doing anything useful. As soon as my PC reached 4.0GB of RAM, Windows showed the 'Close programs and save now' alert and ended the program I was using—FALLOUT FREAKING 4. What a surprise! With only half of my 8GB being used, Windows shouldn’t be warning me about low RAM. After re-enabling it, the issue disappeared but remained bothersome. Even on my server with 16GB of RAM, this happens. How can I stop Windows from closing things like this? My Chromebook doesn’t do this on Windows 10 and has just 2GB of RAM. I’m trying to stay calm but it’s really frustrating.

D
D_J_Wafflez
Member
51
08-23-2016, 08:50 PM
#2
Start with superuser. Proceed at your own risk. Launch the registry editor by clicking the Windows icon, typing “regedit” and pressing Enter. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WDI\Export the folders listed as your backup. Assign ownership of each folder mentioned in step 3. Right-click the folder, select permissions, click Advanced, set owner to your user, then confirm by clicking OK and granting full control to your group. Remove the folders from step 3. Restart your system. Warning: Memory limits will become critical; once it runs out, programs may stop functioning unpredictably. I find this consequence just as bothersome as intrusive pop-ups. If you regularly strain your machine’s memory, reconsider disabling low-memory alerts. You can always recover the three folders from the backup, and Windows Vista will kindly remind you again. Note: This method also works for Windows 7.
D
D_J_Wafflez
08-23-2016, 08:50 PM #2

Start with superuser. Proceed at your own risk. Launch the registry editor by clicking the Windows icon, typing “regedit” and pressing Enter. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WDI\Export the folders listed as your backup. Assign ownership of each folder mentioned in step 3. Right-click the folder, select permissions, click Advanced, set owner to your user, then confirm by clicking OK and granting full control to your group. Remove the folders from step 3. Restart your system. Warning: Memory limits will become critical; once it runs out, programs may stop functioning unpredictably. I find this consequence just as bothersome as intrusive pop-ups. If you regularly strain your machine’s memory, reconsider disabling low-memory alerts. You can always recover the three folders from the backup, and Windows Vista will kindly remind you again. Note: This method also works for Windows 7.

S
sammie3001
Junior Member
46
08-29-2016, 09:26 AM
#3
I experienced low memory alerts recently on a mass spectrometer at work. A background Windows process began leaking memory, prompting it to shut down the instrument. To fix this, I replaced the PC with a newer model featuring more RAM. Although a registry workaround existed, it wasn’t suitable for a critical system, and the time needed to address the memory issue wasn’t justified.
S
sammie3001
08-29-2016, 09:26 AM #3

I experienced low memory alerts recently on a mass spectrometer at work. A background Windows process began leaking memory, prompting it to shut down the instrument. To fix this, I replaced the PC with a newer model featuring more RAM. Although a registry workaround existed, it wasn’t suitable for a critical system, and the time needed to address the memory issue wasn’t justified.

F
Frogimouse
Member
217
08-29-2016, 03:55 PM
#4
F
Frogimouse
08-29-2016, 03:55 PM #4

A
ababanana
Junior Member
42
09-03-2016, 11:56 PM
#5
Thanks for the update. Currently, there are no BSODs with 6.7GB usage. The Task Manager is running and showing activity from FO4 and Chrome.
A
ababanana
09-03-2016, 11:56 PM #5

Thanks for the update. Currently, there are no BSODs with 6.7GB usage. The Task Manager is running and showing activity from FO4 and Chrome.