BSOD - Critical_Structure_Corruption (109)

msmith

New Member
Messages
1
Over the past few days I have been getting a blue screen on my laptop with the error message CRITICAL_STRUCTURE_CORRUPTION. It happens when I am performing any sort of task and can be as frequent as one every few minutes. It seems that the frequency of them has reduced slightly but I would appreciate it if anyone can tell me what might be causing them. I've pasted the contents of one of the minidump files below.

Thank you in advanced.

Code:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.




Loading Dump File [C:\Windows\Minidump\122213-63984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available




************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff802`b461c000 PsLoadedModuleList = 0xfffff802`b48e0990
Debug session time: Sun Dec 22 12:24:45.515 2013 (UTC + 0:00)
System Uptime: 0 days 0:18:02.382
Loading Kernel Symbols
.


Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.


..............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 109, {a3a01f589908b596, b3b72bdeeb87eb55, ffffe0000104b0d0, 1c}


Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )


Followup: MachineOwner
---------


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: a3a01f589908b596, Reserved
Arg2: b3b72bdeeb87eb55, Reserved
Arg3: ffffe0000104b0d0, Failure type dependent information
Arg4: 000000000000001c, 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:
------------------




CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


BUGCHECK_STR:  0x109


CURRENT_IRQL:  2


ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre


STACK_TEXT:  
ffffd000`20c5a188 00000000`00000000 : 00000000`00000109 a3a01f58`9908b596 b3b72bde`eb87eb55 ffffe000`0104b0d0 : nt!KeBugCheckEx




STACK_COMMAND:  kb


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: Unknown_Module


IMAGE_NAME:  Unknown_Image


DEBUG_FLR_IMAGE_TIMESTAMP:  0


IMAGE_VERSION:  


BUCKET_ID:  BAD_STACK


FAILURE_BUCKET_ID:  BAD_STACK


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:bad_stack


FAILURE_ID_HASH:  {75814664-faf6-4b70-bbc7-dc592132ecdd}


Followup: MachineOwner
 

My Computer

System One

  • OS
    Windows 8.1 x64
Back
Top