Win 7 x64 - Chrome crashes "memory could not be read"

Please post your problem description here

Moderator: Barb@Invincea

Post Reply
nicknomo
Posts: 89
Joined: Mon Aug 02, 2010 3:15 am

Win 7 x64 - Chrome crashes "memory could not be read"

Post by nicknomo » Tue Feb 17, 2015 10:41 pm

I get a an error when running chrome with drop my rights:

"The instruction at 0x<various mem addresses> referenced memory at 0x00000000. The memory could not be read"

I'm running Win 7 x64, SBIE 4.15.12, Chrome 40.0.2214.111 m. I had this problem a while ago, and reported it then too. Its never gone away, even after several versions of Chrome and SBIE. If it makes a difference, I'm using the Chrome MSI instead of the one that installs in the user profile folder.

I have EMET and BitDefender free running and installed. EMET has DEP+SEHOP set to opt-out and ASLR set to opt-in.

Not using Drop My Rights seems to work fine.

I created a new Sandbox with the default settings and then only enabled drop my rights. It had the same effect.

Dun
Posts: 350
Joined: Mon Jun 23, 2014 5:00 am
Location: Poland

Re: Win 7 x64 - Chrome crashes "memory could not be read"

Post by Dun » Wed Feb 18, 2015 3:42 am

Do you have UAC disabled?
Sandboxie 5.19.4 personal lifetime license user || Win10 x64 Pro CU (up to date) || ESET SS 10+ x64 || AppGuard 4+ || Firefox 54+ x64 || UAC on

Curt@invincea
Sandboxie Lead Developer
Sandboxie Lead Developer
Posts: 1638
Joined: Fri Jan 17, 2014 5:21 pm
Contact:

Re: Win 7 x64 - Chrome crashes "memory could not be read"

Post by Curt@invincea » Wed Feb 18, 2015 11:26 am

Drop rights and disabled UAC are a bad combination for Chrome.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest