Windows Server automatically rebooting

Hi debuggerau,

Windows Update is not automatic on Server so this is ruled out.
ChkDsk shows up no bad sectors.
Terminations, cables, power all look good.
No Drives have been moved and all look okay.

Worst case looking imminent....

This is dmp is pointing to either a hard disk driver issue or a corrupt page file. First update your drivers, and if that doesn't resolve the issue, delete your page file and recreate it. You should be set. Let me know if you have any questions. Good Luck.

Stormitex,
Have you added any new hardware or installed any new programs or updates?

Most likely this is a sign of hard-disk damage. When windows tries to access a file that resides on a damaged area of the hard disk the program crashes.
Check to see if the HDD's Manufacturer has any driver or firmware updates.

Chkdsk is a great util but you need something that is much more powerful.
I recommend using SpinRite:  http://www.grc.com/sr/spinrite.htm
Spinrite has been around since the late 80s' and I don't know of any program that does it better.

C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector.

If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.

IDE drive are configured as Master Slave, you can have 7 to 16 devices on a single SCSI chanel give or take, based on config and type etc.

For the SCSI devices to work each end on the chain has to be terminated, in the past there was a physical plug that you would insert to terminate the device, then it was changed to a jumper, and eventually self terminating (some devices).  The reason that I am going into this is that lets say you have a scsi tape back drive or scanner or some other SCSI device that was the terminator.  If you remove the device from the chain you need to select what will be the new terminator, otherwise you will have issues.

Hope this info helps, let me know if you have any other questions.

Thanks
Roger

From the debug report, the windows server is crashed with NT Status code c000000d and it is the symptom of coruppted paging space.  Re-define the paging space may resolve the blue screen problem.

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

cpc2004,
The pagefile is corupped, but it could be because one of the sectors it is written on is bad, so when the pointer get to that location time for a little blue :)

The swapfile can be configured to be deleted and regenerated when the computer reboots.  This is used when security issues dictate that the swapfile must be cleared, otherwise someone can recover a great deal of historic data.
If you want to try this run RegEdit to and open:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
Now you should see:
ClearPageFileAtShutdown
The default value is 0 Change it to a 1

If you don't see ClearPageFileAtShutdown then create a New DWORD Value and configure it as:
Value Name: ClearPageFileAtShutdown
Value Type : REG_DWORD
Value         : 1

Thanks
Roger

Hi All,

The Server repeatedly blue screened numerous times this morning.  Also would not start in Safe mode.  We have a Maxtor Drive connected via firewire and a Disk Array attached via a Scsi cable.  I disconnected both and then restarted the Server.  All was fine.  I shutdown the server, connected the scsi cable and restarted.  It hasn't skipped a beat yet.  I doubt that it was simply the Maxtor drive, however I have since uninstalled all software relating to the drive and monitoring the outcome.