We're Sorry Firefox had a problem and crashed.

Well that was a bust. Still doing it.

YOU WERE RIGHT NOT MYSELF lol.

Well back to the other fixes when I have time later. Update did NOT fix the problem.

DeathStalker said:

Well that was a bust. Still doing it.

YOU WERE RIGHT NOT MYSELF lol.

Well back to the other fixes when I have time later. Update did NOT fix the problem.

It is not to worry. For example, I started a thread on mozillaZine about my computer being identified as using Windows 7 after I had installed Windows 8. I subsequently found, rather weirdly, that when I started Fx in Safe Mode, and then restarted in normal mode, MS showed that I was running Windows 10, so I marked the thread as solved.

I then found that my wife's computer was shown as Windows 8, and Safe Mode did not change that, so I created a new Fx profile for her, which so far has taken care of the problem. Meanwhile, my machine reverted to being identified as using Windows 7.

I decided to rename the prefs.js file in the profile as old.prefs.js; when I restarted Fx, which created a new prefs.js file, I was once again using Windows 10, so I reset most, if not all, of the extension options. I don't know when Fx reverted yet again to Windows 7, only that it was less than twenty-four hours after my prefs.js change.

I started a new profile a while ago, copying the critical files from the old profile to the new one, testing each time; as that showed Windows 10. I then copied the Extensions folder, which, as I knew would happen, presented me with a long list of "allow this to be installed" pop-ups, many of which required restarting Fx. I have, so far, reset the important-to-me extension options, and Windows 10 is still showing.

That is just one of the various matters that have arisen since 29 August 2015, some of which, such as Fx, have been quite frustrating The failure of the Windows 10 search feature, when, instead of showing results just presents a black area, and now trying to find out why my computer wakes up after fifteen to thirty minutes are just two of my collection. I did disable the start-ups on the first screen in Task Manager earlier today, but that did not help, so I will do a second group of disabled startups to try to find the culprit.

So far, the usual methods of finding what woke the machine have not presented any useful information; at least I'm not the only Windows 10 user to report that.

Sorry for the delay Notmyself and thanks for all your help.

As far as the problem:

All I have done is keep up to date with the latest Win10 updates, the latest Firefox updates, and the latest GPU updates and the problem went away (a new one has appeared though lol).

What I THINK the problem may have been was the GPU driver. While AMD updated it's drivers, they had the same driver number displayed on the download so while I had THOUGHT I had the latest, I really didn't.

I was looking at Brinks driver sticky and it said there was a new driver. Even though when I clicked on the link it was showing the same driver number as I already had last 4 were 1002, in reality it was the 1004 driver. Since I had nothing else to try, I *re-downloaded* the driver and then I got the package is when I saw it was the 1004.

I think in the end, it was just a matter of just the early bugs in the launch. With the updates to the driver, Firefox and Win10 I have not crashed in about two weeks.