Author Topic: ashServ2.exe Constantly Accessing Hard Drive ?  (Read 8467 times)

0 Members and 1 Guest are viewing this topic.

Offline gearedsteam

  • Newbie
  • *
  • Posts: 13
ashServ2.exe Constantly Accessing Hard Drive ?
« on: October 25, 2004, 02:10:48 AM »
After installing Avast Home 4.1,  I noticed my hard drive light would flicker about every
2 seconds and I could hear it being accessed.   So I went into Windows XP (SP1) task manager and turned on all the "I/O.." options on the "View" tab to see what was going on.

I found that "ashServ2.exe" is reading from the drive about 2K bytes every second.. even when the "A"vast ball in the taskbar is not rotating (indicating that it is scanning an active program).

The only other process that is reading the hard drive every second is LSASS.EXE but it is only reading 200 bytes per second.

Why is  "ashServ2.exe" reading 2K per second from the hard drive and is there a way to deactivate this and still maintain   "On-Access Protection Control".

My concern is Avast will cause premature drive failure with this continuous accessing of the drive.

Attached is a copy of my Task Manager screen with ashServ2.exe hi-lited.


Thanks in advance for any input any one may have...

Dave

http://www.gearedsteam.com/

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re:ashServ2.exe Constantly Accessing Hard Drive ?
« Reply #1 on: October 25, 2004, 02:38:19 AM »
ashServ2.exe is a part from the version 4.5 beta.
I think you're talking about ashServ.exe of the 4.1.
I had noticed CPU usage and not disk access... I can't know it two problems are related as yours CPU usage is null  :-\
The best things in life are free.

Offline RejZoR

  • Polymorphic Sheep
  • Serious Graphoman
  • *****
  • Posts: 9406
  • We are supersheep, resistance is futile!
    • RejZoR's Flock of Sheep
Re:ashServ2.exe Constantly Accessing Hard Drive ?
« Reply #2 on: October 25, 2004, 11:22:24 AM »
Disk access is because ashServ.exe is a On-Access module.
Visit my webpage Angry Sheep Blog

Offline gearedsteam

  • Newbie
  • *
  • Posts: 13
Re:ashServ2.exe Constantly Accessing Hard Drive ?
« Reply #3 on: October 25, 2004, 02:03:39 PM »
To: Technical
Yes, it is ashServ.exe and not ashServ2.exe... my mistake


To: RejZoR

Yes, I know ashServ.exe is an On-Access module as I stated in so many words in my original post.  

The question is ... no program is being actively accessed... so why is ashServ.exe constantly reading the hard drive.   "On-access" is  indicated by the rotating "A"vast ball in the task bar.   My "A"vast ball is not rotating while  the ashServ.exe is contantly reading the drive.

Why is ashServ.exe constantly accessing the hard drive when no program is being accessed?   I expect it to read the hard drive when I fire up a program... but after the program has fully loaded and is idle.. I would not exepect it to be reading the hard drive.  

Thanks in advance,

Dave

http://www.gearedsteam.com/

OisteinR

  • Guest
Re:ashServ2.exe Constantly Accessing Hard Drive ?
« Reply #4 on: October 25, 2004, 02:57:39 PM »
Yes, both ashServ.exe and ashDisp reads from disk.

About 4 reads pr. second. Average of  5k/sec. because ashDisp reads big blocks.

ashServ has read 116.320.000 bytes the last 12 hours.



This can't be right....?


Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11851
    • AVAST Software
Re:ashServ2.exe Constantly Accessing Hard Drive ?
« Reply #5 on: October 25, 2004, 03:07:10 PM »
What is the "scanned count" item for each resident provider?

OisteinR

  • Guest
Re:ashServ2.exe Constantly Accessing Hard Drive ?
« Reply #6 on: October 25, 2004, 08:09:09 PM »
What is the "scanned count" item for each resident provider?

In my case: 456 on Standard Shield, the rest = 0

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11851
    • AVAST Software
Re:ashServ2.exe Constantly Accessing Hard Drive ?
« Reply #7 on: October 25, 2004, 08:13:20 PM »
116320000 / 456 = 250kB per file... sounds OK to me.

OisteinR

  • Guest
Re:ashServ2.exe Constantly Accessing Hard Drive ?
« Reply #8 on: October 25, 2004, 08:35:56 PM »
116320000 / 456 = 250kB per file... sounds OK to me.

Some misunderstanding here... :)

Yes, that number looks ok, but.

Number of I/O reads increases with 4 every second
Number of I/O bytes read increases with ~5Kb every second.
No provider needs to run.

After a fresh boot,  I/O bytes read is about 15Mb, and thats ok, but increases with 5kb every second.
30 min. after boot,  I/O bytes read is ~25Mb
No other activity on is done in that 30 min.

That is ~18Mb every hour, and that still can't be right.....?  ....or?



Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11851
    • AVAST Software
Re:ashServ2.exe Constantly Accessing Hard Drive ?
« Reply #9 on: October 26, 2004, 09:31:27 AM »
OK, I would say that the periodic I/O activity is caused by MS Jet drivers avast! is using. I'm afraid we can hardly do anything about it...
If you are using avast! 4 Home, you can switch the database type from ODBC to XML (e.g. by changing for the corresponding item in avast4.ini) and see if it helps.

OisteinR

  • Guest
Re:ashServ2.exe Constantly Accessing Hard Drive ?
« Reply #10 on: October 26, 2004, 11:31:45 AM »
OK, I would say that the periodic I/O activity is caused by MS Jet drivers avast! is using. I'm afraid we can hardly do anything about it...
If you are using avast! 4 Home, you can switch the database type from ODBC to XML (e.g. by changing for the corresponding item in avast4.ini) and see if it helps.


Yes, that helped, the disk activity stopped...,but I got an errormessage in the error log after reboot:
"During the parsing of C:\Program Files\Alwil Software\Avast4\DATA\avast4.xml XML document, the following error occurred: C."

There is no .XML file in the data dir., but everything seems to work...




Offline gearedsteam

  • Newbie
  • *
  • Posts: 13
Re:ashServ2.exe Constantly Accessing Hard Drive ?
« Reply #11 on: October 26, 2004, 11:59:52 PM »
Igor,

Changing from OCBC to XML worked!!!!  LIFE IS GOOD!
  Thank you  Igor :) !!!

Unlike OisteinR, I didn't get any errors on reboot.


OisteinR,
Thank you for your persistence with this and ultimately helping
me resolve this problem via Igor.    I hope you can ultimately
resolve your error.


Regards,
Dave

http://www.gearedsteam.com/