Bug Check 0x109: CRITICAL_STRUCTURE_CORRUPTION
The CRITICAL_STRUCTURE_CORRUPTION bug check has a value of 0x00000109. This indicates that the kernel has detected critical kernel code or data corruption.
Important Info If You Have Received a STOP Code
If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact info for Microsoft or your computer manufacturer, Contact Support.
If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.
These actions might prevent an error like this from happening again:
- Download and install updates and device drivers for your computer from Windows Update.
- Scan your computer for computer viruses.
- Check your hard disk for errors.
CRITICAL_STRUCTURE_CORRUPTION Parameters
The following parameters are displayed on the blue screen.
| Parameter | Description |
|---|---|
|
1 |
Reserved |
|
2 |
Reserved |
|
3 |
Reserved |
|
4 |
The type of the corrupted region. (See the following table later on this page.) |
The value of Parameter 4 indicates the type of corrupted region.
| Parameter 4 | Type of Corrupted Region, Type of Corruption, or Type of Action Taken That Caused the Corruption |
|---|---|
|
0x0 |
A generic data region |
|
0x1 |
A function modification or the Itanium-based function location |
|
0x2 |
A processor interrupt dispatch table (IDT) |
|
0x3 |
A processor global descriptor table (GDT) |
|
0x4 |
A type-1 process list corruption |
|
0x5 |
A type-2 process list corruption |
|
0x6 |
A debug routine modification |
|
0x7 |
A critical MSR modification |
Cause
There are generally three different causes for this bug check:
-
A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems.
-
A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.
-
A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.
Send comments about this topic to Microsoft
Build date: 4/9/2013
