Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: wonderwrench on March 04, 2013, 03:19:39 PM
-
Since switching from Avast 7 Free to Avast 8 Free I'm getting event log errors related to aswTdi.sys. I also have several other event log errors I have never seen on this PC before. These other errors have no direct correlation to Avast but they do not happen with Avast 8 Free is not installed. Originally I upgraded from 7 to 8. Once I found the aswTdi.sys errors I uninstalled Avast though Programs and Features then rebooted. Then booted to safe mode and ran aswclear for Avast 8 rebooted again into safe mode and ran aswclear for Avast 7. After several normal boots no aswTdi.sys errors were logged in the event logs so I did a clean install of 8.0.1482 Free followed by a reboot. The same aswTdi.sys errors are back. As a test I installed Avast 8 Free on my HTPC also running W8 64bit and get the same error in the event logs. Is anyone else seeing this error? Both PC's seem to run fine but I hate event log errors.
aswTdi.sys error log
Log Name: System
Source: AFD
Date: 3/4/2013 7:08:44 AM
Event ID: 16001
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: SMOKE
Description:
The description for Event ID 16001 from source AFD cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Afd
\Driver\aswTdi
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="AFD" />
<EventID Qualifiers="32768">16001</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-03-04T13:08:44.759526700Z" />
<EventRecordID>164050</EventRecordID>
<Channel>System</Channel>
<Computer>SMOKE</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Afd</Data>
<Data>\Driver\aswTdi</Data>
<Binary>000000000200300000000000813E0080000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
Other errors in the event logs that do not exist without Avast 8 Free installed
Log Name: System
Source: Microsoft-Windows-Kernel-General
Date: 3/4/2013 7:08:39 AM
Event ID: 6
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: SMOKE
Description:
An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): ''.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-General" Guid="{A68CA8B7-004F-D7B6-A698-07E2DE0F1F5D}" />
<EventID>6</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-03-04T13:08:39.673880000Z" />
<EventRecordID>164037</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>SMOKE</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="FinalStatus">0xc000014d</Data>
<Data Name="ExtraStringLength">0</Data>
<Data Name="ExtraString">
</Data>
</EventData>
</Event>
and
Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 3/3/2013 9:22:23 PM
Event ID: 2
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: SMOKE
Description:
Session "" failed to start with the following error: 0xC000000D
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
<EventID>2</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2013-03-04T03:22:23.264362900Z" />
<EventRecordID>14</EventRecordID>
<Correlation />
<Execution ProcessID="356" ThreadID="4648" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>SMOKE</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">
</Data>
<Data Name="FileName">
</Data>
<Data Name="ErrorCode">3221225485</Data>
<Data Name="LoggingMode">276824069</Data>
</EventData>
</Event>
My system specs are in my sig
Thanks
Bill
-
Hi Bill
I'm having exactly the same issues, clean install of v8 Free on Win8 Pro with MC.
I also had the aswVmm issue, partially fixed by the patched file supplied in these forums.
However, my Core i5 2500K is still apparently 'Not Capable' of Virtualisation - totally false!
An explanation and time-to-fix from the powers-that-be would be appreciated.
This really is an excellent product; these issues are taking the 'shine' off it somewhat.
Regards
Ian
-
Same issue here. Looked back in my logs and see it long before I upgraded to Avast Internet Security 8 from version 7. Does not seem to be affecting performance or stability, but I like to eliminate errors and warnings in event log to the extent possible.
-
Well at least its not just me. I hope more people will look into this and report if they are getting these errors also. Better yet it would be nice to get a response from an Avast employee.
Bill
-
@Avast! gurus
Can we PLEASE get an answer to this issue?
Why are event log errors being raised? Performance/stability seems unaffected but is immaterial to the fact that spurious errors should NOT be appearing in this way.
Thanks
-
I just noticed these as well. They just started with Avast 8. See my post here:
http://forum.avast.com/index.php?PHPSESSID=8surp4ktfbe36aipd06c8u7h82&topic=117112.0 (http://forum.avast.com/index.php?PHPSESSID=8surp4ktfbe36aipd06c8u7h82&topic=117112.0)
-
Just did a clean install of 8.0.1483 and problem still exists.
-
Same error here. W8 Pro 64bit clean install (both Windows and Avast).
-
Same error here. W8 Pro 64bit clean install (both Windows and Avast).
Generating and sending a Support Package
https://support.avast.com/index.php?languageid=1&group=eng&_m=knowledgebase&_a=viewarticle&kbarticleid=1061
-
Also have the same error on 2 separate systems. Started happening after upgrade from Window 7 to Windows 8 Pro x64. This happened while on Avast 7 and error persists with Avast 8.
Have tried clean install of Avast but error remains.
-
Windows XP: Click Start> Control Panel> Programs> avast> Repair
Windows Vista / Windows 7/8: Click Start> Control Panel> Programs> Programs and Features> avast> Repair
-
I am getting the same errors. Updated from avast free 7 to 8. I'm running windows 8 x64 enterprise. There hasn't been any activity in this post for 2 weeks? Has a solution been posted?
-
I am getting the same errors. Updated from avast free 7 to 8. I'm running windows 8 x64 enterprise. There hasn't been any activity in this post for 2 weeks? Has a solution been posted?
I see to be working on some update. I do not know tell you about when will exit ?
-
any help would be greatly appreciated. thank you
-
I have tried repairing from control panel > programs and features, and have done a clean install and still get the same errors. Any word on a fix, patch, update, work around, ANYthing?
-
I recently switched from MSE to avast! because of it's consistent high results in most anti-virus lab's test results however, like the users here, since installing it my system has started freezing with Event ID 6. If this can't be patched then I'll have to look elsewhere as it is not acceptable. I have the latest version and have run the repair but the problem persists. I'm running Windows 8 Pro. Please advise.
-
Windows 8 doesn't use MSE, it come pre-installed with Defender which in win8 is a full anti-virus/spyware, installing avast should disable defender, have you checked that this is so?
As you can see from my signature avast 8.0.1489 works perfectly well on win8 systems
-
Yes..I meant Defender. As this thread shows, there is definitely an issue here. It's no coincidence that my system started freezing only after installing avast!
-
Yes..I meant Defender. As this thread shows, there is definitely an issue here. It's no coincidence that my system started freezing only after installing avast!
The issues discussed within this thread are relating to an older version of avast and the aswTdi.sys which is different from your event ID 6 problem which is also a good reason as to why we ask people to create there own topics and not hijack someone elses and get confused with different problems.
-
Hardly hijacking when I'm reporting a similar problem to the OP. In the first post he says:
Other errors in the event logs that do not exist without Avast 8 Free installed
Log Name: System
Source: Microsoft-Windows-Kernel-General
Date: 3/4/2013 7:08:39 AM
Event ID: 6
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: SMOKE
Description:
An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): ''.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-General" Guid="{A68CA8B7-004F-D7B6-A698-07E2DE0F1F5D}" />
<EventID>6</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-03-04T13:08:39.673880000Z" />
<EventRecordID>164037</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>SMOKE</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="FinalStatus">0xc000014d</Data>
<Data Name="ExtraStringLength">0</Data>
<Data Name="ExtraString">
</Data>
</EventData>
</Event>
which is exactly the same problem I am having.
-
@tw33k
Avast Software will not fix this in Avast 8. Source:
Hi Broken Hope, you are right, this will not be solved as it brings no real problems. TDI drivers are completely unsupported by Windows 8 operating system, and we are going to remove aswtdi from avast in avast9.
edit: will be removed on Windows8 installations. Hence my question: has anyone seen this log entry on any other OS than Windows8? If so, we might start wanting to solve it.
(http://forum.avast.com/index.php?topic=120426.msg934796#msg934796 (http://forum.avast.com/index.php?topic=120426.msg934796#msg934796))
EDIT: That log entry (posted by tw33k) might not related to aswTdi.sys, but however... log entry about aswTdi.sys is in OP's post.
-
I had this issue with Windows 7 Ultimate 32 bit and Avast 8 Free.
You need to go to safe mode and issue a command to delete the aswtdi service. If you don't go to safe mode avast will prevent you to delete the service.
Start cmd as an administrator. Issue the following command:
sc delete aswtdi
Enjoy.
I have tested it with Windows 7 32 bit, I don't know if it will work with Windows 8.
Disclaimer: Use at your own risk. The risk is fully of the user.