BDSO error 0x00000109 with driver verifier issues

[Neolore]

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

 

[Northernsoul55]

From your crash logs:

STOP[COLOR=red] 0x00000109[/COLOR]: 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 [COLOR=red]ntoskrnl.exe[/COLOR]
*** 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)
:ar: 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)
:ar: http://www.sevenforums.com/tutorials/433-disk-check.html

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

Driver: [COLOR=red]ASACPI.sys[/COLOR]   
Dated: Mon Mar 28 03:30:36 [COLOR=red]2005[/COLOR]
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:

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:

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

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

:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Tip

Run these tests overnight

Post back any results/feedback

cheers

Dave

 

[x BlueRobot]

[COLOR="Red"]BugCheck 109[/COLOR], {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 )

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

Kernel data has become corrupted for some reason.

Remove:

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.

• http://www.sevenforums.com/performa...registry-cleaner-tests-why-not-use-one-2.html

Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

EDIT: Good work Dave my post was very rushed

 

[Neolore]

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

 

[Neolore]

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.

 

[Northernsoul55]

Please run the SF Tool again and post up a new log.