I posted this the other day and I need an answer. We have 5 windows 8.1 PC that will blue screen randomly since the update to avast. The blue screen message says Critical_ Structure_Corruption.
Is anyone else experiencing this issue with 8.1 since the update?
What is the stop code (0x…) ?
What is the event log saying about it ?
Is there a (mini)dump created ?
Tried a (on one of the systems) :
Repair of avast ?
Clean installation of avast ?
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.
LOG NAME: APPLICATION
SOURCE: WINDOWS ERROR REPORTING
DATE: 12/22/2015 9:02:37 AM
EVENT ID: 1001
TASK CATEGORY: NONE
LEVEL: INFORMATION
KEYWORDS: CLASSIC
USER: N/A
COMPUTER:
DESCRIPTION:
FAULT BUCKET 0X109_3, TYPE 0
EVENT NAME: BLUESCREEN
RESPONSE: HTTP://WER.MICROSOFT.COM/RESPONSES/RESREDIR.ASPX?SID=22494&BUCKET=0X109_3&STATE=1&ID=561B9F07-485B-4BF2-AB71-0727ED0EEFF4
CAB ID: 561B9F07-485B-4BF2-AB71-0727ED0EEFF4
PROBLEM SIGNATURE:
P1: 109
P2: A3A01F5978DEB6C8
P3: B3B72BDFCB5EB48B
P4: FFFFF803EC749000
P5: 3
P6: 6_3_9600
P7: 0_0
P8: 256_1
P9:
P10:
ATTACHED FILES:
C:\WINDOWS\MINIDUMP\122215-25359-01.DMP
C:\USERS\USERNAME\APPDATA\LOCAL\TEMP\WER-195937-0.SYSDATA.XML
C:\WINDOWS\MEMORY.DMP
C:\USERS\USERNAME\APPDATA\LOCAL\TEMP\WER1C14.TMP.WERINTERNALMETADATA.XML
THESE FILES MAY BE AVAILABLE HERE:
C:\PROGRAMDATA\MICROSOFT\WINDOWS\WER\REPORTARCHIVE\KERNEL_109_998C574FB158EEC337A525D5F04A8CDBF132A5_00000000_CAB_0CB745D4
ANALYSIS SYMBOL:
RECHECKING FOR SOLUTION: 0
REPORT ID: 122215-25359-01
REPORT STATUS: 0
HASHED BUCKET:
EVENT XML:
1001
4
0
0X80000000000000
41128
APPLICATION
COMPUTERNAME
0X109_3
0
BLUESCREEN
HTTP://WER.MICROSOFT.COM/RESPONSES/RESREDIR.ASPX?SID=22494&BUCKET=0X109_3&STATE=1&ID=561B9F07-485B-4BF2-AB71-0727ED0EEFF4
561B9F07-485B-4BF2-AB71-0727ED0EEFF4
109
A3A01F5978DEB6C8
B3B72BDFCB5EB48B
FFFFF803EC749000
3
6_3_9600
0_0
256_1
C:\WINDOWS\MINIDUMP\122215-25359-01.DMP
C:\USERS\USERNAME\APPDATA\LOCAL\TEMP\WER-195937-0.SYSDATA.XML
C:\WINDOWS\MEMORY.DMP
C:\USERS\USERNAME\APPDATA\LOCAL\TEMP\WER1C14.TMP.WERINTERNALMETADATA.XML
C:\PROGRAMDATA\MICROSOFT\WINDOWS\WER\REPORTARCHIVE\KERNEL_109_998C574FB158EEC337A525D5F04A8CDBF132A5_00000000_CAB_0CB745D4
0
122215-25359-01
0
These PC’s were upgraded to the latest version of Avast.
You are the only one that I’ve seen reporting it.
This really is something for avast to look at (and help you with)
Several options that seem to be possible to me :
I would say try the chat first.
I just tried an uninstall and re-install of avast one pc to see what happens. If it bluescreens again, I’ll open an actual ticket with Avast support.
I figure that’ll be the first thing they’d want me to try.
Thanks
Same Problem here. Windows 8.1, new version of Endpoint Protection and several(!) customers. Please fix it NOW!
I have began receiving this error on multiple Windows 10 computers. I suspect Avast! is the culprit. I am uninstalling on several machines to see if it clears up.
One Japanese user seems to have the same issue.
Windows 8.1 x64, Bug check code 0x109.
Facing the same issue since December 20, 2015.
I checked RAM, HDD and all drivers without any succes.
Now, I found this discussion and I think the trouble could be between OS and antivir system.
Information update after clean reinstall of Avast EPS and half a day of testing:
It seems that the clean reinstall of Avast EPS SOLVED my problem. If not, I’ll be back to report…
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”. 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).
I have the same problem since before Christmas on 2 PCs, both running 8.1.
Same issue here! Come back from time off at Christmas to find all of our Win 8.1 laptops are BSODing every day. They were all updated to the latest version of Avast just before Christmas. I will try an uninstall and reinstall to see if it fixes things.
We also have an issue on all of our Win 7 PCs - they now report in the security centre that they have no AV installed (see this thread for the same problem: https://forum.avast.com/index.php?topic=180431.0).
It takes Avast months to release a Win10 compatible AV only to break all other OS versions!
For the blue screen issue, I uninstalled avast on the PC’s and reinstalling it by deploying it thru the console. SO far its been a week without bluescreens. Still no resolutions regarding the security center however.
We’re having the same issue as well with our surface pro’s running Win 8.1 Pro. They started around mid to late december. I’ve uninstalled end point protection from one system yesterday. Just waiting to see if it bs.
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. Did a system restore on one machine that had an early December restore point before our Christmas break. I believe the rollback also rolled back an Avast update, so far no issues. Did an EPP remove and reinstall on another machine yesterday and so far no blue screens on it.
The frowny face of death cites a Critical Structure Corruption and an error code with one of the possible causes a driver corruption. The memory dump generated by the system shutdown provides no definitive information on the cause. 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. This filter has not been certified by Microsoft and may cause system instability.” This driver traces back to Avast. On the machine where I did the remove and reinstall this warning event has not reappeared. No explanation as to why it is only occurring on a handful of machines.
I am also experiencing this issue with about 400 windows 8.1 machines on our domain. It seems that the uninstall and reinstall is the cleanest solution that I have found. Thanks again for the info, I currently have an open ticket regarding this matter I will let you know what Avast support says about the issue.
The problem has reappeared on the initial remove and reinstall test machine after three days, so remove and reinstall does not appear to be a viable solution.
Hey. Just wanted to give my 10 cents on this issue. We have been having the same problem on our campus. Came back from Christmas break and several people have reported their office machines having this issue. Surprisingly, I have updated my machine without any issues so far. All of the machines with problems have been Win 8.1. Has anyone heard of any work-arounds, solutions, or patch updates from Avast? Thanks in advance.
We have this issue on 9 out of 10 updated computers. So we stopped updating from console and locked update button in clients aplications to stop it from spreadding (60+ W8.1 computers).
It’s very annoying and only known solution to us so far is to reinstall program manualy. So far 3 days without BSOD on this machines, but it could be only temporary solution (in ref to sholt2).
Followed with security center bug on win 7 and 8 and no updates for this problems from Avast.
/sarkasm on
This is exactly how EP solutions should work, release update and let IT departments install everthing manually, because automatic updates don’t work how they should.
Glad we have only 400+ computers in all locations at least we have something to do. Great work Avast team.
/sarkasm off
>:( >:( >:(
Same problem on our DOMAIN for all PC’s WINDOWS 8.1 64Bit with the last avast endpoint protection client version 8.0.1606
blue screen at least one or two times for day with CRITICAL_STRUCTURE error message, uninstalling Avast the problem disappear
WAITING A RAPID SOLUTION FROM AVAST!!!
THANKS