X
Tap here to go to the mobile version of the site.
Your Firefox is out of date and may contain a security risk! Upgrade Firefox

Support Forum

FF23.0.1 crashing. Can't fix. FF24 works

Posted

I was using 23.0.1 because GIFs play too fast in FF24, which is a WHOOOLE other issue I'm trying to figure out.

Anyways Suddenly FF23.0.1 crashed. I closed it, reopened, crashed. Reinstalled, crashed. Uninstalled, restarted, installed, crashed.

Using Win7 It gives this error message:

Error message is this: Problem signature: Problem Event Name: APPCRASH Application Name: firefox.exe Application Version: 23.0.1.4974 Application Timestamp: 520bc252 Fault Module Name: ntdll.dll Fault Module Version: 6.1.7601.18229 Fault Module Timestamp: 51fb1072 Exception Code: c0000005 Exception Offset: 0002e04e OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 4105 Additional Information 1: e8ad Additional Information 2: e8adce1c2b9e7be834b4063ac3c53863 Additional Information 3: e8ad Additional Information 4: e8adce1c2b9e7be834b4063ac3c53863

Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt

HALP!

Chosen solution

This error:

Fault Module Name: ntdll.dll

Is the Nvidia driver. The driver needed to be updated.

23 can now be opened.

Read this answer in context 0

Additional System Details

Installed Plug-ins

  • Google Update
  • Shockwave Flash 11.8 r800
  • Next Generation Java Plug-in 10.25.2 for Mozilla browsers
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • iTunes Detector Plug-in
  • Adobe PDF Plug-In For Firefox and Netscape 10.1.8
  • DivX Web Player version 3.0.0.155
  • McAfee MSC FF plugin DLL
  • NVIDIA 3D Vision plugin for Mozilla browsers
  • NVIDIA 3D Vision Streaming plugin for Mozilla browsers
  • 5.1.20513.0
  • McAfee MSS+ NPAPI Plugin
  • SiteAdvisor
  • Intel web components updater - Installs and updates the Intel web components
  • Intel web components for Intel® Identity Protection Technology
  • DivX VOD Helper Plug-in
  • NPWLPG
  • The plug-in allows you to open and edit files using Microsoft Office applications
  • Office Authorization plug-in for NPAPI browsers

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0

More Information

Andrew
  • Top 25 Contributor
  • Moderator
251 solutions 3015 answers

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. Press the following shortcut to get a Run window: [Windows] + [R]. This should bring up a window that contains a text field.
  2. In that text field, enter %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 Firefox crashes - Troubleshoot, prevent and get help fixing crashes article.

cor-el
  • Top 10 Contributor
  • Moderator
10738 solutions 96602 answers

Try to disable hardware acceleration in Firefox.

Question owner

I opened that and there is only one crash report at 27-09-2013 10:36pm. So I reinstalled FF23.0.1 and opened to crash, which it did and the AppData is unchanged.

So I'm back on FF24, the AppData is still unchanged but reads as this.

  • Note 27-09-2013 10:36pm is probably when the first crash happened.

So format is File Name | Date Modified :: CODE IN FILE WHEN OPENED WITH NOTEPAD

LastCrash | 27-09-2013 10:36 PM :: 1380335807

Submit | 25-09-2013 11:26 PM :: [EMPTY TXT DOC]

InstallTime20130910160258 | 18-09-2013 11:23 AM :: 1379517792

InstallTime20130814063821 | 1409-2013 12:07 PM :: 1379174864

pending [folder] | 27-09-2013 10:36 PM :: [EMPTY]

Question owner

OK, I did that in FF24 which I'm using now. Uninstalled Installed FF23.0.1 It still won't open, it just crashes.

Back on FF24. I don't think I can adjust those settings since it will not open. It only crashes

Andrew
  • Top 25 Contributor
  • Moderator
251 solutions 3015 answers

Could you please provide the crash id? This will help us to serve you better.

cor-el
  • Top 10 Contributor
  • Moderator
10738 solutions 96602 answers

You can use one of these to start Firefox in Safe Mode:

  • On Windows, hold down the Shift key while starting Firefox with a double-click on the Firefox desktop shortcut
  • On Mac, hold down the Options key while starting Firefox
  • Help > Restart with Add-ons Disabled

Helpful Reply

Was this not it? LastCrash | 27-09-2013 10:36 PM :: 1380335807

I replied to your post with everything in the AppData for Firefox
Andrew
  • Top 25 Contributor
  • Moderator
251 solutions 3015 answers

Helpful Reply

I asked you to paste each ID with bp- into the your reply here.

Question owner

Sorry! Is this how?

LastCrash | 27-09-2013 10:36 PM :: bp-1380335807

Submit | 25-09-2013 11:26 PM :: [EMPTY TXT DOC]

InstallTime20130910160258 | 18-09-2013 11:23 AM :: bp-1379517792

InstallTime20130814063821 | 1409-2013 12:07 PM :: bp-1379174864

pending [folder] | 27-09-2013 10:36 PM :: [EMPTY]

Question owner

I reinstalled 23.0.1 and opened it with Shift held down

It does not open, it just crashes. Same error message in the first post :\

Question owner

I saw another post wher a lady was helped out a few weeks ago and saw the bp- links she was requested to put down. However, no crash IDs like that exist in AppData so... these are the Windows ones

Additional Information 1: bp-e8ad Additional Information 2: bp-e8adce1c2b9e7be834b4063ac3c53863 Additional Information 3: bp-e8ad Additional Information 4: bp-e8adce1c2b9e7be834b4063ac3c53863

Attached is a pic of Firefox CrashReports and the one relevant file

cor-el
  • Top 10 Contributor
  • Moderator
10738 solutions 96602 answers

A number like 1380335807 is a Unix epoch string that specifies the date/time that the crash occurred (1380335807: Sat 28 Sep 2013 02:36:47:0 GMT).

If you can't open Firefox, see:

Question owner

Hi thanks! I was kind of waiting around for a reply.

about:crashes show 'No Submitted Crash Reports' also the text doc with 'submit' is a 0kb empty doc

i'm assuming this is because 23 crashed and could not be opened, so I installed 24, which i'm using right now, and has never crashed. probably erased the 23 data

23 can not be opened, only installed. so i doubt it can create a crash report. i have reinstalled it and it only crashed when opened

im going to try installing 23 on an external HD right now

Chosen Solution

This error:

Fault Module Name: ntdll.dll

Is the Nvidia driver. The driver needed to be updated.

23 can now be opened.

cor-el
  • Top 10 Contributor
  • Moderator
10738 solutions 96602 answers

NTDLL.dll is not the Nvidia driver (those files start with nv), but a Windows library file that contains kernel API code.

Question owner

Oh, interesting. On other forums they had NTDLL fault module under the same circumstances. Everyone concluded it had to do with the Nvidia driver. And more Google searches of 'ntdll.dll' yeilded forums with the same opinion.

The one user I was reading who was instructing others how to fix said they had to revert back to an older version of the driver to resolve.

I however updated the driver to the most current version which resolved the problem.

Is there anything that you think I should be concerned about?

cor-el
  • Top 10 Contributor
  • Moderator
10738 solutions 96602 answers

It is possible that a problem with the Nvidia driver causes a crash in the ntdll.dll library file, but other programs or a recent Windows update can cause this as well.

You can try to boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test to see if that helps.