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: BSOD (randomly) error 0x00000109

17 Feb 2013   #1
technostructura

Windows 7 64bit
 
 
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.


My System SpecsSystem Spec
.
17 Feb 2013   #2
Northernsoul55

Microsoft Community Contributor Award Recipient

Windows 7 Professional 64bit
 
 

Hi Techno,

Please follow these instructions for posting:

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

Cheers

Dave
My System SpecsSystem Spec
17 Feb 2013   #3
technostructura

Windows 7 64bit
 
 

Sorry about the Dave, but I think I've got it up to speed.
Am I still missing something?
My System SpecsSystem Spec
.

17 Feb 2013   #4
Northernsoul55

Microsoft Community Contributor Award Recipient

Windows 7 Professional 64bit
 
 

Hi,

The analysis is Inconclusive:

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

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)

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)

Quote:
I also noted that these drivers are very outdated:

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

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:

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

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
My System SpecsSystem Spec
24 Feb 2013   #5
technostructura

Windows 7 64bit
 
 

Hi Dave,

Thanks a lot for your help.
I had to wait a few days before I could get the time to run all of these tests. But here are my findings:

(1) Memtest86 ran for 11 passes with no errors.
(2) SFC / scannow found no errors.

(3) I ran chkdisk (for almost 24 hours), and I got the following message in the event log:

Quote:
chkdisk results:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
280832 file records processed. File verification completed.
578 large file records processed. 0 bad file records processed. 2 EA records processed. 76 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
356966 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
280832 file SDs/SIDs processed. Cleaning up 1128 unused index entries from index $SII of file 0x9.
Cleaning up 1128 unused index entries from index $SDH of file 0x9.
Cleaning up 1128 unused security descriptors.
Security descriptor verification completed.
38068 data files processed. CHKDSK is verifying Usn Journal...
35570200 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
280816 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
410537918 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

1953503968 KB total disk space.
310778400 KB in 216593 files.
128880 KB in 38069 indexes.
0 KB in bad sectors.
445012 KB in use by the system.
65536 KB occupied by the log file.
1642151676 KB available on disk.

4096 bytes in each allocation unit.
488375992 total allocation units on disk.
410537919 allocation units available on disk.

Internal Info:
00 49 04 00 d0 e2 03 00 1b fd 06 00 00 00 00 00 .I..............
7e ac 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 ~...L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
(4) I've updated the Broadcom drivers

(5) ** "Sonic DVD/CD Driver" -- I couldn't actually find the drivers on the website. I scoured around looking for a place to download, but to no avail. It may just be that I am a bit of a noob, but yeah -- unable to find anything there.

(6) I updated my bios to 1605. The system seemed to not like it at first. After updating and rebooting, I got an error on boot that asked me to reset my "boot settings". I went into the bios and saw that 1605 was the current version. I tried to boot windows again, and on the splash screen I got an error message and system hang/freeze.

I did a hard reboot from that point, and there was no problem getting into Windows. As of now, my bios is 1605, and I haven't BSOD'd yet. (fingers crossed).

(7) All windows updates are installed, and all drivers are up to date.
My System SpecsSystem Spec
25 Feb 2013   #6
Northernsoul55

Microsoft Community Contributor Award Recipient

Windows 7 Professional 64bit
 
 

Good Work

Post back if you experience another BSOD

cheers

Dave
My System SpecsSystem Spec
Reply

 BSOD (randomly) error 0x00000109




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
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...
BSOD Help and Support
BSOD occurring sorta randomly, error 0x00000109
Hey, I have been getting BSOD errors more frequently recently, it has been occurring on a daily basis in the past 2 weeks, and today, it occurred twice. Well it didnt start 2 weeks ago, it started many months, and it used to happen now and then, then start weekly and then daily. I didnt really...
BSOD Help and Support
BSOD randomly occuring after +/- 40 to 45 minutes. Error 0x00000109
Hi, I've been trying to fix my aunts malware infected pc. I've got to the point where all the malware has been removed. Programs used: F-Secure, malwarebytes and Hitman Pro. But now i'm trying to get these BSOD's solved. Ran memtest for over 7 passes to be sure that it isn't a RAM problem. ...
BSOD Help and Support
Random BSOD - error 0x00000109
Hello, I'm trying to figure out why this laptop randomly blue screens... thought it was drive but ran chkdsk and defrag with no issues... checked memory with memtest - let it do 3 passes, no errors... stumped now
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


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

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App