Version 2016.11.2.2260 and KERNEL_SECURITY_CHECK_FAILURE

[Gandalf1369]

Just updated via the GUI and got the Windows 10 blue screen with the error: KERNEL_SECURITY_CHECK_FAILURE.  Was not able to get to the desktop.  The only way to finally boot the computer properly was to boot into safe mode and delete Avast Free altogether.

Here's are the details:

1. Operation System: Windows 10 Pro fully updated (16GB memory - 64bit)
2. Avast version: Avast Free running only the shields, software updater, network scanner, and virtualization.
3. After updating through the GUI tried rebooting and got blue-screened.
4. Booted into safe mode and changed avast to ONLY use shields, software updater, and network scanner.
5. Still blue screened so back to safe mode and total uninstall of Avast free.
6. Booted normally so tried a custom install with ONLY shields, software updater, and network scanner.
7. Still blue screened after reboot.

Checked all of the mini-dumps and memory dumps with "WhoCrashed.exe" and in all cases the error was:

This was probably caused by the following module: aswvmm.sys (aswVmm+0x78C7)
Bugcheck code: 0x139 (0x4, 0xFFFFD001DE8F4BA0, 0xFFFFD001DE8F4AF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE

Right now I'm just running Windows Defender until I can hopefully get this figured out.

Anybody have any ideas??

[Asyn]

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

[Gandalf1369]

Thanks Asyn.  Submitted to support.  We'll see what happens . . . . .

[Asyn]

You're welcome.

[REDACTED]

Thanks a lot for submitting the problem to the support, Gandalf1369, I have the very same problem with Avast Internet Security.
And thanks for the advice, Asyn. I'm going to submit it too.

[Asyn]

And thanks for the advice, Asyn. I'm going to submit it too.

You're welcome, please do so.

[Avast-TS]

Hi,

there is  bug in aswVmm.sys. Only some AMD cpus seems to be affected. Will be fixed by micro update ASAP.  As workaround , please uncheck "Enable HW assisted virtualization" in troubleshooting settings. Sorry for your troubles.

[Gandalf1369]

Hi,

there is  bug in aswVmm.sys. Only some AMD cpus seems to be affected. Will be fixed by micro update ASAP.  As workaround , please uncheck "Enable HW assisted virtualization" in troubleshooting settings. Sorry for your troubles.

Thanks for the update.  Your instructions to "uncheck "Enable HW assisted virtualization" in troubleshooting settings" is not going to be doable (at least for me) since I cannot even get to the desktop with Avast installed to get to the troubleshooting screen!!

Once the micro update has been made available to all users, please place a note to that effect in this message thread so I know that I can try installing avast again.

Thank you . . .

[Spec8472]

1)Boot into safe mode
2)Launch regedit.exe
3)Set  REG_DWORD value "Dont" to value "1"  in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\aswVmm\Parameters" key

Hi,

there is  bug in aswVmm.sys. Only some AMD cpus seems to be affected. Will be fixed by micro update ASAP.  As workaround , please uncheck "Enable HW assisted virtualization" in troubleshooting settings. Sorry for your troubles.

Thanks for the update.  Your instructions to "uncheck "Enable HW assisted virtualization" in troubleshooting settings" is not going to be doable (at least for me) since I cannot even get to the desktop with Avast installed to get to the troubleshooting screen!!

Once the micro update has been made available to all users, please place a note to that effect in this message thread so I know that I can try installing avast again.

Thank you . . .

[Gandalf1369]

I don't have the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\aswVmm\Parameters" key in my registry.  Probably because I had to uninstall avast (as mentioned in my original post) in order to even get to my Windows 10 desktop.  I realize I could install avast again, boot into safe mode, and then try to follow your instructions, and hope it works - but frankly I rather not go thru the hassle.

If you have any other ideas I would be willing to try them.  If not I'll continue to use Windows Defender until avast is updated to fix the AMD bug.

[Spec8472]

You can install Avast and uncheck the virtualization check box in troubleshooting settings before reboot.

I don't have the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\aswVmm\Parameters" key in my registry.  Probably because I had to uninstall avast (as mentioned in my original post) in order to even get to my Windows 10 desktop.  I realize I could install avast again, boot into safe mode, and then try to follow your instructions, and hope it works - but frankly I rather not go thru the hassle.

If you have any other ideas I would be willing to try them.  If not I'll continue to use Windows Defender until avast is updated to fix the AMD bug.

[REDACTED]

The workaround works, thanks a lot guys !

Gandalf1369, you can do as Spec8472 just suggested, it works like a charm.

Or you can wait for the Avast update if you prefer, of course.

[Gandalf1369]

The workaround works, thanks a lot guys !

Gandalf1369, you can do as Spec8472 just suggested, it works like a charm.

Or you can wait for the Avast update if you prefer, of course.

Just tried it - so far so good!  Thanks to both of you.

[REDACTED]

1)Boot into safe mode
2)Launch regedit.exe
3)Set  REG_DWORD value "Dont" to value "1"  in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\aswVmm\Parameters" key

Hi,

there is  bug in aswVmm.sys. Only some AMD cpus seems to be affected. Will be fixed by micro update ASAP.  As workaround , please uncheck "Enable HW assisted virtualization" in troubleshooting settings. Sorry for your troubles.

Thanks for the update.  Your instructions to "uncheck "Enable HW assisted virtualization" in troubleshooting settings" is not going to be doable (at least for me) since I cannot even get to the desktop with Avast installed to get to the troubleshooting screen!!

Once the micro update has been made available to all users, please place a note to that effect in this message thread so I know that I can try installing avast again.

Thank you . . .

Had the same problem. Did you mean to create the Dword in Parameters and give it a value of 1?

I did that and unchecked the Enable HW assisted virtualization in troubleshooting.

Worked great thanks.

[REDACTED]

booted computer today and the BSOD has returned.

Booted into safe mode to find that The Reg  dword "don't" has changed to "0" and when I checked avast "Enable HW assisted virtualization" in troubleshooting the tick was back.

I have now uninstalled Avast and now await a fix which will come very soon I hope.

worf105