Join the AMA (Ask Me Anything) with Firefox leadership team to talk about Firefox priorities in 2024. Mark your calendar! Thursday, June 13, 17:00 - 19:00 UTC.

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Learn More

Firefox crashes

  • 2 одговорa
  • 1 има овај проблем
  • 1 преглед
  • Последњи одговор послао Shadow110

more options

every time i opened Firefox it crashing and even in safe mode also it's crashing

Crash ID: bp-9dbe85ed-d37a-419f-a8e7-8cc9e1171120

every time i opened Firefox it crashing and even in safe mode also it's crashing Crash ID: bp-9dbe85ed-d37a-419f-a8e7-8cc9e1171120

Сви одговори (2)

more options

你尝试将 Firefox卸载了,重新安装Firefox

more options

EXCEPTION_BREAKPOINT crash is related to Video Card Drivers.

Please Update you Video Card Drivers.

I have information that would have been here if you had turned on send info to Mozilla before posting.

Could you go to the Firefox Menu Bar then--> Help --> Troubleshooting Information and copy the contents of that page and paste them here into a reply on the forum. Please take a look in the Accessibility Section if Accessibility is set to "True" there.

If yes, can you please Copy/Paste this whole section into a reply in the forum and see if the following fixes the performance problem: Go to the Firefox 3 Bar Menu --> Options --> Privacy & Security then under Permissions check the setting to prevent Accessibility Services from accessing your browser.

You will find info on your Video Card here if you do now know it. No need to send report.

If still having issues after updating Drivers please move to The Extended Release Version as system is to old : 52.5.0 ESR. It will continue to get security updates until May 2018, and you can download and install it from this page: https://www.mozilla.org/en-US/firefox/organizations/all/ Note : Legacy Extensions will be deleted or removed in any version update after May 2018.

Please let us know if this solved your issue or if need further assistance.