View Profile
View Forum Posts
Private Message
View Blog Entries
View Articles
0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS
Driver requested IRP shut down (IoCompleteRequest) but the packet had been already shut down. Thismistakeisdifficulttodetect. This error may be possibly caused by the driver attempts to shut down the same operation for several times. Another rarer cause is in two different drivers that try to take control over one packet and shut it down. Typically the first one works out and the second one fails. It’s extremely difficult to detect which driver exactly performed the operation as the first driver traces were transcribed by the second one.
0x00000048: CANCEL_STATE_IN_COMPLETED_IRP
This error indicates that I/O Request Packet (IRP) that must be shut down has cancellation order determinated in the very IPR which means that the packet operates in a mode that allows its cancellation. Nevertheless the packet is no longer related to the driver since it has already run into the termination process.
0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF
This is a page fault caused by addressing to memory while IRQ interrupt requests are off.
0x0000004D: NO_PAGES_AVAILABLE
There is no more page memory required for operation termination. Checkifthere’ssomefreediskspace. Replace the driver.
0x0000004E: PFN_LIST_CORRUPT
This error is caused by defective/corrupt driver input-output structure.
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
This error occurs when data requested was not found in memory. The system checked swap-file but the nonpresent data had been indicated as impossible to be recorded in swap-file.
0x00000051: REGISTRY_ERROR
Registration entries input-output error occurred when the system tried to read one of the register files. It follows that the error might have been caused by hardware malfunction or the system fault. It may also indicate that the error originates from refreshing operation which is used by security system only and this error arises when resources run low. If such error happened, check the accounts quantity in Security Account Manager base (SAM).
0x00000058: FTDISK_INTERNAL_ERROR
System booted with the help of salvaged primary array part, therefore libraries report that mirror operates in accordance with the procedure. However, that is not so. The true library images are located in shadow copy. You should boot up using them.
0x00000067: CONFIG_INITIALIZATION_FAILED
This error means that the register cannot dedicate space required for register files to operate.
0x00000069: IO1_INITIALIZATION_FAILED
IO processor cannot be initialized due to unknown reason. It happens when the system installer detects equipment incorrectly during the process of system installation or a user reconfigured the system in a wrong way.
0x0000006D: SESSION1_INITIALIZATION_FAILED
0x0000006E: SESSION2_INITIALIZATION_FAILED
0x0000006F: SESSION3_INITIALIZATION_FAILED
0x00000070: SESSION4_INITIALIZATION_FAILED
0x00000071: SESSION5_INITIALIZATION_FAILED
This code of codes (SESSION1 - SESSION5) indicates error location in NTOS\INIT\INIT.C.
0x00000073: CONFIG_LIST_FAILED
This error means that one of register files is corrupt or not readable. These corrupt files may be the following: SOFTWARE, SECURITY ACCOUNT MANAGER (SAM). Shortage of disk space or RAM memory is possible reason.
0x00000074: BAD_SYSTEM_CONFIG_INFO
This error may result from corruption of SYSTEM register file that boots with the help of NTLDR component. This error may also indicate that some of required register keys and their parameters are absent. BootinginLastKnownGoodwillprobablyresolvetheproblem. Though you may need to reinstall the operating system or use a rescue disk.
0x00000075: CANNOT_WRITE_CONFIGURATION
This error may occur when additional data cannot be stored in system register files (SYSTEM and SYSTEM.ALT) during the first phase of register initialization process (while the access to file systems is available). This error means that there’s no free space on disk and there was an attempt to store the register on “only reading” device.
0x00000076: PROCESS_HAS_LOCKED_PAGES
This error may occur due to some driver that was not fully swapped after input-output operation.
0x00000077: KERNEL_STACK_INPAGE_ERROR
This is a system kernel read page error. The problem originates from virtual memory bad block or disk controller error (it’s very rare case when this error is caused by system resources shortage and specifically by non-virtual memory exhaustion with c0000009a status (STATUS_INSUFFICIENT_RESOURCES)).
If the first and the second error code parameters are equal to zero, that means that the error location in kernel was not found. This implies that the error occurs due to the faulty hardware. Input-output status c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL (STATUS_DISK_OPERATION_FAILED) usually means that data cannot be read because of bad memory block. Disk autotest performed after rebooting will try to detect bad memory block address. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and virtual memory is located on SCSI disk, then you should check SCSI device connection and performance.
0x00000079: MISMATCHED_HAL
HAL checkup level and HAL configuration type are not compatible with system kernel or machine type. This error is most likely caused by manual update either NTOSKRNL.EXE or HAL.DLL. Another possible reason is that machine contains multiprocessor HAL (MP) and uniprocessor kernel (UP) or vice versa.
0x0000007A: KERNEL_DATA_INPAGE_ERROR
The page requested by kernel cannot be read. This error is caused by bad memory block or disk controller error.
0x0000007B: INACCESSIBLE_BOOT_DEVICE
The boot drive driver probably didn’t manage to initialize a device used by system for booting during the process of I/O system installation or the file system that should have read this device either could not initialize or didn’t recognize the data on device as file system structure. In the aforementioned example the first argument is unicode information structure address which is ARC device name used for booting. In latter case the first argument is the address of device object that cannot be installed.
If this error arose while initial system installation, the system was probably installed on disk or SCSI controller which were not supported by this system. Bear in mind that some controllers are supported only by Windows-libraries drivers (WDL) which should be installed in custom setup mode. This error may also occur after installation of the new SCSI adapter/controller or come as a result of system partition update. In this case you should edit BOOT.INI in x86 systems.
0x0000007D: INSTALL_MORE_MEMORY
There’s not enough RAM memory needed for Windows kernel startover (5 MB is required).
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
There’s hardware malfunction, faulty drivers or disk space shortage. This error may also arise while Windows XP updating up to Service Pack 2 or Service Pack 3, or while Windows Vista updating up to Service Pack 1. The error may be caused by device drivers. You should roll back changes in order to restore system state as of the time of Service Pack installation or simply delete the update. To resolve this problem you should download updated device drivers from the software developer’s website.
Sections
Categories
Computer Glossary
Calendar