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

Bad news first: This tab has crashed

  • 4 replies
  • 37 have this problem
  • 35 views
  • Last reply by olusam

more options

Hello, i use Firefox version 50.0, and since i downloaded it on my fresh installed Windows 10 Pro (6th of November), i have gotten regular "Bad news first: This tab has crashed". It really is starting to piss me off (Sorry for my language, but it even crashed when i tried to write this). I really love this browser, and can't get myself to use another one. I have red through multiple threads, and none of them had any solutions. I have reinstalled Firefox numerous times, ran Anti-malware scans (Particularly Malwarebytes Anti-Malware, HitmanPro, and AdwCleaner) and none of them helped. The only add-on i have installed is Adblock Plus (It still crashes even if i don't have it installed)

Hello, i use Firefox version 50.0, and since i downloaded it on my fresh installed Windows 10 Pro (6th of November), i have gotten regular "Bad news first: This tab has crashed". It really is starting to piss me off (Sorry for my language, but it even crashed when i tried to write this). I really love this browser, and can't get myself to use another one. I have red through multiple threads, and none of them had any solutions. I have reinstalled Firefox numerous times, ran Anti-malware scans (Particularly Malwarebytes Anti-Malware, HitmanPro, and AdwCleaner) and none of them helped. The only add-on i have installed is Adblock Plus (It still crashes even if i don't have it installed)
Attached screenshots

Chosen solution

thanks for providing some crash ids. this is a crash caused by your graphics driver - please look into updating your driver version, as amd has already published an update containing a fix for that: https://support.amd.com/en-us/download/desktop?os=Windows+8.1+-+64

Read this answer in context 👍 0

All Replies (4)

more options

Hi MarshalDoge, No need to worry about malware, just because you see that message, that is a new Firefox Feature.

We do need to sort out why you get the tab crash though.

Firefox is now rolling out a multi process made capability. Previously other than a few plugin container processes when Firefox crashed you would have to restart and the whole thing stopped working. Now it is possible for individual tabs to crash and be restarted in due course without interrupting whatever else you are doing.

Visit about:crashes and let us have the last three or four Crash IDs they begin with bp- and we will see if we can work out what the problem is.


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 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.)

aboutcrashesFx29

Thank you for your help!

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

more options

bp-1e9a807d-066d-4d40-b804-4afb72161127 bp-4a8cf11b-6065-45cb-aa6b-7db892161127 bp-8ba89b00-c859-4183-b8db-3e9c52161127 bp-1fe4c11e-972b-4d4e-b9ea-db34f2161127 bp-08e683df-d710-42fe-aa76-7e0ac2161127

Here are my latest crash ID's

more options

Chosen Solution

thanks for providing some crash ids. this is a crash caused by your graphics driver - please look into updating your driver version, as amd has already published an update containing a fix for that: https://support.amd.com/en-us/download/desktop?os=Windows+8.1+-+64

more options

bp-7d4d2c72-77d4-4aa3-961e-b95c62170118 18/01/2017 9:45 AM 8c89a9c4-9d34-4ea9-9e25-1d48c0f9c6a4 09/11/2016 8:04 AM ea8d8fea-51c2-4e94-9d02-9358bcd8c1ba 08/09/2016 10:00 AM bdcb7d59-96e4-409b-9648-92e5405e8ccb 01/02/2016 8:13 AM 6b78210c-d5b9-428b-83e4-1b3e45a02d3b 14/01/2016 4:28 PM