Hey I Don’t know whether or not anyone has mentioned this before but its working just fine on the windows 7 beta test and I wanted to give kudos
great job avast team. keep it up
Yes, already reported…
Did you experience any trouble using any avast feature?
I believe that I had the issue where after an update to the Avast database, Windows 7’s security center still showed Avast as “out of date”. (I had restored an older ghost image, Avast updated its database, and the red flag remained.) I believe a reboot resets the security center to reflect the correct status, which is why it’s typically not seen.
To be honest, it didn’t mean much to me at the time till I saw it mentioned in another thread in this forum, and then I realized what had happened.
Everything else seems to work.
The most common cause of the Windows Security Center showing avast! as “out of date” (if you have the latest VPS) is an incorrect system date. Ensure that your system date is correct, day, month and year.
I would have thought by using an older ghost image, which would have had an even older VPS version would only make things worse, as the gap between the VPS version date and the system date would be greater.
A reboot, depending on settings may possibly synchronise the system clock, but I don’t know.
Hello,
I have big issue with Windows 7 Beta 64bit version and Avast antivirus Home 4.8
When I transfer large amount of data from SAMBA server it usually crash (BSOD) and tell tdx.sys
This issue was solved when I uninstalled Avast antivirus software.
This also can be Microsoft issue. I was already notify then about this problem. If there are some bug/feature in tdx.sys
I can send minidump files of crash
Latest crash callstack:
nt!KeBugCheckEx
nt!KiBugCheckDispatch+0x69
nt!KiPageFault+0x25d
tdx!TdxEventReceiveConnection+0x300
tcpip!TcpIndicateData+0xfe
tcpip!TcpDeliverDataToClient+0x370
tcpip!TcpDeliverReceive+0xa5
tcpip!TcpTcbFastDatagram+0x207
tcpip!TcpTcbReceive+0x275
tcpip!TcpMatchReceive+0x1e9
tcpip!TcpPreValidatedReceive+0x31c
tcpip!IppDeliverListToProtocol+0x4d
tcpip!IppProcessDeliverList+0x59
tcpip!IppReceiveHeaderBatch+0x231
tcpip!IpFlcReceivePackets+0x664
Hi,
currently we consider this to be a bug in Windows 7 since the similar appears with several TDI drivers (not only avast’s Network shield).
tdx.sys is the driver that provides kernel networking api for the drivers called TDI. When no TDI filters are loaded (the default after clean install of Vista or Win7), the tdx.sys layer is not used. I believe that the same bug would be invoked by other TDI filters, like for example Netlimiter, various firewalls or antiviruses.
We will of course monitor this issue, thanks for the report!
Lukas.
I think I will tomorrow test F-Secure or some other software. If that also have samekind of effect to TDX.sys.
I try to report soon.
Now I go sleep
- Juha
OK,
Now I have runned test with other antivirus (Norton 360 v3 Beta) and it have same issue. So this is most likely Microsoft tdx.sys issue.
Minidump callstack is same.
- Juha
I haven’t try it…
I’m getting the “Out Of Date” error, but my system time and date are correct.
Is there anything else I can do to fix it ?
First are you using windows 7 beta as this is about windows 7 compatibility ?
But is your VPS the latest version (current version 090127-0) ?
If not do a manual update, right click the avast ‘a’ icon, select Updating, iAVS Update.
If it is up to date - try a repair of avast. Add Remove programs, select ‘avast! Anti-Virus,’ click the Change/Remove button and scroll down to Repair, click next and follow.
Yes, I am using the Windows 7 beta or I wouldn’t have posted in this thread :
However, I’m just about to try the rest of your advice as soon as I reboot back into W7, and I’ll let you know how I get on.
Thanks again
I went back into Vista to check something, then rebooted back to W7, and it seems to have fixed itself.
All seems OK (touches head in lieu of wood)
thanks
No problem, welcome to the forums.
I’ve tried ADNM, Avast Pro, and Avast Home on a box with a dual-core CPU, NVIDIA chipset, and either Windows 7 32-bit or 64-bit: I keep getting that tdx.sys issue regardless. However, my own home PC running x64 7 that was upgraded from Vista is running Avast Home flawlessly. I suspect 7 and the installers aren’t getting along: there’s already some workaround for some other Windows Installer issues that I applied on my home system for other programs; if I could find that again, I’d try it on the test box. For the moment, I’m trying an install in “Vista compatability mode” and see if that works…
???
Okay… I tried loading Vista x64 SP1, then upgrading to x64 7 with the minimum of updates: ADNM still BSOD; haven’t tried Home or Pro yet. I did want to throw this out there: on my home box, I was using the Service Pack 2 beta for Vista/2008 before upgrading to 7: maybe something in SP2 prevents this issue?
Okay… loaded Vista x64 SP1, then SP2 beta, loaded ADNM, then upgraded to 7 x64. BSOD still occurred, but this time I noticed an IRQ-based error. Went into BIOS and set to Plug-n-Play OS, then back into 7: networking quit at one point, but system did not BSOD. Trying some changes to services and DEP to see if that helps.
I give up. BSOD recurred after next boot. Guess we’ll have to wait for Microsoft on this one.
You can send me the corresponding minidumps (files from the \windows\minidump folder) for further analysis (by email - my address is in my forum profile).
Thanks
Vlk
Tried updating wireless, ethernet drivers, disabling one or other, avast, avg, kapersky - in all cases tdx.sys bsod if mapped drives in use.
For all these tools to fail suggests to me it’s an MS bug.