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

This thread was closed and archived. Please ask a new question if you need help.

Stuck in a crash loop

  • 7 replies
  • 7 have this problem
  • 31 views
  • Last reply by FredMcD

more options

Firefox will not open, it automatically goes to a crash reporter screen. I've also reinstalled and updated Firefox, yet still get the same Report Contents. 1st line is: AbortMessage: [8720] ###!!! ABORT: LoadSheetSync failed with error 80004005 loading built-in stylesheet 'chrome://global/skin/scrollbars.css': file c:/builds/moz2_slave/rel-m-rel-w32_bld-000000000000/build/layout/style/nsLayoutStylesheetCache.cpp, line 758

This all began once I selected some personal appearance changes, then added a theme. I guess they were incompatible. Is there any way to undo those 2 changes and access Mozilla again?

Guidance appreciated :)

Firefox will not open, it automatically goes to a crash reporter screen. I've also reinstalled and updated Firefox, yet still get the same Report Contents. 1st line is: AbortMessage: [8720] ###!!! ABORT: LoadSheetSync failed with error 80004005 loading built-in stylesheet 'chrome://global/skin/scrollbars.css': file c:/builds/moz2_slave/rel-m-rel-w32_bld-000000000000/build/layout/style/nsLayoutStylesheetCache.cpp, line 758 This all began once I selected some personal appearance changes, then added a theme. I guess they were incompatible. Is there any way to undo those 2 changes and access Mozilla again? Guidance appreciated :)

Chosen solution

Signature mozalloc_abort | NS_DebugBreak | ErrorLoadingBuiltinSheet

System Memory Use Percentage; 78

icudt56.dll = International Components for Unicode = The ICU Project

This is for Sumo's Related Bugs 1194856 ASSIGNED --- Startup crash in ErrorLoadingBuiltinSheet


Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac=Options)
key, and then starting Firefox. Is the problem still there?


If you have problems with current Shockwave Flash plugin versions then check this:

  • see if there are updates for your graphics drivers

https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration

  • disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later)

https://forums.adobe.com/message/4468493#TemporaryWorkaround

  • disable hardware acceleration in the Flash plugin

https://forums.adobe.com/thread/891337 See also:

Read this answer in context 👍 1

All Replies (7)

more options

We're sorry to hear that your Firefox seems to be crashing when you open it. Please perform the following steps to give us a crash report ID that helps us find out more about the cause of the crash.

  1. On the keyboard, press [Windows] The image "Windows key" does not exist. + [R]. This should bring up a Run window that contains a text field.
  2. In that text field, type %APPDATA% and press Enter. An explorer window should open.
  3. From that explorer window, double-click on the Mozilla folder, then double-click on Firefox and then on Crash reports. Double-click on submitted.
  4. Now, you should see a list of files that contain reports. Go to View > Arrange Icons by > Modified to get the most recent files at the top of the window.
  5. Open the most recent 5 files with a text editor and copy the IDs.
  6. Paste each ID with bp- into the reply window on the forums.

Thanks in advance!

You can find more information and troubleshooting steps in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

more options

Wow Andrew thanks so much for the quick response and detailed directions! As you requested:

Crash ID: bp-ff0d5861-f040-47f5-95c8-bc5192160409 Crash ID: bp-24c40bed-96f8-4a90-9bd9-217f72160409 Crash ID: bp-894088ad-7dba-4fe8-a309-f49212160210 Crash ID: bp-5b671459-3033-4436-a2f5-58e3a2160122 Crash ID: bp-6abaf705-df6c-412a-8708-ee52b2160122

more options

Chosen Solution

Signature mozalloc_abort | NS_DebugBreak | ErrorLoadingBuiltinSheet

System Memory Use Percentage; 78

icudt56.dll = International Components for Unicode = The ICU Project

This is for Sumo's Related Bugs 1194856 ASSIGNED --- Startup crash in ErrorLoadingBuiltinSheet


Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac=Options)
key, and then starting Firefox. Is the problem still there?


If you have problems with current Shockwave Flash plugin versions then check this:

  • see if there are updates for your graphics drivers

https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration

  • disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later)

https://forums.adobe.com/message/4468493#TemporaryWorkaround

  • disable hardware acceleration in the Flash plugin

https://forums.adobe.com/thread/891337 See also:

more options

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac=Options)
key, and then starting Firefox. Is the problem still there?


THIS WORKED AND THE PROBLEM IS SOLVED. THANK YOU VERY MUCH!

more options

Safe Mode is a troubleshooting mode that temporarily turns off hardware acceleration, resets some settings, and disables add-ons (extensions and themes). If the problem goes away, that tells us one thing. If it does not, that tells us something else.

It could be the work of one of your add-ons. Type about:addons<enter> in the address bar to open your Add-ons Manager. Hot key; <Control>(Mac=<Command>)<Shift> A)

In the Add-ons Manager, on the left, select Extensions. Disable a few add-ons, then Restart Firefox.

Some added toolbar and anti-virus add-ons are known to cause Firefox issues. Disable All of them.

If the problem continues, disable some more (restarting FF). Continue until the problem is gone. After, you know what group is causing the issue. Re-enable the last group ONE AT A TIME (restarting FF) until the problem returns.

Once you think you found the problem, disable that and re-enable all the others, then restart again. Let us know who the suspect is detective.

more options

I am getting this today. Here are last 5 ids as requested:

Crash ID: bp-0e4ec8c7-3e2d-48d0-8968-d59102160913 Crash ID: bp-0ed5751c-bbbf-4f80-be4f-e38072160913 Crash ID: bp-1c220a8b-4d80-43b3-9ad4-b1bd52160913 Crash ID: bp-3f694c12-2b73-4a0d-b32a-78c662160913 Crash ID: bp-4d22ee03-d7a2-4f4b-8932-8514b2160913

more options

bp-0e4ec8c7-3e2d-48d0-8968-d59102160913

Signature: nsAtomicFileOutputStream::Write

AppMonitorDll32_00.dll = unknown

NamespaceToEvents32_00.dll = ? Namespace Provider = FireEye, Inc

sysfer.dll = Symantec CMC Firewall

IPSEng32.dll = Symantec Intrusion Detection

This is for Sumo's Related Bugs 1302343 NEW --- Startup crash in nsFileStreamBase::Write with Symantec/Norton ++++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-0ed5751c-bbbf-4f80-be4f-e38072160913

Signature: @0x1810f6ec

AppMonitorDll32_00.dll = unknown

NamespaceToEvents32_00.dll = ? Namespace Provider = FireEye, Inc

sysfer.dll = Symantec CMC Firewall

IPSEng32.dll = Symantec Intrusion Detection


Symantec/Norton just did an update and screwed something up. They are working on it.