@Kokutestsu: WinFS was an extension of NTFS, not a new filesystem.
Microsoft skips over this in their documentation, as well as BSODs 0x84, 0x86-0x8A, 0x8C, 0x8D, 0x91, 0x95, 0xA8-AA, 0xB2, 0xB3, 0xB5-B7, 0xC0, 0xC3, 0xE5, 0xEE, 0xFB, 0x107, 0x10B, 0x110, 0x118, 0x13E, 0x13F, 0x146, 0x148, 0x172, 0x176, 0x177, 0x17A, 0x17F-0x186, 0x18A, 0x18F, 0x194, 0x19E, 0x19F, 0x1A1, 0x1A2, 0x1A9-0x1AF, 0x1B1-0x1C3, 0x1DA, and probably some others.
In vista, the last regularly numbered BSOD is 0x12C, so I'm only going to look at 0x84-0x12C:
At least according to the message table in NTOSKRNL (there may be more hidden although there likely is not)
- 0x84 is "RECOM_DRIVER". Unknown what this means, although it is driver related.
- The message listed for 0x86 is "Audit attempt has failed.", which most likely is a security violation.
- 0x87 through 0x8A, 0x8C, and 0x8D do not exist in Vista.
- 0x91 is "WIN32K_INIT_OR_RIT_FAILURE", - Win32k
Initalisation or
Reinitalisation failure. Most likely means an error while Win32k.sys was initalizing. Not sure why this one is undocumented.
- 0x95 is "PNP_INTERNAL_ERROR" - An internal error with Plug and Play.
- The 0xA8, 0xA9, and 0xAA message IDs are used for safe mode. Interestingly, they describe themselves as "Minimal Services"
- 0xB2 and 0xB3 do not exist.
- Message IDs 0xB5 through 0xB7 are used for boot logging.
- 0xC0 is "An attempt to access PCI configuration space failed." in the message table. Self-explanatory. Why is it undocumented? Who knows.
- Message ID 0xC3 is used for replacing signatured files with their originals.
- 0xE5 is "POWER_FAILURE_SIMULATE". Used for simulating power failures at Microsoft, I assume.
- The description for 0xEE is "The kernel attempted to ready a thread that was in an incorrect state such as terminated." I assume this would require a bug in the kernel if it was trying to ready a thread that had already been discarded?
- The description for 0xFB is "A machine check exception occurred just after processing a previous machine check, but\r\nbefore an exit from the machine check code could be completed." This has such a narrow use that I assume Microsoft didn't think it worth documenting.
- The description of 0x107 is "A thread is terminating or attempting a win32 callout while running on an expanded stack.". Self-explanatory.
- 0x10B is "DFSC_FILE_SYSTEM". I have no idea what DFSC is. DFS_FILE_SYSTEM is error 0x82, for Microsoft Distributed File System.
http://download.microsoft.com/download/ ... FSC%5D.pdf This link doesn't exist, but it calls itself MS-DSFC.
- 0x118 is "The kernel has detected an inconsistency in hypervisor enlightened operation." For a start, "enlightened". I assume this is what would happen if there was some securtiy problem with Hyper-V.