genuinegemini said

When I login to BoA site in FF 64.0.2 and click on my account view I get a blank white page.

Make sure you are not blocking content.

Start Firefox in Safe Mode {web link}

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

One issue that seems more common lately is Firefox's Tracking Protection feature. When it is blocking content in a page, a shield icon will appear at the left end of the address bar next to the padlock icon. This article has more info on managing this feature: Tracking Protection {web link}

genuinegemini said

FF 64.0.2 has also been crashing on certain sites

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.

The crash report is several pages of data. We need the report numbers to see the whole report.

Using your mouse, mark the most recent 7 - 10 Submitted crash reports, and copy them. Now go to the reply box and paste them in.

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

Thank you for the replies Fred. I had checked all of the tracking protection settings before I posted my original inquiry. I even set tracking protection to off for the BoA site. I also cleared all my cookies, history and refreshed FF, but the issues persist. It only happens on certain sites. Additionally, I did as you suggested for the crash reports, but there are none, which I find very odd. After posting my inquiry yesterday another nasty little bug showed up. On some pages I try to visit, it seems as though FF is causing my PC to shutdown abruptly. Although, it is not a complete power off shutdown as the lights and fans stay running in the tower, but the display and functionality go completely out. I know it's a FF issue because it ONLY happens with FF. Those same pages open fine in Chrome, Edge and IE. I appreciate the efforts you and other go through to help us end-users resolve our problems, but I'm afraid FF 64.0.2 is just a buggy release. I am likely going to uninstall FF 64.0.2 and go back to the previous build until the next update is released. Hopefully they will figure out what is happening and fix it.

Okay. I called for more help.

Ok. I appreciate it. If you guys figure anything out let me know, or if you need additional info from me as well. Hopefully someone will be able to make heads or tails of what's going on. Seems like a ton of people are having issues of a wide variety with this new release. I was just going over my event viewer logs to see if there was a FF reference to the shutdowns, but it only shows up as a Kernel-Power Critical event. However both of the event times correspond with me trying to open a certain page in FF. Not sure what that's all about. I run an AMD FX octa-core CPU on an ASUS Sabertooth with 32GB of RAM and 500GB SSD and a 1000W PSU plugged into a 1200W line conditioning UPS. Like I mentioned before, I had zero issues with FF before the 64.0.2 update.

Get copies of the event log problems. Then post them here and ask for help.

Explain the issue fully. https://support.microsoft.com

http://answers.microsoft.com/en-US/windows/forum/windows_10