BSOD (Blue Screen of Death)

1. We get BSOD if there are any firmware changes took place, any hardware issue or issue with
patches.
2. Once we find a Blue screen try to boot from Safe mode, Safe mode with Networking and
then the Last known good configuration.
3. If still the server does not boot up log into ILO and from the remote option in the ILO try
to launch the server if the server boots then check for the below.
4. Check for the BSOD logs from the going to the computer Advanced System
settingsAdvanced Start up and recovery in the system failure page Uncheck the
Automatically restart option in the write debugging option select the Kernel Memory
dump.
5. Then go to C:\windows\Minidump and open the .dmp file with the help of the win
degu.exe we can convert the .dmp file to notepad and do the require analysis.
6. If the server does not even launch even from the ILO then press F2 go to the BIOS and in
the BIOS settings click on the Advanced option disable both Shadowing and Cacheable
RAM and then try to start the server. The server should start.

BSOD Errors:

1. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED: This is usually caused to disk space or

driver.
We need to check for the respective Disk Space issue and check for the faulty driver form
the device manager console. If we find any issue with the driver first try to update the driver
and if still the issue persists then consider to replace the driver.

2. STOP 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED:

This error message indicates that there could be an issue with the faulty driver of Hardware
device. We need to either consider to change the disk or the hardware.

3. STOP 0x00000024 or NTFS_FILE_SYSTEM:

A problem could have occurred within the NTFS file system and most likely it could be a disk
failure issue. Check the disk space or log into the Symantec Net back up and check of the
disk status. If the disk is found faulty then replace the disk.

4. STOP 0x0000009F or DRIVER_POWER_STATE_FAILURE:

This indicates that there could be an in consistent power supply.