Search for Device Manager and look to see if Windows 10 has replaced your driver with Microsoft's. You do not want that to happen at all as have seen drivers from 2006 being stuck in to systems. https://www.howtogeek.com/302595/how-to-stop-windows-10-from-automatically-updating-hardware-drivers/

Pkshadow said

Hi, Yes saw Win 19 but it has or can have a Linux Shell if you downloaded it. few things why where you running 61.0a1 ? is this now version 60.0.2  ? Help --> About will say. Please update your Video Card Drivers (have no info so can not look for errors) No information on your Extensions so please try : SAFE MODE

• https://support.mozilla.org/kb/Safe+Mode
• https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

In Firefox Safe mode these changes are effective:

• all extensions are disabled (about:addons)
• default theme is used (no persona)
• userChrome.css and userContent.css are ignored (chrome folder)
• default toolbar layout is used (file: localstore-safe.rdf)
• Javascript JIT compilers are disabled (prefs: javascript.options.*jit)
• hardware acceleration is disabled (Options > Advanced > General)
• plugins are not affected
• preferences are not affected

TEST''''is issue still there ?

Win 10, v. 1803's Linux has not been installed as I do not plan to run Windows Linux. My Win 10 is the original Win 10 upgraded years ago for free. It is Win 10 Pro.

I have run the latest version of Quantum (60.0.2) in Safe Mode several times. Will run it again if you want. I have no idea where you got 61.0a1.

The browser runs just fine for a long time before it crashes. In fact, I opened it and left it alone while I am using the Developer Edition. Quantum is running again while I'm typing this.

Why should I update my video cards. Win 10 keeps them updated. Plus, I have been using Quantum since it came out with no crashes. I don't think the video cards are the problem. Everything that has been using the video cards have had NO problems for years.

Pkshadow said

Search for Device Manager and look to see if Windows 10 has replaced your driver with Microsoft's. You do not want that to happen at all as have seen drivers from 2006 being stuck in to systems. https://www.howtogeek.com/302595/how-to-stop-windows-10-from-automatically-updating-hardware-drivers/

I've read that HowtoGeek article long ago. It explains how you can stop the updates if you are having an hardware problem. I am not. I have run a hardware troubleshooter which found no problem. Device Manager shows no problems.

Microsoft has explained why the dates on the drivers never change from 2006. I believe only the version number changes. They are not stuck. Windows does update the drivers all the time. The date just does NOT change reflecting the update. These may explain why:

https://www.windowscentral.com/heres-why-microsoft-dates-all-windows-drivers-june-21-2006

https://blogs.msdn.microsoft.com/oldnewthing/20170208-00/?p=95395

hi, this problem will occur if you have manually enabled dns over https on firefox 60 - the feature isn't ready on release and will lead to the crashes you're experiencing. to solve the issue, please either reset the network.trr.mode preference in about:config or switch to the beta version of firefox 61...

philipp said

hi, this problem will occur if you have manually enabled dns over https on firefox 60 - the feature isn't ready on release and will lead to the crashes you're experiencing. to solve the issue, please either reset the network.trr.mode preference in about:config or switch to the beta version of firefox 61...

I think you nailed it! That's why I mentioned that the problem might be in the config file. "network.trr.mode " was set to "2". Reset it to "0".

Reason why I thought it may be in the config file is because Quantum hasn't crashed for hours now since I have not surfed. I just let it run while I used the Developer Edition. This is while "network.trr.mode " was still set to "2".

Thanks for hanging in there with me. I'm sure that is the problem. Will let you know.

philipp said

hi, this problem will occur if you have manually enabled dns over https on firefox 60 - the feature isn't ready on release and will lead to the crashes you're experiencing. to solve the issue, please either reset the network.trr.mode preference in about:config or switch to the beta version of firefox 61...

Looks like this was the problem. Browser has been up and running for over a day with no crashes. I think I changed the Config and forgot it since it seemed to be OK. Only thing that gets me is why it took so long to start crashing since the change was made a long time ago. :D

Thanks for spotting the problem and all the help.