[FIXED][2263-2269] Invalid access to memory location

Consumer Products Public Beta Avast Antivirus Beta
1

Hello all,

I updated to 2263 via AvastUI and now I got this error message “Invalid access to memory location” when I try to log-in to windows… I mean, I can’t log-in to windows :frowning:

I’m not exactly sure that this is caused by avast beta as I noticed Windows Update was updating something during reboot, but I decided to post this for notice.

In details,

  1. Updating avast via Avast UI
  2. Reboot the computer, WU updated something
  3. Log-in to Windows, no Avast icon on taskbar, almost all app could not run because of “Access to memory location is invalid” error, including taskmgr.
  4. Tried to manually create kernel dump and seems failed (no memory.dmp on HDD, stuck at “Dumping physical memory: 100”)
  5. Hard reboot, cannot log-in to Windows as described. Tried 3 soft reboots with no success.
  6. Safe mode works

If some of the devs have interest in this issue, I can provide logs as I keep the machine untouched.

Thanks.

Edit: fix error message translation
Edit2: fix error message translation

2

Hello NON!
Thanks for the report. Would it be possible to get specific files and folders from the machine in the safe mode and share it with us for evaluation?
In this case, both
“C:\Program Files\AVAST Software”
and
“C:\ProgramData\AVAST Software\Avast”
folders, zipped, would be very helpful.
Please let me know if you needed help with getting or sharing these files.

Petr

3

Hello Petr, thank you for your reply.

I just booted my machine in Safe Mode and found both folder have more than 1GB in size. :o
This is mostly because there are some .mdmp files which has about 200MB each, and some huge log files (over 300MB).

I’ll try to compress them before uploading to avast ftp, but even after compress they will still have quite a size.
Do you have some specific directories to send you first? Or should I just upload all of them in one (or two) archives?

4

OK, I finished compressing both folders.

Firstly uploaded ProgramData folder.
Filename: NON_Avast_ProgramData_160510.7z

Program Files will be uploaded soon… :slight_smile:
Uploaded. Filename: NON_Avast_ProgramFiles_160510.7z

5

Thanks a lot NON! We are going to look into it.

6

OK, I updated avast using “Safe Mode with networking” and again got the same issue.

I’ll try clean reinstall.

7

After clean reinstall this beta just works fine, until restoring its settings to previous one.
So this means some of the settings breaks avast since 2263 beta.

8

Finally found the cause. It’s HIPS!
When I change HIPS level from default (minimum), the issue arises.
If I revert it to default by modifying FileSystemShield.ini file, the issue disappear.

So, something must be wrong with beta HIPS.

9

Hi NON,

just to let you know, similar reports in the German section (you’re not alone).

Asyn

10

Still not fixed with latest beta 2265.

11

Still happening with 2266. Reboot is not needed, just set HIPS to maximum and most application could not run.

12

According to your sig, you also use Comodo HIPS on your system.
I’d suggest to disable it for testing or vice versa the Avast HIPS…

13

Thanks Asyn for suggestion.

Quick check (change Comodo HIPS to disable) shows it has no relation to this issue, however, I’ll try disable Comodo HIPS then reboot and try again.

14

I had this nonsense as well today with 2267 build. I figured it out the hard way as well… ::slight_smile:

15

:frowning:

Still happening with 2267 beta with Comodo HIPS disabled.

16

Time for the devs to chime in here.

17

I only have avast! installed and it does this if I crank HIPS sensitivity to highest setting.

18

I am not sure, but I think that HIPS is disabled yesterday in 11.2.2262.
Can someone from Avast confirm this ?

19

Start a new topic here: https://forum.avast.com/index.php?action=post;board=2
We’re discussing the latest beta versions.

20

Problem still exists with the version 12.1.2268.

TerraX