In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

The crash report is several pages of data. We need the report numbers to see the whole report.

1. Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
2. Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.

Note: If a recent Report ID does not start with bp- click on it to submit the report. (Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

In addition to the standard indications provided above, if you visit websites displaying lots of ads, they might end up using most of your RAM and that's why your Firefox crashes.

I'd recommend using Adblock Plus to prevent ads from being displayed.

Try installing a more recent graphics driver from here. Also see if you can reproduce the crash in Firefox Safe Mode.

To Mattcamp five last reports: bp-9a3f14c4-6649-4310-9997-cd9ca1170729 29.7.17 16:51 bp-60de3dbb-02df-439e-832e-17b9d1170727 27.7.17 16:07 bp-3f9efea1-3619-4057-b70f-e387c1170726 26.7.17 13:56 bp-d618f22c-f086-45af-9789-f8b920170725 25.7.17 22:04 bp-efa527c1-34a3-40c3-b41f-c04ce1170701 1.7.17 16:56

I found a solution that apparently worked for another case where the crash reason was the same (EXCEPTION_ACCESS_VIOLATION_WRITE).

The link to the solution is available here.

Sorry, mattcamp, I disabled the hardware- acceleration. Didn't help.

Maybe Adblock Plus could help you with this issue, then.

Please read my previous message and have a look at this and this bug.

You could test a nightly build or Beta 55 to find out if these bugs are valid for you and to see if the issue will be resolved in 55. Another option would be to wait until next week when 55 is scheduled for release. _{And a third would be to experiment with previous Intel driver versions, given their number of recent updates and the bug info. ;)}

Warning: if you want to test with 55, be sure to create a new and separate profile for it (or copy your current profile folder somewhere and restore it before reverting to 54), since they will not be backwards compatible after using them with 55.