![]() I need to exclude entire network drives as users maintain their own user profile there and unknown subfolders with temporary builds. As Avast Business clearly aims to attract business users (which contain developers often), temporarily created solutions with no fixed or switching locations on network paths are really no rarely imaginable scenario.Īs for us it is very annoying that DeepScreen exclusions are file based. Exclusions (doesn't matter if its DeepScreen or any other) are supposed to to work in an intuitive way (why would i want to exlude a file from the normal scan but not the DeepScreen or any other scan in general makes no sense at all - I'd demand that exclude means exclude. No explanation as to why it is only occurring on a handful of machines.Sad to see no official reaction on this yet. On the machine where I did the remove and reinstall this warning event has not reappeared. ![]() This filter has not been certified by Microsoft and may cause system instability." This driver traces back to Avast. The machines that have been experiencing the system shutdowns all seem to have a warning in Event Viewer\Windows Logs\System, Source AFD, Event ID 16001 that "A TDI filter (\\Driver\aswTdi) was detected. The memory dump generated by the system shutdown provides no definitive information on the cause. The frowny face of death cites a Critical Structure Corruption and an error code with one of the possible causes a driver corruption. Did an EPP remove and reinstall on another machine yesterday and so far no blue screens on it. I believe the rollback also rolled back an Avast update, so far no issues. Did a system restore on one machine that had an early December restore point before our Christmas break. Same problem here with a handful of machines in a domain situation starting on the first machine early in December, all desktops are using Avast Endpoint Protection Plus running Windows 8.1. So the trouble could be in bad system communication between Avast EPS and Windows 8.1 after last Avast OR Windows upgrade (around December 20). Note for Avast developers: I remember some fuzzy messages of Windows Action Center which blinked several times during my problematic period telling that "there is no antivir SW recognized". It seems that the clean reinstall of Avast EPS SOLVED my problem. Information update after clean reinstall of Avast EPS and half a day of testing: It looks like something is causing corruption of GDT.īSOD arrives offten shortly after waking up from sleepmode. Ģ6 crashes since Decemtill now (noon of Janury 2, 2016).īSOD bug code 0x109_0x03 pointing to ntoskrnl.exe file causing the problem. So, I have Windows 8.1 OS and Avast Endpoint Protection Suite. Now, I found this discussion and I think the trouble could be between OS and antivir system. I checked RAM, HDD and all drivers without any succes. Below is what's logged in the application log (I've removed the user and computer names) I suspect the PC goes to a blue screen when it receives its virus definition.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |