The paging file is too small for this operation to complete.

The problem is obviously as it is , is that I don't have enough memory , this is the message from windows event log right before my whole PC crashes

now the problem is that I don't know what the problem is , let us start with that I have windows 10 and I have limited pagefile.sys to 10gb which is more than enough as I see it since I have 16GB ram and here is the actual problem , the message before paging file is too small was a warning telling me a low virtual memory but here where things dont add up :- only 4gb of memory was in use when my computer crashed:

"

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Decompress.exe (2084) consumed 2461761536 bytes, chrome.exe (6276) consumed 662761472 bytes, and eclipse.exe (8008) consumed 618754048 bytes.

"

so I did the mast for you thats a total of :

Decompress.exe 2.461761536 gb

chrome.exe 0.662761472 gb

eclipse.exe 0.618754048 gb

so first of all i have no idea what Decompress.exe is even , second of all i have 10gb pagefile sys and 16gb physical ram , what could the cause be for my computer crashing on 4gb ?

-Things worth noting the crashes are random , I do have 16gb installed ram when I check my PC , I do play demanding games that easily demand 12-16gb ram and I can get consistent several continuous hours in them without crashes , but chrome and other simple apps on togther seem to crash my PC :/.

-Thanks in advance , all help would be appreciated ..

Low virtual memory warnings relate to the commit charge and have nothing to do with RAM usage. The commit charge is shown in Task Manager - Performance tab when showing memory info. In Windows the commit charge cannot exceed the commit limit which is approximately RAM size + pagefile size. How much RAM is in use is irrelevant to this.

The number shown as "Commit" in Task Manager - Performance tab is the important one. Note that high commit charge may not be due to a process. There are potential major users of the commit charge that are not processes, not all of which are shown in Task Manager.

The commit charge can be difficult to understand. Many Internet articles get it wrong.

LMiller7 said:

Low virtual memory warnings relate to the commit charge and have nothing to do with RAM usage. The commit charge is shown in Task Manager - Performance tab when showing memory info. In Windows the commit charge cannot exceed the commit limit which is approximately RAM size + pagefile size. How much RAM is in use is irrelevant to this.

The number shown as "Commit" in Task Manager - Performance tab is the important one. Note that high commit charge may not be due to a process. There are potential major users of the commit charge that are not processes, not all of which are shown in Task Manager.

The commit charge can be difficult to understand. Many Internet articles get it wrong.

okay but how can I identify the culprit behind this much commit charge?

- - - Updated - - -

zinou said:

You need to identify what Decompress.exe is. it seems that's a program installed by a game!

What is decompress.exe? Is it Safe or a Virus? How to remove or fix it

You can use the Task manager to see where this program is located.

the problem is i dont see this Decompress.exe inside task manager , i only saw it inside the windows event log...

- - - Updated - - -

So as most of you guessed , decompress.exe is one of the main aspects behind this program .. i found another windows event log which shows leaked memory before the crash and decompress.exe is always in it using around 2.4gb of RAM as well as I see always an additional 2.4gb of ram unaccounted for in taskmanager but the problem is Decompress.exe is no where to be found ... I have ran 3 different antivirus checks including malwarebytes, bitdefender and windows defender .. all of which found nothing , as well as i tried searching automatically and manually for decompress.exe and found nothing as well as it doesnt even show up in task manager(and yes taskmanger is elevated .. , any idea how the hell i could get rid of this infected hell decompress.exe ?

The PC crashes may be independent or unrelated to the page file.
How come you limited the page file size?
Had you worked up the crashes?

The explanation to why Decompress.exe isn't showing in Task Manager is simple. It was running when the event log entry was made but was not at a later time. Processes come and go all the time.

But the evidence that Decompress.exe is the cause of the problem is really quite weak. Out of memory warnings occur when the commit charge reaches the commit limit. With 16 GB RAM and a 10 GB pagefile the commit limit will be 26 GB. The contribution of Decompress.exe to that is less than 10%.

Post a screenshot of Task Manager - Performance tab showing memory information. This may show something useful.

It is entirely possible that the only real problem is the artificially restricted pagefile. It is best to set it to System Managed unless there is some compelling reason to do otherwise. The belief that 10 GB is more than enough is due to misconceptions of how the pagefile is used. The primary use of the pagefile is to expand the commit limit. The commit charge has NOTHING to do with how much RAM is being used. Having a high commit charge and low memory usage are not in any way contradictory.

oh guys my bad ! , I thought I mentioned that before but apparently i didnt, so I made pagefile.sys auto managed by system and put it on my second hard drive with 100+gb of free space so currently I have virtual memory on system managed and it is reaching size of 20gb + but the same problem still occurs .. so I really doubt pagefile.sys limitation had anything to do with it , * I repeat I have had my VM automatically managed by system now for a quite a while and that didnt even remotely help*
(I also tried the default system managed virtual memory on main(aka system hard drive) and still same problem - but on my main hard drive i even ran out of space some times because of huge pagefile.sys size

- - - Updated - - -



i have had crashes with 10gb of memory only commited ,
and btw i have tested my ram with a full memtest run overnight and no errors found ..
the reason why i suspect decompress.exe is because even though it doesnt take up alot of memory , there is always a leak warning before the crash in the windows event logs that tells me that decompress.exe and few others apps are leaking (still the leaks all the times dont even pass 5gb) but my pc still crash weirdly enough :/