Unable to reproduce the issue on Windows 7 for chrome stable version 52.0.2743.116. Installed a fresh instance of chrome and no crashes observed.

@elcibersincafe: Request you to please try a system restart, reset chrome and try again. If still nothing works out can you please try a reinstallation.

Please update us with your observations.

Thanks.!

Thank you. This has been going on for several weeks. I have restarted my PC many times, and reinstalled chrome as well. It ovbiously does not happen in every PC with the specifications I have, but in the forums I have found at least another person with the same problem. I filled in this report after a suggestion from an expert on the chrome forums.

Is there any other specification I could send you that would be helpful?

I guess, The profile would have been corrupted. Can you please try creating a new profile or please try a fresh installation of chrome. Please update us with your observations.

Thanks.!

I followed these instructions to create a new profile:

https://support.google.com/chrome/answer/142059?hl=en

But it didn't work. I also deleted C:\Users\MyUser\AppData\Local\Google and reinstalled Chrome, but the problem persists. Y have tried opening chrome from another Windows user profile, but it does no work either.

Is there any other specification I could send you that would be helpful?

Hi all!

I'm Nicolás from Chrome-Es product forums.

In the last two weeks, we seen a lot of issues related with Windows 10 updates and "Aw spap" errors. Common solutions (https://support.google.com/chrome/answer/95669?hl=en) don't fix the problem.

I can't be sure if some of those update affects Windows 7 OS too.

Regards,
Nicolás.

I had the same issue with windows 7 after version 53 was promoted to stable.  Chrome Canary would work, but all tabs and extensions in Chrome would "aw, snap" immediately.

Removing chrome.exe from the EMET application configuration list fixed the issue.

Please note that there's some known compatibility issues between EMET and Chrome and so we recommend to not use it on Chrome: https://www.chromium.org/Home/chromium-security/chromium-and-emet

Thank you for your feedback. I believe I am not using EMET, I have never installed it and, as far as I know, it is not included by default on Windows 7.

I had same issue after upgrading Chrome to version 53.0.2785.89m (64-bit) on September 1st.

User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.89 Safari/537.36

In my case, neither Canary release nor any of the other fixes made a difference. "Aw Snap" on every page even in safe mode.

Only temporary workaround was to uncheck the EMF+ option for chrome.exe entry in list of apps via EMET 5.5 GUI. Chrome worked fine on this machine with every previous version of Chrome so revision 53 did something EMET really doesn't like.

EMET is required by corporate policy so no option to remove or disable it.