We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

exception code 8xc0020043 then MS shuts down FF 17

  • 1 reply
  • 1 has this problem
  • 48 views
  • Last reply by LeoDV

LeoDV
LeoDV
more options

After updating from R16 through the update channel this problem has been consistent. It has never happened before with other releases. I will be surfing and then suddenly a popup appears indicating that the program has stopped working and that it has to be closed. I have since uninstalled FF and downloaded fresh from Mozilla and rebooted. The problem persists. FF version 17.0.0.4706

After updating from R16 through the update channel this problem has been consistent. It has never happened before with other releases. I will be surfing and then suddenly a popup appears indicating that the program has stopped working and that it has to be closed. I have since uninstalled FF and downloaded fresh from Mozilla and rebooted. The problem persists. FF version 17.0.0.4706

All Replies (1)

LeoDV
LeoDV Question owner
more options

Updated to 17.01 this morning and it completed the update successfully and my extensions were checked. Then I opened GMAIL and I got the MS popup that FF was no longer working and had to be shutdown. I took a look in the event viewer again and got a different exception code this time. Exception code 0xc0020043. RPCRT4.dll is still the faulting module. I have saved the entire event info to notepad, but I have no idea who to send it to. Can somebody tell if this would be useful information to someone at Mozilla.