Author Topic: Freezing system bad! Bad system, bad!  (Read 4756 times)

0 Members and 1 Guest are viewing this topic.

Offline Zorque

  • Newbie
  • *
  • Posts: 4
  • Heh-heh. Llama, that's rich
Freezing system bad! Bad system, bad!
« on: September 07, 2003, 10:52:36 PM »
Heh, humor.


Anyways, I tried to scan my hard drive for the first time, and after about 14,000 files scanned, my computer freezes and when I move the cursor it restarts. I think, "My computer is a glorified pile of tin, it's normal" and I forget about it. Next day, or today, I try again, it freezes a few files earlier, of course this time it doesn't restart by itself. I get to do that myself! Yay!

I'm using the Home version, because I'm cheap, if that helps.

Please help.

Offline whocares

  • Super Poster
  • ***
  • Posts: 1698
  • I'm not a llama! :-)
Re:Freezing system bad! Bad system, bad!
« Reply #1 on: September 08, 2003, 04:41:57 PM »
Hi,
some info on your

- Win-version&Servicepacks/Updates,
- hardware & HD-partitioning
- startup-programs
- evtl. the file(s) avast hangs

could be real helpful here..

-have you changed anything in avast-config from the default settings ? if so, please list..
-
have you done a check with diagnostic tools fro your RAm & harddisk(s)
 :)

Offline Zorque

  • Newbie
  • *
  • Posts: 4
  • Heh-heh. Llama, that's rich
Re:Freezing system bad! Bad system, bad!
« Reply #2 on: September 09, 2003, 04:00:47 AM »
Win95
Um... I am not really sure
lwbwheel.exe, systray.exe, MSGSRV32.exe, cacheman.exe, MSNMSGR.EXE, ashserv.exe
C:\My Documents

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11808
    • AVAST Software
Re:Freezing system bad! Bad system, bad!
« Reply #3 on: September 09, 2003, 09:14:16 AM »
Does the problem depend on the scanning of archives turned on or off?

Suppose the problem occurs on a particular file - is it possible to locate the file (I mean something more specific than C:\My Documents)? If you turn on the report file creation (in Program settings) and set the "OK files" to be written to the report file, you should see all the files being scanned. Then you can check if the problem occurs at the same place (or at least approximatelly - if the operating system hangs, the file cache may not be flushed correctly each time) - it should be "close" to the end of the report...