Hi just wondering how much ram should be used on idle for windows 7. I am using the cpu/ram guage on my desktop and when nothing is going on, it stays on 25% which is 1gb out of my 4gb. Is this normal? I understand that windows allocates ~600mb for itself and I have avg running in the icon tray but that shouldnt add up to 1gb should it?
You may not be doing anything, but the computer certainly is not idle. Windows is trying to utilize as much idle resources it can to fulfill the needs of background task while the system is not under load. None of that RAM is locked to the OS, a minimum 200 MB is reserved depending on if you configured the Kernel to be paged out or not.
My advice, do not concern yourself with idle resource usage.
Hello Cobalt,
Yes, this is about normal. Resource Monitor can help give you a better detailed idea of what all is using your memory under the memory tab.
Hope this helps,
Shawn
With the DisablePagingExecutive Registry entry of course.
DisablePagingExecutive
ChuckR - this is a popular phantom tweak. This setting is useful when debugging drivers and generally recommended for use only on servers running a limited well-known set of applications. Applies only to ntoskrnl.exe
I note the link is for Windows 2000 Server, not w7.ChuckR - this is a popular phantom tweak. This setting is useful when debugging drivers and generally recommended for use only on servers running a limited well-known set of applications. Applies only to ntoskrnl.exe
I make it a point to never manually make any Reg changes, ever.
This now (to me) raises general questions of:
chuckr is really a dummie !!!
Once he's paged out, who's "in charge"?
With "PagingExecutive" disabled, who brings him back in?
Must be more to 'Debug' stuff than meets the eye...
(Changed C..R to c..r, deliberately for no Shift_key -- Avoids 'Carpull Tunnel Psychosis'...)
Don't be misled by the name of the reg setting. Read it as "Disable the writing of ntoskernel to the page file."
Thank you for the reg info.
Heck,
That's just another 'c' program:
No wonder it sux !!!
Don't need 'x-ray vision' for that stuff...NTOSKRNL.EXE, the core file of the kernel-mode component of Windows NT, contains the Cache Manager, the Executive, the Kernel, the Security Reference Monitor, the Memory Manager, and the Scheduler, among other things, and is in charge of getting NT up and running. You may be surprised to know that it has a standard main() that is executed when it is loaded by the OSLOADER:
//
// NTOSKRNL main
//
int main( boot parameters )
{
//
// Fire up NT!
//
KiSystemStartup();
return 0;
}
Quote
