[SOLVED] Consistent 0xC5 BSODs after logon.

[reventon]

Hello all,

Thought I would write down what happened to me today, on the offchance it (or the process I went through) helps anyone.

Turned on my desktop this morning - logged in and had just enough time to see the wallpaper before being greeted by a blue screen with 0x000000C5 on it! I have it set to not automatically reboot, so I had a quick look at it before manually restarting - assuming it was simply a one off glitch of the kind that invariably happens on 5 year old hardware. No driver was mentioned, and I could not recall any common cause for 0xC5.

It booted fine, I logged in again with the intention of looking at the minidump and at roughly the same point I received another identical BSOD.

At this stage my thought process was:

• Two identical crashes at roughly the same point in start up - most likely software related

• Given it happened after logon both times - probably 3rd party software related.

Based on the above I booted into Safe Mode to retrieve the minidumps, however they weren't there. No big deal, it just meant I would have to do it the hard way.

Looked in EventViewer and the WER entries in MSINFO - prior issues listed but nothing relevant to the morning's crashes.

At this point I decided to try a bit of elimination. I disabled all non-Microsoft services and startups with Autoruns, then rebooted normally. Logged in without issue.

Next I enabled the core 3rd party drivers and services (Graphics/Networking/Sound) and rebooted. Logged in again without issue.

Added just ESET to the above enabled items and rebooted again. Logged in and immediately received a 0xC5 BSOD. Aha!

Based on the above it was a safe guess that either ESET or the networking drivers were at fault. After rebooting into Safe Mode with Networking I located the latest network driver. Rebooted after installation - still received the BSOD.

Despite knowing ESET5 was out, I had not got around to updating from ESET4 yet. So, my next course of action was to remedy that and I am pleased to say that solved the issue.

Lessons:

• I should remember to take advantage of free software updates. :lol:

• Basic elimination techniques can be very effective.

 

[zigzag3143]

There has been quite a spate of ESET related BSOD's of late. Most are from 4.x and have core dates of 2011. Since I use ESET I had more than a passing interest.

It seems to subsided in the last week or so. Perhaps an update to defs, or something different.

 

[jcgriff2]

The 0xc5 bugcheck = attempt to access invalid memory

Very similar to 0xa and 0xd1

ESET 4 Amon driver = eamon.sys

ESET 5 Amon driver = eamonm.sys - updated

Thanks, Ben!

John

 

[JaidynM]

So apparently ESET is BSOD prone (or v4 is anyway). I've only ever seen AVG & avira cause BSOD's.

 

[jcgriff2]

The older version - ESS 4 should be updated to ESS 5 for Vista and Windows 7.

ESS/NOD32 Amon driver eamon.sys can clash (reference invalid memory) with updated Microsoft OS drivers after Windows Updates come.

 

[zigzag3143]

So apparently ESET is BSOD prone (or v4 is anyway). I've only ever seen AVG & avira cause BSOD's.

I wouldnt say "prone" like some of the others, and it seems to have started overnight. It stopped just as quickly.