Author Topic: BLUE SCREEN WINDOWS 8.1  (Read 33246 times)

0 Members and 1 Guest are viewing this topic.

Offline Bassmaster

  • Jr. Member
  • **
  • Posts: 83
BLUE SCREEN WINDOWS 8.1
« on: December 22, 2015, 03:48:53 PM »
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?


Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31307
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: BLUE SCREEN WINDOWS 8.1
« Reply #1 on: December 22, 2015, 04:02:14 PM »
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 ?

Offline Bassmaster

  • Jr. Member
  • **
  • Posts: 83
Re: BLUE SCREEN WINDOWS 8.1
« Reply #2 on: December 22, 2015, 05:13:56 PM »
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://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:
<EVENT XMLNS="http://HTTP://SCHEMAS.MICROSOFT.COM/WIN/2004/08/EVENTS/EVENT">
  <SYSTEM>
    <PROVIDER NAME="WINDOWS ERROR REPORTING" />
    <EVENTID QUALIFIERS="0">1001</EVENTID>
    <LEVEL>4</LEVEL>
    <TASK>0</TASK>
    <KEYWORDS>0X80000000000000</KEYWORDS>
    <TIMECREATED SYSTEMTIME="2015-12-22T14:02:37.000000000Z" />
    <EVENTRECORDID>41128</EVENTRECORDID>
    <CHANNEL>APPLICATION</CHANNEL>
    <COMPUTER>COMPUTERNAME</COMPUTER>
    <SECURITY />
  </SYSTEM>
  <EVENTDATA>
    <DATA>0X109_3</DATA>
    <DATA>0</DATA>
    <DATA>BLUESCREEN</DATA>
    <DATA>http://HTTP://WER.MICROSOFT.COM/RESPONSES/RESREDIR.ASPX?SID=22494&AMP;BUCKET=0X109_3&AMP;STATE=1&AMP;ID=561B9F07-485B-4BF2-AB71-0727ED0EEFF4</DATA>
    <DATA>561B9F07-485B-4BF2-AB71-0727ED0EEFF4</DATA>
    <DATA>109</DATA>
    <DATA>A3A01F5978DEB6C8</DATA>
    <DATA>B3B72BDFCB5EB48B</DATA>
    <DATA>FFFFF803EC749000</DATA>
    <DATA>3</DATA>
    <DATA>6_3_9600</DATA>
    <DATA>0_0</DATA>
    <DATA>256_1</DATA>
    <DATA>
    </DATA>
    <DATA>
    </DATA>
    <DATA>
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</DATA>
    <DATA>C:\PROGRAMDATA\MICROSOFT\WINDOWS\WER\REPORTARCHIVE\KERNEL_109_998C574FB158EEC337A525D5F04A8CDBF132A5_00000000_CAB_0CB745D4</DATA>
    <DATA>
    </DATA>
    <DATA>0</DATA>
    <DATA>122215-25359-01</DATA>
    <DATA>0</DATA>
    <DATA>
    </DATA>
  </EVENTDATA>
</EVENT>

Offline Bassmaster

  • Jr. Member
  • **
  • Posts: 83
Re: BLUE SCREEN WINDOWS 8.1
« Reply #3 on: December 22, 2015, 05:16:03 PM »
These PC's were upgraded to the latest version of Avast. 

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31307
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: BLUE SCREEN WINDOWS 8.1
« Reply #4 on: December 22, 2015, 07:03:05 PM »
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 :
- Use the contact/support instructions provided in the mail that you received when purchasing the product.
- Login at https://business.avast.com and start a chat
- Submit a ticket

I would say try the chat first.

Offline Bassmaster

  • Jr. Member
  • **
  • Posts: 83
Re: BLUE SCREEN WINDOWS 8.1
« Reply #5 on: December 22, 2015, 08:21:42 PM »
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

Offline gmeiner

  • Newbie
  • *
  • Posts: 6
Re: BLUE SCREEN WINDOWS 8.1
« Reply #6 on: December 23, 2015, 08:21:25 AM »
Same Problem here. Windows 8.1, new version of Endpoint Protection and several(!) customers. Please fix it NOW!

Offline Mithandir

  • Newbie
  • *
  • Posts: 2
Re: BLUE SCREEN WINDOWS 8.1
« Reply #7 on: December 23, 2015, 03:48:25 PM »
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.
« Last Edit: December 23, 2015, 04:01:55 PM by Mithandir »

Online NON

  • Japanese User
  • Avast Überevangelist
  • Ultra Poster
  • *****
  • Posts: 4745
  • Whatever will be, will be.
Re: BLUE SCREEN WINDOWS 8.1
« Reply #8 on: December 25, 2015, 03:29:55 PM »
One Japanese user seems to have the same issue.

Windows 8.1 x64, Bug check code 0x109.
Main: Win10 Pro 20H2 64bit / Core i5-7400 3.0GHz / 16GB RAM / Avast 21 Premier Beta / Comodo Firewall 12 (testing again)
Mobile: Win10 Pro 20H2 32bit, Vista SP2 32bit / Core 2 Duo SU9300 1.2GHz / 4GB RAM / Avast 20 Free / Windows Firewall Control

Avast の設定について解説しています。よろしければご覧ください。

Offline vitar

  • Newbie
  • *
  • Posts: 1
Re: BLUE SCREEN WINDOWS 8.1
« Reply #9 on: January 02, 2016, 12:48:28 PM »
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.

So, I have Windows 8.1 OS and Avast Endpoint Protection Suite 8.0.1606.
26 crashes since December 20, 2015 till now (noon of Janury 2, 2016).
Always the same symptoms:
BSOD bug code 0x109_0x03 pointing to ntoskrnl.exe file causing the problem.
It looks like something is causing corruption of GDT.
BSOD arrives offten shortly after waking up from sleepmode.
-----------------------------------------------------------------------------------------------------------
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).
« Last Edit: January 02, 2016, 08:19:31 PM by vitar »

Offline paulmarzifan

  • Newbie
  • *
  • Posts: 1
Re: BLUE SCREEN WINDOWS 8.1
« Reply #10 on: January 03, 2016, 11:51:35 AM »
I have the same problem since before Christmas on 2 PCs, both running 8.1.

Offline mcoleran

  • Newbie
  • *
  • Posts: 10
Re: BLUE SCREEN WINDOWS 8.1
« Reply #11 on: January 04, 2016, 02:09:59 PM »
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!

Offline Bassmaster

  • Jr. Member
  • **
  • Posts: 83
Re: BLUE SCREEN WINDOWS 8.1
« Reply #12 on: January 04, 2016, 04:31:31 PM »
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. 

Offline dgtroubleshoot

  • Newbie
  • *
  • Posts: 1
Re: BLUE SCREEN WINDOWS 8.1
« Reply #13 on: January 06, 2016, 03:26:06 PM »
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.
« Last Edit: January 06, 2016, 03:36:27 PM by david.gonichie »

Offline sholt2

  • Newbie
  • *
  • Posts: 3
Re: BLUE SCREEN WINDOWS 8.1
« Reply #14 on: January 06, 2016, 06:43:45 PM »
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.
« Last Edit: January 06, 2016, 07:08:05 PM by sholt2 »