I posted in the update thread about the problem below. I think I can send the dump files from the crashes if someone tells me how. I only have access to my laptop at the moment and have rolled it back to version of Avast Internet Security. I won’t have access for a while to the desktop computer that had the SafeZone problem described at the end of the post.
I updated both of my computers (desktop and laptop) to Avast Internet Security 7.0.1451 a few hours ago. I used the internal program updater. I thought everything was going well until I tested out running Google Chrome sandboxed. When I go to EICAR and click on one of their files, I get an Avast warning as normal. When I close the browser, however, I get an instant crash and computer reboot. This does not happen if I run Chrome outside the sandbox and check the EICAR files. It does not happen with Firefox or IE either. It happens with Chrome sandboxed on both my laptop and desktop. I have repeated it about three times on both machines. Oh, it also only seems to happen when a warning notice has been encountered. If I run Chrome sandboxed and just go to regular pages, it closes without crashing the computer.
I am uninstalling and going back to the previous version of Avast Internet Security on my laptop. I will see how it goes.
Here are the specifics of my machines:
Desktop – AMD Phenom IIx4 820 2800Mhz, Windows 7 Home Premium, 64 bit, 6GB RAM, Avast Internet Security 7.0.1451, MBAM Pro 1.61.0.1400 Realtime, Google Chrome 19.0.1084.56 m
Laptop - Intel® Core™2 Duo Processor SU7300 : 1.3 GHz, Windows 7 Home Premium, 64 bit, 4GB RAM, Avast Internet Security 7.0.1451, MBAM Pro 1.61.0.1400 Realtime, Google Chrome 19.0.1084.56 m
It looks like my Chrome just updated to 20.0.1132.47 m. Now when I go to SafeZone on my desktop, the browser does not start but an error box pops up. It says these exact words:
The exception Breakpoint
A breakpoint has been reached
(0x80000003) occurred in the application at location 0x625ac1d0.
Click Ok to terminate the program
Outside of SafeZone, Chrome still crashes when running sandboxed as I described above. I guess I should also mention that I had been using SafeZone with no problems before updating.