Stop 0x109 BSODs may take some time to fix.
Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus.
- Apply > OK
- Accept then restart.
Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.
http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm
Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
http://www.extreme.outervision.com/psucalculatorlite.jsp
Also let us know the wattage of the PSU, too.
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Stress test the CPU.
Hardware - Stress Test With Prime95
Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of
Speccy. Alternatively, you can publish a Speccy snapshot too:
http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .
Update the Intel HD Graphics Driver, either from our forum link,
http://www.sevenforums.com/graphic-...-graphics-driver-windows-7-a.html#post2166304, or You may get it from
Intel Download Center.
Moreover, you may run the
Intel (R) Driver Update Utility to auto detect the appropriate driver for your computer.
Let us know the results. We will decide the further steps seeing the situation.
_____________________________________________________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d895f3565f, b3b7465ee8719409, fffff80000b96bb0, 6}
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt_fffff80000b95000+1bb0 )
Followup: MachineOwner
---------
2: 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: a3a039d895f3565f, Reserved
Arg2: b3b7465ee8719409, Reserved
Arg3: fffff80000b96bb0, Failure type dependent information
Arg4: 0000000000000006, 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_fffff80000b95000+1bb0
fffff800`00b96bb0 48895c2408 mov qword ptr [rsp+8],rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x109
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`035bd498 00000000`00000000 : 00000000`00000109 a3a039d8`95f3565f b3b7465e`e8719409 fffff800`00b96bb0 : nt!KeBugCheckEx
STACK_COMMAND: kb
FOLLOWUP_IP:
nt_fffff80000b95000+1bb0
fffff800`00b96bb0 48895c2408 mov qword ptr [rsp+8],rbx
SYMBOL_NAME: nt_fffff80000b95000+1bb0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt_fffff80000b95000
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5149a99c
FAILURE_BUCKET_ID: X64_0x109_6_nt_fffff80000b95000+1bb0
BUCKET_ID: X64_0x109_6_nt_fffff80000b95000+1bb0
Followup: MachineOwner
---------
