Drivers · critical

How to fix CRITICAL_STRUCTURE_CORRUPTION (0x109)

Drivers troubleshooting guide

What this error means

Windows stopped because it detected that critical kernel code or data had been changed. 64-bit Windows does not allow its kernel to be modified except by Microsoft's own hot patches, so when something changes it, Windows stops. Microsoft lists three causes: a driver that modified kernel code or data, accidentally or on purpose; a developer setting a breakpoint with a kernel debugger attached after startup; or hardware corruption, such as kernel data stored in memory that failed.

Updated

Applies to
Windows 11 and Windows 10 (64-bit)
Difficulty
Intermediate
Before changes
Low

Reviewed by Matyáš Rada · Documentation checked: 2026-10-31 · Checked against Microsoft's bug check documentation; not tested on every configuration.

Before you begin

Photograph the blue screen and think about what you installed recently, especially tools that change how Windows or games work at a low level. If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Find the driver named in the crash

Microsoft recommends disabling a driver named in the bug check or getting an update from its maker.

  1. Look for a .sys file name on the blue screen and search it to find the program or device it belongs to.
  2. Check Event Viewer (Win + R, eventvwr.msc) > Windows Logs > System for errors that identify a device or driver near the crash time.
What to expect

You know which driver is suspected.

If it does not help

If a driver is named, update it or uninstall its program. If not, continue with step 2.

Browse related errors
02Remove software that hooks into Windows

The most common cause is a driver that modifies kernel code, which older or low-level tools sometimes do.

  1. Uninstall recently installed or old versions of antivirus, firewall, VPN, virtualization or emulator software, and system tweaking or overclocking tools (Settings > Apps > Installed apps).
  2. Uninstall game cheat, trainer or mod loader tools that use a driver.
  3. Restart and test.

Keep Microsoft Defender on while another antivirus is removed.

What to expect

The crashes stop.

If it does not help

If you need a program, install its newest version that supports your Windows version.

Browse related errors
03Scan for malware

Rootkits modify the kernel deliberately to hide themselves, which triggers this stop code.

  1. Open Windows Security > Virus & threat protection > Scan options.
  2. Choose Microsoft Defender Antivirus (offline scan) and click Scan now; the PC restarts to scan before Windows loads.
What to expect

No threats are found, or they are removed.

If it does not help

If threats were found, change your important passwords from a clean device.

Browse related errors
04Test the memory

Microsoft lists hardware corruption, such as kernel data in failing memory, as a cause and recommends Windows Memory Diagnostic.

  1. Turn off XMP, EXPO and any overclock in the BIOS for testing.
  2. Run Windows Memory Diagnostic (Win + R, mdsched.exe) > Restart now and check for problems.
  3. Check the MemoryDiagnostics-Results entry in Event Viewer > Windows Logs > System.
What to expect

No memory errors are found.

If it does not help

If errors are found, follow the memory test errors guide on this site.

Browse related errors
05Run hardware diagnostics

Microsoft recommends the manufacturer's hardware diagnostics and checking that new hardware is compatible.

  1. Run the hardware diagnostics from your PC or laptop maker, if available.
  2. If you added hardware recently, remove it and test, and check that it supports your Windows version.

Switch off and unplug the PC before removing internal parts.

What to expect

The hardware tests pass.

If it does not help

Replace parts that fail the tests.

Browse related errors
06Update drivers and the BIOS

Current drivers and firmware avoid known compatibility problems.

  1. Run Windows Update, including Optional updates > Driver updates.
  2. Install current graphics, chipset and network drivers from the device makers, and the latest BIOS/UEFI from your PC or motherboard maker.

Do not switch off the PC during a BIOS update.

What to expect

Drivers and firmware are current.

If it does not help

Use the PC normally for a few days and watch for new crashes.

Browse related errors
07Repair system files

This makes sure the Windows files themselves are intact.

  1. Open Terminal (Admin).
  2. Run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, and restart.
What to expect

SFC reports no integrity violations, or that it repaired them.

If it does not help

If crashes continue, see the blue screen errors overview on this site or use System Restore to a point before the problem began.

Browse related errors

Possible causes

  • A driver that modifies the Windows kernel, accidentally or on purpose
  • Outdated security, virtualization or system tweaking software
  • Game cheat tools or malware (rootkits) that tamper with the kernel
  • Faulty RAM
  • A kernel debugger attached after startup (developers only)

Useful Windows tools

These commands open Windows tools. Review changes before applying them.

eventvwr.msc
mdsched.exe

Sources & further reading