PROBLEM WITH PAGEFILE SIZE

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

AFTER INSTALLING WINDOWS XP SP1 AND OFFICE 2003 I'M HAVING PROBLEMS WITH THE
PAGEFILE SIZE. THE PC EVERY NOW AND THEN RESTARTS AND I GET AN ERROR WITH
MINIDUMP FILE WHICH I SEND TO MICROSOFT OFF COURSE.

DOES SOMEBODY KNOW HOW TO HELP?

P.S. I HAVE SELECTED THE PAGEFILE TO BE AUTOMATICALLY CHANGED BY THE SYSTEM
EACHSELF.
 
Hi,

What is the exact error message and when does it occur?



Please, do not use the capslock key when you reply, as it makes it hard on
the eyes to read.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
My physical memory ram is 512mb. Well i setted the minimum size at
768*2=1536mb and the maximum at 1536*2=3072mb. The error message goes like
this: the system has recover from a serious error.....For more information
check the report.....And in the technical information it refers the minidump
file. The problem although i changed the default values in the pagefile size
remains. What is causing this problem?

Thank You!
 
Stefanos_Karametos said:
My physical memory ram is 512mb. Well i setted the minimum size at
768*2=1536mb and the maximum at 1536*2=3072mb. The error message goes like
this: the system has recover from a serious error.....For more information
check the report.....And in the technical information it refers the minidump
file. The problem although i changed the default values in the pagefile size
remains. What is causing this problem?

Probably something quite unrelated to the page file. In any case I
would regard the initial size you have set for that as grossly too much.
(see my page www.aumha.org/win5/a/xpvm.htm). Try 256 initial and say
1000 Max. Then you have something that is crashing and the system's
'automatically restart' is cutting in. Turn this off: in Control Panel
- System - Advanced, click Settings in the Startup and Recovery section.
There uncheck 'automatically restart'. You may now get a Blue screen
failure instead, but at least will get some guidance as to what is
happening. Quite likely a driver - see the bottom line of the Blue
screen for something.sys then look for it in system32\drivers and take
its properties
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top