I've installed the latest version on a brand new W7 PC and FF keeps crashing.
This is a brand new PC with Windows 7 Pro. I've installed 38.0.5 and within the last 90 minutes FF has crashed 4 or 5 times. In fact when I sat down in front of the PC and started FF, it would start and the instant I moved the mouse or touched the keyboard, it would crash. I've rebooted the PC, Refreshed FF and am running the same add-ons as on my current PC (the one being replaced).
All Replies (12)
Hi, we're sorry to hear that your Firefox seems to be crashing when you open it. Please perform the following steps to give us a crash report ID that helps us find out more about the cause of the crash.
- On the keyboard, press [Windows] The image "Windows key" does not exist. + [R]. This should bring up a Run window that contains a text field.
- In that text field, type %APPDATA% and press Enter. An explorer window should open.
- From that explorer window, double-click on the Mozilla folder, then double-click on Firefox and then on Crash reports. Double-click on submitted.
- Now, you should see a list of files that contain reports. Go to View > Arrange Icons by > Modified to get the most recent files at the top of the window.
- Open the most recent 5 files with a text editor and copy the IDs.
- Paste each ID with bp- into the reply window on the forums.
Thanks in advance!
You can find more information and troubleshooting steps in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options) key, and then starting Firefox. Is the problem still there?
Crash ID: bp-50ebd5bf-1b7f-4dbf-9d32-bee902150618 Crash ID: bp-97deb149-c397-41d2-b247-1833d2150618 Crash ID: bp-97825df2-1c17-4bd8-90d0-9a3a62150618 Crash ID: bp-c96ec6e3-efd5-4a7f-91ea-302f72150618 Crash ID: bp-ce51b82d-0d61-42de-82c6-c79522150618
Congratulations on the new PC! Were you able to transfer over your old data successfully?
Your four most recent crash reports indicate you have extensions from LastPass and Webroot. In another thread, a user with that combination encountered incessant crashing when visiting YouTube (or perhaps any page with Flash media: https://support.mozilla.org/questions/1066740). I don't which makes more sense to disable for the time being, one of those extensions or the Shockwave Flash plugin, but I thought I would mention it in case you want to try something along those lines.
I meant to suggest starting in Firefox's Safe Mode. As you know, that's a standard diagnostic tool to deactivate extensions and some advanced features of Firefox. More info: Diagnose Firefox issues using Troubleshoot Mode.
If Firefox is not running: Hold down the Shift key when starting Firefox.
If Firefox is running: You can restart Firefox in Safe Mode using either:
- "3-bar" menu button > "?" button > Restart with Add-ons Disabled
- Help menu > Restart with Add-ons Disabled
and OK the restart.
Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).
I'm assuming Firefox will be more stable in Safe Mode. Then try setting Flash to Click-to-Play ("Ask to Activate"). This will delay Flash from starting on a page until you approve it.
To set "Ask to Activate", open the Add-ons page using either:
- Ctrl+Shift+a
- "3-bar" menu button (or Tools menu) > Add-ons
In the left column, click Plugins. Look for "Shockwave Flash" and change "Always Activate" to "Ask to Activate".
When you visit a site that wants to use the Flash, you should see a notification icon in the address bar and one of the following: a link in a black rectangle in the page or an infobar sliding down between the toolbar area and the page.
If you do not need Flash, you can ignore the notification(s). Anyway, this is to test whether Firefox will now start normally (not in Safe Mode) with Flash disabled.
Any difference?
Well, I've been logged to FF for about 30 minutes now and no problems. The PC had been rebooted and FF restarted due to a power outage after I sent the first query for help. I'll wait and see what happens tomorrow. I'm on USA EDT and it's now about 7:40PM.
After about another 30 minutes FF won't run for more than a minute before crashing. I'm running FF on my old PC with XP SP3 with the exact same configuration, same add-ons, etc. and don't have a problem. Is this a W7 issue?
I'm now running in Safe Mode and will let it sit for a while to see what happens.
jbacinti said
Is this a W7 issue?
I think it is premature to speculate, but certainly there are significant differences between Windows XP and Windows 7 in their security model that can lead to more/different memory access errors when programs do something considered suspicious.
The Shockwave Flash plugin also implements the protected mode feature on Windows 7 but not Windows XP. If the Safe Mode / disable Flash test yields positive results, we can return to that issue.
This is what I posted in the other post;
I think it's time to get tough. Download the current full installers for Webroot and Lastpass. Save them somewhere. Now, Totally uninstall both programs. After, reboot the computer. Then run a registry scanner/repair program. Reboot again. Note: DO NOT reinstall those programs at this time. Start Firefox normally. How is it doing?
LGG62 said
The Webroot and LastPass programs are legit, so I don’t know why they’re being flagged.
Before we can fix the problem, we need to find its source. By removing a suspect program, we know it is, or is not the root problem.
In the end, with both programs removed, Firefox started normally.
The problem it still being dealt with.
Modified
FredMcD,
Did as you suggested and FF seems to be behaving well. I'll use if without LastPass and Webroot today and see how it goes. I'll install one of them late today and watch again for a while. I really need Webroot but can get by for a while without LP although it's a great program and runs perfectly on my old XP machine.
jscher2000,
Haven't yet moved over much data but what I have moved seem to be OK. I have set Shockwave to only activate when asked by a site. Has been OK for about 90 minutes now.