Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

firefox crashes in safe mode

  • 5 antwoorden
  • 4 hebben dit probleem
  • 4 weergaven
  • Laatste antwoord van Volleyjosh

more options

Firefox updated to a new version (firefox.exe is 16.0.2, but dated 11/12/2012, today is 11/29/2012) and now crashes in normal,safe and -profile mode. I have many crash dump ID's, i've put the most recent two into the Troubleshooting information.

Firefox updated to a new version (firefox.exe is 16.0.2, but dated 11/12/2012, today is 11/29/2012) and now crashes in normal,safe and -profile mode. I have many crash dump ID's, i've put the most recent two into the Troubleshooting information.

Bewerkt door Volleyjosh op

Gekozen oplossing

Update Firefox to 17.0.1 (releasing later today) Update Firefox to the latest release

Then try to retest.

Dit antwoord in context lezen 👍 2

Alle antwoorden (5)

more options

Gekozen oplossing

Update Firefox to 17.0.1 (releasing later today) Update Firefox to the latest release

Then try to retest.

more options

Disable hardware acceleration.... Intructions here: https://support.mozilla.org/en-US/kb/forum-response-disable-hardware-acceleration

Bug info here: https://bugzilla.mozilla.org/show_bug.cgi?id=700840 <p> From that page: "The user disabled the Hardware Acceleration in Firefox and the issue seemed to be gone. His computer has Nvidia SLI technology (Q6600, Win 7 x64 and SLI of GTX460), surely the culprit..."

more options

That bug is totally different than the crash ID's the user gave. Disabling Hardware Acceleration may be useful, but that bug report is wrong.

more options

Ofcourse the crash ID is different What do you mean the bug report is wrong? Same crash reason, same operating system.

more options

Newest version fixed the issue. Thanks!