If anyone has any interest in taking a look, here are my two most recent crashes, which just happened a few minutes ago.

This one happened when I clicked on an Imgur link: bp-e63393b9-f8e1-402d-8f37-0e8492150714

And this one happened when I was trying to view about:crashes: bp-b57b3f96-f249-40af-829c-361b92150714

Looks like one of them is affecting another user with Sea Monkey, can you please try a new profile to see if this continues to happen?

• Profile Manager - Create, remove or switch Firefox profiles

Is the message about plugin-container.exe coming from Windows 7 instead of from Firefox? If so, does it come before or after the Mozilla Crash Reporter dialog?

I'm puzzled that you could have seven crash reports each of which has a different crash signature. Usually there's a pattern and it's very hard to spot here.

I wouldn't consider the Nvidia driver a prime suspect, as it was not in the "crashing thread".

Since you have quite an impressive collection of extensions, unfortunately I have to suggest testing in Firefox's Safe Mode. 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).

Any difference?

Thanks for the responses. I believe the plugin error message is coming from Windows itself. I've attached a screenshot of what I see every time Firefox crashes. The error pops up immediately after Firefox crashes; it comes up at the exact same time as the Mozilla Crash Reporter.

While running Firefox in Safe Mode, I didn't experience any crashes (which may not say much because I sometimes go a few days without issues), but the browser was uncharacteristically sluggish. Watching Youtube videos was especially troublesome and Firefox would temporarily stop responding while watching any video that was at least a minute long. After getting frustrated with this, I tried testing out a new profile and didn't experience any issues. I needed to switch over to my default profile for a minute and when I closed the browser, it crashed. I restarted Firefox (still using the new profile) and there was a new entry in the crash log at 12:44 AM, but I couldn't open it (it started with "cb" instead of the typical "bp"). When I restarted Firefox with my default profile, that log was gone, but there was a new one from 12:51 AM: bp-7a9d3378-682d-4929-8908-7c10b2150714

And then Firefox crashed twice more within the span of a minute: bp-04c53f25-7b10-430e-a964-527312150714 bp-dc4b5c39-cd65-469b-bd42-c9f032150714

It seemed like the browser was crashing while trying to load the crash reports I had open, so I closed those tabs in Session Manager and haven't had any further crashes so far.

Although I can't say for sure, I suspect another ongoing issue I have may perhaps be related: https://support.mozilla.org/en-US/questions/1069586

Ever since updating Firefox, I've been getting errors when viewing Youtube videos. It usually happens in Safe Mode as well, but that wasn't the case tonight. It was lagging and causing unresponsiveness like I mentioned earlier, but no error messages.

EDIT: Another crash, for the sake of reference: bp-10c32479-50e5-4c5e-8ad0-e04242150714

That first report is a shutdown hang. A few versions ago, Firefox started timing its shutdown and if it didn't finish within the expected time, it logged a shutdown hang as a crash so data about it could be collected. Unfortunately, we often can't tell why there was a delay in shutdown. However, users generally have better luck avoiding them by using the menu ("Exit") instead of the "red X" button to close Firefox.

The other three reports, from your regular profile, are again diverse. I do not see a pattern.

Since the Safe Mode test seems to have been successful in avoiding crashes, you could individually troubleshoot some of the features disabled in Firefox's Safe Mode, including:

• Extensions
• Hardware acceleration of graphics
• JavaScript compilers

I listed extensions first because you have so many and I think it would be worth testing with everything you won't need during the next 24 hours disabled. You can make the change on the Add-ons page. Either:

• Ctrl+Shift+a
• "3-bar" menu button (or Tools menu) > Add-ons

In the left column, click Extensions. Then, if in doubt, disable.

Often a link will appear above at least one disabled extension to restart Firefox. You can complete your work on the tab and click one of the links as the last step.

Any improvement in stability?

Regarding stalling, a common cause of unresponsive script errors on Windows 7 is the protected mode feature of the Flash player plugin. That feature has security benefits, but seems to have serious compatibility issues on some systems. There is a hidden setting to disable it; I suggest trying this for a day to see whether it helps:

(A) In a new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

(B) In the search box above the list, type or paste flash and pause while the list is filtered

(C) Double-click the dom.ipc.plugins.flash.disable-protected-mode preference to switch its value from false to true.

This might not take effect until all Flash has been unloaded for a few minutes, or you close Firefox.

Note: if you already edited the mms.cfg file to disable the Flash protected mode, then you would not notice any change as a result of the above.

Thanks for the screen shot regarding the plugin-container crashing. It appears at this point that it is crashing as a result of Firefox crashing, and not the other way around, but I guess we'll see.

Thank you for taking the time to try to help me. Because there doesn't seem to be any rhyme or reason to when a crash occurs, testing out my various extensions could take quite a while, but I will try it out over the next week or so and keep you posted. I'm really hoping that if I can get my Youtube issue worked out, it will help with this issue as well. I doubt I'll be so lucky, but my fingers are crossed!