Avast BSOD Win 7

nightshade · 2017-03-20T13:33:29.000Z

petr.chytil post:43:

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.

Mac · 2017-03-20T13:42:59.000Z

Thanks for the detail Petr!

JoshP · 2017-03-20T14:36:29.000Z

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.

system · 2017-03-20T14:47:52.000Z

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.

JoshP · 2017-03-20T14:50:39.000Z

Chip2 post:47:

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.

GopherJohn · 2017-03-20T15:05:34.000Z

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.

Asyn · 2017-03-20T15:09:46.000Z

Gopher John post:49:

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)

nightshade · 2017-03-20T15:11:43.000Z

Asyn post:50:

Gopher John post:49:

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?

Asyn · 2017-03-20T15:14:21.000Z

nightshade post:51:

Asyn post:50:

Gopher John post:49:

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.

chytil · 2017-03-20T15:15:08.000Z

Virus definition version 170320-1 has not been released yet.

Asyn · 2017-03-20T15:17:34.000Z

petr.chytil post:53:

Virus definition version 170320-1 has not been released yet.

Erm, @Gopher… ??? :-\

nightshade · 2017-03-20T15:19:01.000Z

petr.chytil post:53:

Virus definition version 170320-1 has not been released yet.

5pm is quoted, which timezone would this be referring to?

Asyn · 2017-03-20T15:20:41.000Z

nightshade post:55:

petr.chytil post:53:

Virus definition version 170320-1 has not been released yet.

5pm is quoted, which timezone would this be referring to?

CET

GopherJohn · 2017-03-20T15:22:02.000Z

petr.chytil post:53:

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.

nightshade · 2017-03-20T15:24:56.000Z

Should be officially released then in just over 30 mins.

system · 2017-03-20T15:53:07.000Z

I’ve uninstalled avast and installed avg and I’m still getting the crashes :-\

Alikhan · 2017-03-20T15:54:35.000Z

stephen209 post:59:

I’ve uninstalled avast and installed avg and I’m still getting the crashes :-\

They both use the same VPS.

system · 2017-03-20T16:42:03.000Z

If i unistall avast the problem disappear?

BeSecure · 2017-03-20T16:42:33.000Z

Virus definition update 170320-1 is available.
Manually update via :

Avast - Settings - Update - Virus Definitions - Update - ok - ok.

BOSD Fixed with 170320-1.

nightshade · 2017-03-20T16:46:20.000Z

Alikhan post:60:

stephen209 post:59:

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?

Announcements