Hi Rich, you had posted about crashes on Windows 8 in Firefox 38.0.5. Does this seem to be a continuation of the same problem, or a new issue with Firefox 40 on Windows 10?

When your Firefox 40 is crashing, are you getting the Mozilla Crash Reporter dialog, or a Windows crash dialog?

If you do not get the Mozilla Crash Reporter dialog, then Windows may have terminated Firefox for violating a security boundary without an opportunity for Firefox to detect the crash itself.

If you do get the dialog, could you check the about:crashes page for crash report IDs? I think you already are familiar with that page, but it's also described in the last section of our support article "Troubleshoot Firefox crashes (closing or quitting unexpectedly)".

In the 'about:crashes' dialogue box ....nothing submitted. There are too many issues that can foul up....also suspect in this case when downloaded a pdf file and cannot open as the internal adobe version is disabled, then it seeks deployment online. The security boundary and timings; I suspect this is the issue...as previously Windows has doubted my email address with the server that I use and the exceptions flagged up....when it is perfectly without doubt. The Acer notebook E5- displays a FF health check time of 1 sec, so there is nothing up with the browser # notebook. Mystified.

Okay, let's rewind a bit to my earlier question: When your Firefox 40 is crashing, are you getting the Mozilla Crash Reporter dialog, or a Windows crash dialog? If it's Windows, what does it say?

A little delve into the event logs----suspect it is a Windows problem in the Boot sector. I'm no expert, but see jpg below. It looks to me 95% MS issues.

I'm not sure what Windows considers an "administrative event". The categories I remember are System, Security, and Application event logs. Do any of the other logs refer either to Firefox or to plugin-container.exe as a crashing application?

The more I examine this mystery, it's something in windows10 or FF messing with the network internet family controller, as it shows "device is working normally" (when something isn't), but a cold system reset clears the bug and restarts connection again. That implies something's not correctly configured. If there is a command entry in FF that does this, then there's the issue. The device drivers are the latest is in. What else is there that initiates the IE side ? The annoying part is whatever crash happens, it pulls down the DSL modem to go offline as well, so that requires a cold reset too. The whole climate around this seems haphazard esp on slow speed links. Unfortunately the windows diagnose engine is probably the worst in the industry. Each time I enter the even viewer it crashes. I am at a loss.

I don't know whether this TCP/IP reset might help: After upgrade to window 10, cannot access internet from firefox or chrome.

Here it is before it crashes again.....a bug pulling down the network controller, see jpg..who's the culprit ? Seems to me a netwrok controller refresh...will do it.

I think a PCIe ethernet adapter is an internal component of your system. To check for updates for the relevant driver or firmware, you probably should check your computer manufacturer's site.

(I looked at Realtek's site, and I just don't know if you'll be able to accurately identify your specific product there: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&P...)

Thanks jscher....We must be getting close... the TCP IP business could be incorrectly set.....However it looks Mozilla got off from being carp'd again....see jpg .........Win 10 is the money behind the organ.

If you check Firefox's File menu when this happens (you can tap the Alt key to display the menu bar if you do not normally display it), does it show that Firefox switched to Work Offline? If so, does clicking that restore its ability to use the network?

"off-line" as I see it is to hit the menu --> "developer" tab and there it is on the lowest.

I didn't realize Work Offline was on the Developer menu now. But that's not the problem, Firefox taking itself offline?

Sorry, this seems to be getting into areas of Windows that are beyond my knowledge.

Ok, you can see as I have, that crash topic has gone way off course, created appears to be a TCP/Ip6_4 confusion within the network gateway provider. How it started is no-ones idea. I went further into windows 10; however I wouldn't advise those who are unsure with system tools, as they can be very disruptive and often hard to get back where one was..Don't tinker!!

System&Security->Admin tools-> system configuration and one arrives at a panel with selective start_diagnosic_& norm. I ran diagnostic, let it run, then power down and restart. Then return to the panel and click the default remains with the 'selective start'. My notebook now runs much faster after doing it. So far no IE hangups. For how long ??