Hmm, I don't think using a 64-bit beta test build of Firefox is going to net out to being more secure stable than the 32-bit release build. There also is a lack of 64-bit plugins, so if you rely on any plugins other than Flash, that may be an issue for you.

If you want to try it, I suggest this procedure:

Clean Reinstall

We use this name, but it's not about removing your settings, it's about making sure the program files are clean (no inconsistent, corrupted, or alien code files). As described below, this process does not disturb your existing settings. Do NOT uninstall Firefox, that's not needed.

(A) Download a fresh installer for Firefox 42 64-bit beta from https://www.mozilla.org/firefox/beta/all/ to a convenient location. (Scroll down to your preferred language.)

(B) Exit out of Firefox (if applicable).

(C) Rename the program folder, either:

(64-bit Windows + 32-bit Firefox)

C:\Program Files (x86)\Mozilla Firefox

to

C:\Program Files (x86)\Fx41

(32-bit Windows or 64-bit Windows + 64-bit Firefox)

C:\Program Files\Mozilla Firefox

to

C:\Program Files\Fx41

(D) Run the installer you downloaded in (A). It should automatically connect to your existing settings.

Success?

Perhaps more importantly -- sorry to hear about the crashes!

If you are getting the Mozilla Crash Reporter form, your Firefox may have logged some data that would help track down the cause of the problem. You can submit that data to Mozilla and share it with forum volunteers to see whether it points to the solution. Please check the support article "Firefox crashes - asking for support" for steps to get those crash report IDs from the about:crashes page, and then post some of the recent ones here.

On the other hand, if the problem is long freezes and having to "kill" Firefox using the Task Manager, then Firefox doesn't record useful data. This article has tips for that situation: Firefox hangs or is not responding - How to fix.

Also, since Flash can cause this problem (and is used pervasively through the web), I suggest the following to minimize potential issues with Flash during your troubleshooting:

(1) To avoid unnecessary pain on sites where Flash is not actually essential, try setting Flash to Click-to-Play ("Ask to Activate"). This will delay Flash from starting on a page until you approve it.

To set "Ask to Activate", open the Add-ons page using either:

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

In the left column, click Plugins. Look for "Shockwave Flash" and change "Always Activate" to "Ask to Activate".

With this setting, when you visit a site that wants to use Flash, you should see a notification icon in the address bar and usually (but not always) one of the following: a link in a dark gray rectangle in the page or an infobar sliding down between the toolbar area and the page.

The plugin notification icon in the address bar typically looks like a small, dark gray Lego block. (If it's red, Flash needs updating.)

The delay in activating Flash can help distinguish between problems caused on initial page load, styling, and script activation vs. loading/running Flash.

If you see a good reason to use Flash, and the site looks trustworthy, you can go ahead and click the notification icon in the address bar to allow Flash. You can trust the site for the time being or permanently.

But some pages use Flash only for tracking or playing ads, so if you don't see an immediate need for Flash, feel free to ignore the notification! It will just sit there in case you want to use it later.

(2) A common cause of unresponsive script errors on Windows Vista and higher 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. You can disable it using the Add-ons page. Either:

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

In the left column, click Plugins. On the right side, find "Shockwave Flash" and click the More link. Then uncheck the box for "Enable Adobe Flash protected mode" and try that for a day to see whether it helps.

32-bit Plugins whether on Windows, Mac OSX or Linux will not work on 64-bit Firefox. For the Win64 as said only the 64-bit Flash Player is currently white listed to run.

Whether you keep 32-bit Firefox or not on Windows you should not try to install Win64 Firefox over 32-bit as mixing has been known to cause crashes in past.

I do not believe 32-bit Firefox users on Windows, 7, 8 and 10 will get a update to Win64 Firefox as updates will still be 32-bit Firefox.

The earliest Release to may have Win64 is Firefox 42.0 however it will not be on www.mozilla.org or www.mozilla.org/firefox/all but on the ftp.mozilla.org

Thank you. I'm afraid I'll just have to live with the instability.