View Profile
View Forum Posts
Private Message
View Blog Entries
View Articles
0x00000001: APC_INDEX_MISMATCH
This is an internal kernel error. The problem originates from drivers failures, shortage of RAM memory or hard drive space.
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Intervention in virtual memory of the high level IRQ internal process has happened. The most typical cause of such error is device driver utilizing a faulty address. The error occurs because of installed drivers bugs.
0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
This is the most common error. The deprecated address usually indicates a driver or a function which caused BCoD. Always pay attention not only to the driver indicated but also to the very errant address. Mostlikelyit’sexceptioncode 0x80000003. This error means that the breakpoint or handler initialized while addressing to memory but the system booted with the help of /NODEBUG keyword. If this error arises regularly, make sure that debugger is enabled and the system is booted with the help of /DEBUG keyword.
0x00000020: KERNEL_APC_PENDING_DURING_EXIT
The error definition identifies the defective/disabled APC-counter. If you encounter such situation, check all file systems installed on your PC. The current IRQL must be equal to zero. If it’s not, then drivers swapping-out certain order may cause this error while returning to IRQL higher level. Try to memorize what you were doing or what applications you were closing and what drivers were installed on your PC when BSoD appeared. This symptom indicates some serious problems in third party software (drivers).
0x00000023: FAT_FILE_SYSTEM
Reading or writing operation error in FAT fixed disk partition has occurred. Such failure may be caused by file system fault or disk bad sectors appearance. It also may originate from the software changing disk
structure, for instance, an encryption program.
0x00000024: NTFS_FILE_SYSTEM
Reading or writing operation error in NTFS-format fixed disk partition has occurred. Such failure may be caused by file system fault or disk bad sectors appearance. It also may originate from the software changing disk structure, for instance, an encryption program.
0x0000002A: INCONSISTENT_IRP
I/O Request Packet (IRP) does not function. This happens when one or more joining fields are incorrect in comparison with IRP saved status. For example, IRP was off whereas device driver was waiting for some order.
0x0000002B: PANIC_STACK_SWITCH
This error arises when kernel stack is overfull and the kernel driver utilizes too much stack space. Possible cause of this error may also be in kernel corruption.
0x0000002E: DATA_BUS_ERROR
This STOP-error most often occurs because of RAM memory faults. It also may happen when driver addresses to nonexistent memory address.
0x00000031: PHASE0_INITIALIZATION_FAILED
System initialization has not been completed at early stages. The error must be investigated thoroughly as this error code conveys nothing.
0x00000032: PHASE1_INITIALIZATION_FAILED
System initialization has not been completed at late stage. The error must be investigated thoroughly as this error code conveys nothing.
0x00000035: NO_MORE_IRP_STACK_LOCATIONS
High-level driver has made an attempt to activate low-level driver through the IoCallDriver interface but system possessed no free stack space and for this reason the low-level driver failed to obtain required parameters as setting any parameters is not be possible in such circumstances. This is a fatal failure as the high-level driver considers that the low-level driver parameters have been fixed. It often happens because of stack memory units’ faults. Memory and drivers possible errors checkup is required.
0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO
Device driver made an attempt to remove some component of its device from the system but this component access counter was not equal to zero which means that there were some outstanding tasks under this component (the counter specifies error code and that’s why this component cannot be swapped out). This is a driver activation error.
0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
Multiprocessor system is asymmetrical relative to each other. To obtain symmetry processors must be of the same type and level. In addition, х86 systems must be configured in such a way that either all the processors or none of them could provide floating-point calculation.
0x0000003F: NO_MORE_SYSTEM_PTES
This error is usually caused by some driver that poorly cleans up swap-file and it’s getting overfull. Swap-file excessive fragmentation may also be a cause of this error.
0x00000040: TARGET_MDL_TOO_SMALL
Driver has activated IoBuildPartialMdl feature and passed MDL to it in order to recognize part of MDL origin but MDL acceptor extent is too small to represent required addresses limits. This is a driver error.
0x00000041: MUST_SUCCEED_POOL_EMPTY
System driver has called for space in Must Succeed Pool. This feature cannot be executed as the system does not dedicate any space in Must Succeed Pool. Replace or update invalid system driver.
Sections
Categories
Computer Glossary
Calendar