Firefox crashes often, report example inside
Hi, firefox has been crashing a lot for the past few weeks and I've tried just about everything.
I've tried running it in firefox safe mode, I've tried reinstalling, I've tried Malwarebytes, superantispyware, AVG, Housecall, TDSS Killer (malware bytes found two trojan agents, but that didn't resolve the problem) I've tried doing virus scans in safe mode, I've even reset my whole machine to factory settings.
https://crash-stats.mozilla.com/report/index/da09d95d-9289-45fe-a6da-769ca2130810
Here's the latest report. Any ideas? I'm guessing from the lengths I've gone to with antiviruses that isn't the problem...
Всички отговори (8)
We are aware of this issue and is being tracked: here. IMPORTANT: DO NOT COMMENT IN THE BUG... IF YOU HAVE SOMETHING TO ADD, POST IT HERE AND WE'LL ADD IT TO THE BUG FOR YOU.
Please also try to download all windows updates available to see if it helps.
Променено на от Andrew
https://crash-stats.mozilla.com/report/index/39ff6f3d-b77c-4a25-ab5e-22ff72130810
I also got this one shortly after.
what does it mean by EXCEPTION_ACCESS_VIOLATION
It shows up on most of the reports.
The crash link you just provided relates to the same bug. Could you provide the crash id for the crash with the signature "EXCEPTION_ACCESS_VIOLATION "?
That was it, it was the reason given in the report.
Sometimes it says READ after violation, other times WRITE. I know nothing about coding of course, but those two love to pop up.
Oh, and one final report I guess.
https://crash-stats.mozilla.com/report/index/4f8e7b4f-c10c-4dda-8525-2cd152130810
Not sure if its any use to you, but this time it was in safe mode.
Your crash seems to be caused by a Internet Explorer update.
You could try to modify the connection settings.
- Tools > Options > Advanced > Network : Connection > Settings
- https://support.mozilla.org/kb/Options+window+-+Advanced+panel
If you do not need to use a proxy to connect to internet then try to select "No Proxy".
See "Firefox connection settings":
The crash being caused by an IE update makes sense when I think about it, the problems did start just after a large update.