Solved Multiple BSOD's on windowslogon/random

[soulswiper]

Getting BSODS from windows login and around 5mins from being on windows startup,

Kinda weird it's happening due to it being clean formatted, so thinking possibly either something on hardware is on its way out?

 

[Arc]

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

*******************************************************************************
*                                                                             *
*                        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.

 

[soulswiper]

Thanks Arc, shall get onto the driver verifier

Had no BSOD's since last ones so far without it on, but i'll run

 

[soulswiper]

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?

 

[Arc]

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.

 

[badkarma11]

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.

 

[soulswiper]

Hmm, weird i did the safemode way turn it off gets me back into normal boot.

also did only have non microsoft checked & and i've gotten no further BSODs so far, tonight when im home i'll disable eyefinity and chill for abit without it

Rather get these BSOD's sorted before

 

[soulswiper]

Anyone around to be able to help with this?


-goes and finds koolkat- :>

 

[koolkat77]

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 [URL="http://www.carrona.org/drivers/search.php?id=eamonm.sys"]eamonm.sys[/URL]
 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

 

[soulswiper]

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 [URL="http://www.carrona.org/drivers/search.php?id=eamonm.sys"]eamonm.sys[/URL]
 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

Thanks yussi, i've installed MSE now and uninstalled ESET, will get back to you in couple days or less if i BSOD

 

[koolkat77]

No problem. Keep us posted either way

 

[soulswiper]

Got some crashes, overnight weirdly dont get BSOD's anymore i just get black screens of evilness

 

[koolkat77]

STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION  
Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
BugCheck 109, {a3a039d89cbdd6bd, b3b7465eef3aa613, fffff800031890a8, 1}
Probably caused by : memory_corruption

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP  
Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
BugCheck 7F, {8, 80050031, 6f8, fffff880012b9289}
Probably caused by : memory_corruption

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
→ Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

 

[soulswiper]

Ok thanks koolkat gonna run these memtests again just looked up guide haha

 

[soulswiper]

Hey koolkat, how long would 6x 2gb ram sticks take to test one at time? or an estimate

Also if i pass one stick fine, should i just pop in another or just clear them all to 8 passes?

 

[koolkat77]

Hey koolkat, how long would 6x 2gb ram sticks take to test one at time? or an estimate

Also if i pass one stick fine, should i just pop in another or just clear them all to 8 passes?

That's gonna take long but yes. You should as both the dumps and usual causes say that theres a problem with memory

 

[soulswiper]

Ok thanks i hope this finds some errors on the sticks, also reverted my bios to factory could been something related in there aswell?

 

[koolkat77]

BIOS to factory? Not sure what you mean?

 

[soulswiper]

i had memory overclocked abit, so i reset the bios to fail safes


and im on the last ram stick now none of the others error'd

 

[koolkat77]

Oh yup, you should do that. No overclocking please.