This message problem that is running on Windows XP, you may receive one of the following error messages
- Stop 0x00000077
- KERNEL_STACK_INPAGE_ERROR
How to fix Problem KERNEL_STACK_INPAGE_ERROR Blue Screen :
STEP 1 :
Download This Update Pack :
http://support.microsoft.com/kb/322389
This file obtain the latest Windows XP service pack
or
STEP 2 :
Run a disk scanner
A disk scanner can locate and repair hard disk errors for you. To run a disk scanner, try to restart the computer. Then, select from the following problemss.
If the computer restarted successfully
Option 1: Autochk automatically runs
If the computer restarted successfully, the Autochk disk scanner will automatically run to locate and to repair any hard disk errors.
Option 2: Manually run Chkdsk
If Autochk does not automatically run, you can manually run the Chkdsk disk scanner. To do this, follow these steps:
1. Click Start, click Run, type chkdsk /f /r, and then click OK.
2. At the command prompt, type Y to let the disk scanner run when you restart the computer.
3. Restart the computer.
4. Chkdsk will run.
If the computer did not restart successfully, manually run the Chkdsk disk scanner from the Recovery Console. To do this, follow these steps:
1. Restart the computer.
2. When the Welcome to Setup screen appears, press R to start the Recovery Console.
3. If you have a dual-boot or a multiple-boot computer, select the installation that you need to access.
4. When you are prompted, type the administrator password. If the administrator password is blank, press ENTER.
5. At the command prompt, type chkdsk /r, and then press ENTER.
6. When Chkdsk has finished running, read the results, and then take any steps that are required to complete the process. For example, you may be prompted to run chkdsk /f to fix certain problems.
7. Restart the computer.
STEP 2 :
Run a current virus-checking program to scan your computer for viruses. Select from the following options.
1. Run the computer's virus-checking program
2. Run Microsoft Security Essentials safety scanner
Other Information :
This problems can occur if a requested page of kernel data could not be read from the paging file into memory, or the master boot record is infected with a virus.
To determine the possible cause, you must interpret the error message. If both the first and the third parameters are zero, the four parameters are defined as follows:
1. 0 (zero)
2. Page Table Entry (PTE) value at time of error
3. 0 (zero)
4. Address of signature on kernel stack
If either the first or the third parameter is not a zero, the following definitions apply:
1. Status code
2. I/O status code
3. Page file number
4. Offset into page file
If this is the case, the cause of this problems may be determined from the second parameter (the I/O status code) by using the following information in which the "value of second parameter" indicator is followed by a "general cause" format:
- 0xC000000E, or STATUS_NO_SUCH_DEVICE: the drive is unavailable, possibly because of a bad hard disk drive, a bad disk array, or a bad controller card.
- 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES: lack of nonpaged pool resources.
- 0xC000009C, or STATUS_DEVICE_DATA_ERROR: bad blocks on the hard disk.
- 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED: bad cabling, non-termination, or the controller cannot access the hard disk.
- 0xC000016A, or STATUS_DISK_OPERATION_FAILED: bad blocks on the hard disk.
- 0xC0000185, or STATUS_IO_DEVICE_ERROR: incorrect termination, or defective cabling of SCSI-based devices, or two devices are trying to use the same IRQ.
0 comments:
Posting Komentar