0xc000007b when running boot scan

system · 2017-05-27T13:55:04.000Z

So I have several systems which have different hardware. I have not tried this on any systems that have the older BIOS, but ran into this on the systems that have the UEFI. This happened on Windows 10 and Windows 8.1, both pro and 64-bit systems. All systems have an SSD as drive C and some systems have the Sam 950 Pro as drive C.

I tried running the boot scan (after installing the specialized definitions) and set to scan at reboot. When I did it seems that the scan begins and then I get the error about my PC ran into a problem…error 0xc000007b. I went reading in the forums and found other similar situations, but the main reason was completely different than mine.

I don’t remember, but does this have to do with some setting in the UEFI? I may remember something about the new UEFI’s had security which needs to be turned off in order for boot scan programs to do their thing? I may be wrong though.

All systems have Avast version 17.4.22294 build (17.4.3482.0)

system · 2017-05-28T03:13:21.000Z

Anyone?

Asyn · 2017-05-28T07:12:49.000Z

Follow instructions: https://www.avast.com/faq.php?article=AVKB33#artTitle

igor0 · 2017-05-28T18:00:48.000Z

Do you mean the boot-time scan ended with error 0xc000007b (printed under the rest of the boot-time scanner output), or did you get a system crash?
If it’s the first case, could you please post/attach the file C:\ProgramData\AVAST Software\Avast\log\aswBoot.log?
Thanks.

Announcements