Emsisoft Antimalware causing Firefox Application Error!

[Amit]

Hi,

After closing Firefox a small window appears with the title saying firefox.exe - Application Error.

If I click OK the appears again, and again and again. No matter how much I click OK or try to Exit the window it just will not go away.

The window says, The intruction at "0x1fb37800" referenced memory at "0x1fb37800". The memory could not be "read".

Click on OK to terminate the program"

And this happens particularly after installing Emsisoft Antimalware. I tried it twice and can confirm that the problem does appears after installing EAM.

Please kindly help me.

Best Wishes,
ams963

[Thankful]

Best place to post:
http://support.emsisoft.com/forum/52...-anti-malware/

[1chaoticadult]

Or post in this thread http://www.wilderssecurity.com/showthread.php?t=309241

[markusg]

or send mail to:
helpdesk@emsisoft.com

[zerotox]

Originally Posted by ams963

Hi,

After closing Firefox a small window appears with the title saying firefox.exe - Application Error.

If I click OK the appears again, and again and again. No matter how much I click OK or try to Exit the window it just will not go away.

The window says, The intruction at "0x1fb37800" referenced memory at "0x1fb37800". The memory could not be "read".

Click on OK to terminate the program"

And this happens particularly after installing Emsisoft Antimalware. I tried it twice and can confirm that the problem does appears after installing EAM.

Please kindly help me.

Best Wishes,
ams963

I found what can solve (at least temporarily) the problem. I know you-re using EAM together with WSA. This causes a conflict, I'm with the same combo at the moment and had the same error on closing Firefox. When I shut down temporarily WSA, there were no more errors. Then I did something else - enabled WSA but on the Identity/Privacy button, then View/Edit protected applications, I put the check for Firefox to allow instead of protect and the problem is solved. I know that this lowers the security scope of WSA protecting sensitive info but for now this is the solution for me. The faulting module of the Firefox error though belongs to EAM - it is a2hooks32.dll, belonging to the behavior blocker part (you can see it in the Event viewer). May be it is overkill 2 behaviour blocking applications monitoring firefox at once.

P.S. I found a better solution (protection-wise I think). Enabled again the protected mode for Firefox in WSA Identity/Privacy protection and excluded Firefox in EAM behaviour blocker guard by adding it manually. No more errors for the time-being.

[Brummelchen]

WSA means what?
http://www.abbreviations.com/WSA

[G1111]

Originally Posted by Brummelchen

WSA means what?
http://www.abbreviations.com/WSA

Webroot SecureAnywhere

[whitedragon551]

WSA is Webroot Security Anywhere.

Pick one (EAM or WSA) and stick with it. Dont use 2 real time. If you want the online protection in browser go with PrevX SafeOnline from their Facebook offer.

[zerotox]

Originally Posted by whitedragon551

WSA is Webroot Security Anywhere.

Pick one (EAM or WSA) and stick with it. Dont use 2 real time. If you want the online protection in browser go with PrevX SafeOnline from their Facebook offer.

At the moment they are working perfectly together. If I want less overheat, I'll set EAM to check files on execute only.
Anyway I don't see why NIS 2012 or NOD32 should work OK together with WSA and EAM wouldn't.

[Brummelchen]

Pick one (EAM or WSA) and stick with it. Dont use 2 real time.

+1

thats the main rule whatever single experience will tell.
at least both will fail and crying for help will come.

the point is that those users didnt had any issue where normal way of infection
was passed. any actual av can handle the most of malware, but not the
newerly infections or most of the 15.000 daily variations of it.
so behavior blocker, cloud or sandboxes ar THE upcoming features.
and those ones need solely access to work properly.

[Coresix]

I had the same issue and through a bit of problem solving I found that what was causing the error was a conflict between the Identity Protection with WRSA and Emsisoft -- the faulting module was A2hooks.dll. I had to turn it off for Firefox for the time being. I'm pretty sure both companies know about it.

-Coresix

[Cutting_Edgetech]

I have a problem on XP Pro x 32 right now with Online Armor Premium causing an application error in Firefox as well. It said something about Firefox not being able to read from memory. I checked my RAM, and it all tested ok. If i shut down OA then I don't have this problem. Hopefully it will be fixed in an upcoming build soon.

[Amit]

Thank you all for your suggestions, assurance and all the help. I really appreciate it.

Fabian Wosar at the Emsisoft Forum was able to replicate the problem and solved it immediately. The solution is in the beta update right now. http://support.emsisoft.com/topic/77...ication-error/

No more application error, yay

[Amit]

Originally Posted by Coresix

I had the same issue and through a bit of problem solving I found that what was causing the error was a conflict between the Identity Protection with WRSA and Emsisoft -- the faulting module was A2hooks.dll. I had to turn it off for Firefox for the time being. I'm pretty sure both companies know about it.

-Coresix

ah! I see. Thank you for the assurance. Both companies know about it now. I've informed Joe and he is well aware though Emsisoft already fixed it.

[Amit]

Originally Posted by Cutting_Edgetech

I have a problem on XP Pro x 32 right now with Online Armor Premium causing an application error in Firefox as well. It said something about Firefox not being able to read from memory. I checked my RAM, and it all tested ok. If i shut down OA then I don't have this problem. Hopefully it will be fixed in an upcoming build soon.

oh! OA causing as well?.....are you using OA with WSA also in that PC?....

Originally Posted by Cutting_Edgetech

Hopefully it will be fixed in an upcoming build soon.

not unless you report it to Emsisoft......go to the forum and ask to fix the prob....

[Cutting_Edgetech]

Yep, I was using OA, and WSA together on that PC. I had to roll it back to an earlier image though now for beta testing purposes. I'm getting ready to see if the problem has been fixed in the latest beta. If it hasn't then I will send a ticket. I did not have time to report it at the time I discovered the bug.

[Amit]

Originally Posted by Cutting_Edgetech

Yep, I was using OA, and WSA together on that PC. I had to roll it back to an earlier image though now for beta testing purposes. I'm getting ready to see if the problem has been fixed in the latest beta. If it hasn't then I will send a ticket. I did not have time to report it at the time I discovered the bug.

great then....well don't forget to post here is the prob with OA & WSA still persists if and when you try them on your pc.....