nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pagefile Utilized pegged at 100%

BenClark

My Pagefile Utilized percentage has suddenly pegged itself at 100% over the past few hours, when it typically sits at 0% to around 7.5%. Not sure if it's related or not, but I've also just had Server crash/restart itself and the application server is telling me that it's running low on memory. What might be causing this?

Thank you,

Ben

Find more posts tagged with

Accepted answers

MMBR

Your machine is running out of RAM memory, when this happens the machine starts to use the swap paging file on disk to cope with the workload demand, performance of the system drops considerably, if the paging file reaches its maximum allowed size, then the machine can crash. You will need to allocate more RAM memory to the machine and or monitor which processes are consuming most of the memory and try to diagnose from there. I hope this helps.

All comments

AndrewSakowicz

@BenClark , your observation might be correct that page file utilization is related to process crash. It is not unusual that page file utilization will be high even if you have available RAM. In that case, the key is to size page file correctly first, before you consider adding RAM, @MarceloMarques , see Introduction to the page file - Windows Client | Microsoft Learn,

Support for system crash dumps

Page files can be used to "back" (or support) system crash dumps and extend how much system-committed memory (also known as "virtual memory") a system can support.

For more information about system crash dumps, see system crash dump options.

MMBR

You can monitor cpu/memory/disk/network in Task Manager then if you want to get more details click in "Open Resource Monitor", in the Resource Monitor you can sort the processes and identify the processes that are consuming most of the memory.

BenClark

Thanks for the explanation, Marcelo. That's just what support told me too. After a reboot of the machine stuff is back to normal, but I'm worried about it happening again. Do you think looking at service statistics in the Server Manager logs would be a good place to start?

MMBR

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.