Today I manually updated to .2215 thru the GUI. After the reboot I observed thru the task manager as a number of new avast processes loaded and ran, NG tool among them. Shortly thereafter, I experienced a fleeting black screen, whereupon the system abruptly rebooted again. After that reboot my system seemed fine, and stable, until my firewall indicated that NG tool was again trying to load and required kernel access. I granted permission. Within moments of it loading I got a BSOD. (see attachment). I can also send a zip file of the mini-dump file if needed.
I read somewhere on this forum that in order for the NG tool to function virtualization must be enabled in BIOS. I have a Dell Optiplex 740 and nowhere in the BIOS setup (version 2.2.7) is there function feature to enable virtualization, which Speccy shows to be supported but disabled. Could this be the problem? Thanks
PC Tools Firewall+. What I know at this point is the issue only surfaced after the program update, and at each time the NG tool process was running. I never saw that process in my task manager until today after the update. Nor AvastVBoxSVC.exe
Uninstall Avast by control panel [If you don’t have Avast in control Panel go to #3]
Uninstall in safe mode using Avastclear. [Running Avastclear is normal mode will give a prompt to go into Safe Mode]
Check : Once uninstalled check in device manager>view>show hidden devices if there is anything related to avast with a yellow triangle… if so, uninstall it and reboot.
Install the version you downloaded.
Reboot.
Free: If you have the Free version, register the product for free for a year from the avast! UI.
Paid: If you have a paid license, insert the license key/activation code after the reboot at stage 6.
If you have any questions, please don’t hesitate to ask. It’s better to ask than make a mistake and start over again with the process.
Ok, the system has been stable for the past hr. But I’ll err on the side of caution and do a clean install, as you advised. Will let you know if there is an issue after doing that. Thanks.
Considering the BlueScreenView isn’t showing any avast services involved and the faulting (caused by) process/service as ntoskrnl.exe - I don’t know if this is down to avast or not.
Personally I would wait a little before doing a clean install and see if this is a one off or a regular occurrence.
Update: 3:35pm. Uninstalled program in safe mode w/avastclear. rebooted and installed from provided link. Had firewall disable during the process. After it installed, it ran a startup scan but minutes later got another BSOD (see attachment). Won’t waste anymore time on this. Will uninstall and employ another AV.
Better to e-mail it to kominek atavast.com. For the time being, you can uninstall “Secure Virtual Machine” component (in the Control Panel or just run the installer again and uncheck it in the custom install.
Done. I’ll keep an eye on the forum for your thoughts/findings. Meanwhile, I don’t want my system in this loop of BSODs so I’ll remove avast for now. Thanks.
Some additional data that may be useful. Event Viewer shows several instances of this after the in GUI update, and also after the subsequent clean install.
[b]The description for Event ID 0 from source AvastVBoxSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: