Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

more options

Random FireFox crashes daily, sometimes multiple times daily. Updated FF, ran in safe mode, reset FF, full uninstall and reinstall. Windows 7 x64.


From Windows Event Log: - System

 - Provider 
  [ Name]  Application Hang 

 - EventID 1002 
  [ Qualifiers]  0 

  Level 2 

  Task 101 

  Keywords 0x80000000000000 

 - TimeCreated 
  [ SystemTime]  2014-01-21T22:17:44.000000000Z 

  EventRecordID 234910 

  Channel Application 

  Computer LAPTOP-FREEMANW.stanford.edu 

  Security 

- EventData

  firefox.exe 
  26.0.0.5087 
  1d9c 
  01cf16ca180b2121 
  125 
  C:\Program Files (x86)\Mozilla Firefox\firefox.exe 
  d260cacf-82e9-11e3-98d4-b00594f73334 
  55006E006B006E006F0077006E0000000000 



Binary data:


In Words

0000: 006E0055 006E006B 0077006F 0000006E 0008: 0000


In Bytes

0000: 55 00 6E 00 6B 00 6E 00 U.n.k.n. 0008: 6F 00 77 00 6E 00 00 00 o.w.n... 0010: 00 00 ..

Random FireFox crashes daily, sometimes multiple times daily. Updated FF, ran in safe mode, reset FF, full uninstall and reinstall. Windows 7 x64. From Windows Event Log: - System - Provider [ Name] Application Hang - EventID 1002 [ Qualifiers] 0 Level 2 Task 101 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2014-01-21T22:17:44.000000000Z EventRecordID 234910 Channel Application Computer LAPTOP-FREEMANW.stanford.edu Security - EventData firefox.exe 26.0.0.5087 1d9c 01cf16ca180b2121 125 C:\Program Files (x86)\Mozilla Firefox\firefox.exe d260cacf-82e9-11e3-98d4-b00594f73334 55006E006B006E006F0077006E0000000000 -------------------------------------------------------------------------------- Binary data: In Words 0000: 006E0055 006E006B 0077006F 0000006E 0008: 0000 In Bytes 0000: 55 00 6E 00 6B 00 6E 00 U.n.k.n. 0008: 6F 00 77 00 6E 00 00 00 o.w.n... 0010: 00 00 ..

All Replies (3)

more options

Have you disabled the Shockwave Flash plugin as part of your diagnosis? Very thorough.

Are you getting any of the Mozilla Crash Reporter dialogs, or are you only getting dialogs from Windows, or is Firefox hanging and requiring you to "kill" it?

When Firefox crashes rather than being terminated externally, it usually records information about what was happening at that moment. You can submit that data to Mozilla and share it with forum volunteers to see whether it points to the solution. Please check the support article "Firefox Crashes" (especially the last section) for steps to get those crash IDs, and then post some of the recent ones here.

Also, could you try disabling Firefox's use of hardware acceleration for graphics? This feature is sensitive to graphics card driver changes and incompatibilities can cause symptoms from display aberrations to blue screen crashes. I don't know whether this is relevant in your case, but it's worth a try.

orange Firefox button (or Tools menu) > Options > Advanced

On the "General" mini-tab, uncheck the box for "Use hardware acceleration when available"

This will take effect after you exit and restart Firefox.

more options

I've disabled hardware acceleration and just removed Shockwave.

The most recent crash dump is Crash ID: bp-37b441d3-0742-4922-8bdc-4dc1a2140131

more options

Hi ResolverBob, thanks for the new crash report.

I don't understand most of it, but "oom" indicates an Out of Memory condition, and the report shows that physical memory was 90% full. If you typically keep over 100 tabs open, you may be pushing the limits of Firefox's ability to use memory. Or you may have found a site that exposes a problem in Firefox's ability to properly manage memory. I don't have any specific recommendations on this one.