I have today installed ClamWin v0.97 and it is locking up when I run a scan. It locks up so tight the mouse pointer does not move, CapsLock does not work and Ctrl-Alt-Del is ignored. Powering off and on is required.

It has locked up when scanning a .ZIP file containing some very old .TXT emails.
It has locked up when scanning a directory containing loads of old Outlook .EML files.

It runs clean over and over on a drive with a wide variety of files, but no email in it.
If I copy the ZIP file and the .EML file onto the drive which works and scan it, ClamWin does not lock up.

There are no files matching *.dmp anywhere.

ClamAV 0.97
Virus DB Version: (main: 53; daily: 12833)
Intel Pentium 4
Windows ME v4.90.3000
255 MB RAM

When I installed it I chose not to include the Outlook option as I do not use email on this PC any more. There are, however, directories containing emails.

(This thread "https://ftp.clamwin.com/viewtopic.php?t=3064 Computer Locks Up Scanning Thunderbird Folders" may be the same problem.)

I have now tried running this on the PC's C: drive; it died after about 90 minutes of scanning.

It had run through all of C:\WINDOWS and C:\PROGRAM FILES and all of C\WORK which contains 20 years' of my documents.

It gave up on a copy of a Usenet posting stored as a text file which, of course, is very similar to an email.

Something about text files that contain email headers is locking up ClamWin.

#############################

Having rebooted, there are now FILEnnnn.CHK files on the drive pointed to by %TEMP%, created by the SCANDISK after turning the PC back on. The most recent of these is a Usenet posting, the one before that (same time stamp, so merely lost blocks from another part of the disk) is the Usenet FAQ that was shown as the last file scanned by ClamWin. BUT, both contain the line "Received: by clamd (bounce)" at the top.

In E:\TEMP, which is pointed to by %TEMP% there are now 22 directories:

E:\TEMP\clamav-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.fff3b647.clamtmp

each containing a file

clamav-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.fff3b647.clamtmp

each of which contains Usenet posting(s). There are another 8 of those files in E:\TEMP too, all being zero bytes.

This suggests ClamWin is coughing and dying over some sorts of Usenet or email text files.