computers running chkdsk on boot after NOD32 installed

Discussion in 'ESET Smart Security' started by greggs, Aug 25, 2009.

Thread Status:
Not open for further replies.
  1. greggs

    greggs Registered Member

    Joined:
    Aug 18, 2009
    Posts:
    2

    I have installed NOD 32 v4 on about 180 workstations now, and I am starting to get complaints from users that chkdsk runs every time they boot up the computer. Interestingly, this is only happening so far on a bunch of Dell GX-620 machines, all running WXP SP3.

    These machines have run fine for years, and the NOD32 install is the only recent software change.

    I don't see anything in the forum on this problem.

    Anybody got a hint for me?

    g
     
  2. trjam

    trjam Registered Member

    Joined:
    Aug 18, 2006
    Posts:
    9,057
    Location:
    North Carolina
    never heard of it, might I ask what they did run before Eset.
     
  3. trjam

    trjam Registered Member

    Joined:
    Aug 18, 2006
    Posts:
    9,057
    Location:
    North Carolina
    greggs, there are plenty of support people here to assist with this issue if you can respond please to my question. Thank you.
     
  4. Davec2

    Davec2 Registered Member

    Joined:
    Jan 18, 2009
    Posts:
    11
    Location:
    Montreal, Canada
    I just upgrade to Win 7 from Vista, and had CHKDSK run twice in the past week on startup. Both times no errors found.

    The event viewer shows this error logged the day before:
    Error Ntfs Event ID:55 Task Category (2)
    The file system structure is corrupt and unusable. Please run chkdsk utility.

    Of course the chkdsk then runs automatically the next time the computer is started.
    I ran the more thorough chkdsk that checks all the files and free space as well and it also did not see any errors.

    Has anyone else seen this happen ?
    Of course I cannot be sure that it is anything to do with ESS, but have seen references on the internet to other antivirus programs causing this exact same problem.

    I have just updated ESS to version 4.0.474.0 to see if that helps.
     
  5. Davec2

    Davec2 Registered Member

    Joined:
    Jan 18, 2009
    Posts:
    11
    Location:
    Montreal, Canada
    Running latest version of ESS with Win7 32-bit.
    Still getting CHKDSK running sometimes at startup.
    Caused by system logging "Error NTFS Event ID 55" the previous day.
    I have spent many many hours troubleshooting this, and finally found that the Event 55 is logged when I either transfer pictures from my camera with USB cable, or when I put SD card in the reader and transfer pictures to the computer (just using the generic Windows "Import Pictures & Videos". Most times there is no error message when I transfer the pictures, and the pictures are fine, but Event 55 is put into the log. I think it may only happen when a new folder is generated, but not 100% sure about that. (A new folder is generated in My Pictures if the date has changed.)

    If I turn off ESS real-time file system protection the error does not occur.
    Come to think of it I think I have only been having this problem since I upgraded to Win7 and re-installed ESS.

    If someone from ESET is reading this, hopefully they can suggest a fix. I cannot leave the file system protection turned off, and I'm going crazy seeing CHKDSK run every time I start the computer.
     
    Last edited: Dec 19, 2009
  6. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
    does the chkdsk fix errors when it is run? it sounds like hd is slowly going bad
     
  7. Davec2

    Davec2 Registered Member

    Joined:
    Jan 18, 2009
    Posts:
    11
    Location:
    Montreal, Canada
    Sorry, forgot to mention that CHKDSK never finds any problem or errors.
    I have also ran the hard drive manufacturers (Seagate) drive check utility with no errors found.
     
    Last edited: Dec 19, 2009
Thread Status:
Not open for further replies.