On a Windows 10 system, Process Explorer and PSlist64 report over 100 processes with Virtual Size over 2151700000 K (2 petabytes, each or > 200 petabytes total). Then there is a break in size (when sorted in descending VM size), and the VM values continue with values like 50,000,000 K (50 TB).
Are these 2 Petabyte values accurate and realistic? Maybe in a 64 bit environment, this is not impossible, but it seems odd.
I observe that all the values seem to be of the form 2^31 + X where X is a value that could be considered a "reasonable value" of a few GB. Is it possible there is some type of high bit "tag" of 0x80000000 on some, which is not accounted for in the display of VM values?
I'm trying to diagnose a progressive "resource exhaustion" situation, where Windows eventually starts filling the log with Event ID 2004 "Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: OUTLOOK.EXE (7376) consumed 655523840 bytes, WavesSvc64.exe (13124) consumed 513835008 bytes, and streem.exe (12428) consumed 481574912 bytes." Concurrently, the Physical Memory use reported by t ProcExp and Resource Monitor goes above 95%. This causes system instability and failure. After rebooting the physical memory used is about 30% (12 G of 32G installed) which slowly starts to grow again over a day or two.
While 655 GB of virtual memory for Outlook is huge, these numbers are far smaller than the VM values reported in PSLIST and ProcExp for processes such as svchost.exe, msedgewebview2.exe, and Teams.exe which are in the petabyte range as described above.
Does anyone have any information on how Virtual Memory values in Sysinternal tools are interpreted?