*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a01f595b785539, b3b72bdfadf70a78, fffff802bbfc3a6c, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [COLOR=#ff0000]memory_corruption[/COLOR]
Followup: memory_corruption
---------
1: 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:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) 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.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01f595b785539, Reserved
Arg2: b3b72bdfadf70a78, Reserved
Arg3: fffff802bbfc3a6c, Failure type dependent information
Arg4: 0000000000000001, 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
Debugging Details:
------------------
PG_MISMATCH: 2000
MEMORY_CORRUPTOR: ONE_BIT
FAULTING_IP:
hal!HalpAddMcaToProcessorSpecificSection+0
fffff802`bbfc3a6c 4c8bdc mov r11,rsp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x109
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
STACK_TEXT:
ffffd000`bd8cd188 00000000`00000000 : 00000000`00000109 a3a01f59`5b785539 b3b72bdf`adf70a78 fffff802`bbfc3a6c : nt!KeBugCheckEx
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
fffff802bbfc3ab0 - hal!HalpAddMcaToProcessorSpecificSection+44
[ d5:95 ]
1 error : !hal (fffff802bbfc3ab0)
MODULE_NAME: [COLOR=#ff0000]memory_corruption
[/COLOR]
IMAGE_NAME: [COLOR=#ff0000]memory_corruption[/COLOR]
FOLLOWUP_NAME: [COLOR=#ff0000]memory_corruption[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit
FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: memory_corruption
---------
