I got this on Windows 8.1 today but my driver don’t do anything strange so
hopefully it was “too warm computer” or something like that?
/Bo Brantén
3: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel
code or data have been corrupted. There are generally three causes for a
corruption:
- A driver has inadvertently or deliberately modified critical kernel
code or data. See
http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx - A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal
breakpoints, “bp”, can only be set if the debugger is attached at boot
time. Hardware breakpoints, “ba”, can be set at any time. - A hardware corruption occurred, e.g. failing RAM holding kernel code or
data.
Arguments:
Arg1: a3a01f58afc8b8a2, Reserved
Arg2: b3b72bdf0248bdfd, Reserved
Arg3: ffffd001995e90c0, Failure type dependent information
Arg4: 0000000000000002, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification