Citrix states in their article: CTX101595

CTX101595 - Troubleshooting Fatal System Errors and Server Restarts

This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX101595

Document ID: CTX101595, Created on: Mar 5, 2003, Updated: Aug 5, 2003

Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000, Citrix MetaFrame XP 1.0 for Microsoft NT 4.0 Server Terminal Server Edition, Citrix MetaFrame 1.8 for Microsoft Windows 2000, Citrix MetaFrame 1.8 for Microsoft NT 4.0 Server Terminal Server Edition

This article assists with the investigation of Fatal System / Blue Screens and System Restarts / Reboots.

Fatal System Error

1.
Disable the “automatic restart” option. In Windows 2000, right click My Computer > Properties > Advanced > Startup and Recovery > System Failure.

2.
Ensure the system is set up to write a memory dump. See MicroSoft TechNet Articles Q274598, Q192463, Q239552, Q173277, Q254723, and Q129845 for additional information.

3.
Supply the memory dump and the exact fatal system error to the manufacturer of the offending file and check with the manufacturer for recent file updates or known issues concerning the error code.

4.
Ensure that the server only uses a single swap-file located on the root drive. Do not use multiple swap files on different drives/partitions.

5.
In the Startup and Recovery Options; Set the server to produce a "Complete Memory Dump".

Note: It is important to disable the Compaq AutoRecover feature before a memory dump or remote debug. If the AutoRecover function is enabled, it may interfere with debugging the system.

1.
Restart the server.

2.
After initializing the SCSI RAID controller, press F10 to enter Setup. The Compaq System partition starts (it is a DOS-based tool).

3.
Select System Configuration.

4.
Select Configure Hardware (the .cfg files are initializing. This is an EISA configuration tool).

5.
Select Review Settings. Look for Automatic Server Recovery at the bottom of the page.

6.
Mark Enabled.

7.
Press Enter.

8.
Select Disabled.

9.
Confirm by pressing F10.

10.
Save the settings and restart the server.

Hints About Fatal System Error Messages During Installation

Some of the more common error codes include the following:

F002 - This indicates a parity error or a non-maskable interrupt occurred. In most cases, this error is memory related, although some network and video adapters can also generate this error. If you receive this error, run a system diagnostic on the computer, check the BIOS memory refresh rates, and check the cache settings. In some cases, this error can be caused by a poorly seated SIMM. Remove each SIMM, clean it with an eraser, and reinstall it.

0000001E - Most of the time, this unhandled kernel exception indicates a problem with the file system. If you receive this error, look at the bottom of the screen for the stack dump and look for possible causes. For instance, if Rdr.sys is listed, that indicates a problem with the network redirector; check your network adapter settings. If Ntfs.sys or Fastfat.sys is listed, that is an indication that there is an error in the NTFS or FAT partitions. Run the Chkdsk.exe program on all the drives with the /F option (to fix any errors).

0000000A - This is a catastrophic error and generally indicates an interrupt, I/O, or DMA conflict. Check the hardware to ensure that you are not sharing any IRQs or have any other resource conflicts.

0x0000007B - This is an indication that the boot drive is inaccessible. Possible causes are the disk drives being greater than 1,024 cylinders, unsupported disk partitioning schemes, accidentally compressing the boot drive with an MS-DOS compression program in a dual-boot environment, or a boot sector virus.

This is by NO means an all-encompassing solution but hopefully this will shed some light on decoding what some of these messages mean.

Server Reboots

Users often inquire as to why their servers mysteriously reboot.

Compaq Servers have a feature called Automatic Server Recovery. You can disable the Automatic Server Recovery feature in the CMOS configuration. Automatic Server Recovery restarts the server if the hardware “thinks” that the machine is hung.

1.
Disable the “automatic restart” option. In Windows 2000, right click My Computer > Properties > Advanced > Startup and Recovery > System Failure. The server may be trapping.

2.
Ensure users do not have the right to shut down the server. Press Ctrl+Alt+Del at the console or Ctrl+F1 inside an ICA session to see if this right is enabled. You can use Microsoft policies.

3.
If Citrix Resource Manager Version 2.0 is installed, check to see if and when a reboot schedule is configured.