Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Name: Eric
My office's NT server (built on a clone) has this terrible habit of rebooting itself on & off without warning. The vendor suggested changing the power supply as that could be the source of the problem. However, nothing improves after the change.
I have read here that Pagefile setting might have something to do with it in the sense that if the hard disk does not have sufficient physical space left (1.5x the physical RAM), rebooting is bound to happen.
We have 2 SCSI HDD where the primary HDD (8GB) is partitioned to 2 logical drives C: (2GB - Win NT O/S plus basic applications) and G: (6GB - purely Words files). The other HDD (D: 4GB - dedicated application software) is not partitioned. Free space at the moment - C: (1GB), G: (2GB) & D: (2GB).
The pagefile has only been created in C: (533MB) whereas the other 2 drives don't have any pagefile. I read in one of the postings here that each drive should have its own pagefile for optimal performance.
Is this correct? And if it is, what should the pagefile size be for each of the drive?
I checked the CPU utilisation - only about 10% is being used.Any guidance will be appreciated.

Regarding the pagefile, the default recommendation is RAM plus 12 MB. You may want to check out your Startup and Recovery options. I have a feeling you are blue screening and not knowing it since it's probably set up to automatically reboot. Try setting it to not reboot after a failure, you'll get to see if it's a blue screen and you can go from there. Hope this helps.

I too have seen the info saying each drive should have its own pagefile. Now that was each physical drive not drive letter. Big difference.
It is my opinion that you should NEVER have multiple pagefiles. My testing using performance monitor clearly shows that NT/W2K/XP do not, as advertized, use all the pagefiles at the same time or that multiple pagefiles are better then one.
As far as I am concerned the rules are pretty simple
1. if you have two physical drives in the system place the pagefile on the drive not containing the OS
2. pagefile min and max should be set the same so no "dynamic" growth takes place.
3. pagefile should be right sized to usage. In NT it is the max used plus a bit as found in NT diagnostics memory tab. This stat should be used after a month of running without reboot. In W2K and xP a combo of using performance monitor and task managers memory stat will give you a close approximation of actual memory usage. Both of these are usually LESS then the "recommended" especially when considering larger then 512meg of ram.
4. best place to put a pagefile if raided is [in decending order] raid 10, 0+1, 1, 5, 50, 0. Raid 0 is actually the fastest but since it has no fault tolerance it is listed last. I would never put the page file on 50 or 5 unless I had no choice like with HP/Dell/Compaq systems that sell you a raid5 disk system and then partition for OS and data on the same disk set [bad design due to difficulty associated with adding space]

Oh forgot to add that your reboot issue, I believe, is not related to the pagefile. What you discribe is a software and or hardware issue. Overheating is the most common. Check all your fans [just cuz they move doesn't mean they are cooling properly] and add a fan to the system. Reseat the cpu and the ram. Next look at server apps you are running. Look at the applicaiton log and system log for errors proceeding the crashes. Reapply your service pack! A simple step that can fix many issues.

Thanks a lot Wanderer. Really appreciate the insight provided. Will check out the recommendations you suggested.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |