This BSOD appears on exit from a system call and it is an outcome of internal error in kernel.
This is an uncommon Blue screen error harmful to devices.
Rare bugcheck and doesn’t appear commonly.
Again an occasionally occurring error that indicates an incorrect data access trap.
This BSOD commonly appears when a driver requests the KeAttachProcess function and the thread is attached to a different process.
The BSOD appears after calling KeStackAttachProcess routine and afterward KeUnstackDetachProcess. The process is necessary for the driver’s implementation of callback function PLOAD_IMAGE_NOTIFY_ROUTINE.
Infrequent occurring bugcheck.
Rare Blue Screen
Error message implies Windows or a kernel-mode driver accessed paged memory at an invalid address while at an IRQL.
This BSOD is the consequent of improper use of FsRtlCancellableWaitForMultipleObjects or KeWaitForMultipleObjects.
Appears when a control returns from the initial thread procedure during starting a system thread
Result of a recursive request for a spin lock or comparable function.
Consequences of reference count of an object which is illegal for the present state of the object.
Corrupt pool header at the time of current request generates this issue.
Different flaws in memory management cause this BSOD.
Doesn’t occur in Windows 10 currently
Appears very infrequently.
Faulty Services or driver to cause a kernel mode program to create exception. Error handler fails to catch this exception.
Rare Blue Screen Error
BSoD occurs when an asynchronous procedure call was remaining in pending state when a thread exited.
This Stop error appears after quota charges are mishandled by returning more quota. This occurs to a particular block than was previously charged.
BSoD happens because of corruption in FAT file system mostly due to Bad sectors or blocks in disk.
Driver file ntfs.sys messes that allow the system to write and read to NTFS drives generate this flaw.
Issues in NPFM File System lead to this Blue Screen.
Corruption in CDFS File System causes this stop error mostly because of Bad sector in disk.
Depletion of nonpaged pool memory leads to issues in SMB redirector file system that finally results in this error.
Seldom occurring bugcheck
Inconsistent I/O request packets are the main reason behind this issue.
kernel-mode driver using more stack space is the prime cause of this stop code.
Rare stop error
Mainly occurs because of memory issues or configuration.
Rare Stop code
Stack pointer in a trap frame having an invalid value leads to this problem
In this situation, System initialization fails at a very early stage.
Depletion of nonpaged pool memory causes issues with file system’s cache manager that ends up with this error.
This BSOD appears due to IoCallDriver packet that has no more stack locations remnant in the packet.
Driver tried to remove a device object still the reference count didn’t become 0.
The worker routine returned back without freeing the mutex object that it owned.
Seldom occurring error
Appears when executing code has an exception and thread system thread is under this value.
Rare stop code
System contains more than one processor, but they are not symmetric to each other.
Page table entries in fragmented state has been generated because of too many I/O actions.
target MDL too large to map the whole range of addresses requested by a driver.
This Blue Screen appears because must-succeed pool couldn’t fulfill the requests of Kernel-mode thread.
Driver has tried to request an I/O request packet be completed that is already complete.
BSoD occurs because an IRP was completed, and then was hereinafter canceled.
Stop code appears because of the Thread that is returning back from a system call to user mode whereas its IRQL is higher than PASSIVE_LEVEL.
Infrequent Blue Screen
The error occurs when free pages are unavailable to continue operations.
Shows up when page frame number list becomes corrupted.
Occurs when system references invalid memory.
Indicates that registry is damaged and malfunctioning.
Error appears after system is booted from the incorrect copy of a mirrored partition.
nonpaged pool memory, when got depleted may lead to Pinball file system.
Failed HAL initialization leads to throw BSOD issue
When machine tries to run run an unsupported processor this Blue screen appears.
When Registry configuration gets failed the stop code appears.
Infrequent Blue Screen
initialization of the I/O system failed leads this stop code to appear.
Seldom occurring Bliue screen
Initialization of the OS failed causes this stop code.
Windows OS Initialization failure leads to throw this BSOD.
When Core registry hives are unable to link the registry tree this error appears.
Corruption in registry is the main cause of this blue screen.
When registry hive file fails to be converted to a mapped file this BSoD shows up.
Device Driver tries to unlock pages that are previously unlocked or locked and fails to do so throwing the error.
Memory fails to read requested page of kernel data coming from the paging file and throws BSOD.
An unexpected crash during HAL initialization cause this issue.
The prime cause of this error is Hardware Abstraction Layer revision level or configuration that fails to match that of the computer or kernel.
Memory finds itself unable to read the requested page of kernel data.
Windows OS cannot access the system partition while starting up.
Windows identifies a defect in Networking driver.
Lack of memory to start Windows.
Intel CPU gives rise to a trap and kernel becomes unable to catch this.
A malfunction is progressing into hardware.
fatal error occurred during setup.
This stop code appears when mismatch happens in the MBR checksum
The error handler fails to identify exception created by kernel-mode application.
Error appears when Plug and Play manager is not able to be initialized.
Windows is running on multiprocessor however driver is assembled to work on only one.
BSoD generated when Kernel code attempted to end protected or invalid handle.
Blue screen occurs with this stop code because thread exits while its kernel stack is specified as not swappable
BSoD appears when queue entry is deleted that includes a NULL pointer.
Appears when trial period of Windows comes to end.
Blue screen crops up when ExInterlockedExtendRegion or ExInitializeRegion is called with an invalid set of parameters.
Violation of licence agreement leads to shape up this BSoD error.
Damage in UDF File System produces this issue.
When fatal machine check exception eventuates this error appears.
The Components of critical user-mode are unable to fulfil a health check
BSoD shows up when a driver remains in an invalid or inconsistent power state.
Occurs due to power policy manager that encounters a fatal error.
PCI Bus driver identifies inconsistency difficulties in its internal structures and fails to continue.
Damage in image of an executable file living in memory leads to this problem.
This mess up occurs because ACPI driver enucleates an internal inconsistency.
Reason of the problem is damage in CNSS file system filter.
Advanced Configuration and Power Interface BIOS is not perfectly acquiescent with the ACPI specification.
The flaw occurs due to “kernel-mode handle table” that identifies an inconsistent entry state.
During this bug situation, session device driver doesn’t release its pool allocations prior to a session unload.
Hardware abstraction layer fails to find enough amount of non-paged memory pool for a critical requirement.
Video port generates a minidump to satisfy the driver’s request.
Windows cannot access graphics mode.
DPC tried an illegitimate operation.
A session driver mapped views cannot be unmapped before session unloaded.
Windows is unsuccessful to boot off a network.
Issue occures when and extra identical IP address is assigned to the pc while booting off a network.
Memory image created by hibernation is not compatible with the previous hardware configuration.
Shape up when thread tries to acquire ownership of a mutex it owns sofar.
A thread requests invalid pools.
Malfunctioning of driver verifier gives rise to this code.
This BSoD appears when system tries to approach invalid memory at a process IRQL that is extremely high.
Driver tries to access a released memory pool.
The BSOD appears when DPC or kernel timer remains somewhere in memory where it is not permitted.
IRQL of processor has not the value what it should be currently.
I/O violation by driver verifier throws this issue.
BSOD prompts when Plug and Play Manager confronts a severe error.
I/O manager or driver is unsuccessful to free locked pages subsequent to an operation.
System has referenced memory which was previously released.
The BSOD prompts when system accesses memory beyond the end of some driver’s pool allocation.
The issue takes place when driver fails to terminate pending operations prior to unloading.
Driver, incorrectly ported to the terminal server cause this problem.
The issue occurs because system tries to access invalid memory at a process IRQL that is extremely high.
Kernel-mode driver attempted to access pageable memory while the process IRQL that was too high.
Issue running in an NDIS driver
System attempted to access pageable memory at a process IRQL that was too high.
Driver doesn’t close pending operations previous to unloading.
Driver has referenced memory which was earlier freed.
Issue appears when driver accesses memory further away than the end of its pool allocation.
Driver is attempting to unmap mapped address.
Page table entries are not available further.
BSOD occurs because of damage in internal locked-page tracking structures.
BSoD shows up because of Page table entry routine which has been used in an improper method.
Driver tries to access memory at an invalid IRQL, possibly because of damage in system Page table entries.
Driver accessed a stack address that resides under the stack pointer of the thread.
Driver has malfunctioning pool memory that is used for holding pages designated for disk.
Work item did not disable impersonation before it completed.
Any component is faulty
A worker thread completed and returned with IRQL => DISPATCH_LEVEL.
This Blue screen appears when a user purposely initiates a crash dump from either keyboard or kernel debugger.
Occurs after a thread tries to free a resource it didn’t own.
Issue is commonly the result of the memory which driver releases but it still contains an executive work item.
Refers to entire Driver Verifier DMA Verification violations.
Floating-point state stored by a thread is invalid.
Invalid file object was passed to IoCancelFileOpen
Blue Screen shows up because of termination of an active executive worker thread.
Thread in a driver is everlastingly spinning.
Blue screen appears when free pages are unavailable to further continue operations.
BSOD appears because input and output subsystem tries to mount the boot volume and it fails.
Occurs when critical system process died.
The prime cause is the storage Miniport driver that fails to satisfy a SRB request.
The Blue Screen of Death refers to entire Driver Verifier SCSI Verification violations.
Occurrence of this BSOD is because of the kernel that discovers an interrupt storm.
Windows fails to shut down because of short of memory.
A process or thread crucial to system operation has unexpectedly exited or been terminated.
Blue Screen of Death appears due to the Filter Manager which encountered unrecoverable failure.
PCI driver is verifying an error in BIOS or another device.
A driver has overrun a stack-based buffer.
When RAM disk is used to boot an initialization failure takes place.
A device driver returned “STATUS_REPARSE” to an IRP_MJ_CREATE request without trailing names.
Http.sys has come to a corrupted state and unable to recover.
The Blue Screen of Death bug shows up when trying to execute a non-executable memory.
BSOD occurs due to unable to continue basic system operations because of unavailability of free pages.
USB driver encounters error.
The issue appears due to overflow of Queue because of inserting new item into a reserve queue.
Reason of this problem is either the loader block is invalid, or it does not match the system that is being loaded.
Secondary processor experience an expected clock interrupt. This occurs in a multi-processor system that doesn’t receive under allocated interval.
Blue screen of death appears because Deferred Procedure Call watchdog routine isn’t executed in allocated time interval.
Reason of the BSOD is Multiple UNC provider that has experienced invalid or unexpected data.
Graphic Processing Unit writes to a range of AGP memory that had not earlier been committed.
Blue screen appears because GART is corrupt.
An unauthorized agent has re-programmed AGP hardware.
File system filter or 3rd party file system encounter an unrecoverable issue.
Kernel has identified critical kernel code or data corruption.
Blue Screen occurs when a violation is detected in the FsRtl ECP package.
KMDF identify that Windows find an error in a framework-based driver.
In this Blue screen condition, video memory manager is unable to recover from.
BSod refers to the unrecoverable state of resource manager.
A non-maskable-interrupt happens while a previous NMI was going on.
In this issue, Msrpc.sys driver has started a bug check.
When trying to reset display driver furthermore recover from a timeout fails and prompts BSoD.
Graphics driver is unable to respond in a timely method.
BSoD prompts because video scheduler has encountered a fatal violation.
A driver has returned from a cancel routine that holds the global cancel lock.
The issue occurs when configuration manager read-only protected storage is written.
Blue Screen of Death appears because of the Event Tracing sub-system that has experienced an unexpected fatal error.
A file system has produced lots of recursive faults under low resource conditions that cannot be handled.
Somebody has stopped the initial handle for a driver between inserting the driver object and referencing the handle.
BSoD occurs because BitLocker drive encryption encountered an issue that it cannot recover from.
Driver has caused a violation.
An internal issue takes place in the Windows Hardware Error Architecture.
Cryptographic subsystem failed a mandatory algorithm self-test during bootstrap.
A fatal error in hardware has occurred.
NMR has found an invalid state.
An invalid pool request has been made to netio managed memory pool, e.g. FSB and MDL.
Blue Screen of Death appears when a page isn’t filled with 0 but it should be.
A worker threads IOPriority was incorrectly changed by the called worker routine.
A worker threads Paging IOPriority was wrongly modified by the called worker routine.
BSOD stop code occurs when Windows doesn’t notice installed, licensed language packs for the default UI language.
A damage in memory manager caused by a component that accesses memory through physical addressing.
exFAT file system encountered an issue.
Volsnap attempted to access a common table from two different threads which may result in table corruption and eventually corrupt the table.
This is typically a driver bug.
Blue Screen of death appear because of initialization failure that take place while trying to boot from a VHD.
Occurs when new processor is incompatible with the current configuration
Appears when restoring or saving extended processor state.
BSoD refers to supply of invalid resource owner pointer.
When faulty driver code doesn’t perform its work within the allotted time frame
Drive extender component has encountered a serious internal error that stops continued operation.
Blue Screen of death appears because of an unhandled exception in a registry filtering driver.
When trying to boot via VHD an initialization failure occurrs.
win32k/ntuser handle manager encounters a fatal error.
BSoD occurs when GPIO class extension driver experienced a fatal error.
Kernel has identifies the damage in a critical data structure.
Kernel mode heap manager identifies a damage in a heap.
Kernel has encountered problems with passive-level interrupt.
BSoD occurs when a thread exits with an invalid Input or output boost state.
Blue Screen of Death prompts when early kernel initialization has failed.
This mess up happens when storage driver stack experiences proportion of responsiveness violations surpassing the threshold, or other failures to respond.
Either of the display engines is unable to to respond in timely method.
Display hardware cannot be accessed by an app .
Appears when PPM driver experiences a fatal error.
Occurs due to damage in USB 3 driver.
A necessary operation not being performed or invalid policy leads to prevent the starting of secure Boot policy enforcement.
The issue appears when Windows undergo an abnormal reset
A file system error has occurred.
Blue Screen of death appear because a fatal error occurs in internal kernel WMI subsystem.
System on a Chip subsystems experienced an unrecoverable issue.
System has abnormally reset.
Appears because System encounters internal inconsistency in exception dispatching
A critical System on a Chip device has been unexpectedly failed or removed.
A system cannot to return from standby because component is unable to respond within the allocated time period.
Until the send queue is fully drained NIC active reference should isn’t freed.
Prompts when you try to execute code via an unsupported processor instruction mode.
flags supplied to one of push lock APIs were invalid.
Before a thread releases entire AutoBoost lock entries it is terminated.
Unexpected exception occurs in store component.
Blue Screen of Death appears because IOMMU has delivered a page fault packet for an invalid ASID.
IOMMU vender has delivered a page fault against an ASID that was in the process of being freed.
SD-attached device encountered unrecoverable hardware failure.
Blue screen occurs when called worker routine leaks worker thread’s system page priority
BSOD occurs because a system component becomes unable to respond within the allocated time period and prevent from exiting or entering standby.
SoC subsystem encountered a critical fault and captured a live kernel dump.
NDIS has captured a live kernel dump.
Blue Screen appear because an issue prompts in connected standby watchdog timeout.
Win32k function has violated an ATOMICCHECK.
Blue Screen occurs because the system administrator requested the collection of a live system memory dump.
A thread that doesn’t own a lock has freed the lock tracked by AutoBoost.
Kernel worker threads raised a failure.
Win32k has encountered a critical failure.
SMB client on the non-coordinating node complains that an IO on coordinating node is taking too long and fails all IOs with STATUS_IO_TIMEOUT.
BSOD occurs after Cluster Resource call takes more time than configured timeout.
Cluster Service call to the volume snap to query snapshot information took too long.
Blue screen throwse up because Cluster Shared Volume state transition takes too long.
CSV Manager was asked to create a new volume device object, and it has not reached in time.
Blue Screen occurs because a CSV Manager volume removal request has timed out.
Cluster service user mode watchdog identified that a thread is not progressing for a long.
The reason of this Blue Screen error is the flags supplied to one of the rundown protection APIs which were invalid.
flags supplied to one of the slot allocation API were invalid.
target thread pointer supplied to ExReleaseResourceForThreadLite was invalid.
CSV next state transition request has not reached.
Blue Screen throws up when internal error in the crypto libraries occurs.
Cluster disconnect is not making forward progress.
CoreMessageCall encountered an unrecoverable error.
Blue Screen appears when CoreMessaging detects an unrecoverable error.
System has abnormally reset Windows phone or unrecoverable error occurred.
Early Launch Antimalware driver detected a fatal error.
SMB client on the initiator node complains that an IO to a target node is taking too long and fails all IOs with STATUS_IO_TIMEOUT.
BSoD prompts up when thread has been holding PDC lock too long.
System unexpectedly revokes activator.
Either one or multiple processors in the configuration have loaded inconsistent microcode.
Video fell back to Behavior-Driven Development rather than using the IHV driver.
CSV File System initiated this livedump to help debug an inconsistent state.
Occurs because of damage in OBJECT_HEADER.
Secure kernel confronts a fatal error.
Blue Screen throws up because kernel has identified critical kernel or code data have been corrupted.
Secure fault originated by the secure kernel could not be handled.
Issue takes place because a partition was improperly dereferenced.
Win32k has encountered a critical failure.
A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
dxgkrnl causes a livedump.
BSOD prompts when SMB server encounters an issue and has captures a kernel dump to gather debug information.
OS loader edition doesn’t match the OS.
WIN32K experiences security failure.
UFX livedump occurred.
Blue Screen of Death appears since storage slot fails to be released because there is an object using it.
“A worker thread attached to a silo and did not detach before returning”.
BSOD occurs when Terminal topology manager (TTM) encountered a fatal error.
Win32k didn’t turn on the monitor in a timely method.
SVHDX initiated this livedump to help debug an inconsistent state.
Terminal topology manager (TTM) identified that some device specific operations did not compete with the configured timeouts .
A call has not returned within the timeout period.
bthport.sys has tried to recover and reset the radio from an irremediable internal condition.
SMB redirector has identified an issue and has gathered a kernel dump to collect debug information.
A user initiated DXGKRNL livedump for the scenarios of black screen.
A kernel mode thread pool experienced a deadlock condition.
A current thread is carrying out an invalid call to a fast resource routine.
The store component identified a malfunction in its data structures.
System freezes and not processing timer ticks.
A thread cannot detach from a silo prior to exiting.
A deadlock situation or heavy contention which can lead to performance problems.
BSOD occurs because the callback stack seems to be a user mode address which is illegitimate.
In the middle of context switch, an invalid initial kernel stack address was encountered.
System freezes and is not processing timer ticks.
ACPI driver was not able to perform a task in expected allotted time.
Issue throws up when a Telemetry Assert verification fails.
The problem refers to the invalid state of an executive worker thread.
A Filtering Platform callout carries out an invalid operation.
An UcmUcsi class extension has experienced an error.
A driver is not able to perform a PnP operation under a specific time.
A worker thread modified its workload class and didn’t revert it prior to returning.
An Encrypting File System error situation has occurred such that cannot be handled without data loss or data corruption.
UCSI class extension has experienced an issue.
HAL IOMMU library encountered an internal error issue.
Blue screen of death prompts when a processor gets stuck in an IPI loop for more than the allowed time.
BSOD throws up because eractrl.sys driver fails to transition the Xbox console to or from standby after an extended time.
A driver has caused a violation.
Bluetooth miniport extensible driver verifier has caught a violation.
Issue prompts because hypervisor has experienced a fatal error.
Similar to SYSTEM_THREAD_EXCEPTION_
Similar to UNEXPECTED_KERNEL_MODE_TRAP
Similar to KERNEL_MODE_EXCEPTION_NOT
Simliar to THREAD_STUCK_IN_DEVICE
Blue Screen of Death throws up because a driver obtained a mutex on a thread that exited before it could be freed.
As the code says registry file could not be loaded.
BSOD appears when Winlogon process is unexpectedly closed.
A system DLL or driver has been damaged.
Blue Screen of Death prompts when a User intentionally initiated a crash dump using keyboard or kernel debugger.