Multiple BSOD's on windowslogon/random

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

The bugcheck analysis stands as

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89f37b6d8, b3b7465ef1b4862e, fffff80003188ae0, 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 : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

So, let us search for any faulting driver at first. Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

Sorry for the late reply ... you needed assistance there instantly, but I was at work.

If it goes to black screen at startup, it gives a screen, isn't it? If so, follow the onscreen information. Otherwise, boot into safe mode, disable verifier, boot normally, enable it again, making it sure that you have checked only the non-microsoft drivers.

soulswiper said:

Interesing, computer doesnt load up properly when eyefinity is on and driver verifier, just gets after windows start up and goes to black screens, any suggestions?

For what it's worth, the first time I enabled Driver Verifier and rebooted, it behaved just as you describe. Turned out it was bluescreening and rebooting before I even SAW the bluescreen. Disable Verifier as Arc said and check for dump files at the times you restarted (C:\Windows\mindumps). You might have something there that will help.

Code:

fffff880`0337e848  fffff880`0421c62cUnable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
 eamonm+0x662c

"Eset Amon" driver seems to be causing a problem for you there. Please uninstall Eset and all its components from your computer. Use MSE instead. It does not cause problems with the windows 7 system.

• Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
• Microsoft Security Essentials - Free Antivirus for Windows