Daily BSOD, error 0x00000109

[TrueNorth67]

I've been struggling with two different BSODs - a memory_management issue I fixed after running memtest86+ (one of my two 4 GB modules was corrupted) and then there is the remaining ntoskrnl.exe bug check code 0X00000109. I understand this to be a CRITICAL_STRUCTURE_CORRUPTION. Unfortunately, this doesn't tell me much - and I have no idea how to interpret a dump file.

These BSODs have pretty much been there since day one, when I built the computer. I struggled a bit with a very large cpu-fan and fumbled a lot with the screws etc. Could this potentially have led to something? I have an Asus Xonar DG card and have had some problems with it. Could this be something? I've had no problems with the card after I switched to the alternative UNIXonar drivers. I've had no temperature issues.

Other than the BSOD everything works as it should - and have been for the past two years. Any assistance would be greatly appreciated!

 

[TrueNorth67]

Bump

 

[Golden]

*******************************************************************************
*                                                                             *
*                        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: a3a039d89bcf677f, Reserved
Arg2: b3b7465eee4c36d5, Reserved
Arg3: fffff80003710ed0, 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:
------------------


FAULTING_IP: 
nt!SeQuerySecurityAttributesToken+0
fffff800`03710ed0 488bc4          mov     rax,rsp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x109

PROCESS_NAME:  System

CURRENT_IRQL:  0

Host Name:                 STIGS-PC
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Stigs
Registered Organization:   
[COLOR="Red"][B]Product ID:                00426-OEM-8992662-00006[/B][/COLOR]
Original Install Date:     27.08.2013, 23:09:22
System Boot Time:          09.01.2014, 13:49:59
System Manufacturer:       Gigabyte Technology Co., Ltd.
System Model:              Z68X-UD3H-B3

I would start with a clean installation of a genuine Windows 7 - an ACER OEM on a retail motherboard violates the Microsoft EULA and is considered a counterfeit installation. Depending on the source of the crack, there could be all sorts of issues with the installation. A genuine installation is less likely to result is the issues you are experiencing.

 

[TrueNorth67]

Ops. Got it.