Oh, and set it to a static size - upper and lower limits the same. Saves a lot of grief if done at time of original OS install, as it keeps the page file from fragmenting furiously on a loaded machine.
1-5 fragments are OK for a page file. 50-500 fragments (or more!) not so OK for a page file. I speak from experience... Kurt On Tue, Apr 7, 2009 at 16:39, Sam Cayze <[email protected]> wrote: > I can't find anywhere if it's the initial size, or the max size that has > to be larger than the RAM? > > Don't recall ever changing the page file settings on this box (or > anywhere). I'm not well versed in page file technology. > > > > -----Original Message----- > From: Ben Scott [mailto:[email protected]] > Sent: Tuesday, April 07, 2009 6:32 PM > To: NT System Admin Issues > Subject: Re: Memory.dmp > > On Tue, Apr 7, 2009 at 5:44 PM, Sam Cayze <[email protected]> > wrote: >> I think the Page File might have been too small :( > > That will do it. To get a full memory dump, a page file has to be on > the System Drive (the drive containing Windows), and that page file has > to be at least the size of RAM plus a few MB extra for dump metadata. > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
