Quote:
Originally Posted by administrator
|
Blue Screen of Death!! it was scary to hear Who ever experienced Blue Screen of Death? If have experienced it, then display a blue layer that displays error messages are no longer competitive. BSOD, according to Wikipedia, can be interpreted as an error message that appears in the Windows system damage that cannot recover.
BSOD is caused due to emergence of a variety of problems both from the system and the hardware. The emergence of BSOD can actually help us to know where the damage that causes the computer we become confused. But for ordinary users, the emergence of BSOD can be pretty scary, because exactly the messages on the BSOD can be confusing ordinary user, and frankly, just a lot of messages on the BSOD that seemed “disconnected” in explaining the location of the problem sector. At the time the author found the first BSOD on a computer writer, author of almost hopeless to deal with problems that prompted the BSOD.
Okay, we just peeled the contents of this BSOD. Above BSOD parts are categorized as follows:
Message damage / error messages: Contains the main error message, which we will discuss means
Troubleshooting: Contains suggestions or advice about what to do to correct the error. Located under the error message.
Hexadecimal codes: who wrote the code crashes.
Memory Dump Message: indicates that the process was taking place in memory is copied into a file on disk for debugging purposes. This debugging file usually required the technicians to analyze and correct errors.
In this discussion we will only discuss the meaning of error messages contained in the main BSOD, not including the detailed troubleshooting, that if there is no obstacle to the post InsyaAllah next time :
IRQL_NOT_LESS_OR_EQUAL (0X0000000A)
This is the mastermind of pure BSOD culprit. Why? Because generally the BSOD, this message most often appears. This error message is generally caused by a mismatch because they have the drivers installed on your computer. List of Causes:? Problem drivers clash or unsuitable? Problems Video Card, this includes the video card overclock you exceed the limit or just changed your video card and drivers do not uninstall the old video card from a different chipset? Audio Cards problems, including configuration errors or bugs in the
NTFS_FILE_SYSTEM or FAT_FILE_SYSTEM (0X00000024) or (0X00000023)
Now, this message at least was a little “disconnected” gives a picture in which the damage is, namely in the partition or filesystem but not on the hard drive. We can check by examining the SATA or PATA cable or can check the partition with chkdsk tool.
UNEXPECTED_KERNEL_MODE_TRAP (0X0000007F)
When you get a message like this, can be caused by:? Hardware Overclock too much? Overheated computer component? BIOS is corrupt? Memory and CPU is defective
DATA_BUS_ERROR
This message is caused because of the possibility that the memory or the memory slot on the motherboard is damaged.
PAGE_FAULT_IN_NONPAGED_AREA
Caused because of damage to hardware, including main memory, video card memory, or memory in the processor (L2 cache)
INACCESSIBLE_BOOT_DEVICE
Caused because of an error in configuration jumper the wrong disk, boot sector viruses, the IDE controller driver is wrong, or the chipset driver error.
VIDEO_DRIVER_INIT_FAILURE
error occurred on the installation of video card drivers are not perfect restart during installation or can also occur because of errors in installing the drivers.
BAD_POOL_CALLER
this error can occur because of errors or incompatible drivers. Often occurs during the installation of XP from an upgrade, or not from the new installation.
PEN_LIST_CORRUPT
this message because of the damage caused MACHINE_CHECK_EXCEPTION RAM CPU Caused by the defect, or that the overclock is aggressive, and power supply shortages or damaged resources. That’s ten messages are appeared in the BSOD, hopefully this article can help you to analyze the damage on your computer.
Blue Screen Data
When Microsoft Windows encounters a condition that compromises safe system operation, the system halts. This condition is called a bug check. It is also commonly referred to as a system crash, a kernel error, or a Stop error.
If crash dumps are enabled on the system, a crash dump file is created.
If a kernel debugger is attached and active, the system causes a break so the debugger can be used to investigate the crash.
If no debugger is attached, a blue text screen appears with information about the error. This screen is called a blue screen, a bug check screen, or a Stop screen.
The exact appearance of the blue screen depends on the cause of the error. The following is an example of one possible blue screen:
STOP: 0x00000079 (0x00000002, 0x00000001, 0x00000002, 0x00000000)
Mismatched kernel and hal image.
Beginning dump of physical memory
Physical memory dump complete. Contact your system administrator or
technical support group.
On the other hand, some blue screens look like this:
STOP: c000021a {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly with
a status of 0x00000001 (0x00000000 0x00000000).
The system has been shut down.
The hexadecimal number following the word "STOP" is called the bug check code or Stop code. This is the most important item on the screen.
Each bug check code has four associated parameters. In the first blue screen shown here, all four parameters are displayed after the bug check code. However, in the second kind of blue screen, these parameters have been rearranged within the explanatory text. Regardless of the amount of rearrangement, they will always appear sequentially. If fewer than four parameters appear, the remaining parameters can be assumed to be zero.
The remainder of the text on the blue screen gives additional information. For some bug checks, this may be an explanation of what happened or suggestions for how you can deal with the problem. If a kernel-mode dump file has been written, this will usually be indicated as well.
Under some conditions, Windows will display only the first line of the blue screen. This can occur if the vital services needed for the display have been affected by the error.
Bug Check 0x79: MISMATCHED_HAL
The MISMATCHED_HAL bug check has a value of 0x00000079. This bug check indicates that the Hardware Abstraction Layer (HAL) revision level or configuration does not match that of the kernel or the computer.
Parameters
The following parameters appear on the blue screen. Parameter 1 indicates the type of mismatch.
Parameter 1 Parameter 2 Parameter 3 Parameter 4 Cause.
0x1 The major processor control block (PRCB) level of Ntoskrnl.exe. The major PRCB level of Hal.dll. Reserved The PRCB release levels are mismatched. (Something is out of date.)
0x2 The build type of Ntoskrnl.exe. The build type of Hal.dll. Reserved The build types are mismatched.
0x3 The size of the loader parameter extension. The major version of the loader parameter extension. The minor version of the loader parameter extension. The loader (ntldr) and HAL versions are mismatched.
When Parameter 1 equals 0x2, the following build type codes are used:
• 0: Multiprocessor-enabled free build
• 1: Multiprocessor-enabled checked build
• 2: Single-processor free build
• 3: Single-processor checked build
Cause
The MISMATCHED_HAL bug check often occurs when a user manually updates Ntoskrnl.exe or Hal.dll.
The error can also indicate that one of those two files is out of date. For example, the HAL might be designed for Microsoft Windows 2000 and the kernel is designed for Windows XP. Or the computer might erroneously have a multiprocessor HAL and a single-processor kernel installed, or vice versa.
The Ntoskrnl.exe kernel file is for single-processor systems and Ntkrnlmp.exe is for multiprocessor systems. However, these file names correspond to the files on the installation media.After you have installed the Windows operating system, the file is renamed to Ntoskrnl.exe, regardless of the source file that is used. The HAL file also uses the name Hal.dll after installation, but there are several possible HAL files on the installation media. See Installing Just the Checked Operating System and HAL for details.
Resolving the Problem
Restart the computer by using the product CD or the Windows Setup disks. At the Welcome screen, press F10 to start the Recovery Console. Use the Copy command to copy the correct HAL or kernel file from the original CD into the appropriate folder on the hard disk. The Copy command detects whether the file that you are copying is in the Microsoft compressed file format. If so, it automatically expands the file that is copied on the target drive.
Bug Check 0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
The STATUS_SYSTEM_PROCESS_TERMINATED bug check has a value of 0xC000021A. This means that an error has occurred in a crucial user-mode subsystem.
Parameters
The following parameters are displayed on the blue screen.
Parameter Description
1 A string that identifies the problem
2 The error code
3 Reserved
4 Reserved
Cause
This error occurs when a user-mode subsystem, such as WinLogon or the Client Server Run-Time Subsystem (CSRSS), has been fatally compromised and security can no longer be guaranteed. In response, the operating system switches to kernel mode. Microsoft Windows cannot run without WinLogon or CSRSS. Therefore, this is one of the few cases where the failure of a user-mode service can shut down the system.
Mismatched system files can also cause this error. This can occur if you have restored your hard disk from a backup. Some backup programs might skip restoring system files that they determine are in use.
Resolving the Problem
Running the kernel debugger is not useful in this situation because the actual error occurred in a user-mode process.
Resolving an error in a user-mode device driver, system service, or third-party application: Because bug check 0xC000021A occurs in a user-mode process, the most common culprits are third-party applications. If the error occurred after the installation of a new or updated device driver, system service, or third-party application, the new software should be removed or disabled. Contact the manufacturer of the software about a possible update.
If the error occurs during system startup, restart your computer, and press F8 at the character-based menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. If this does not resolve the error, try manually removing the offending software. If the system partition is formatted with file allocation table (FAT), use an MS-DOS startup disk to gain access to the computer's hard disk. If the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty software. If the faulty software is used as part of the system startup process in Safe Mode, you need to start the computer using the Recovery Console in order to access the file. If a newly installed piece if hardware is suspected, remove it to see if this resolves the issue.
Try running the Emergency Recovery Disk (ERD) and allow the system to repair any errors that it detects.
Resolving a mismatched system file problem: If you have recently restored your hard disk from a backup, check if there is an updated version of the Backup/Restore program available from the manufacturer. Make sure the latest Windows Service
http://www.computersecurity-protection.com/
Microsoft offers prank Blue Screen Of Death
Linear Mode
