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

Constant crashed with blue death screens Firefox after Win 8.1 to Win 10 upgrade

  • 8 uphendule
  • 1 inale nkinga
  • 28 views
  • Igcine ukuphendulwa ngu FredMcD

more options

Hi all,

Since I switched to Win 10 Firefox constantly crash on my computer.

  • Tried fresh install no change
  • Tried repair no change
  • Switched off extension and then on (one by one) no change
  • Deleted cache - History - etc .. :( it worked for only a few days since I did a full scan with Microsoft Defender.
  • Since this last crash (as I could not launch Firefox anymore I used shift + click on Mozilla shortcut)I decided to switch off the graphic card acceleration and all the other option in this menu and it seems to help

Could you tell me how to send you the crash report ( I do have 8-10 of them already sent to Mozilla)

Hi all, Since I switched to Win 10 Firefox constantly crash on my computer. * Tried fresh install no change * Tried repair no change * Switched off extension and then on (one by one) no change * Deleted cache - History - etc .. :( it worked for only a few days since I did a full scan with Microsoft Defender. * Since this last crash (as I could not launch Firefox anymore I used shift + click on Mozilla shortcut)I decided to switch off the graphic card acceleration and all the other option in this menu and it seems to help Could you tell me how to send you the crash report ( I do have 8-10 of them already sent to Mozilla)

Isisombululo esikhethiwe

I don't know how to read the report. You should contact Memtest support or talk to a local computer tech. You may need to replace some of your chips.

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0

All Replies (8)

more options

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 Submitted crash reports, and copy them. Now go to the reply box and paste them in.

Please, Do not post a screenshot ! !

aboutcrashesFx57

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support +++++++++++++++++++++++++++ If you can't get Firefox to open, you will have to do this the hard way. https://support.mozilla.org/en-US/kb/mozillacrashreporter

Open the file browser / explorer on your computer. Note: You may have to enable Show Hidden Folders / Files. Enter this in the address bar;

Windows: %APPDATA%\Mozilla\Firefox\Crash Reports\submitted Win 7/Vista: C:\Users\<username>\AppData\Roaming\Mozilla\Firefox\Crash Reports\submitted Win XP/2000: C:\Documents and Settings\<username>\Application Data\Mozilla\Firefox\Crash Reports\submitted Win 10: Press <Windows> + R on the keyboard. A Run dialog will open. In the Run dialog, type %APPDATA%\Mozilla\Firefox\Crash Reports\submitted <Enter>


Mac OS: /Users/<username>/Library/Application Support/Firefox/Crash Reports/submitted Linux: /home/<username>/.mozilla/firefox/Crash Reports/submitted

Copy the most Recent 5-7 File Names in the folder. Press the Reply button. Now go to the reply box and paste them in.

Helpful?

more options

Hi Fred,

Thx for the fast answer I hope I did it well, You will find at the end of this message the number of 4 crash I cannot send error message : "échec" (maybe because I deleted some cache files I don't know..)

Here are the number :

Identifiant du rapport Date d’envoi bp-2b962f8c-d295-4168-bfaf-74dd20211209 09-12-21, 06:58 bp-a5702d19-a97c-4384-8c65-561270211209 09-12-21, 05:17 bp-ae4d8f87-f844-4854-81e8-178ac0211209 09-12-21, 05:17 bp-1e7535c1-95f5-4ba7-ad4a-2da0f0211209 09-12-21, 05:17 bp-65dcb9da-d31b-4c0e-bd68-b33210211209 09-12-21, 05:17 bp-856a5940-1dd2-4ef6-ad1b-e763c0211209 09-12-21, 05:17 bp-be0a506f-55af-4034-9230-e5d370211209 09-12-21, 05:17 bp-358c5d47-7c6a-4069-b3f8-ca4ec0211209 09-12-21, 05:17 bp-7fd59ed3-32e3-49fb-8ad6-7179d0211209 09-12-21, 05:17 bp-78f6f50c-9a65-4983-b479-561d30211209 09-12-21, 05:17 bp-9cc384a1-d96f-4fe4-93d1-aca020211209 09-12-21, 05:17 bp-f8171663-779e-442d-8f52-ad50f0211209 09-12-21, 05:17 bp-aefd6aac-4025-4946-9b35-e0d010211209 09-12-21, 05:17 bp-bc41eb92-892e-4c42-8d19-3b7aa0211203 03-12-21, 07:02

Error when trying to send these ones :

Rapports de plantage non envoyés (not send)

Identifiant du rapport Date du plantage 7544ebdd-00e9-4a24-8660-38eb7b44a493 09-12-21, 05:06 44acc003-63fc-4ed3-9c4c-5609e48b755a 08-12-21, 17:10 9e30984e-94fe-427d-9657-1c44d25aead0 03-12-21, 07:02 d6e3d2c8-3a90-4f1b-8713-35a285636e0c 03-12-21, 06:26

Helpful?

more options

When a crash report fails to submit, it means the servers decided they don’t need that report.

About:Throttling “You're seeing this page because the crash report you selected was held back from submission. For statistical purposes, we don't need every crash report and sometimes we decline the submission of a crash report as a form of throttling." ++++++++++++++++++++++++++++++++++++++++++++++++++++ Bug 1662317 About Throttling Steps to reproduce:

My Firefox crashed but did not submit the crash report.

Actual results:

I tried to manually send the report, and the system gave me the message: About Throttling

Expected results:

If Mozilla does not need the report, I, the user, still want to know what happened. How else can I fix or understand what went wrong?

Helpful?

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.

Helpful?

more options

Product Firefox Release Channel release Version 95.0 Build ID 20211129150630 (2021-11-29)

bp-2b962f8c-d295-4168-bfaf-74dd20211209 = Uptime 1 seconds Signature: js::frontend::RewritingParseNodeVisitor<T>::visit

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

This is for Sumo's Related Bugs 1547561 Access Denied You are not authorized to access bug 1547561 +++++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 94.0.2 Build ID 20211119140621 (2021-11-19)

bp-856a5940-1dd2-4ef6-ad1b-e763c0211209 = Uptime 4 seconds Signature: EMPTY: no crashing thread identified; ERROR_NO_THREAD_LIST

Crash Reason

Attention Sumo's there are 15 related bug reports +++++++++++++++++++++++++++++++++++++++++++++ bp-65dcb9da-d31b-4c0e-bd68-b33210211209 = Uptime 8 seconds Signature: WarpCacheIRTranspiler::transpile

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ +++++++++++++++++++++++++++++++++++++++++ bp-1e7535c1-95f5-4ba7-ad4a-2da0f0211209 = Uptime 2 seconds Signature: xpc::XrayWrapper<T>::getOwnPropertyDescriptor

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ +++++++++++++++++++++++++++++++++++++ bp-ae4d8f87-f844-4854-81e8-178ac0211209 = Uptime 1 seconds Signature: nsAttrValue::ToString

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

This is for Sumo's Related Bugs 733712 RESOLVED FIXED Don't call atk_object_set_name

731813 RESOLVED FIXED Crash [@ nsAttrValue::ToString] listening for DOMAttrModified and removing a missing attribute

495555 RESOLVED WORKSFORME Crash [@ nsAttrValue::ToString] with aria-labelledby, observes and groupbox

391132 VERIFIED FIXED Crash [@ nsAttrValue::ToString] with input type=image inside label and with display: table-cell +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-a5702d19-a97c-4384-8c65-561270211209 = Uptime 1 seconds Signature: js::frontend::ScopeStencil::createSpecificScope<T>

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

Helpful?

more options

Your crashes are all over the place. Sometimes this means 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 LAST UPDATED : 12/04/2020 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}

Helpful?

more options

Hi FredMcD,

I ran Memtest thanks, and it is horrible. But I cannot say if error(sssss) comes from CPU or from Memory blanks ?

Could you check below the pictures and tell me what do you think about it ?

Thanks a lot,

Regards,

Helpful?

more options

Isisombululo Esikhethiwe

I don't know how to read the report. You should contact Memtest support or talk to a local computer tech. You may need to replace some of your chips.

Helpful?

Buza umbuzo

Kufanele ulogele ukungena ku-akhawunti yakho ukuze uphendule amaphosti. Uyacelwauqale umbuzo omusha, uma ungekabi nayo i-akhawunti namanje.