Max Commit Charge less than Total RAM?

I turned off paging file to see if it would result in any performance increase (haven't had time enough to tell yet) or possibly better battery life from not utilizing the hard drive as much, but noticed right after reboot that somehow my maximum Commit Charge is only 1936892 KB instead of 2097152 (2 GB). That's 156.5 MB of difference - certainly more than the 2 MB or so I'd expect. If I had integrated graphics I would expect some of my system memory to be lost to the video card - but I have dedicated graphics. Even if the system had to map every bit in the GPU to the system memory I'd expect to lose 256 MB - not 156 MB.

So how'd I end up losing 156.5 MB from the Commit Charge?

Physical Memory still is with 4 MB of what it should be, so I'm not too concerned there. Just confused over how the Commit Charge is lower than physical memory.

Other stats: System Cache is about 241,000 KB. Currently have Windows turned to Programs mode rather than System Cache. I don't imagine turning Windows to System Cache mode could possibly help program performance as well? Kernel Memory around 98,500 KB.

Note: Memory usage is consistantly below 1 GB with 2 GB installed. Wouldn't try this if I were approaching 2 GB memory usage.

 

I think(but not 100% sure) that there may be some programs(maybe windows) using threads that must always reside in RAM, thus that memory is marked as non-pageable, and it wouldn't show in the Commit Charge.

 

That would make sense - but the Kernel Memory is Windows, and that's only 2/3 of the missing RAM. There's still 58 MB floating around out there.

Still getting the 1,936,000 KB figure after a reboot, BTW. Kernel memory is up to 110 MB this time around.