Crashing on numerous websites
Got a new t470 Laptop (windows 10) and trying very unsuccessfully to use firefox. I had been using firefox for years on a W520 laptop.
I copied my profile over but that seems to crash all the time. Tried Refresh. Created a new profile. Downgraded to 32-bit firefox. Turned off Nod32 antivirus. Did a Malware scan. Tried safe-mode.
It seems that most of the pages causign crashes have video or audio, but sometimes I can see an advert starting and that crashes the browser.
The entire browser crashes and no problem reports are created. It does create a windows event log: Faulting application name: firefox.exe, version: 55.0.3.6445, time stamp: 0x599ed78a Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x802f667e Exception code: 0xc0000374 Fault offset: 0x000d9aba Faulting process id: 0x3964 Faulting application start time: 0x01d33250611c01ed Faulting application path: C:\Program Files (x86)\Mozilla Firefox\firefox.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 2915c56c-8e9b-45f1-bf14-e57634308cec Faulting package full name: Faulting package-relative application ID:
At my wits end on this one. Do not want to move to chrome, but this horrible instability may force me into a corner.
Alle Antworten (11)
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
The crash report is several pages of data. We need the report numbers to see the whole report.
- Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
- Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
As I mentioned, there are no crash reports created when this occurs. The entire browser crashes and the only information I have is from the windwos event log.
See if this helps; This is not a cure, but should let the web page load without crashing.
Flash block {web link} Never be annoyed by a Flash animation again! Blocks Flash so it won't get in your way, but if you want to see it, just click on it
Flash Block helps, but I still get full crashes. Any other suggestions?
Post the crash reports.
Unfortunately, there are no firefox crash reports created when this occurs. I only get two windows eventlog entries:
1) Event ID 1000 Faulting application name: firefox.exe, version: 55.0.3.6445, time stamp: 0x599ed78a Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x802f667e Exception code: 0xc0000374 Fault offset: 0x000d9aba Faulting process id: 0x3f20 Faulting application start time: 0x01d333ca996a28a2 Faulting application path: C:\Program Files (x86)\Mozilla Firefox\firefox.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 7d8bb5b2-d94d-40e4-87fa-f20acd932648 Faulting package full name: Faulting package-relative application ID:
and 2) Event 1001 Fault bucket 109136239576, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0
Problem signature: P1: firefox.exe P2: 55.0.3.6445 P3: 599ed78a P4: StackHash_a0b2 P5: 10.0.15063.608 P6: 802f667e P7: c0000374 P8: PCH_D2_FROM_ntdll+0x000722CC P9: P10:
Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D54.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F0B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F0A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F1A.tmp.txt
These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_firefox.exe_5cd8ceeedc7e31c446fa4812bf8ad45a48d75e18_1b22b5b5_0406d98e
Analysis symbol: Rechecking for solution: 0 Report Id: 7d8bb5b2-d94d-40e4-87fa-f20acd932648 Report Status: 268435456 Hashed bucket: 11c643110ceebd407910f15308695c95
I got two crash reports but the symptoms were not the same. I did not get the "firefox has stopped working" windows prompt.
bp-145f4527-ef83-4aa3-bed1-3533d0170922 bp-a366610e-e736-4660-bf3f-14d201170922
Tachikomad said
Faulting module name: ntdll.dll, version: 10.0.15063.608
ntdll.dll = Microsoft
Perform a System File Check to fix corrupted system files
Win 7, 8, 10, Vista: https://support.microsoft.com/en-us/kb/929833 Win XP: https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/system_file_checker.mspx?mfr=true
Wiki - Windows 10 System File Check http://answers.microsoft.com/en-us/windows/wiki/windows_10-update/system-file-check-sfc-scan-and-repair-system-files/bc609315-da1f-4775-812c-695b60477a93
Product Firefox Release Channel release Version 55.0.3 Build ID 20170824053622 OS Windows 10 OS Version 10.0.15063
bp-145f4527-ef83-4aa3-bed1-3533d0170922 bp-a366610e-e736-4660-bf3f-14d201170922
Signature: eplgfirefox.dll@0x1c37
eplgFirefox.dll = ESET
Update ESET. If the problem continues, disable it.
Sorry for the delay in the response. I seem to have found the culprit. I use the Plantronics DA45 USB headset adapter for my VOIP headset. The crashes ONLY occur when I have this adapter plugged in and they ONLY occur in firefox. I can browse all the same sites with Chrome or Edge without crashing.
Are there any troubleshooting steps or options that might fix this incompatibility issue?
First, thank you so much for chasing that down.
Other users have mentioned crashes from time to time related to audio devices such as bluetooth headsets, but more in the context of a device that was removed (Firefox looked for it and couldn't live without it?) rather than a device that is present.
Is this a once-and-one problem where Firefox will crash after a device change and then work fine until the next device change, or it just seems to be totally incompatible with your headset adapter?
Since the Mozilla Crash Reporter is unable to intercept, it's hard to tell whether this is related to other headset-related crash bugs already on file. Looking at those, it does not appear that a solution is imminent.
- Crash in mozilla::widget::AudioSession::OnSessionDisconnectedInternal
- crash in MMDevAPI.dll when inserting or removing a usb headset
See also: