Reply to thread

Message: <blockquote data-quote="Billl Gates" data-source="post: 5166942" data-attributes="member: 97732">Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE    The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.    The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:    •    Disks or storage controllers that are failing, defective, or improperly configured.     • Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.     Possible Resolutions:    • During I/O system initialization, the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. File system initialization might have failed because of disk or controller failure, or because the file system did not recognize the data on the boot device.     • Repartitioning disks, adding new disks, or upgrading to a new disk controller might cause the information in the Boot.ini file, or Boot Manager, to become outdated. If this Stop message occurs after installing new disks to your system, edit the Boot.ini file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller, verify that the new hardware is functioning and correctly configured.     • Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. If you are unsure, consult your computer's documentation about restoring default firmware settings or configuring your system to auto-detect settings. If the error occurs during Windows XP Professional setup, the problem might be due to unsupported disk controller hardware. In some cases, drivers for new hardware are not in the Windows XP Professional Driver.cab library, and you need to provide additional drivers to complete the Windows XP setup successfully. If this is the case, follow the hardware manufacturer's instructions when installing drivers. Periodically check for driver and firmware updates.     • Hard disk corruption can also cause this Stop message. For more information about checking hard disk integrity, see the instructions provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.     • Problems that cause 0x7B errors might also cause Stop 0xED errors. For more information about 0xED Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" later in this list.      Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP    The Stop 0x7F message indicates that one of three types of problems occurred in kernel-mode:    •    A condition that the kernel is not allowed to have or intercept (also known as a bound trap).     •    Software problems.     •    Hardware failures.     Possible Resolutions:    • Stop 0x7F messages are typically due to defective, malfunctioning, or failed memory hardware. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.     • Running the CPU beyond the rated specification, known as "overclocking," can cause Stop 0x7F or other error messages due to heat buildup. When diagnosing problems on overclocked systems, first restore all clock and bus speed settings to the manufacturer recommended values to determine if this resolves the issues.     • The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.     • Stop 0x7F messages can occur after installing incompatible applications, drivers, or system services. Contact the software manufacturer about possible Windows XP specific updates. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.     Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE    The Stop 0x9F message indicates that a driver is in an inconsistent or invalid power state.  Possible Resolutions:    • Stop 0x9F messages can occur after installing faulty applications or drivers or system services. If a file is listed by name and you can associate it with an application, uninstall the application. For drivers, disable, remove, or roll back that driver to to determine if this resolves the error. If it does, contact the hardware manufacturer for a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.     • For information about troubleshooting standby and hibernate mode issues, see KB article Q266169, "How to Troubleshoot Problems with Standby Mode, Hibernate Mode, and Shutting Down Your Computer in Windows 2000."     Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY    The Stop 0xBE message indicates that a driver attempted to write to read-only memory.    Possible Resolutions:  • A Stop 0xBE message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.      Stop 0xC2 or BAD_POOL_CALLER    The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:    •    By allocating a memory pool size of zero bytes.   •    By allocating a memory pool that does not exist.   •    By attempting to free a memory pool that is already free.   •    By allocating or freeing a memory pool at an IRQL that was too high.     This Stop message is typically due to a faulty driver or software.    Possible Resolutions:    • A Stop 0xC2 messages might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.     • A Stop 0xC2 messages might also be due to failing or defective hardware. If a Stop message points to a category of devices (such as disk controllers, for example), try removing or replacing the hardware to determine if it is causing the problem.     • If you encounter a Stop 0xC2 message while upgrading to Windows XP, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP, contact the hardware manufacturer to obtain compatible updates.     Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS    This Stop messages indicates that a driver failed to cancel pending operations before exiting.    Possible Resolutions:  • Stop 0xCE messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.     Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL    The Stop 0xD1 messages indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.    Possible Resolutions:    • Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.      Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER    A device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter or a faulty video driver.    Possible Resolutions:    • Stop 0xD1 messages can occur after installing faulty drivers (especially video drivers) or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.      Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME    The kernel mode I/O subsystem attempted to mount the boot volume and it failed. This error might also occur during an upgrade to Windows XP Professional on systems that use higher throughput ATA disks or controllers with incorrect cabling. In some cases, your system might appear to work normally after you restart.    Possible Resolutions:    • If using higher throughput ATA disks and controllers, those capable of data transfer rates above 33.3 megabytes per second, replace the standard 40-pin cable with an 80-pin cable. Using an 80-pin cable is optional for transfer rates up to and including 33.3 megabytes per second, but is mandatory for higher transfer rates. The additional grounded pins are required to avoid data loss.     • Some firmware enables you to force higher transfer rates even when you are using the incorrect cable type. Your firmware might issue a warning but allow the startup process to proceed. Restore the default firmware setting for ATA cable detection.     • Problems that cause 0xED errors might also cause Stop 0x7B errors. For more information about 0x7B Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" earlier in this appendix.     Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH    This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this Stop message to appear.    Possible Resolutions:    • You can use Driver Rollback or System Restore from safe mode, to restore a previous driver. You can also use Windows XP Professional recovery features such as the Last Known Good Configuration startup option, Backup, or Automated System Recovery to restore a previous working configuration. After restoring from backup media, you might need to reapply service packs or hotfixes, depending on when the backups were made.     • If the Stop message names the specific file, try replacing it manually with a fresh copy from the Windows XP Professional operating system CD using safe mode or Recovery Console. For systems using the FAT16 or FAT32 file system, you have the option of using a Windows 98 or Windows Millennium Edition Emergency Boot Disk to access the hard disk.   If the original file from the operating system CD has a file name that ends with an underscore (_) character, you cannot use the file until it is uncompressed. The Recovery Console's Copy command is ideal for copying compressed files because it detects and expands them. If you do not specify a destination file name, you must rename the expanded file with the correct extension before using it. From safe mode or Recovery Console, you can use the Expand command to uncompress and copy a file to a destination location. In Recovery Console, the expanded file is given the correct name after being copied to the destination location. For more information about the Copy or Expand commands, see Windows XP Help and Support Centre.</blockquote>

Verification: Payakata winadi keeyak tibeda?

Top Bottom