These are some of the most common Stop Messages along with cause and suggested resolution:

Stop Code: STOP 0x0000000A IRQL_NOT_LESS_EQUAL
   Faulty device drivers, or services from backup utilities or virus scanners
Recommended Resolution: Remove, disable or stop the offending drivers, backup utilities or anti-virus programs. Get updated software from the manufacturer.

Stop Code: STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED
    Some driver files may be causing a problem.
Recommended Resolution: Remove, disable or update the driverfile listed in the error message. Verify if new hardware installation is correct.

Stop Code: STOP 0x00000024 NTFS_FILE_SYSTEM
    Usually caused by disk corruption in the NTFS file system or third-party disk defragmenters.
Recommended Resolution: Use hard disk diagnostic software to verify that the hard disk is working. Remember to always Use Microsoft-certified disk defragmenters.

Stop Code: STOP 0x0000002E DATA_BUS_ERROR
    Caused by a parity error in the system memory. Almost always caused by hardware problems—a configuration issue, defective hardware, or incompatible hardware.
Recommended Resolution: If physical RAM was recently added to the system, remove it and see if the error still occurs. If the error persists, try disabling memory caching in the BIOS. Else remove, repair or reinstall the defective hardware.

Stop Code: STOP 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA
Code Meaning : Caused when requested data is not found in memory; the system checks the page file, but the missing data is identified as unable to be written to the page file
Recommended Resolution: Remove any newly-added hardware or run diagnostic software supplied by the manufacturer to check if the component has failed. Install updated device drivers or roll back to a previous driver.

Stop Code: STOP 0x00000071 SESSION5_INITIALIZATION_FAILED
   What happens to cause the SESSION5_INITIALIZATION_FAILED problem is damage to the active system configuration profile in the registry that is being used to tell the system how to boot up properly. This can happen in a number of ways. In our customer's case, the registry was probably damaged because of filesystem damage. Our customer's computer is a newer Vista computer with a hard drive that was pulled from an older XP system because 100% of the older computer's motherboard capacitors had blown out, mangling the filesystem and various files along the way. It seems that specific NTFS filesystem damage is the number one cause of STOP 0x71 errors, because CHKDSK seems to frequently be the trigger of STOP 0x00000071 and the BSOD triggers a "CHKDSK loop" where the system alternates between automatic disk checks and STOP 0x71 BSODs. When we first encountered the devil that is 0x71, we didn't manage to figure it out, and all signs pointed to reinstall, but we've found a possible (albeit very experimental) alternate solution.

Stop Code: STOP 0x0000007A INACCESSIBLE_BOOT_DEVICE
    In general, the 0x7A occurs when the OS is unable to read page file data from the disk into memory. The logs actually suggest that the disk device was not available at the time. Prior to that, a similar process terminated because it could not access resources on the disk as well. Not something that would show up in a chkdsk given the last error, which would reveal problems with data or bad sectors on the platter itself would not cause this kind of error. Also, the disk not being available might explain why the logs are not always being saved to disk.

Stop Code: STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE
    Caused when Windows loses access to the system partition during the Startup process. This can be caused by: an incorrect driver for a SCSI, RAID, or UDMA IDE controller; incorrect ARC path in the Boot.ini; or a failed boot device. 
Recommended Resolution: Verify that the disk storage device is installed correctly and working. Reinstall or update the device driver. Verify that the BIOS setting for the device is correct. Verify the integrity of the hard disk.

Stop Code: STOP 0x0000007F UNEXPECTED_KERNEL_MODE_TRAP
    Caused when the CPU generates an error that the kernel does not catch. Usually hardware related—especially RAM. Can also be caused by CPU overclocking, or defective components on the motherboard.
Recommended Resolution:
1. Run the memory diagnostic to test RAM.
2. Restore overclocked settings to previous values.
3. Repair/replace the motherboard.
4. Disable sync negotiation in SCSI BIOS; check SCSI termination.

Stop Code: STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Occurs when the system attempts to access pageable memory at a process IRQL that is too high 
Recommended Resolution: Very similar to STOP 0xA. Remove, disable or stop the offending drivers, backup utilities or anti-virus programs. Get updated software from the manufacturer.

Stop Code: STOP 0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED
    Caused when the user-mode subsystem (Winlogon or CSRSS) is fatally compromised and security cannot be guaranteed. The most common causes are third-party applications or mismatched system files.
Recommended Resolution:
1. Remove, disable, or roll back any newly-installed device driver.
2. Uninstall any newly-installed software.
3. Use Windows-compatible backup/restore programs.
4. Restore full control permissions to the local SECURITY account on the systemroot folder by doing a fresh parallel installation of Windows on a separate partition.