I was running AVG free and decided to switch to avast and try out the home edition. after a successful uninstall of AVG (reboot) and then a install of avast. on reboot my computer made it to my login screen where I could see my account names, but after 5 seconds I get a BSOD pointing out aswTdi.sys
I can uninstall avast and it goes away. I can also boot into the microsoft recovery console and remove the .sys file in my system32/drivers/aswTdi.sys and my computer will successfully boot and login without a blue screen. then I can uninstall avast or try and repair but no matter what I do I am stuck with the BSOD.
I am also running outpost pro firewall but I don’t think that should cause aswTdi.sys to bluescreen. what information can I provide so we can figure out why avast is being pointed out on my bluescreen?
Well apart from not having had avg8 on this system my system is basically the same as yours with outpost firewall (pro 2009 in my case) and no issues.
The aswtdi.sys is a driver and it could be possible there are remnants of avg8 left behind and there is a conflict.
Try the AVG Remover, download tool from here, http://www.grisoft.com/ww.download-tools there is a 32bit and 64 bit windows version, ensure you use the correct one. Once you have done that reboot and install avast again and see if that resolves the problem.
i used AVG remover tool to deinstall AVG because AVG would not uninstall with the normal installer.
so thats how i started. AVG is definetally removed from my system, but avast wouldn’t take without kicking the BSOD on aswTDI.sys
I actually was at work when I remote desktop installed avast and since it blue screened on the reboot it just cycled all day long until I got home so I have 99 minidump’s which I assume are all identical from the 99 reboots my computer did all day long while I worked I uploaded those to the FTP folder.
Hi Zurie,
thanks for the dumps, they are indeed identical and the crash seems to be in only one place inside aswtdi.sys. I still don’t understand how that could happen. It is a piece of code that was not changed since Network Shield was introduced. Would it be possible to generate a kernel dump for us and upload it? The minidump is always a little bit too small and contains almost nothing more than the stack trace.
I am having this same issue and am running Outpost Firewall as well. BSOD really sucks, I really want to run AVAST!
I grabbed the latest HOME edition online last night so it would be your latest build. I just uploaded my minidump as well to the ftp site, file is called: Mini122708-08.dmp
Hope you guys are able to fix this soon, really lame issue that as well forced me to have to uninstall AVAST in safe mode to take control of my computer again.
REPRO STEPS:
1.) Had Outpost Firewall Pro installed and running on my XP Pro SP3 latest updates 32-bit
2.) Installed latest HOME (4.8 i believe) edition of AVAST.
3.) Reboot with a boot time virus scan
RESULTS:
Once I boot into Windows, about 5 seconds later I get the aswtdi.sys BSOD
I too have the outpost firewall pro 2009, xp pro sp3 and no problem.
do you happen to have the OP anti-spyware module active as that will be running on boot (exactly when is the question). I know that OP detects avast and asks if you want to disable the OP anti-spyware for compatibility. I would suggest that you do that and see if it makes any difference.
I do not get the BSOD on first boot. However, whenever I start utorrent and let it run for some time eventually I’m getting the BSOD. Debugging tools tells me that the error was caused by aswTdi.SYS. I can’t force the error to occur, it takes some time before the BSOD occurs.
Doing stuff without utorrent started lets my computer run flawlessly.
I will set the dump to kernel memory dump and post it as soon as I get the BSOD.
we have seen such dumps with uTorrent and netlimiter. Do you have by any chance Netlimiter installed?
Regarding to the crash dump analysis - as you probably know, the aswtdi is a TDI filter and hence any network access request goes via aswtdi and aswtdi’s code will be on the stack. Knowing how !analyze works, it will probably not surprise you that every network related crash will automatically show the first non Microsoft code on the stack which will be aswtdi.sys. Do you have any TDI filters installed? Can you try to load the 3rd party filter first (by editing the LoadOrder registry key) and see if the carsh occurs in aswtdi.sys or in other filter.
Yes, I have netlimiter installed. Forgot to mention it in the last post. With respect to editing the load order: what is the location of the registry key? I searched for LoadOrder with regedit but it appears to be non-existent.
I also got (once) a BSOD on nlTDI.sys. aswTDI.sys gave me 4 BSOD’s in comparison. (all in a weeks time; since I installed netlimiter I guess)
I assume nltdi.sys is related to NetLimiter.
Apart from deinstalling NetLimiter to get rid of the BSODs (…is that a solution btw?..), is there anything that avast is able to do to get rid of the BSODs? Or should I send in a bug report to netlimiter. I’m running the program on a trial. I was thinking about buying a license, but with these crashes I probably will not.
As soons as I get a crash, I will post the dump file.
As far as I know there is nothing we can do, as a TCP filter we must hand down any request from upper layer (netlimiter here) and it appears that the IRP contains wrong buffers.
I also got (once) a BSOD on nlTDI.sys. aswTDI.sys gave me 4 BSOD's in comparison. (all in a weeks time; since I installed netlimiter I guess)
I assume nltdi.sys is related to NetLimiter.
How did you find out it is a problem in aswtdi.sys ? Did it crash inside the code of aswtdi.sys ? I would really like to see that!!!
First, I’m a noob to the forum. Glad to find it! (& thanks, Scroogle!)
I am presently getting a dump log indicating aswtdi.sys as the cause-- and I’m running both NetLimiter (2 Pro) and uTorrent (v1.8.2).
I run NetLimiter 24/7. uTorrent I run less consistently, but typically when I do, for long periods (hours/days).
Unfortunately, I’ve been running Minidumps so I can’t help (yet?) with a Kernel dump/crash stack trace-- but I’ve changed my settings to “Full” dump for if and when I get another BSOD/crash occurs.
My crashes thus far have been sporadic, typically weeks between, with no indication of any noticeable pattern. I’ve had no boot crashes (between uTorrent and NetLimiter, the latter is the only auto-start at boot along with avast)
Regarding to the crash dump analysis - as you probably know, the aswtdi is a TDI filter and hence any network access request goes via aswtdi and aswtdi's code will be on the stack. Knowing how !analyze works, it will probably not surprise you that every network related crash will automatically show the first non Microsoft code on the stack which will be aswtdi.sys.
Actually, I didn’t know this, so I’m glad you posted the info!
Do you have any TDI filters installed? Can you try to load the 3rd party filter first (by editing the LoadOrder registry key) and see if the carsh occurs in aswtdi.sys or in other filter.
I’m unfamiliar with TDI filters. If you might be so kind as to give us a little more info, I’d be glad to look into doing this. [meanwhile, I’ll check yet another Scroogle…] 8)
I uploaded those to the FTP folder.
