Home > Articles > Software > Blue Screen of Death (BSOD)
Blue Screen of Death (BSOD)

 

stop icon Have you ever have problems in the start of the system or during its execution?? Its common to see “blue screens” during this process. Lets see how to react when we face this.

On Microsoft site we discover those screens are called BSOD (Blue Screen of Dead).

After this particular event is difficult for the system to recover, the last versions of Windows (2000, XP and Vista) restarts continuously as default after receiving a blue screen.

It is possible to divide the messages related to BSOD in two categories: the ones mentioning problems in Hardware and the “Stop” messages.

Any of the cases are caused by the lack of solving the problems of Windows. Every Operative System has a KERNEL, which is the main core of the programs. This Kernel can detect unexpected errors that cannot handle, and the messages related with the bad operation of the Hardware occur when the processor detects a problem in the Hardware that cannot solve.

The text showed in the screen is sometimes difficult to understand:

*** STOP: 0x0000001E (0xC0000005, 0xFDE38AF9, 0x00000001, 0x7E8B0EB4) KMODE_EXCEPTION_NOT_HANDLED ***

The BSOD is divided in three sections:

  • Bugcheck information
  • Recommended User Action
  • Debug Port Information

If only the first section appears, the problem is affecting the services capable of providing the information.

Bugcheck information

In this section we find the error code defined by the developer (0x0000001E) and the name given to the error KMODE_EXCEPTION_NOT_HANDLED. It is possible to find a line including the hexadecimal address of the system memory where the problem happened, with the particular name of the device or associated driver.

Recommended User Action

Tells some steps to follow by the user. Sometimes the problem is solved by restarting the system but if the problem continues it should be studied.

Debug Port Information

Here we can find information of the parameters of configuration of the COM port, and the bits per second for data transmission used by the Kernel Debugger. It also tells if it will be saved in the Memory Dump.

The STOP messages

It is possible to group this messages in four categories:

  • General Messages
  • Installation Messages
  • Messages in the sequence of start of the executive core
  • Messages of the Capture of Software

 

General Messages

Can occur in any moment while the operative system is working, and are usually caused by a driver or application that produce an illegal operation Windows cannot handle.

Installation Messages

Normally caused by incompatible Hardware with Windows Version.

A Possible Solution is to visit Microsoft site and look for the list of Hardware supported by the version of the installed system. Don´t alarm if you don´t find a component in the list, remember that it only indicates the products checked by Microsoft. Other possible solution is manually removing the devices one by one and restart the system, until you find the one in trouble.

Messages in the sequence of start of the executive core

The start of the operative system occurs in two subphases:

 

  • Subphase 0: starts the abstraction layer of the Hardware: (HAL: Hardware Abstraction Layer)
  • Subphase 1: the system operates completely and opens Windows subcomponents.

If the error occurs during subphase 0 – Microsoft recommends to execute the diagnostic tools provided by the manufacturer if it is a owner form factor, or a Diagnostic Software developed by thirds (Sisoft Sandra, Everest, etc).

Possible solution

If it doesnt detects any problem in hardware, reinstall Windows.If you still have the same error start an exhaustive investigation of the hardware. Try removing an adapter and restart the system.

ID and symbolic names of the Stop Messages of subphase 0:

 

0x31 - PHASE0_INITIALIZATION_FAILED;

0x5C - HAL_INITIALIZATION_FAILED

0x5D - HEAP_INITIALIZATION_FAILED

0x5E - OBJECT_INITIALIZATION_FAILED

0x5F - SECURITY_INITIALIZATION_FAILED

0x60 - PROCESS_INITIALIZATION_FAILED

 

The error occurs during the subphase 1 – Normally means the problem drifts from Windows files. The possible solution is Windows reinstallation.

 

ID and symbolic names of the Stop messages of subphase 1:

 

0x32 - PHASE1_INITIALIZATION_FAILED

0x61 - HAL1_INITIALIZATION_FAILED

0x62 - OBJECT1_INITIALIZATION_FAILED

0x63 - SECURITY1_INITIALIZATION_FAILED

0x64 - SYMBOLIC_INITIALIZATION_FAILED

0x65 - MEMORY1_INITIALIZATION_FAILED

0x66 - CACHE_INITIALIZATION_FAILED

0x67- CONFIG_INITIALIZATION_FAILED

0x68 - FILE_INITIALIZATION_FAILED

0x69 - IO1_INITIALIZATION_FAILED

0x6A - LPC_INITIALIZATION_FAILED

0x6B - PROCESS1_INITIALIZATION_FAILED

0x6C - REFMON_INITIALIZATION_FAILED

0x6D - SESSION1_INITIALIZATION_FAILED

0x6E - SESSION2_INITIALIZATION_FAILED

0x6F - SESSION3_INITIALIZATION_FAILED

0x70 - SESSION4_INITIALIZATION_FAILED

0x71 - SESSION5_INITIALIZATION_FAILED

 

Message of Capture of Software

 

The development of the applications for Windows should follow certain parameters that not always are taken into account during the process of programming. The microprocessor detects the design errors by the impossibility of executing its code.

Possible solution:

Write down the text of the message and restart the system. If the error repeats, try following the suggested instructions by the second part of the message or the generic procedures mentioned above.

 

General Procedures to solve problems

 

  1. If a new Hardware or Driver was installed before having problems, remove it and try restarting the system.
  2. Try with the Hardware Diagnostic Tools.
  3. Consult in the manufacturer of the motherboard website if there is available a BIOS update.
  4. Check in the inside of the computer that every cable is plugged correctly and every adapter is securely inserted.
  5. Check the HCL to see if the Hardware is compatible or not.
  6. Examine the hard drive with an updated antivirus. The screens are sometimes caused by virus.
  7. Uninstall the installed software before the error.
  8. Visit Windows Update if there is any available update.
  9. Check with unmarking the BIOS options “caching and “shadowing”.
  10. Check the Event Viewer to see any additional information about the error.
  11. Visit the Microsoft KB (Knowledge Base) to see if there is any available documentation about the problem.

http://search.support.microsoft.com/kb/c.asp

   12.  Microsoft recommends only in extreme cases to use the kernel debugger (Only for expert programmers).

 

 

 

 

 



( 1 Vote )
Comments
Add New Search
+/-
Write comment
Name:
Email:
 
Website:
Title:
 
:D:angry::angry-red::evil::idea::love::x:no-comments::ooo::pirate::?::(:sleep::););)):0
 
Please input the anti-spam code that you can read in the image.
Powered by Whispers Team

Whispers Team . All rights reserved."