Code:
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...tPatching.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: a3a01f592ec14700, Reserved
Arg2: 0000000000000000, Reserved
Arg3: ee3274faf73cc52d, Failure type dependent information
Arg4: 0000000000000101, 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
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
PG_MISMATCH: 10
MEMORY_CORRUPTOR: ONE_BIT
Code:
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffab005332672, 2, 0, fffff8016074c812}
Probably caused by : memory_corruption ( nt!MiDecrementAndInsertStandbyPages+d2 )
Followup: MachineOwner
Make sure your SSD Firmware is up to date and see if they have a utility to test it's health. Please run Seatools for DOS on your Mechanical Hard Drive http://www.sevenforums.com/tutorials...s-how-use.html
Are you running the X64 version of Chrome? If so, please uninstall it and install the X86 version.