<P> With the release of Windows Server 2012, the BSoD was changed, removing all of the above in favor of the error name, and a concise description . Windows 8 added a sad emoticon as well . The hexadecimal error code and parameters can still be found in the Windows Event Log or in memory dumps . Windows 10 Build 14393 added a QR code for quick troubleshooting . </P> <P> The blue screen of death frequently occurs in Microsoft's home desktop operating systems Windows 95, 98, and ME . In these operating systems, the BSoD is the main way for virtual device drivers to report errors to the user . It is internally referred to by the name of "_VWIN32_FaultPopup ". A Windows 9x BSoD gives the user the option either to restart or continue . However, VxDs do not display BSoDs frivolously--they usually indicate a problem that cannot be fixed without restarting the computer, and hence after a BSoD is displayed the system is usually unstable or unresponsive . </P> <P> The most common BSoD is on an 80 × 25 screen which is the operating system's way of reporting an interrupt caused by a processor exception; it is a more serious form of the general protection fault dialog boxes . The memory address of the error is given and the error type is a hexadecimal number from 00 to 11 (0 to 17 decimal). The error codes are as follows: </P> <Ul> <Li> 00: Division fault </Li> <Li> 02: Non-Maskable Interrupt </Li> <Li> 04: Overflow Trap </Li> <Li> 05: Bounds Check Fault </Li> <Li> 06: Invalid Opcode Fault </Li> <Li> 07: "Coprocessor Not Available" Fault </Li> <Li> 08: Double Fault </Li> <Li> 09: Coprocessor Segment Overrun </Li> <Li> 0A: Invalid Task State Segment Fault </Li> <Li> 0B: Not Present Fault </Li> <Li> 0C: Stack Fault </Li> <Li> 0D: General Protection Fault </Li> <Li> 0E: Page Fault </Li> <Li> 10: Coprocessor Error Fault </Li> <Li> 11: Alignment Check Fault </Li> </Ul>

Most of the windows blue screens are caused due to