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.

Firefox crashes

  • 2 replies
  • 1 has this problem
  • 29 views
  • Last reply by FredMcD

evil.orange.peel
evil.orange.peel
more options

I'm at a loss, I've tried: Safe mode Profile refresh Deleting the profile Reinstalling Uninstalling/Reinstalling Uninstalling/Deleteing All mention of mozilla or firefox in the windows registry/Reinstalling Removing flash Disabling all antivirus, hips and firewall services Stopping any unrelated services Installing firefox 53.0.3 Running it in a sandbox Running it as administrator Running it with compatibility mode

No matter what it still just crashes directly after starting. I didnt even mess with it, I shut down my computer and was away for the weekend. When I came back this was happening.

Crash ID: bp-13f2235a-4c6c-4ebb-9365-1634f0170702 Crash ID: bp-15ff2342-431d-404e-a5cb-3a6c50170702 Crash ID: bp-190e0035-8c66-4353-969c-6041d1170702 Crash ID: bp-1d25d63c-79f8-4aef-bc8c-41a6c1170702 Crash ID: bp-208fad85-9077-48f0-97b0-3b47e1170702 Crash ID: bp-2650377b-2735-4bcc-88d5-5ae571170702 Crash ID: bp-2d885f8f-ad39-40ce-9835-5a7c71170702 Crash ID: bp-37abdc1d-a9a2-4dbd-8192-43e2f0170702 Crash ID: bp-39723e9a-214c-4928-a7d3-ed9be0170702 Crash ID: bp-3dc784f4-8190-4296-81a6-251100170702 Crash ID: bp-4155b239-3012-48df-a6fd-932f51170702 Crash ID: bp-44241589-9a35-48b0-91c8-e4f1f1170702 Crash ID: bp-4a162293-7030-4136-9b68-870971170702 Crash ID: bp-503e4e07-9987-478a-9bea-0188c1170702 Crash ID: bp-517d850a-c7f4-4c1f-b56b-0971c0170702 Crash ID: bp-66fc1982-e9d1-412e-8416-384bf1170702 Crash ID: bp-68193608-f857-4d2a-aad2-c96e11170702 Crash ID: bp-68df3533-1ce5-4ead-b383-5ac4e1170702 Crash ID: bp-8c93007b-7bb8-46f4-9538-ee9631170702 Crash ID: bp-93e0c30a-4ddc-41c7-8d82-cbde21170702 Crash ID: bp-9a2ffe0e-1fe4-4a88-923a-e0e5b1170702 Crash ID: bp-a8b2a1a6-225f-4ca2-b2d4-7036f1170702 Crash ID: bp-bedc8483-5f1e-442b-801d-8f6781170702 Crash ID: bp-c1c5db47-335c-4571-8d5a-535c31170702 Crash ID: bp-cd51bebd-4f79-45b1-bb2b-f7ddf0170702 Crash ID: bp-d13c3d53-156c-44f7-ae89-226631170702 Crash ID: bp-d32d6392-f252-4efc-9e30-3908a0170702 Crash ID: bp-dd002430-91c1-46ea-99be-201401170702 Crash ID: bp-ee5333a0-fe73-45f3-b074-9d8960170702 Crash ID: bp-f0d8c923-f22e-4a0a-b18e-0d8c71170702 Crash ID: bp-f1e5d76b-1ae8-49b7-af8f-e07341170702 Crash ID: bp-fe8e5609-ec1f-4cdb-9aa6-1d4ff1170702 Crash ID: bp-ff133365-2f90-4cfc-ae05-ac59b1170702

P.S. Your "Troubleshooting Information: Automatically Add" button on this page redirects to a "We couldn't fine the page your looking for", which caused me to loose the entire initial message I typed.

I'm at a loss, I've tried: Safe mode Profile refresh Deleting the profile Reinstalling Uninstalling/Reinstalling Uninstalling/Deleteing All mention of mozilla or firefox in the windows registry/Reinstalling Removing flash Disabling all antivirus, hips and firewall services Stopping any unrelated services Installing firefox 53.0.3 Running it in a sandbox Running it as administrator Running it with compatibility mode No matter what it still just crashes directly after starting. I didnt even mess with it, I shut down my computer and was away for the weekend. When I came back this was happening. Crash ID: bp-13f2235a-4c6c-4ebb-9365-1634f0170702 Crash ID: bp-15ff2342-431d-404e-a5cb-3a6c50170702 Crash ID: bp-190e0035-8c66-4353-969c-6041d1170702 Crash ID: bp-1d25d63c-79f8-4aef-bc8c-41a6c1170702 Crash ID: bp-208fad85-9077-48f0-97b0-3b47e1170702 Crash ID: bp-2650377b-2735-4bcc-88d5-5ae571170702 Crash ID: bp-2d885f8f-ad39-40ce-9835-5a7c71170702 Crash ID: bp-37abdc1d-a9a2-4dbd-8192-43e2f0170702 Crash ID: bp-39723e9a-214c-4928-a7d3-ed9be0170702 Crash ID: bp-3dc784f4-8190-4296-81a6-251100170702 Crash ID: bp-4155b239-3012-48df-a6fd-932f51170702 Crash ID: bp-44241589-9a35-48b0-91c8-e4f1f1170702 Crash ID: bp-4a162293-7030-4136-9b68-870971170702 Crash ID: bp-503e4e07-9987-478a-9bea-0188c1170702 Crash ID: bp-517d850a-c7f4-4c1f-b56b-0971c0170702 Crash ID: bp-66fc1982-e9d1-412e-8416-384bf1170702 Crash ID: bp-68193608-f857-4d2a-aad2-c96e11170702 Crash ID: bp-68df3533-1ce5-4ead-b383-5ac4e1170702 Crash ID: bp-8c93007b-7bb8-46f4-9538-ee9631170702 Crash ID: bp-93e0c30a-4ddc-41c7-8d82-cbde21170702 Crash ID: bp-9a2ffe0e-1fe4-4a88-923a-e0e5b1170702 Crash ID: bp-a8b2a1a6-225f-4ca2-b2d4-7036f1170702 Crash ID: bp-bedc8483-5f1e-442b-801d-8f6781170702 Crash ID: bp-c1c5db47-335c-4571-8d5a-535c31170702 Crash ID: bp-cd51bebd-4f79-45b1-bb2b-f7ddf0170702 Crash ID: bp-d13c3d53-156c-44f7-ae89-226631170702 Crash ID: bp-d32d6392-f252-4efc-9e30-3908a0170702 Crash ID: bp-dd002430-91c1-46ea-99be-201401170702 Crash ID: bp-ee5333a0-fe73-45f3-b074-9d8960170702 Crash ID: bp-f0d8c923-f22e-4a0a-b18e-0d8c71170702 Crash ID: bp-f1e5d76b-1ae8-49b7-af8f-e07341170702 Crash ID: bp-fe8e5609-ec1f-4cdb-9aa6-1d4ff1170702 Crash ID: bp-ff133365-2f90-4cfc-ae05-ac59b1170702 P.S. Your "Troubleshooting Information: Automatically Add" button on this page redirects to a "We couldn't fine the page your looking for", which caused me to loose the entire initial message I typed.

Chosen solution

cmdshim32.dll = COMODO Internet Security 29Jun 17 This reported issue is caused by incompatibility with Microsoft Windows update KB4022716. Comodo teams is working over the fix. Dates of the Hotfix releases will be published later this week. Till that Hotfixes we strongly recommend users to not install mentioned Windows update KB4022716.

Read this answer in context 👍 0

All Replies (2)

evil.orange.peel
evil.orange.peel Question owner
more options

Just realized this is related to https://bugzilla.mozilla.org/show_bug.cgi?id=1376831 I'm the future it might help if I knew I could view https://crash-stats.mozilla.com/report/index/bp-13f2235a-4c6c-4ebb-9365-1634f0170702

FredMcD
FredMcD
more options

Chosen Solution

cmdshim32.dll = COMODO Internet Security 29Jun 17 This reported issue is caused by incompatibility with Microsoft Windows update KB4022716. Comodo teams is working over the fix. Dates of the Hotfix releases will be published later this week. Till that Hotfixes we strongly recommend users to not install mentioned Windows update KB4022716.