Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Ky sajt do të funksionojë me kufizime, teksa bëjmë mirëmbajtjen e tij për të përmirësuar punën tuaj. Nëse një artikull nuk e zgjidh problemin tuaj dhe dëshironi të bëni një pyetje, kemi bashkësinë tonë të asistencës, e gatshme për t’ju ndihmuar, te @FirefoxSupport në Twitter dhe/r/firefox në Reddit.

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

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

  • 5 përgjigje
  • 1 e ka hasur këtë problem
  • 7 parje
  • Përgjigjja më e re nga 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.

Zgjidhje e zgjedhur

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.

Lexojeni këtë përgjigje brenda kontekstit 👍 0

Krejt Përgjigjet (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

Zgjidhja e Zgjedhur

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.