This warning is for real and cannot be resolved by uninstalling Avast 8.0.1482. Once Avast 8 is reinstalled the error returns. To make things more complexed, the warning only occurs on a system reboot. It does not show up on a cold restart. I did an uninstall and a clean reinstall of Avast 8 and the problems still exists.
My specs:
Windows 8 Pro with a clean install of Avast 8.0.1482 (virus definitions are current). I did a custom installed (deselected bloatware), selected minimum install, and am now running at default options. See image below for error information:
IMHO, this warning requires immediate attention because I’m also seeing others warnings at times (on reboot) that I do not see when I have Avast 8 uninstalled; however, to keep things simple, my guess is that this one is the root cause of any other errors/warnings that might be associated. I am really hoping that the Avast team will address this one immediately and I am here to do additional testing for them if necessary.
There is a program update 8.0.1483 available, now I personally don’t know if this is resolved in this build, but it makes sense to have the latest version and check again.
Hopefully someone with knowledge of aswTdi.sys, the avast! Network Shield Support, can pick up on this topic. It might help if you modify the topic Subject (from your first post) to include the aswTdi.sys, something like the subject I gave my post. This may draw a response from someone with knowledge if this driver.
Please check your logs in event viewer and if you are also getting this warning please keep this thread alive so the Avast team knows that this issue is real. However, if you are not getting this warning on a reboot, it would also be useful to know that as well.
I was under the impression that this was a forum to “help each other” so everytime I see someone in need, I try to help (if I think I can). AND, I have even created step-by-step tutorial responses if I were that well-versed in fixing a given situation. HOWEVER, this time I am in need of support with this issue, and, I can see that at least 202 “fellow forum members” have read this post and have decided not to contribute a simple reply as requested. All I’m asking for is a simple check of your Event Viewer logs to see if you are also getting this error on a reboot so please take the time to do a simple check and help out this old-timer.
Yep, I’m getting this Event Log warning and an error 6 under ‘Kernel-General’ about flushing a blank registry hive (WTF???), mentioned in other forum threads with similar titles…is anyone from avast! looking into all this???
Oh, and I can confirm they happen on every system boot, whether ‘cold’ or ‘warm’.
@ plsrepliThe number doesn’t mean unique views, everyone contributing (would clock up many views) and some will just be watching not necessarily out of they have this problem but general interest. I certainly haven’t seen this one in the forums.
The views can also be from guests, not members, who can’t post unless they register, there are currently 728 Guests and 41 Users so that will give you an idea of the ones who can’t post.
You have to remember that people are in different time zones and commitments, you can’t push them into doing things, especially if they aren’t experiencing any problem.
We are looking at entries relating to this particular Subject “Avast 8 aswTdi Driver Warnings in Event Viewer (Event ID 16001).” So similar in this regard isn’t going to be close enough.
You can start you own new topic, and someone can try to help but you would need to provide more information as in the first post of this topic.
Thanks for responding and I do have a response that encompasses all of your remarks in the previous two replies:
My intention was not to “push” anyone; however, I felt I had to state what I felt and is that so bad?
I don’t know what you mean by the word “similar” and what that refers to?
When you said “We are looking at” who is we? Avast I hope.
This is my thread and I don’t need any remedial assistance from others in this particular case because I am certain this is an Avast problem.
And finally, thank you for taking the time to confirm this problem.
In summary, I am done with this thread. So my plan, going forward, is to just watch this thread and test for an Avast fix within a reasonable timeframe.
As unless anyone with event log errors that aren’t the same then your topic gets hijacked by other posts unrelated to your problem and it can get very confused. I admit I was somewhat confused in the the fact that you started the topic, didn’t read back far enough.
We is in terms of the topic gathering information I don’t work for avast; I’m an avast user like yourself. So if anyone has exactly the same symptoms, this may help avast.
Yet I see nothing in your post that mentions any of those
I'm getting this Event Log warning and an error 6 under 'Kernel-General' about flushing a blank registry hive
Which is either lacking in detail or is not the same or the unrelated “error 6 under ‘Kernel-General’ about flushing a blank registry hive” is confusing the issue.
Please look again at the post by ‘wonderwrench’ - the second error I mention is immediately underneath that section.
The errors appear exactly as they do in Bill’s post - within 5 seconds of each other.
These 2 errors appear on every boot.
The third error in Bill’s list, ID 2 under Microsoft-Windows-Kernel-EventTracing (Session “” failed to start with the following error: 0xC000000D), appears occasionally (three times so far since installing avast! 8 Free), 15 minutes or so after startup or on initiating a system shutdown/reboot.
They never appeared before the installation of avast! 8 Free.
There is no confusion. They are related to avast! 8.
