We're sorry to hear that Firefox is crashing. 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 list of Submitted/Unsubmitted Crash Reports will appear, similar to the one shown below.
2. Copy the 5 most recent Submitted 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.

bp-2bd1d436-703c-4e25-b2c8-442830220124

bp-c0a6b0cf-82e3-4735-b956-d8b4b0220124

bp-9a2e748d-0966-45b7-9228-d7f3b0220124

bp-8a1c7429-d11e-4154-a907-4a08d0220124

bp-e2fa77a8-784c-44c6-bcb6-a4a200220124

These are the last five, if you need more let me know!

Thanks.

bp-2bd1d436-703c-4e25-b2c8-442830220124 = Uptime 31 seconds Signature: nsTArray_Impl<T>::Compare<T> | NS_QuickSort | mozilla::PreferencesWriter::Write

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-c0a6b0cf-82e3-4735-b956-d8b4b0220124 = Uptime 360 seconds (6 minutes) bp-9a2e748d-0966-45b7-9228-d7f3b0220124 = Uptime 36 seconds

Signature: nsTArray_Impl<T>::Compare<T> | NS_QuickSort | NS_QuickSort | NS_QuickSort | mozilla::PreferencesWriter::Write

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-8a1c7429-d11e-4154-a907-4a08d0220124 = Uptime 271 seconds (4 minutes and 31 seconds) Signature: nsTSubstring<T>::AppendASCII | nsBufferedOutputStream::Init

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-e2fa77a8-784c-44c6-bcb6-a4a200220124 = Uptime 3 seconds Signature: nsTSubstring<T>::AppendASCII

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

The crashes look to be all over the place. This could mean there is a problem with the RAM.

https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster

https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix

https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram

https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding

https://support.mozilla.org/en-US/kb/firefox-takes-long-time-start-up

https://support.mozilla.org/en-US/kb/quick-fixes-if-your-firefox-slows-down

https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources

MemTest Could you please run a tool from http://memtest.org/ in order to check the integrity of your RAM?

You will need a thumb or disk drive to install it on.

Do you let Windows handle the page file or did you set a fixed size ? Control Panel -> System -> Advanced -> Performance -> Settings

If you use a fixed size for the page file then try the former and let Windows handle the page file. How to determine the appropriate page file size for 64-bit versions of Windows {web link}

You can check for problems with preferences. You can delete possible user.js and numbered prefs-##.js files and rename/remove the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in current Firefox releases.

You can use the button on the "Help -> More Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page (Root directory).

• Help -> More Troubleshooting Information -> Profile Folder/Directory:
  Windows: Open Folder; Linux: Open Directory; Mac: Show in Finder
• https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data

You can create a new profile as a quick test to see if your current profile is causing the problem.

See "Creating a profile":

• https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

• https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile