Random BSOD, error 0x00000109

[Darkhound64]

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 will only update two drivers per day)

The Blue Screen error code is 0x00000109

I'm not sure what other information I can give here, but I'm hoping I can finally finish posting this topic before my computer crashes for a third time.

It has been running great for two years now with no problems and I don't know whats wrong with it

 

[koolkat77]

Grab All. Please follow the tutorial fully:

• Blue Screen of Death Posting Instructions

 

[Darkhound64]

Grab All. Please follow the tutorial fully:

• Blue Screen of Death Posting Instructions

I don't understand? I used the program supplied by the forums, and clicked the big yellow "grab all" button to make the folder.

 

[koolkat77]

The Msinfo and Systeminfo files are missing from your zip.
Please re-run the SFDT.

 

[Darkhound64]

The Msinfo and Systeminfo files are missing from your zip.
Please re-run the SFDT.

Did it work this time?

 

[koolkat77]

Yes, thank you.

• STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION
• Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

Eset can be a cause of BSOD's. Please uninstall it and use MSE for the time being.

Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

• Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
• Help protect your PC with Microsoft Security Essentials
• Malwarebytes Free

   Note

:info: Do not start the trial version of MalwareBytes

You may also take a look at:

• Good & Free System Security Combination

------------------------

Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public

Daemon Tools (also Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall Daemon Tools.

• DuplexSecure - FAQ

As an alternative:

• We recommend the use of Total Mounter or Magic ISO

------------------------
Reduce the start-up items, Antivirus software is basically whats required.

• Remove Startup Programs in Windows 7
• Clean Startup in Windows 7

------------------------
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow - read here

Run Disk Check on your Hard Drive for file system errors and bad sectors on it - read here
------------------------
Upload a screenshot using:

• CrystalDiskInfo:tip: For how to upload a screenshot or file, read here

Test your Hard Drive(s) by running:

• Hard Drive Diagnostic Procedure

------------------------
Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to Part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d895ded4f5, b3b7465ee85d1137, 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
---------

0: 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: a3a039d895ded4f5, Reserved
Arg2: b3b7465ee85d1137, 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`031d25d8 00000000`00000000 : 00000000`00000109 a3a039d8`95ded4f5 b3b7465e`e85d1137 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
---------

 

[Darkhound64]

Yes, thank you.

• STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION
• Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

Eset can be a cause of BSOD's. Please uninstall it and use MSE for the time being.

Eset has been removed, however, every time I attempt the SFC /scannow command, it will get to 70-80% before my computer has to recover from BSOD once again.

 

[koolkat77]

Upload new logs and continue with rest of the steps.

 

[Darkhound64]

Sorry for the large gaps between my responses, I'm rather sick at the moment.

The SFC /scannow test came back with "Windows Resource did not find any integrity violations."

I'm going to do the RAM test shortly