AVAST 17.1.2286 BSOD on win7-login screen

Avast Free Antivirus / Premium Security
1

Unfortunately this version consistently gives BSOD on the windows login screen.
Had to roll back to the previous version in safe mode.

(Running Win7Pro with almost all updates installed, including quite a few optional ones - I’m thinking maybe one of the optional updates could have created a compatibility issue.)
(My system is very stable; uptime is usually weeks between restarts - which are due to updates only.)

I’m a programmer myself, so I know this kind of stuff happens sometimes.
Just posting it here to let others know you can fix this by booting into safe-mode in case you happen to be unlucky like me.

(Asus Z97-A, i5 4690K, GTX970, SB X-Fi)

[b]EDIT: In the meantime, the fix reported here works: https://forum.avast.com/index.php?topic=196445.msg1364852#msg1364852[/b]
(Go to Avast Settings → Troubleshooting and disable Hardware assisted virtualization.)

2

@Ben B: can you please send me the latest minidump file from \Windows\Minidump folder to kurtin@avast.com? Thanks.

3

@pk: Done!
Subject line is “Minidump BSOD AVAST 17.1.2286” from guwdo*****.kra****@gmail.com

Let me know if you need anything else.

4

got it, thanks,
can you please compress \windows\memory.dmp (7zip would be best) and upload it somewhere? e.g. avast ftp instructions: https://www.avast.com/faq.php?article=AVKB160

5

Well… that would be a bit more of a hassle…

It is set to automatically delete the memory dump if I have less than 25GB of free space on c:
…and I have less than 25GB free on c: so I would have to reinstall and crash again.

Do you absolutely need it?

(Edit: I’ve changed my memory-dump save location to another drive now, something I should have fixed a long time ago…)

6

well, it’s not necessary, we just wanted to be sure it’s caused by nested paging feature in our HW assisted-virtualization driver
it’s up to you

changing pagedump location to different volume than C won’t help, because crash dump doesn’t support it

7

@pk: Reinstalled, crashed, got the memory-dump. I’ll let you know once I’ve uploaded it. (103MB compressed)

@Eddy: I got this http://imgur.com/a/sDpke

8

c00l, thanks a lot!

9

Thanks for the screenshot.

I leave the rest to PK (and his team).

10

That is not true, I just dumped it on my 4TB T: drive :slight_smile:

For it to work you either need to have a large page-file on c:
or no page-file on c: (deactivated) and a large page-file on another drive.
Having a small page-file on c: will cause it to not work (even if you have a large page-file on another drive… just windows-things ::slight_smile: ).

Although I’m talking about a kernel-dump (~800mb), a full dump still requires a ram-sized page-file on c: if I’m not mistaken.

(I’m fairly sure you are correct when it comes to winXP though.)

(EDIT: Sorry for the delay in upload - multitasking some other things…)

11

@pk: Ok, uploaded!
(Repacked with some more info, including new mini-dump, so filesize grew to 108MB)
File-name is my email… same as before.
Used the “virus” password, even though it’s not a virus, but thought maybe you have some filters on such things.

EDIT: yes I have vmWare installed…
…and disabling Hardware assisted virtualization did indeed prevent the BSOD, just as reported by helmar74
https://forum.avast.com/index.php?topic=196445.msg1364852#msg1364852

12

Same problem me too with same condition (VMware installed). Solved following the above link instruction. I spent hours to solve this sever issue; I am thinking to leave Avast, each new version it becomes always more invasive.

Regards
Bix

13

Malware also becomes more invasive with each new version. :wink: