Error map
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Blue screen: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E)
Windows · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (7). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (7)
Blue Screen: IRQL_NOT_LESS_OR_EQUAL (Stop code 0x0000000A)
A driver accessed memory at an interrupt level where that’s not allowed — almost always a faulty or incompatible driver, sometime…
Blue screen: DRIVER_POWER_STATE_FAILURE (0x0000009F)
A driver didn’t complete a power transition (sleep, wake, shutdown) in time.
Blue screen: SYSTEM_SERVICE_EXCEPTION (0x0000003B)
A system call into the kernel crashed — almost always a driver bug (graphics, audio, antivirus, VPN) or corrupt system files.
Blue screen: KERNEL_SECURITY_CHECK_FAILURE (0x00000139)
The kernel detected corruption of a critical data structure — usually a bad driver, memory issue or disk corruption.
Blue screen: DPC_WATCHDOG_VIOLATION (0x00000133)
A driver spent too long at high priority (DPC level) — typically SSD/NVMe firmware, storage controller drivers (iaStorA.sys) or g…
Blue screen: PAGE_FAULT_IN_NONPAGED_AREA (0x00000050)
The kernel or a driver accessed memory that wasn’t there — faulty drivers, antivirus, RAM or disk issues.
Blue screen: KMODE_EXCEPTION_NOT_HANDLED (0x0000001E)
A kernel-mode program raised an exception nothing handled — usually a driver; sometimes caused by Fast Startup or RAM.
Two steps away (11)
Blue Screen: CRITICAL_PROCESS_DIED (Stop code 0x000000EF)
A process Windows can’t run without (csrss, wininit, smss…) stopped unexpectedly, so the system halted.
Blue Screen: MEMORY_MANAGEMENT (Stop code 0x0000001A)
Windows detected a severe memory-management error — commonly faulty RAM, unstable memory settings or a bad driver.
ERROR: bind message supplies 2 parameters, but prepared statement requires 1
The number of query parameters sent doesn’t match the $1, $2 … placeholders in the SQL.
ERROR: could not determine data type of parameter $1
PostgreSQL can’t infer a parameter’s type from context (e.g. $1 IS NULL or SELECT $1).
Blue screen: WHEA_UNCORRECTABLE_ERROR (0x00000124)
The hardware reported an error Windows couldn’t recover from — CPU, RAM, overclock/undervolt, overheating or power delivery.
Blue screen: VIDEO_TDR_FAILURE (0x00000116) — nvlddmkm.sys / atikmpag.sys / igdkmd64.sys
The graphics driver stopped responding and Windows couldn’t reset it in time.
Blue screen: UNEXPECTED_STORE_EXCEPTION (0x00000154)
The memory/store manager hit an exception — commonly a failing SSD/HDD, outdated storage drivers, or antivirus.
Blue screen: CLOCK_WATCHDOG_TIMEOUT (0x00000101)
A CPU core stopped responding to clock interrupts — usually overclocking/undervolting, BIOS/microcode bugs, or CPU/power hardware…
Windows Resource Protection found corrupt files but was unable to fix some of them
SFC detected damaged system files but couldn’t restore them because its own source (the component store) is damaged too.
Blue screen: INACCESSIBLE_BOOT_DEVICE (0x0000007B)
Windows lost access to the system drive during boot — storage driver/controller mode change, failed update, or disk/BCD problems.
INSTALL_FAILED_INSUFFICIENT_STORAGE: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
The device or emulator doesn’t have enough free internal storage to install the APK.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError