Author Topic: Blue screen when closing sandboxed Chrome - 7.0.1464  (Read 1418 times)

Offline Driver8

  • Newbie
  • *
  • Posts: 19
    • Personal Message (Offline)
Blue screen when closing sandboxed Chrome - 7.0.1464
« on: August 11, 2012, 02:51:54 AM »
I am getting a blue screen of death every time I close Chrome when running in sandboxed mode.  This does not happen when running Chrome normally.  Also, the SafeZone Chrome works fine for me.

I am running AIS 7.0.1464 and Chrome 21.0.1180.75.  I have the Windows 7 operating system on a 64 bit machine.  The only other anti-malware software I am running resident is MalwareBytes Pro.  I do have exceptions set for Avast and MBP.

What can I do to troubleshoot this problem?

Thanks.
« Last Edit: August 11, 2012, 03:08:42 AM by Driver8 »

Offline Driver8

  • Newbie
  • *
  • Posts: 19
    • Personal Message (Offline)
Re: Blue screen when closing sandboxed Chrome - 7.0.1464
« Reply #1 on: August 11, 2012, 10:57:55 AM »
I may have fixed this problem.  I have a laptop with the same configuration and was having the same bluescreen crash with Chrome sandboxed.  I uninstalled Chrome and reinstalled it without any extensions.  The problem does not occur now.

I decided to try it on my desktop and just disable all five of my extensions.  This worked as well ... no more bluescreen when running Chrome in the Avast! sandbox.  I added the extensions back one by one to see if any of them were causing the problem, but I know have them all enabled and I am still running fine.

So, I really don't know what is going on with this or how extensions might play into the problem, but my installation of AIS is working great right now.  My computer is fast and I have no more bluescreens of death when closing sandboxed Chrome.  I am happy and I hope it lasts.

Offline igor

  • Moderator
  • Serious Graphoman
  • *
  • Posts: 11131
  • Gender: Male
    • AVAST Software
    • Personal Message (Offline)
Re: Blue screen when closing sandboxed Chrome - 7.0.1464
« Reply #2 on: August 11, 2012, 11:10:17 AM »
Do you have any minidump file (in C:\Windows\Minidump folder) with the timestamp corresponding to the bluscreen?
If yes, can you please upload it to ftp://ftp.avast.com/incoming and post a note about the upload filename here?
Thanks.

Offline Driver8

  • Newbie
  • *
  • Posts: 19
    • Personal Message (Offline)
Re: Blue screen when closing sandboxed Chrome - 7.0.1464
« Reply #3 on: August 11, 2012, 05:09:09 PM »
Well, my computer is not doing the bluescreen crashing anymore.  I know it created some minidump files when it was but now that folder is empty.  I did run a cleaning utility that may have cleaned that and other similar window temp and log folders.  I am getting a different problem now however.  It is a problem I had a week or two ago.  When I go to SafeZone, Chrome won't start and an error pops up saying there is some kind of exception error.  I will go find my other post on this topic and paste the text of the error message here. 

Here is the error that pops up when I go to SafeZone.  Again, my Chrome now seems to work perfectly fine in regular and sandboxed mode.  It won't start in SafeZone and I get a popup that says this:

The exception Breakpoint
A breakpoint has been reached
(0x80000003) occurred in the application at location 0x625ac1d0.
Click Ok to terminate the program

« Last Edit: August 11, 2012, 05:11:58 PM by Driver8 »

Offline pk

  • avast! team
  • Super Poster
  • *
  • Posts: 1866
    • Personal Message (Offline)
Re: Blue screen when closing sandboxed Chrome - 7.0.1464
« Reply #4 on: August 12, 2012, 03:52:08 PM »
Please clean up SafeZone contents: go to Additional Protection -> SafeZone -> Expert Settings -> Cleanup button. Let me know if it helps, thanks.

Offline Driver8

  • Newbie
  • *
  • Posts: 19
    • Personal Message (Offline)
Re: Blue screen when closing sandboxed Chrome - 7.0.1464
« Reply #5 on: August 13, 2012, 01:23:09 AM »
Thanks.  That seemed to do the trick.  I think I everything is now running fine.  My system seems to have settled down after all the bluescreens and strange error messages.  It is running pretty quickly and is starting to feel snappy like it did a few versions ago.  That is awesome because I love your product ... plus I want to get my money's worth out of the 3pc, 2yr license I bought in mid-June.   :D