Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: AspireAcademyTrust on March 20, 2017, 11:01:06 AM
-
Anybody else experiencing BSOD this morning on windows 7 devices?
Ive just disabled all shields via the admin dashboard which seems to have fixed the issue for now, but we have had it reported to us from several different sites with different hardware.
-
Same here.
Something with last micro-update build 17.2.3419.64
-
Yes, 12 machines affected here on 4 different sites.
Different hardware but common denominator is that the ones I've seen so far are all 32bit.
Removing Avast! In safe mode solves it for now.
-
Hi,
We're also experiencing this on our 32Bit Windows 7 machines.
BSOD 0x0000000A
-
Yes thinking about it the ones which have reported are likely to be our older win 7 32bit installs. Great fun for a Monday morning..
-
Great fun for a Monday morning..
Tell me about it!
-
Guys, you're in the wrong forum section here.
-> https://forum.avast.com/index.php?board=77.0
-
Problem is with Avast consumer products and Avast for Business too.
-
Problem is with Avast consumer products and Avast for Business too.
OK, I see.
-
All my clients with windows 7 32 bit blue screen every 2 minutes.
-
All my clients with windows 7 32 bit blue screen every 2 minutes.
I already reported it to the devs.
-
Same problem here with PCs running 32bit Windows 7 Pro
-
All my clients with windows 7 32 bit blue screen every 2 minutes.
Disabling the shields seems (not ideal!) to stop the blue screens.
Trying to see if I can identify which one is causing it. I've got my money on the behaviour shield.
-
All my clients with windows 7 32 bit blue screen every 2 minutes.
Disabling the shields seems (not ideal!) to stop the blue screens.
Trying to see if I can identify which one is causing it. I've got my money on the behaviour shield.
Disabling the shields wasn't enough for me. I have had to completely uninstall avast on our 32bit PCs. We are using avast for business.
-
Same here.
Windows 7 x86.
Avast Free 17.2.2288 (build 17.2.3419.64)
-
It's happening with only Win7 32 bit - both Free and Business versions. Resolution for now - uninstall the software.
-
I've just joined up to confirm this, seven machines now BSODing if Avast is running. Stopping the shields or the Avast service cures the BSOD.
Needs a fix ASAP.
-
First there was the problem of AVAST and AutoCAD 2011 (Win 7 (resolved through the key in the registry) and Win XP (is not solved)) after the update, after 2 days BSOD on 3 computers Win 7 32 bit. When will you fix it? >:(
P.S. Earlier Avast worked a year without problems. Better to test before release of updates
-
Had a Windows 7 32Bit machine running for about 30 minutes with just the behaviour shield disabled.
Previously they were BSOD every 10 minutes or so.
-
Experiencing the same on Windows 7.
I find that it shows bs not long after running a program.
Is this down to an update to the program this morning? as mine still shows same version.
-
Experiencing the same on Windows 7.
I find that it shows bs not long after running a program.
Is this down to an update to the program this morning? as mine still shows same version.
Does disabling the behaviour shield fix the BSOD?
-
I've yet to try disabling anything in avast, hope it's possible without a Bluescreen appearing, can this be done in safe mode?
-
I've yet to try disabling anything in avast, hope it's possible without a Bluescreen appearing, can this be done in safe mode?
No need to go in Safe Mode.
Try this :
Avast UI > Settings > Components > Behaviour Shield > [untick] Behaviour Shield and disable it until next restart...
Does that solve the BSODs?
-
idem for me
avast pro on 12 computer (win7), on 6 sites customers differents, blue screen, HELPPPPPPPPP
-
Same here, Windows 7 Professional 32bit SP1 Spanish. Uninstalling.
-
We are currently investigating the root cause. The fix will be delivered ASAP. Will keep you posted.
-
Does disabling the behaviour shield fix the BSOD?
I've had to disable all shields again. It also seems that changes to the service state (so enabling or disabling a shield) can trigger a blue screen. Had several blue screen when I pushed out an update through the cloud interface!
-
Does disabling the behaviour shield fix the BSOD?
I've had to disable all shields again. It also seems that changes to the service state (so enabling or disabling a shield) can trigger a blue screen. Had several blue screen when I pushed out an update through the cloud interface!
Don't disable all of them, just the file shield temporarily.
-
The decision on 03/20/2017 15.21 (UTC + 03.00): Disabling AVAST forever in the tray on Windows 7 32 bit ONLY. Wait for program update
-
We are currently investigating the root cause. The fix will be delivered ASAP. Will keep you posted.
What do you advise in the meantime and will the update fix be automatic?
-
We are currently investigating the root cause. The fix will be delivered ASAP. Will keep you posted.
Please write here when you find a solution so that you can start AVAST on computers and how to update so that there is no BSOD in steps
-
Disable FileSystem shield is a temporary workaround. Fix will be delivered by the next Virus Definition Update. I will post the "fixed" virus definition version number when released.
-
Ive had to keep all shields turned off since this morning. Not had any reports of any BSOD since. Keen for a patch soon! :o
-
Ive had to keep all shields turned off since this morning. Not had any reports of any BSOD since. Keen for a patch soon! :o
Is this the same as the file system shield? If not can this be disabled from the system tray?
It's ok, I found it under components.
-
Thanks, disabling FileSystem shield and waiting for the definition update.
Disable FileSystem shield is a temporary workaround. Fix will be delivered by the next Virus Definition Update. I will post the "fixed" virus definition version number when released.
-
5 machines presented blue screen in Windows 7 32bits, expecting updating of Avast, for now I disabled it.
Rgs
Win
Brazil/Brasil
-
Same here! 3 Machines down. Win 7 32bit.
Fileshield disabled for now.
-
32 bit Blue Screen
64 bit without Blue Screen
-
Same here, all machines with Windows 7 32bit have BSOD
-
The fix is going to be present in the next virus definition update. Estimated time of delivery is CET 4pm (in about 2 hours from now). Will keep you posted.
-
Have you a beta tester?
-
The fix is going to be present in the next virus definition update. Estimated time of delivery is CET 4pm (in about 2 hours from now). Will keep you posted.
May I ask, when did the update that caused this begin as it was fine yesterday evening?
-
Sticky post with latest updates: https://forum.avast.com/index.php?topic=199176.0
@nightshade:
It was caused by a virus definition update, which was released this morning.
-
Sticky post with latest updates: https://forum.avast.com/index.php?topic=199176.0
@nightshade:
It was caused by a virus definition update, which was released this morning.
@petr.chytil
Thanks for confirming.
-
Thanks for the detail Petr!
-
For those of you with Avast Business - go into your web panel -> Network -> Settings -> Go to the Template -> Turn off components
This has resolved it across the board for me. I was on fire, the fire is put out for now. I plan to re-enable the shields after I confirm the update is applied.
-
I just wanted to confirm we are seeing this issue on 64-bit Windows 7 machines as well. I do not believe this to be exclusive to 32-bit platforms.
-
I just wanted to confirm we are seeing this issue on 64-bit Windows 7 machines as well. I do not believe this to be exclusive to 32-bit platforms.
+1 I am as well. I am not seeing this on any Windows 10 workstations.
-
Running Win 7 Pro SP1, this machine was just powered up about 50 minutes ago. No BSOD yet. And, VPS 170320-01 has been released just now.
-
Running Win 7 Pro SP1, this machine was just powered up about 50 minutes ago. No BSOD yet. And, VPS 170320-01 has been released just now.
Seems you're lucky. 8)
-
Running Win 7 Pro SP1, this machine was just powered up about 50 minutes ago. No BSOD yet. And, VPS 170320-01 has been released just now.
Seems you're lucky. 8)
Are you saying you've updated to the latest definition and you're still receiving the BSOD?
-
Running Win 7 Pro SP1, this machine was just powered up about 50 minutes ago. No BSOD yet. And, VPS 170320-01 has been released just now.
Seems you're lucky. 8)
Are you saying you've updated to the latest definition and you're still receiving the BSOD?
Nope, he says the opposite.
-
Virus definition version 170320-1 has not been released yet.
-
Virus definition version 170320-1 has not been released yet.
Erm, @Gopher... ??? :-\
-
Virus definition version 170320-1 has not been released yet.
5pm is quoted, which timezone would this be referring to?
-
Virus definition version 170320-1 has not been released yet.
5pm is quoted, which timezone would this be referring to?
CET
-
Virus definition version 170320-1 has not been released yet.
It's on my machine, with 4 definitions in it's folder. How is this explained, if it wasn't released?
I see, that's only the stream. Sorry.
-
Should be officially released then in just over 30 mins.
-
I've uninstalled avast and installed avg and I'm still getting the crashes :-\
-
I've uninstalled avast and installed avg and I'm still getting the crashes :-\
They both use the same VPS.
-
If i unistall avast the problem disappear?
-
Virus definition update 170320-1 is available.
Manually update via :
Avast - Settings - Update - Virus Definitions - Update - ok - ok.
BOSD Fixed with 170320-1.
-
I've uninstalled avast and installed avg and I'm still getting the crashes :-\
They both use the same VPS.
So I take it the AVG forums are filled with this?
-
I pushed it out as a task on the cloud console to update the virus definitions.
-
170320-1 is released, see: https://forum.avast.com/index.php?topic=199176.msg1379208#msg1379208
-
170320-1 is released, see: https://forum.avast.com/index.php?topic=199176.msg1379208#msg1379208
Won't let me update as it brings up the BSOD when executed.
-
170320-1 is released, see: https://forum.avast.com/index.php?topic=199176.msg1379208#msg1379208
Won't let me update as it brings up the BSOD when executed.
Disable all the shields and try.
-
170320-1 is released, see: https://forum.avast.com/index.php?topic=199176.msg1379208#msg1379208
Won't let me update as it brings up the BSOD when executed.
Disable all the shields and try.
How can I do that if it won't open?
-
170320-1 is released, see: https://forum.avast.com/index.php?topic=199176.msg1379208#msg1379208
Won't let me update as it brings up the BSOD when executed.
Disable all the shields and try.
How can I do that if it won't open?
Then restart the pc and go to safe mode(F8) with network and do that.
-
170320-1 is released, see: https://forum.avast.com/index.php?topic=199176.msg1379208#msg1379208
Won't let me update as it brings up the BSOD when executed.
Disable all the shields and try.
How can I do that if it won't open?
Then restart the pc and go to safe mode(F8) with network and do that.
It will not open in safemode. Brings up UI FAILED TO LOAD. Green options below don't help.
-
The fix is going to be present in the next virus definition update. Estimated time of delivery is CET 4pm (in about 2 hours from now). Will keep you posted.
Time for you to get a new QA manager & test setup.
This is not the first time avast has massively screwed its customer base over.
-
170320-1 is released, see: https://forum.avast.com/index.php?topic=199176.msg1379208#msg1379208
AVAST works 12 hours on Windows 7 32 bit all right. Thank you ! :)