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: BDSO error 0x00000109 with driver verifier issues


16 Apr 2013   #1

windows 7 professional 64
 
 
BSOD error 0x00000109 with driver verifier issues

Hi all,

I'm having regular BDSO's with error 0x00000109 since last week. System restore, RAM check (Memcheck86), memory check, Disk check, uninstalling a lot of apps/games, didn't help.

I red the forums here and activated driver verifier, but since then, when the error occurs, my screen goes all crazy, but no BDSO (memory dump) is activated and so I can't upload the minidumps since then. I will deactive it now and see if I get my BSDO back without freezing my whole rig.

I used the SF_Diagnostic tool and uploaded the zip in this thread.

Sorry for some messages beeing in dutch as that's the OS's language.

Thanks for looking into this,

Neo

My System SpecsSystem Spec
.

16 Apr 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Professional 64bit
 
 

From your crash logs:

Code:
 
STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION    
Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d89bfeb92f, b3b7465eee7cf871, 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 )
Run SFC 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)
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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)
http://www.sevenforums.com/tutorials/433-disk-check.html

This driver predates Win 7 and is known for BSOD issues, please remove:

Code:
 
Driver: ASACPI.sys   
Dated: Mon Mar 28 03:30:36 2005
Navigate to: C:\windows\system32\drivers     
Find the driver  ASACPI.sys, right click and delete, reboot.
Remove Advanced SystemCare 6 as Win 7 does not require registry tweaking and may do more harm than good.

From your error logs:
Driver: a2ddax64.sys
Dated: Fri Mar 08 04:41:40 2013
Refers to: A2 Direct Disk Access Support Driver root\legacy_A2DDA\0000
which is a possible driver remnant from emsisoft (anti-malware program):

Is this device Disabled/or has no drivers installed????

Uninstall the program, if no program is installed, uninstall the driver:

Code:
 
Goto device manager, click the view tab and select "show hidden Devices"
Expand Disk Drives and search for the device.(may be called A2DDASD)
Look for the driver, click on the offending driver and select uninstall.
Test the hard drive with either the manufacturer's diagnostic tools/Prime95:

http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html
Hard Drive Diagnostic Procedure

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Tip   Tip
Run these tests overnight


Post back any results/feedback

cheers

Dave
My System SpecsSystem Spec
16 Apr 2013   #3

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Code:
BugCheck 109, {a3a039d89f37f619, b3b7465ef1b6355b, 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 )
Code:
Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
Kernel data has become corrupted for some reason.

Remove:

Code:
Start Menu\Programs\Advanced SystemCare 6
Windows 7 doesn't require any programs which make changes to the operating system and registry, these programs tend to cause problems by modifying and deleting files.Scan for any missing, modified or corrupted protected Windows files with:EDIT: Good work Dave my post was very rushed
My System SpecsSystem Spec
.


16 Apr 2013   #4

windows 7 professional 64
 
 

Thanks guys. I'll try all that when I get home this evening. The system care app was installed after I got the blue screens. If not needed, I will remove it too.

Neo
My System SpecsSystem Spec
20 Apr 2013   #5

windows 7 professional 64
 
 

OK, so I did all the above. Memcheck86, removed the drivers you mentioned, reinstall some of my drivers (sound, video), upgraded my BIOS, checkdisk, did an SFC....

But still the same issue.
My System SpecsSystem Spec
20 Apr 2013   #6

Microsoft Community Contributor Award Recipient

Windows 7 Professional 64bit
 
 

Please run the SF Tool again and post up a new log.
My System SpecsSystem Spec
Reply

 BDSO error 0x00000109 with driver verifier issues




Thread Tools



Similar help and support threads for2: BDSO error 0x00000109 with driver verifier issues
Thread Forum
Random BSOD, error 0x00000109 BSOD Help and Support
Using Driver Verifier to identify issues with Drivers Crash and lockup debug 'How To'
Random BSOD - error 0x00000109 BSOD Help and Support
BSOD while doing nothing, error 0x00000109 BSOD Help and Support
BSOD error 0x00000109 BSOD Help and Support
BSOD (randomly) error 0x00000109 BSOD Help and Support
BSOD driver verifier error 0x000000c9 IO Manager Violation 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 11:17 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33