Windows 10: Memory leaks on System D but not system A-both 16 GB Win 10 64

I use a desktop system A and a laptop system D. Both are Win 10 Pro 64, and both have 16 GB of RAM. As much as possible, these machines have identical configurations. Both MS Office and various other application programs running on them. I use the laptop whenever I'm not at my desk, which is at least several times a week, and when I'm traveling for my job.

Only on the laptop, System D, do I get this error message when I start Outlook: "There is not enough free memory to run this program. Quit one or more programs, and then try again" I don't get this error message every time I start Outlook. It seems random as to when I do get this message. I don't understand why I would get this message on the laptop, but never on the desktop, when both machines have the same OS, same applications, and pretty much the same configuration. I don't get this error running any other MS Office applications or Adobe software like Lightroom or Photoshop.

If it matters, the desktop system is a home-built rig with an ASUS P9X79Pro motherboard with an i7-3930K CPU. The laptop is a late model Lenovo T560 with an i7-6600U CPU.






:)

 

Windows 10 System Memory leak

Had the same issue. As ridiculous as it sounds, below is what fixed my Win 10 memory leak on System, PID 4.

(I have no affiliation with the below, other than it fixed my issue which looks exactly like what I see here.)

From http://www.bidnessetc.com/business/how-to-fix-microsoft-windows-10-memory-leak-issues/ :

Open Settings. Navigate to System > Notifications & Actions.
Unselect "Show me tips about Windows" and reboot your PC.

 

Windows 10 System Memory leak

This is not an error on MS side, at least concerning the one where disabling network data usage monitoring fixes it (the first posted regedit fix). It's related to wonky NIC drivers. Some (mostly older) Realtek cards affected by this also exhibit the same
behaviour on Win 8 and 8.1 (where NDU was introduced).

However, the System leak due to Runtime Broker and Superfetch is weird indeed. Mostly because they run their own processes and they are not a part of the System process. There is a known Win10 Runtime Broker memory leak, but it eats available memory with
its own process, not System. Superfetch, if faulty, should also eat memory using svchost.exe. I wonder why it happened in case of MaXi32.

 

Memory leak issue

The term "memory leak" means that an application fails to return all its RAM to the operating system when it exits. The leftover RAM is unusable to the operating system.

Step one is to identify the application that is leaking memory. Step two is to contact the application's developers and provide as much detailed data on the memory leak as you can. For example: which processes are still in RAM after the application exits
and how much RAM they occupy. Application developers never want their applications to leak memory and they will be grateful for the details you provide, particularly if they can replicate the leak on their own computers.