Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Open

Nonstop crashing after latest update

jbr replied
Banana Mike

Since the 152.0 update I've experienced near nonstop browser crashing, it crashed twice as I was trying to type up and submit this message,

Is this a known issue or solely on my end? running 64 bit, windows 10

Since the 152.0 update I've experienced near nonstop browser crashing, it crashed twice as I was trying to type up and submit this message, Is this a known issue or solely on my end? running 64 bit, windows 10

All Replies (4)

Let's see if you can check the recent crash reports got submitted already, and paste some of their IDs to see what's the culprit:

  1. Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted (and Unsubmitted, if any) 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.)

Fx115aboutcrashes

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

Let's see if there are any obvious patterns.

In case you're affected by faulty Raptor Lake CPU, chances are you're observing this: bugzilla.mozilla.org/2039575

There is a workaround shipping already: www.firefox.com/en-US/firefox/152.0.1/releasenotes/

Same thing here. All tabs crashing like crazy and often the entire program. (Raptor Lake CPU here, fully microcode-patched from start.)

Downgrading to v150 stabilised everything it seems but I had to enter a cutom policy json file to stop auto-updates since Firefox will eventually FORCE you to update even if you don't want to.

Been using Firefox since it was (sort of) Netscape... and it's never been this bad.

Same as above — please paste the submitted crash IDs here. Some are having workarounds considered, some are just too random. (There are even questions whether to rewrite the compilers to completely avoid these registers at the cost of size and performance to work around these flawed CPUs.)

یک سؤال بپرسید

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.