As above, turning off on access scanner solves problem, image attached
Is this also NT4?
No it’s XP Home with SP2
Please send me the latest file from \minidump.
At which stage does it crash? Immediately after reboot?
Thanks
Vlk
No goes for about 1 min then crashes
I’ve had both updates today 4.5.517 & 4.5.518 without problem on XP SP2.
Long shot - but try unplugging any USB devices and starting your pc. I had a similar problem ages ago (not Avast related) and it was the USB mouse that it suddenly decided to dislike.
If that works just plug the USB devices back in while in windows,
nimrod666: please download http://cs.felk.cvut.cz/~kurtip1/aswTdi.sys and replace the installed one in your \Windows\System32\Drivers folder, please let us know if it helps
Note: the file is not for WinNT 4.x system
went 2-3 mins then BSOD again
Hi!
No, certainly it is NOT a problem of any USB-releated hardware. I’m more than 99% sure that it is Avast-related problem!
I also have WinXP Home Edition with SP2 (as nimrod666) and it went WITHOUT any problems or reinstall or nothing since THREE years now. Since todays morning, when avast engine has updated and computer has rebooted after that, I started to have exactly the same problem as nimrod666 described to you.
I see that updated file aswTDI.sys does not solved the problem so I’m not going to install it. But I try to uninstall avast completly and report to you if it helped.
Currently working under Emergency Mode, so my computer works fine. But any atempt to run it normally ends after 1 to 10 mintest with BSOD and reset.
Best regards!
Tom
nimrod666: I see, the actvive aswTdi.sys is still the old one, try to replace it with the fixed one; maybe it was replaced back, so try it under safe-mode. The problematic aswTdi.sys has sth around 32K, the fixed one should has 28,672 bytes, could you please comfirm it ?
f77a1000 0 ( 0 k) 0 ( 0 k) aswTdi.SYS Fri Nov 12 17:49:51 2004
thanks
Renamed the old file and replaced with new which is 28K, will try again
Same problem with ASWTDI driver using Precision workstation 420, dual CPU’s and Win 2K - image reversion back to 4.1 pro has eliminated the problem… 
Have you tried the fixed version of aswTdi.sys ? The link is above.
Also, please send me the latest *.dmp file from \Windows\minidump folder to my email. Thanks.
Fixed version of aswTdi.sys seems to be working OK, latest *.dmp file has been sent tp Petr
Had similar problem. XP home SP2, have been running 4.1 for 6 mo.
After update to 4.5, got repeated auto reboots on serious error, Microsoft report system decoded to graphics driver stuck thread.
Do not have any aswtdi.sys file in w\sys32\drivers
Uninstall 4.5 and reinstall 4.1 works fine, problem gone.
Can send all minidumps if you wish.
Any thoughts?
Thanks
PS: Graphics Driver is imbedded Intel 82865G
If you dont have any aswTdi.sys (avast v4.5) so Network Shield wasn’t probably installed and then i dont know what were caused of BSODs. Anyway, send me some latest minidumps on my email: kurtin@asw.cz. Thanks
So, if we all get to conlussion that aswTdi.sys file (which came with today’s update) caused the problem, the only question that left is, when you are about to release new update that comes with fixed aswTdi.sys file?
Or maybe we should install / update to newest version and try to immediatelly patch the file with the one available under link posted some posts ago?
I’m currently uninstalled avast! and the problem gone. Wating until fixed updated or install will be available.
Tom
Trejder I recommend trying to use the patched driver. After all, nimrod confirmed that it solved the problem for him (at least so far).
Would be interesting to know if it solves the problem in your case as well.
Make sure to reboot the machine after replacing the driver. AND one more thing - the avast auto-updater will probably try to replace the patched driver with the original (official) version so don’t reboot after replacing the driver and rebooting (I hope you understand what I mean).
In other words:
- install avast, don’t reboot
- replace the aswTdi.sys file
- reboot (this will complete the installation process)
- after the machine starts, try not to reboot (even if avast asks you to do so).
Thanks
Vlk
Hi!
Of course I understand! As fast as I will be able to do, what you wrote, I’m going to write you what are the effects on my machine.
Would it be more safetly to completely turn-off automatic update before reboot that finalizes installation (if I will be able to run avast! before reboot) or right after it?
Tom
I’m afraid that wouldn’t help. The “auto-correct” feature is somewhat independent of the update settings. It is a security feature designed to prevent viruses from altering the program binaries (which once altered, can have pretty much undefined effects…).
Thanks,
Vlk