Author Topic: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.  (Read 13404 times)

0 Members and 1 Guest are viewing this topic.

Offline zurie

  • Newbie
  • *
  • Posts: 2
Avast Build 4.8.1296

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?



Online DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 83348
  • No support PMs thanks
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #1 on: December 20, 2008, 04:24:36 PM »
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.
WinXP ProSP3/ Core2Duo E8300/ 4GB Ram/ avast! free 18.5.2342/ Firefox ESR, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ DropMyRights/ WinPatrol+/ Drive Image 7.1/ SnagIt 10.0/ avast! mobile security
Windows 10 Home 1909 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 20.5.2415 (build 20.5.5410.561) UI-1.0.532/ WinPatrol+/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11747
    • AVAST Software
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #2 on: December 20, 2008, 07:03:37 PM »
Can you upload the corresponding minidump file (from Windows\Minidump folder) to ftp://ftp.avast.com/incoming ?
Thanks.

Offline zurie

  • Newbie
  • *
  • Posts: 2
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #3 on: December 23, 2008, 08:20:56 PM »
ok.

1) 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 :D  I uploaded those to the FTP folder.


Offline lukor

  • Avast team
  • Super Poster
  • *
  • Posts: 1877
    • AVAST Software
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #4 on: December 23, 2008, 11:24:09 PM »
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.

Thanks a lot.
Lukas.

Offline uriel242

  • Newbie
  • *
  • Posts: 1
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #5 on: December 27, 2008, 11:22:15 PM »
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

Online DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 83348
  • No support PMs thanks
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #6 on: December 28, 2008, 12:03:34 AM »
I too have the outpost firewall pro 2009, xp pro sp3 and no problem.

1. 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.

WinXP ProSP3/ Core2Duo E8300/ 4GB Ram/ avast! free 18.5.2342/ Firefox ESR, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ DropMyRights/ WinPatrol+/ Drive Image 7.1/ SnagIt 10.0/ avast! mobile security
Windows 10 Home 1909 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 20.5.2415 (build 20.5.5410.561) UI-1.0.532/ WinPatrol+/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro

Offline wvrick1958

  • Jr. Member
  • **
  • Posts: 26
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #7 on: December 28, 2008, 04:08:38 AM »
I had it do restarts on my newly built PC, its something with XP Pro sp3, I have XP sp2 and no problems, Avast will not run on my new pc with sp3

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11747
    • AVAST Software
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #8 on: December 28, 2008, 11:45:56 AM »
wvrick1958, do you also use Outpost?
Can you upload a few of the latest minidimp files (from Windows\Minidump folder) to our FTP?
Thanks.

Offline pk

  • Avast team
  • Super Poster
  • *
  • Posts: 2085
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #9 on: December 28, 2008, 12:37:45 PM »
wvrick1958: yes, we would appreciate your minidumps.

Also wait for lukor's reply, because what I've seen, uriel242's minidump is better to tell us what was happening than zuries's minidumps (no offence).

Offline lukor

  • Avast team
  • Super Poster
  • *
  • Posts: 1877
    • AVAST Software
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #10 on: December 29, 2008, 03:38:40 PM »
Hello guys,

could anyone with the problem reproducible upload a kernel memory dump? Thanks a lot.

Lukas.

Offline Arutha

  • Newbie
  • *
  • Posts: 2
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #11 on: February 09, 2009, 11:44:16 AM »
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.

Kind regards!

BTW, I'm using AVAST Home edition V4.8.1335.

Offline lukor

  • Avast team
  • Super Poster
  • *
  • Posts: 1877
    • AVAST Software
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #12 on: February 09, 2009, 05:11:25 PM »
Hi Arutha,

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.

Or post the crash stack trace.
Thanks.

Lukas.

Offline Arutha

  • Newbie
  • *
  • Posts: 2
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #13 on: February 10, 2009, 09:43:53 AM »
Hi Lukas,

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.

Regards!

Offline lukor

  • Avast team
  • Super Poster
  • *
  • Posts: 1877
    • AVAST Software
Re: aswTdi.sys BSOD my win XP SP3 box after install, first boot BSOD.
« Reply #14 on: February 10, 2009, 10:48:46 AM »
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.

Quote
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!!!

What I have seen is for example this:

STACK_TEXT: 
ba134848 f3a139f8 01000000 1f000000 00000001 nt!MmMapLockedPagesSpecifyCache+0x370
ba134868 f3a097f8 01000000 00000010 842e0009 tcpip!TcpipBufferVirtualAddress+0x24
ba134888 f3a0d2b7 00001cfe 842ec248 83fae568 tcpip!XsumSendChain+0x44
ba134908 f3a0d0cf 83f73430 83fae568 84146500 tcpip!UDPSend+0x3ca
ba13492c f3a0d135 00134950 84146440 842ec288 tcpip!TdiSendDatagram+0xd5
ba134964 f3a09881 84146500 84146570 84146500 tcpip!UDPSendDatagram+0x4f
ba134980 804ef19f 847d7710 84146500 85314510 tcpip!TCPDispatchInternalDeviceControl+0xff
ba134990 f75e7449 841465b8 00000000 853144e0 nt!IopfCallDriver+0x31
ba1349f4 f75e77e2 853144e0 84146500 84146594 aswTdi!xxxTdiSendDatagram+0x1234
ba134a54 804ef19f 85314428 84146500 841465dc aswTdi!xxxDispatchInternalDeviceControl+0x4321
ba134a64 f399e7d6 84146500 841465b8 847b6710 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
ba134a78 f399e944 847b6710 84146500 85314428 nltdi+0x7d6
ba134aa8 804ef19f 847b6710 84146500 840a1578 nltdi+0x944
ba134ab8 f385f807 ba134ba8 00000008 ba134b1c nt!IopfCallDriver+0x31
ba134b10 f3856b5e 80562134 031afaa4 f3856b5e afd!AfdFastDatagramSend+0x2fd
ba134c5c 80580487 855fb218 00000001 031af974 afd!AfdFastIoDeviceControl+0x2a7
ba134d00 80579274 000002cc 00000370 00000000 nt!IopXxxControlFile+0x255
ba134d34 8054162c 000002cc 00000370 00000000 nt!NtDeviceIoControlFile+0x2a
ba134d34 7c90e4f4 000002cc 00000370 00000000 nt!KiFastCallEntry+0xfc
031afa64 00000000 00000000 00000000 00000000 0x7c90e4f4



« Last Edit: February 10, 2009, 10:55:02 AM by lukor »