Firefox 28 with EMET 4.1
Recently added EMET 4.1 to my PC [Win 7 Home SP1] but having frequent FF28.0 crashes even after applying all .NET 4.0 Windows updates. Some are identified specifically as DEP errors by EMET. The best I am able to do is use FF safe mode with EMET on [except DEP] or turn off all EMET protection except SEHOP & NUL page protection. Been experimenting with turning on/off FF add-ons and EMET options individually but everytime I get a configuration I think works, another crash occurs. What configurations of EMET are folks having success with? FF addons include Foxit Reader, Google Talk, Google Update, Intel Identity Protection & Flash. I want to get one PC solid before adding FF to EMET on my other PCs. Machine has been full scanned for viruses, etc in the past few days.
All Replies (6)
I don't think forum users have a lot of experience with EMET. Here are a few threads I found in a search (earlier versions of EMET, probably).
Firefox 18 user reported success: Are there caveats associated with adding firefox.exe into Microsoft Enhanced Mitigagation Toolkit(EMET) ?
Firefox 25-26 user reported crashes: firefox 25 to 26 has been crashing on my laptop
Firefox Nightly (future version 30) tester had to disable "deep hooks" mitigation: Nightly crashing on start
Thank you for your input. I thought this might be a "straight forward" thing to do as the EMET documentation claims to be fully compatible with FF [but it does not specify which version[s]. Many of the crashes have to do with plug in container so I suspect a plug in conflict. I am still experimenting and, as suggested in another post I read earlier today, I have just updated my video drivers from the Intel website. I will keep at it as time permits to see if I can find compatible settings. Right now I have all addons enabled in FF and only have SEHOP and NUL page pre-allocation selected in EMET and all seems well [fingers crossed].
Here's all the crash reports that I've submitted in the past 2 days. Others were not submitted.
bp-973b1c38-e735-4ffb-b9e1-1cb6d2140403 4/3/2014 8:25 AM bp-ee7fd86c-baf6-43c5-98c8-155172140403 4/3/2014 8:03 AM bp-0afe587b-3915-45de-8cc1-545192140403 4/3/2014 7:58 AM bp-ae557f6c-91eb-46be-b1f7-888632140403 4/3/2014 7:23 AM bp-d1f64e9c-ea86-4ad2-b7e4-36abe2140402 4/2/2014 4:02 PM bp-1677f485-859f-47f7-b6e3-362bf2140402 4/2/2014 3:47 PM bp-bd78bb8c-82a5-480f-a412-67b672140402 4/2/2014 3:42 PM bp-e26941b4-68da-4809-9c2a-b8ed22140402 4/2/2014 3:42 PM bp-412982fd-f7a7-48a3-9e34-cb5652140402 4/2/2014 10:21 AM bp-e50764a2-deed-47b4-8195-ffa7b2140402 4/2/2014 10:19 AM bp-0546c49d-8518-459a-8dee-f2aad2140402 4/2/2014 10:04 AM bp-cfad22b4-3a83-4cec-bd35-735572140402 4/2/2014 8:23 AM bp-b2a366cb-9a61-49ae-9395-4feaa2140402 4/2/2014 8:20 AM bp-1ac8eff9-3aa5-4582-a122-5afc82140402 4/1/2014 9:08 PM
Modified by cor-el
The first 4 of those (starting from the top) reference LoadRemoteLibraryAndGetAddress which seems to be part of the crash reporter. Probably something crashed Firefox earlier that caused the crash reporter to display, but I don't have the expertise to see what happened there.
When I link over to the database of other crash reports, only one other comment is shown: "New Yahoo toolbar has been installed; now firefox is crashing." I don't think that is relevant to your configuration.
Hello. If you still have the problem try disabling EAF mitigation on plugin-container.exe
Thanks but still no joy. My firefox.exe settings in EMET work fine so long as I only have SEHOP and NUL Page Prealloc checked & NOTHING ELSE. Plugin-container is not listed at all in EMET. If I check any other mitigations, I get Firefox crashes [either Firefox directly or plugin-container]. Decided to settle for some protection rather than nothing but too bad FF isn't fully compatible. Maybe in the future? Working with Linux now....maybe things will be better over there!