We're Sorry Firefox had a problem and crashed.

We're Sorry

Firefox had a problem and crashed. We'll try to restore your tabs and windows when it restarts.

To help us diagnose and fix the problem, you can send us a crash report.

It happens CONTINUOUSLY.

Why?

I'm tired of signing into yahoo 50 times a day or here 30n times a day.........

Start here:

Standard diagnostic - Firefox - MozillaZine Knowledge Base

Is this a clean install or an update of Windows 10? One thing you can try if it's an update is to uninstall Firefox and then reinstall it from the latest installer. Might correct whatever is wrong.

@Notmyself: Thanks. I didn't find that when I tried a google lol. I did the first thing first and I'll see how it works and then try other steps if needed. That was just what I was looking for.
@thunderclap: It's a new install from disc on a new HDD. I already uninstalled/re-installed it once. It worked for a little bit and then gave the error message again. Thanks for the advise though.

Not overly likely under the circumstances, but you may still have a problem that the procedure for which I provided a link may help. Depending upon what changes you may have made to the Fx profile, such as adding extensions, something may have gone astray.

The testing does not take long, but may not find anything. I was waiting for the result of your testing before suggesting the next step, but here it is:

1. Go to Index page mozillaZine blog and register, as you have to be a member to post in all but one of two of the blog on that site.

2. When ready, go to the first Forum, and start a new thread, with a meaningful title. Add a short text, explaining what you had done so far, such as the testing I wrote about.

3. Before submitting the message, in the Fx URL box, type "about:crashes" without the quotation marks. (I am assuming that Fx created crash reports, which does not always happen.) If there are any entries, then copy a few of the latest crash report numbers, NOT the text of the reports, which some people do. If there are no reports, end your text with that information. If there are reports, they will be looked at by some of the mozillaZine experts (and there actually are people there who qualify as such,) who may be able to pinpoint what is causing the problem(s).

Thanks for all your help. It's still buggy so I have to complete the remaining steps. I'm remodeling my house right now so my time to fix this is limited.

When I complete the steps as you outlined, I'll let you know how it turned out. I know how frustrating it can be to help someone and then never hear if it worked or not lol.

Thanks for all your help. It's still buggy so I have to complete the remaining steps. I'm remodeling my house right now so my time to fix this is limited.

When I complete the steps as you outlined, I'll let you know how it turned out. I know how frustrating it can be to help someone and then never hear if it worked or not lol.

You are welcome; in return, thanks for realizing that, yes, it is frustrating to not find out the result. The other thing people do all too often, and for some reason I see it all too often on mozillaZine, is to post the result. "I solved it,' with no explanation whatsoever as to how it was solved. Doing that means that no one else can possibly benefit from the solution.

Well this is anti climatic. When I saw the new update for Firefox, 39.0.3 I installed it and SO FAR (it's only been an hour or so) I haven't gotten that message. If it's still good tomorrow, I'll declare it was Firefox and they fixed it with the updated lol.

Well this is anti climatic. When I saw the new update for Firefox, 39.0.3 I installed it and SO FAR (it's only been an hour or so) I haven't gotten that message. If it's still good tomorrow, I'll declare it was Firefox and they fixed it with the updated lol.

Possible, but rather unlikely, as the only change, as far as is known publicly, from 39.02 to 39.03 was a security update for a zero-day flaw.

Firefox exploit found in the wild | Mozilla Security Blog

Well that's all good and cool lol, but the fact remains that as of now I have NOT had the Firefox crash issue since I upgraded.

Of course it's not like MS has hated Firefox since their inception. Firefox was for years about the only decent alternative to IE and MS has sabotaged it in EVERY release of a new OS...... allegedly of course. Bite the hand that feeds and one finds oneself banned lol.

I'm sure it was because the pesky Russians were searching for an exploit, using of course their new brothers the Ukrainians, that would allow them to conquer the world through my computer. Firefox working in Windows 10 after being sabotaged for the first few days, was just a coincidence. As was Firefox being sabotaged........

Edit: If I STILL haven't crashed this time tomorrow lol, I'm calling it solved and the update the cause.