Windows BSOD Error 0x0000002B — What It Means & How to Fix It

What Does This Error Mean?

BSOD 0x0000002B (PANIC_STACK_SWITCH) means Windows detected that the kernel stack — the internal memory area Windows uses to track what it is doing — switched unexpectedly. This is almost always caused by a faulty driver, corrupted system files, or failing hardware. Windows crashes immediately to prevent data corruption or worse damage.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows 7

Common Causes

A device driver has a bug that corrupts the kernel stack memory
System files are damaged — often from a bad Windows Update or sudden power loss
Failing RAM is writing incorrect data into the stack memory area
A rootkit or malware has tampered with kernel-level structures
An incompatible or outdated chipset or storage driver is interfering with stack operations

How to Fix It

Run the System File Checker to repair corrupted Windows files. Open Command Prompt as Administrator (right-click Start > Terminal (Admin) or Command Prompt (Admin)) and type: sfc /scannow — then press Enter. Wait for it to finish.

This scan checks every protected Windows system file and replaces any that are damaged. It can take 10 to 30 minutes. Do not close the window while it runs.
Run DISM to repair the Windows image itself. In the same Administrator Command Prompt, type: DISM /Online /Cleanup-Image /RestoreHealth — then press Enter. This goes online to download clean replacement files.

DISM fixes problems that SFC cannot fix on its own. Always run SFC again after DISM completes to make sure all files were repaired correctly.
Test your RAM with Windows Memory Diagnostic. Press the Windows key, type 'Windows Memory Diagnostic', and open it. Choose 'Restart now and check for problems.' The test runs automatically and shows results after your PC restarts.

Corrupted stack memory is often caused by faulty RAM. If errors are found, test each stick individually by removing the others one at a time.
Check for driver updates — especially for storage controllers, chipset, and network adapters. Open Device Manager by right-clicking Start. Look for any yellow warning icons. Visit your PC or motherboard manufacturer's website for the latest drivers.

Kernel stack errors are frequently triggered by storage or chipset drivers. If you recently updated a driver before the crashes started, try rolling it back via Device Manager > device Properties > Driver tab > Roll Back Driver.
Run a full malware scan using Windows Defender or Malwarebytes (free version). Open Windows Security > Virus & Threat Protection > Scan Options > Full Scan. Rootkits and kernel-level malware can cause stack switching errors.

Some malware specifically targets kernel structures to hide itself. If Malwarebytes finds anything, follow its instructions to quarantine or remove the threat, then restart and monitor for further crashes.

When to Call a Professional

If SFC, DISM, and RAM tests all pass but the crashes keep happening, the issue may be hardware-level. A technician can run advanced diagnostics on your motherboard and CPU. If malware is suspected and your antivirus cannot remove it, a professional can clean the system safely.

Frequently Asked Questions

How do I see which driver caused the crash?

Download the free program WhoCrashed from resplendence.com. It reads the minidump files Windows creates during each BSOD and tells you which driver file caused the crash. Minidump files are saved in C:\Windows\Minidump automatically after each crash. Once you know the driver name (it ends in .sys), search for it online to find out which program or device uses it.

Could a virus cause this BSOD?

Yes — some advanced malware and rootkits operate at the kernel level. They can corrupt kernel structures including the stack, which causes exactly this type of crash. Run both Windows Defender and Malwarebytes in full scan mode. If you suspect a rootkit, use a bootable scanner like Kaspersky Rescue Disk that runs before Windows loads.

Will a Windows reset fix this error?

A Reset (keeping your files or removing everything) will fix this error if it is caused by corrupted system files or a bad driver. Go to Settings > System > Recovery > Reset this PC. Choose 'Keep my files' first to preserve your documents. If the error returns after a reset, the cause is likely hardware — RAM, storage, or the motherboard itself.