Firefox crashes
Nightly crashes at start up. It says firefox is already running, you have to shut down session before starting another. I have checked the task manager to make sure it is not running first, still get same message. Last crash report is this, but I have uninstalled and reinstalled Nightly already. I have also Tried regular firefox with the same out come. ERROR=Crash ID: bp-fac7a40f-c2b6-4f4a-848a-2dbf40170430
Opaite Mbohovái (9)
Product Firefox Release Channel nightly Version 55.0a1 Build ID 20170410030221 OS Windows 7 OS Version 6.1.7601 Service Pack 1
bp-fac7a40f-c2b6-4f4a-848a-2dbf40170430 Signature: IPCError-browser | ShutDownKill
Attention Sumo's there are 20 related bug reports
igd10umd64.dll = used to handle the startup services of Immunet Virus Removal
Update Immunet Virus Removal. If there is still a problem, disable it.
Moambuepyre FredMcD rupive
Try to start Firefox with the about:blank page by creating a copy of the current Firefox desktop shortcut. Add a space and -url "about:blank" to the target field in the Properties.
Try to disable multi-process windows in Firefox to see if that has effect.
You can disable multi-process windows in Firefox by setting these prefs to false on the about:config page.
- browser.tabs.remote.autostart = false
- browser.tabs.remote.autostart.2 = false
You can open the about:config page: via the location/address bar. You can accept the warning and click "I'll be careful" to continue.
Moambuepyre cor-el rupive
FredMcD----- I don't what, Update Immunet Virus Removal, is but I have spy-bot and AVG showing no viruses. And I don't not know how to disable it. I looked for "igd10umd64.dll" everywhere in all systems, could not find it. Any further help in what I'm not understanding with this is WELCOME!
cor-el---- I inserted -url "about:blank" into the properties, must have done it wrong, wouldn't take it. Tried different ways with no success. I can not even start firefox (nightly). So no success with the about:config without a running browser. Good ideas, just couldn't implement them is all. Still have a DEAD FireFox...lol
FredMcD said
Update Immunet Virus Removal. If there is still a problem, disable it.
One of the programs flagged in the crash report is Immunet Virus Removal. My instruction above means you need to check for updates for it. If there is still a problem, disable it.
@drews1166 - can you please provide more recent crash reports? the one listed in your question is 2 weeks old and didn't happen on startup so it won't give much insight into the issue you're currently having. please also disregard the comment about igd10umd64.dll - it's part of your intel graphics driver and there's no indication that it would be part of the problem.
I haven't been able to start firefox to get a more recent report. Hince my problem. It just says firefox is already running, you have to shut down session before starting another. Thats where I am can start it, no broswer window, I've uninstalled it, cleaned up left overs, then a fresh install. Nothing different. I ran the new update once. Came back another day and no firefox. I even tried a regular firefox install. I guess firefox is a no go for me. It was my best browser up to this point.
next to the security software already in place, please run scans with various other security tools like the free version of malwarebytes, adwcleaner & eset online one-time scanner and see if this changes anything.
I have NO viruses. Have scanned drive from an independent source remove from computer, nothing clean drive... Firefox just sux I guess... THANX FOR ALL YOUR HELP!!
Hi drews1166 Firefox will work as expected for most of us.
As you are using Windows and have no working Firefox browser possibly you may wish to consider installing Firefox Portable, as a temporary solution. it is a third part build of Firefox and will install on to a HDD or a memory stick as an alternative and separate browser
- See https://portableapps.com/apps/internet/firefox_portable
- If you try that does it work without crashing?
You mentioned you tried regular Firefox with the same outcome. Would you be able to try that again and let us have a couple of the crash IDs if that crashes.