Friday, 20 April 2007

Blue Screen

When windows xp detects an error from which it can recover, it reports error information in full screen, non-windowed, text mode. These stop messages, which also referred to as stop errors or blue screens, provide information that is specific to the problem detected by the windows xp kernel. File system errors, viruses, hard disk corruption or controller problems can cause the following stop messages;

Stop 0x00000024 or NTFS_FILE_SYSTEM

This stop message also known asa Stop 0x24, indicates that a problem occurred within Ntfs.sys, which is the driver file that allows the system to read and write to NTFS volumes.

This stop message also known as stop 0x50, occurs when requested data is not found in memory. The system generates a fault, which indicates that invalid system memory has been referenced. This fault can occur due to a variety of error conditions, such as bugs in antivirus software, a corrupted NTVS volume or faulty hardware (typically related to defective RAM, be it main memory, L2 RAM cache or video RAM).

This stop message also known as stop 0x77, indicated that requested page of kernel data from the paging file could not be read into memory. Stop 0x77 can be caused by a number of problems, such as:
  • Bad sectors on the hard disk
  • Defective or loose cabling, improper SCSI termination or the controller not seeing the hard disk
  • Another device is causing a resource conflict with the storage controller
  • Failing RAM

This stop message also known as stop 0x7A, indicates that the requested page of kernel data from the paging file could not be read into memory. One of the following conditions usually causes a stop 0x7A : a bad sector in a paging file, a virus, a disk controller error, defective hardware or failing RAM. In rare cases a stop 0x7A occurs when nonpaged pool resources run out

This stop message also known as stop 0x7B, indicates that windows xp lost access to the system volume or boot volume during the startup process. This error always occurs while the system is starting and is often caused by one of the following:
  • Hardware problems
  • Corrupted or incompatible storage drivers
  • File system problems
  • Boot sector viruses
  • Outdated firmware
During I/O system initialization, this error can occur when:
  • The controller or driver for the startup device (typically the hard disk) failed to initialize the necessary hardware
  • File system initialization failed because the system did not recognize the data on the boot device

No comments: