Blue screens & stop codes troubleshooting

Repeated stop-code crashes, driver/hardware isolation and recovery-oriented diagnosis.

Start here

Record the exact stop code, named module and recent hardware/driver changes before the next crash erases context.

Escalation boundary

Repeated crashes without a clear device branch may require memory diagnostics, dump analysis or vendor hardware tests.

A safe-first route for repeated Windows 11 stop-code crashes that separates recent hardware, drivers and recovery options.

Scoped errors

Error records in this system

Microsoft identifies WHEA_UNCORRECTABLE_ERROR as a hardware error path; start with updates/drivers and recovery around recent changes.

Use the stop-code context to check recent drivers and memory rather than treating the crash as a generic Windows error.

Microsoft defines bug check 0x9F as a driver in an inconsistent or invalid power state.

Bug check 0x7E means a system thread generated an exception that the error handler did not catch.

Microsoft defines bug check 0x50 as an invalid system-memory reference; driver and memory evidence matter.

Bug check 0x116 occurs when Windows attempts to reset the display driver after a timeout and recovery fails.

Microsoft describes bug check 0xD1 as a kernel-mode driver accessing pageable or invalid memory at an IRQL that was too high.

When Event ID 1001 says the computer rebooted from a bugcheck, the useful evidence is the exact bugcheck code, parameters and saved dump.