Windows Bug Check Code
Indicates that a kernel-mode process or driver attempted to access the memory location to which it did not have permission or that the kernel IRQL was to high. Result of faulty or incompatible hardware or software.
Indicates that the kernel detected an illegal or unknown processor instructions share similarities to the 0x0A that they can be due to invalid memory and access violations.
0x24 or NTFS_FILE_SYSTEM
Indicates a problem that happened inside the ntfs.sys the driver file that allows the system to read and write to the NTFS file system drives.
A system memory parity error typically from defective RAM including motherboard ,level2 cache or video memory.
The page table entries are depleted or fragmented. Result of a faulty device driver or an appliction that is allocating large amount of kernel memory.
Requested data was not in memory. Defective or incompatible software causes the problem
A page of kernel data form the paging file could not be found or read into memory disk hardware failure, disk data corruption or possible virus infection
Indicates that the operating system has lost access to the system partition or boot volume during startup process incorrect device drivers when installing or upgrading storage adapter hardware.
A condition that the kernel is not allowed to have or intercept Result of hardware or software problem.
Driver failed to cancel pending operations before exiting
0xD1 DRIVER_IRQL_NOT _LESS_OR_EQUAL
Attempt to access pageable memory using a kernel process IRQL that was to high.Drivers that have used improper addresses typically causes this error.
The kernel mode I/O system attempted to mount to the boot volume and failed can also occur during an upgrade to vista on systems that use higher-throughput ATA disks or controllers with incorrect cabling.
This error occur because 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.And because Microsoft Windows cannot run without WinLogon or CSRSS,windows shut down the system. Mismatched system files can also cause this error.