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!

Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Firefox does not start, switches to safe mode, crashes.

  • 5 отговора
  • 1 има този проблем
  • 1 изглед
  • Последен отговор от FredMcD

more options

Running Windows 10. Starting Firefox results in a dialog: Firefox closed unexpectedly while starting. ..... If I select "Start in Safe Mode", I then get a crash dialog. Submitted the crash to Mozilla.

Here are some of the crash IDs that got submitted: Crash ID: bp-06614331-6a2d-4fa4-a399-0efb90201015 Crash ID: bp-06614331-6a2d-4fa4-a399-0efb90201015 Crash ID: bp-06614331-6a2d-4fa4-a399-0efb90201015

I am loathe to scrub it and start over - I will lose my bookmarks, my tab setup, and also my saved passwords.

Running Windows 10. Starting Firefox results in a dialog: Firefox closed unexpectedly while starting. ..... If I select "Start in Safe Mode", I then get a crash dialog. Submitted the crash to Mozilla. Here are some of the crash IDs that got submitted: Crash ID: bp-06614331-6a2d-4fa4-a399-0efb90201015 Crash ID: bp-06614331-6a2d-4fa4-a399-0efb90201015 Crash ID: bp-06614331-6a2d-4fa4-a399-0efb90201015 I am loathe to scrub it and start over - I will lose my bookmarks, my tab setup, and also my saved passwords.

Избрано решение

Thanks FredMcD

I checked my McAfee and it had no pending updates. Unfortunately, I cannot disable it - corporate controlled environment.

But Firefox seems to be back on its feet now. I rebooted my laptop a few times - it froze each time during Windows startup. Eventually, after a bunch of power cycles, it came up fine and then Firefox too started without issues. I have no idea what happened to the system but it appears to have gotten into a bad state that was rectified by all the restarts (I think 5 of them, in total).

I guess I'll chalk it up to cosmic rays or something <shrug>

Hmm.. how do I tag this as "not an issue"? I can't say "solved" because I have no idea how things got on track.

Прочетете този отговор в контекста 👍 0

Всички отговори (5)

more options

This was working fine earlier today - my laptop rebooted after a firmware upgrade and since then, Firefox cannot be started.

more options

Product Firefox Release Channel esr Version 78.3.1esr Build ID 20200929151419 (2020-09-29) Buildhub data OS Windows 10 OS Version 10.0.18363

bp-06614331-6a2d-4fa4-a399-0efb90201015 Signature: nsHtml5Module::GetStreamParserThread

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

EpMPApi.dll = McAfee Endpoint

more options

Update McAfee. If the problem continues, disable it.

more options

Избрано решение

Thanks FredMcD

I checked my McAfee and it had no pending updates. Unfortunately, I cannot disable it - corporate controlled environment.

But Firefox seems to be back on its feet now. I rebooted my laptop a few times - it froze each time during Windows startup. Eventually, after a bunch of power cycles, it came up fine and then Firefox too started without issues. I have no idea what happened to the system but it appears to have gotten into a bad state that was rectified by all the restarts (I think 5 of them, in total).

I guess I'll chalk it up to cosmic rays or something <shrug>

Hmm.. how do I tag this as "not an issue"? I can't say "solved" because I have no idea how things got on track.

more options

Please flag your last post as Solved Problem as this can help others with similar problems.

It's possible that the rebooting fixed the issue. Perhaps an update that got stuck.