BSOD (randomly) error 0x00000109

Hello folks,

My system has been randomly BSOD-ing, but usually when idle.

Temperatures seem to be stable.

The event log says:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a039d89ddab4f8, 0xb3b7465ef05883ee, 0xfffff800035c3510, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021713-40451-01.

And I've attached the dump file link here:
https://dl.dropbox.com/u/104635481/021713-40451-01.dmp

And the results from using the SF diagnostics tool:
https://dl.dropbox.com/u/104635481/SF_17-02-2013.zip

While I am a fairly tech savvy fella, I won't suggest that I am very familiar with digging deep into the bowels of my PC. For this reason, please respond with fairly idiot-proof terminology and I would be grateful.

Thanks.

Hi Techno,

Please follow these instructions for posting:

https://www.sevenforums.com/crashes-d...tructions.html

Cheers

Dave

Hi,

The analysis is Inconclusive:

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BugCheck 109, {a3a039d89ddab4f8, b3b7465ef05883ee, fffff800035c3510, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
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 Patching Policy for x64-Based Systems
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.

First test to try:
Please run Memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.:

RAM - Test with Memtest86+

Please run System File Checker to check the integrity of all Windows 7 system files:

Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
Type SFC /scannow at the prompt (note there is a space between SFC and /scannow)

SFC /SCANNOW Command - System File Checker

Also please Run chkdsk /f/r in an elevated command prompt.

Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
At the command prompt please type: chkdsk /f/r
(Note: there is a space between chkdsk and /f/r)

Disk Check

I also noted that these drivers are very outdated:

ebdrv Broadcom NetXtreme II Kernel 31/12/2008 12:29:28 PM

http://www.broadcom.com/support/ethe...etxtremeii.php

fffff880`0119b000 fffff880`011a6ae0 PxHlpa64 PxHlpa64.sys Mon Dec 10 23:49:01 2007 (475DD06D)
Refers to: Sonic CD/DVD driver (used by many different CD/DVD programs), help here:

pxHelp20.sys programs

[BIOS Information (Type 0) - Length 24 - Handle 0000h]
Vendor American Megatrends Inc.
BIOS Version 1503
BIOS Starting Address Segment f000
BIOS Release Date 09/20/2012
BIOS ROM Size 400000

Plan to update your BIOS to version: 1605 (help to improve stability), found here:

ASUSTeK Computer Inc. -Support- Drivers and Download M5A97

Also please ensure your device drivers are up-to-date (drivers at Asus site) and all Windows updates are installed.

Post back any results / observations, or if you experience another BSOD after all updates carried out, then please post back the new .dmp log.

Cheers
Dave

Good Work :)

Post back if you experience another BSOD

cheers

Dave