What size paging file to trap memory.dmp?

[Knack]

Is it RAM+1MB or RAM+10MB? Or perhaps even a larger value for reliability?

A friend is running a dogfight game on his 512MB PC and the BSODs are
occurring so often that he really needs to get memory.dmp analyzed. Tech
Support by Gateway (for the OEM OS) and Microsoft (for the game) have been
contacted a number of times, and they've already advised all of the easiest
trouble-shooting steps, which turned up nothing.

 

[Alex Nichol]

Is it RAM+1MB or RAM+10MB? Or perhaps even a larger value for reliability?

A friend is running a dogfight game on his 512MB PC and the BSODs are
occurring so often that he really needs to get memory.dmp analyzed. Tech
Support by Gateway (for the OEM OS) and Microsoft (for the game) have been
contacted a number of times, and they've already advised all of the easiest
trouble-shooting steps, which turned up nothing.

Provided the maximum size is significantly larger than the memory that
is being dumped (and I would have that anyway) the initial one does not
really matter. So for a full memory dump have that max as say 550MB at
least - but you might well want more for regular use. What matters is
that the space must be available on the drive that the initial boot goes
to (called by MSoft, very confusingly, the 'system' drive) - normally
C:. Along with boot.ini and other boot files. For a Kernel dump you
need 256 MB