Author Topic: all Win7 BSOD  (Read 11783 times)

0 Members and 1 Guest are viewing this topic.

REDACTED

  • Guest
all Win7 BSOD
« on: March 20, 2017, 11:41:04 AM »
In the morning, a similar problem began on all computers windows 7.

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.

REDACTED

  • Guest
Re: all Win7 BSOD
« Reply #1 on: March 20, 2017, 11:45:27 AM »


Same here.

machines are dropping out as we speak.

disable leaves the devices wide open


Offline Asyn

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 76213
  • Urlaub/Vacation
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: all Win7 BSOD
« Reply #2 on: March 20, 2017, 11:45:38 AM »
I reported it for you. Cheers.
W8.1 [x64] - Avast PremSec 22.7.7366.BC [UI.713] - Firefox ESR 91.11 [NS/uBO/PB] - Thunderbird 91.11
Avast-Tools: Secure Browser 103.0 - Cleanup 22.2 - SecureLine 5.18 - DriverUpdater 22.2 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline Tim.W

  • Newbie
  • *
  • Posts: 1
Re: all Win7 BSOD
« Reply #3 on: March 20, 2017, 12:07:40 PM »
This is such a bloody mess, after the issues with broken updates less than 2 weeks ago. I've had a 50+ machine network falling over all morning over this.

REDACTED

  • Guest
Re: all Win7 BSOD
« Reply #4 on: March 20, 2017, 12:22:59 PM »
Same here, starting this morning, several Windows 7 computers with BSOD IRQL_NOT_LESS_OR_EQUAL 0x0000000a about 10 minutes after startup.

REDACTED

  • Guest
Re: all Win7 BSOD
« Reply #5 on: March 20, 2017, 12:26:46 PM »
thankfully it is not completely bolloxed up,
there is still time for the clients to get an update before they BSOD.

if it had been immediate, then the potential for non recovery would be massive.
no computer to DL an update.....

REDACTED

  • Guest
Re: all Win7 BSOD
« Reply #6 on: March 20, 2017, 12:53:27 PM »
Same issue for us this morning, BSOD every few minutes until Avast is uninstalled or Shields turned off.
It's not doing it to all clients (yet) but there seems to be no pattern to the ones which have the error.

Bug reported to Avast but no response yet.


Offline Martin Svoboda

  • Avast team
  • Full Member
  • *
  • Posts: 102
Re: all Win7 BSOD
« Reply #7 on: March 20, 2017, 12:56:34 PM »
Hi, which version of the client are you using?
Product manager | Avast Business | 🗺 Roadmap

REDACTED

  • Guest
Re: all Win7 BSOD
« Reply #8 on: March 20, 2017, 01:00:12 PM »
Hi, which version of the client are you using?
17.2.2517 (build17.2.3419.64)

REDACTED

  • Guest
Re: all Win7 BSOD
« Reply #9 on: March 20, 2017, 01:00:40 PM »
Good Morning All,

Same issue here on multiple machines,

Version 17.2 (2517), release date 03/01/2017

REDACTED

  • Guest
Re: all Win7 BSOD
« Reply #10 on: March 20, 2017, 01:14:04 PM »
Same situation here, multiple Windows 7 computers down here.  Build 17.2.3419.64.


REDACTED

  • Guest
Re: all Win7 BSOD
« Reply #11 on: March 20, 2017, 01:17:37 PM »
Same issue here on 60 machines

REDACTED

  • Guest
Re: all Win7 BSOD
« Reply #12 on: March 20, 2017, 01:25:31 PM »
Today is Monday. All faculty booting computers and getting a BSOD. New client 17.2.2517 has been installed on close to 2000
computers. for my school district. computers getting this all over the District. I have disconnected my 2 bench test computers running Windows 7. Boot into safe mode and removed Avast Business Client 17.2.2517.

Restarted computers 6 times, with no error's. Looks like big bug in version 17.2.2517. Please help how am I going to fix close to 2000 computers.

Offline Endt

  • Avast team
  • Full Member
  • *
  • Posts: 141
Re: all Win7 BSOD
« Reply #13 on: March 20, 2017, 01:29:21 PM »
We are currently investigating the root cause. The fix will be delivered ASAP. Will keep you posted.

REDACTED

  • Guest
Re: all Win7 BSOD
« Reply #14 on: March 20, 2017, 02:04:49 PM »
I performed clean install of version 17.2.2517 (Build 17.2.3419.64) I restarted the 2 bench computers 6 times.

There was no BSOD screen on the computers.

Could the cause be in the upgraded from version 12.3.2515?