1. #1

    Consistent 0xC5 BSODs after logon.

    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.

    • Basic elimination techniques can be very effective.
    Trouble and axe0 say thanks for this.


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    zigzag3143's Avatar
    Join Date
    Mar 2012
    Posts
    3,741
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        DV7
      • Cooling:
        Coolermaster U3 best in class
      • Operating System:
        Win 8 RTM

    Re: Consistent 0xC5 BSODs after logon.

    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.

    MS-MVP Windows IT-PRO 2010-2017
    MCC-2013-2017
    Wankiya & Dyami
    Team ZigZag





  3. #3
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    15,839
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Re: Consistent 0xC5 BSODs after logon.

    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
    axe0 says thanks for this.

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015

  4. #4
    JaidynM's Avatar
    Join Date
    May 2012
    Location
    Somewhere Over The Rainbow
    Posts
    1,011
    • specs System Specs
      • Manufacturer:
        Custom Build
      • Motherboard:
        ASUS P5G41T-M LX
      • CPU:
        Intel Pentium Dual Core E6700 3.2GHz
      • Memory:
        Strontium 8192MB DDR3 1333Mhz
      • Graphics:
        msi GeForce N560GTX-M2D1GD5 1GB
      • Sound Card:
        Realtek HD Audio
      • Hard Drives:
        Seagate Barracuda LP Green 2TB Internal HDD + WD Elements Desktop 1TB External HDD
      • Disk Drives:
        Black eMaxx ATX Mini Tower Case
      • Power Supply:
        SHAW Viper-1500w Gaming PSU
      • Display:
        CHIMEI CMV 221D 22" (1680x1050)
      • Operating System:
        Windows 7 Ultimate x64/Windows 8 Consumer Preview x64/Ubuntu 11.04

    Re: Consistent 0xC5 BSODs after logon.

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

    "No bird soars to high, if he soars with his own wings." - William Blake


  5. #5
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    15,839
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Re: Consistent 0xC5 BSODs after logon.

    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.

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015

  6. #6
    zigzag3143's Avatar
    Join Date
    Mar 2012
    Posts
    3,741
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        DV7
      • Cooling:
        Coolermaster U3 best in class
      • Operating System:
        Win 8 RTM

    Re: Consistent 0xC5 BSODs after logon.

    Quote Originally Posted by JaidynM View Post
    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.

    MS-MVP Windows IT-PRO 2010-2017
    MCC-2013-2017
    Wankiya & Dyami
    Team ZigZag





Similar Threads

  1. How To Disable Logon Passwords in Windows 8
    By JMH in forum Microsoft News
    Replies: 0
    Last Post: 06-08-2012, 03:16 AM

Log in

Log in