BSOD 0x00000109 Driver Issues?

Hi magepker.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the CPU.
Hardware - Stress Test With Prime95

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Uninstall the following programs:

• AMD VISION Engine Control Center
• AMD Overdrive
• ASUS\AI Suite II
• MSI Live Updates
• MSI Afterburner

Let us know the results.
______________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8a19556d1, b3b7465ef4122627, fffff80002aabdc0, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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.

Hello Magepker,

Please note that we only have a few crash dump analysts at the SevenForums, and sometimes we are overwhelmed by the new threads and it can take us a while to catch up with our threads, please understand this.

----------

Please don't bump your thread; it's against the forum rules and disadvantageous for you as it makes the thread seem more busy as if you were receiving assistance.

2) No useless posts, e.g., thread bumping, useless one liners, junk posting to increase post count, and identical multi-postings in different forums.

Read here: Forum Rules

----------

Please do run Memtest and post the results just to be sure.
And what are the results of running Prime95?

Please try to provide as much details as possible from what you have done, we need all possible information in order to assist you.

----------

To remove AI Suite, please use the following program;

• Download and install Revo Uninstaller.
• Right click the program that needs to be removed, and click on Uninstall.
• Select "Advanced" as uninstall mode.
• Let Revo remove the program, and afterwards please follow the displayed steps to remove all entries of the program as well.
• When all programs have been uninstalled, please restart your machine.

----------

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8a19556d1, b3b7465ef4122627, fffff80002aabdc0, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

More info Bug Check 0x109
Usual cause: Failing hardware, faulty drivers.

----------

As you can see, your dump file points to failing RAM, so please do follow Arc's suggestion to test your RAM with Memtest, even if you have already done this in the past.

----------

Code:

0: kd> !sysinfo cpuspeed
sysinfo: unknown error 80004005

I assume that this error is why Arc asked you if you where overclocking.
Just to be sure, please reset your BIOS back to the default settings in case that you are overclocking and unaware of it.
Clear CMOS

   Tip

Be sure to write down whether your SATA mode is either AHCI or IDE. After clearing the CMOS be sure to set the SATA mode to the correct mode.

   Warning

If any hardware is overclocked, be sure to also set it back to the default speed!

Good luck and keep us posted,
Nommy