Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Daily BSOD, error 0x00000109

09 Jan 2014   #1

Windows 7 Ultimate x64
Daily BSOD, error 0x00000109

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!

My System SpecsSystem Spec
10 Jan 2014   #2

Windows 7 Ultimate x64

My System SpecsSystem Spec
10 Jan 2014   #3
Microsoft MVP

Windows 7 Ult. x64

*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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
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.
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:

fffff800`03710ed0 488bc4          mov     rax,rsp





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:   
Product ID:                00426-OEM-8992662-00006
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.
My System SpecsSystem Spec

10 Jan 2014   #4

Windows 7 Ultimate x64

Ops. Got it.
My System SpecsSystem Spec

 Daily BSOD, error 0x00000109

Thread Tools

Similar help and support threads
Thread Forum
Random BSOD, error 0x00000109
It has occurred only once, while I was on the internet. Note: I have installed other RAM, but it worked fine until now. (got it from a other computer) I tested the Ram for 8 passes with memtest86+ without any error. The only strange thing is that windows RAM test won't go any further than...
BSOD Help and Support
Random BSOD, error 0x00000109
Not sure at to what has caused it, but it started five or so days back and happens every thirty minutes on average, although the time between crashes can often change, becoming longer or shorter for no apparent reason. I have updated most of my drivers (a slow process as the free program I have...
BSOD Help and Support
BSOD while doing nothing, error 0x00000109
Hi guys I had my computer for about 2 years now and have been getting BSOD several times in the last month and a half.I get the blue screen simply when my computer is on and not running any specific programs. The dump file reads:...
BSOD Help and Support
BSOD error 0x00000109
For about the past week, I've been getting this blue screen within about 30-40 minutes of turning my computer on. Works fine in safe mode, but on a normal boot it's consistently crashing with this same error every time. I've attempted to follow various other threads of users who had similar issues,...
BSOD Help and Support
Daily BSOD 0x00000109
I'm facing BSOD's on my computer, they occur daily. I tried different things to fix it (like: other antivirus software, updating drivers), I also tested my memory with Memtest but the BSODs still occur and I cant seem to find the problem here. See the attachment for the latest minidumps,...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 00:23.
Twitter Facebook Google+