Virtual memory keeps running out

Blackbat · 15 Jun 2020

My PC has 32GB of memory and I've never had an issue with virtual memory in the past. I'm now running out of virtual memory every few days which seems to be caused by the commit size for searchindexer.exe constantly increasing. I noted today when I ran out of VM that the commit size for searchindexer was up to around 27GB. I had Windows managing VM, and VM allocated grew to something like 60GB although now I've set it manually to the min/max recommended (16/4918).

Can anyone suggest why this might be happening, please? It's possibly tied in with the install of the 2004 update I did a few weeks a go as I don't recall the issue happening before that. Stopping and restarting the search indexing service frees up virtual memory, but then it just starts increasing again. In the time I've taken to type this the commit size has gone up from 38k to over 200 although there is no CPU activity showing for the search indexing service.

Megahertz · 15 Jun 2020

Must be something wrong.
With 32GB of memory you shouldn't even need virtual memory.
I have 8G and never seen more than half in use.

Do you have a hardware monitor?
I use Open hardware monitor. Extract and run. Don't need to be installed. Under options you may set to run on start up.

Blackbat · 16 Jun 2020

I can run a hardware monitor but I'm not sure how doing that will help resolve the issue.

- - - Updated - - -

Just to expand on my ramblings above, it appears that searchindexer is gradually using up physical memory to the point that other processes need to start using virtual memory as there's not enough physical memory left, and finally paging file space runs out. So the question is how can I stop the search indexer process using up all the memory. Currently it's just indexing my start menu and IE history, and yet after the last time I rebooted memory usage is 8GB and rising.

Paul Black · 16 Jun 2020

Hello @Blackbat,

Welcome to TenForums!

Have a look at this and see if you think it would be beneficial! => MemTest86.

I hope this helps!

Pejole2165 · 16 Jun 2020

There is definitely something wrong with your system, using 2004 on a system with 40Gb RAM my VM commit is only 2.8Gb (rises on opening apps) but never triggers an out of memory error.
On this system with default search indexing options the indexer service uses approx. 30Mb RAM.

That figure only increased by about 2Mb when i navigated through several folder layers and created a test.txt file in each layer (6 layers deep).
Maybe try running SFC and/ or DISM to see if there is an issue with the indexer service or dependencies.

Paul Black · 16 Jun 2020

Hello @Blackbat,

Yes, running SFC as @Pejole2165 has mentioned might gleam some information!

Can you please perform the following . . .

[1] Goto this TenForums link => Batch Scripts / Programs.
[2] Goto the heading SFC [ System File Checker ] . . .
[3] Download and Run the .bat file, Options [2] & [3].
[4] Upload the results => How to Upload and Post Screenshots and Files at Ten Forums.

I hope this helps!

Blackbat · 16 Jun 2020

Thanks for the suggestions. I've run SFC as requested. Results attached below.

Attachment 283576

Paul Black · 16 Jun 2020

Hello @Blackbat,

Blackbat said:

Thanks for the suggestions. I've run SFC as requested.

Was there a message saying "Windows Resource Protection did not find any integrity violations."?

Blackbat · 16 Jun 2020

Paul Black said:

Hello @Blackbat,

Was there a message saying "Windows Resource Protection did not find any integrity violations."?

There was.

Paul Black · 16 Jun 2020

Hello @Blackbat,

I thought so, I just wanted to check.
The file you attached was clear of errors anyway!