This is NOT avast! anti-virus specific but whenever I run a FULL anti-virus scan under Windows 2000 (SP4) regardless of who’s product it is, it crashes my computer with a 0x0000001e bugcheck. I am running avast! home version 4.7-942
I can run an avast 4.7 home scan at boot time and it runs fine without finding any virus…well, it did find a win32:ctx virus in PANDA’s pskavs.dll file but I’m told this is simply a false-positive and I deleted it anyway…
I’m running Windows 2000 service pack 4 with automatic updates turned on and no other A/V software (at least none that I know of)… I don’t seem to have any problems unless I try to run anti-virus, anti-spyware or registry fixers. IT consistently crashes whenever I run a FULL scan and can be intermittant at other times… Can this happen due to low memory or something? Sometimes when I run long Youtube video clips my computer crashes as well.
Here’s my system summary report:
System Information report written at: 01/22/2007 01:13:49 AM
[System Summary]
Item Value
OS Name Microsoft Windows 2000 Professional
Version 5.0.2195 Service Pack 4 Build 2195
OS Manufacturer Microsoft Corporation
System Name R3L5D3
System Manufacturer SYNTAX
System Model S635MP
System Type X86-based PC
Processor x86 Family 6 Model 7 Stepping 3 CentaurHauls ~796 Mhz
BIOS Version 10/09/03
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\Harddisk0\Partition1
Locale United States
User Name R3L5D3\Administrator
Time Zone Eastern Standard Time
Total Physical Memory 261,616 KB
Available Physical Memory 65,312 KB
Total Virtual Memory 891,696 KB
Available Virtual Memory 493,292 KB
Page File Space 630,080 KB
Page File C:\pagefile.sys
Thanks for the recommendations. I ran a full defrag on ther hardisk w/o errorr using perfectdisk and I don’t have any problems except when I try to run a full scan or when memory resident stuff is loaded ontop of Windows 2k.
The article at microsoft is only applicable to obsolete SCSI devices and I don’t beleive that applies to me. Microsoft recommends not performing the fix unless the issues with the old devices exist.
F-Prot claims they have the issue fixed in their just released version 6.0.5.1 which I’m trying now. W2K just doesn’t like non-microsoft apps hooking into it. These problems apparently don’t exist in XP because the hooks are handled differently.
I can’t beleive they didn’t get this resolved under Windows 2000 though. IT was a very stable release as far as I could see without this issue cropping up… What, did noone run antivirus software under W2K for all the years it was the standard? I can’t beleive that.
I’ll keep you all posted on the F-Prot 6.0.5.1 results.
What? :o
Are you trying to use two antivirus at the same time in the same computer?
Disabling one won’t be enough in most cases… you need to uninstall one of them :