Try disabling graphics hardware acceleration. Since this feature was added to Firefox, it has gradually improved, but there still are a few glitches.

You might need to restart Firefox in order for this to take effect, so save all work first (e.g., mail you are composing, online documents you're editing, etc.).

Then perform these steps:

• Click the orange Firefox button at the top left, then select the "Options" button, or, if there is no Firefox button at the top, go to Tools > Options.
• In the Firefox options window click the Advanced tab, then select "General".
• In the settings list, you should find the Use hardware acceleration when available checkbox. Uncheck this checkbox.
• Now, restart Firefox and see if the problems persist.

Additionally, please check for updates for your graphics driver by following the steps mentioned in the following Knowledge base articles:

Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems

Upgrade your graphics drivers to use hardware acceleration and WebGL

Did this fix your problems? Please report back to us!

That's not a crash from Hardware Acceleration. do you have Websense Endpoint on your machine? Please contact websense to update their software to stop this crash.

Hi amitshree, Tylerdowner

Thank you for your responses.

I am unable to enter Firefox to try anything - I keep getting the Mozilla Crash Reporter.

Yes, I have Websense Endpoint - it is a work PC and hence IT have this installed - maybe they have updated it? I'll contact IT.

Regards Jeff

Get your IT dept to update websense, you are running and out of date version that is causing Firefox to crash.

I can't find a working webpage to report a problem. None of those that appear to be designed for that purpose will accept a post and return an error. That is exceedingly irritating after spending time to write the report, only to have it go "poof" and disappear, without allowing the recovery of what had been written using Back. That which I tried to report was as follows:

A previous attempt to discuss a problem caused time spent to make the report to be lost. This may have been because "cookies" were not enabled. After this many years it would seem that programs would request to enable cookies to prevent this. Also, the message given displayed when using the "Firefox Made Me Sad" pathway was, “Forbidden (403), CSRF verification failed. Request aborted” (whatever that’s supposed to mean). I was logged in at the last to see if that was a requirement, but that didn't help. If this is a none working reporting center it seems it should either be abandoned or fixed.

The problem at hand is that Firefox 23.0, since it was just installed, has frozen. This took place while using the Solitaire Add-on. It appears that it interfered with the Febe Add-on. Solitaire began to act strangely because it prevented a move that would have ended the current game and given the score. At the same time Febe attempted to perform a backup. Firefox hung and the only way to recover was to logout, which was the only option available.

The Event Viewer, which was just accessed, shows many errors dating back to when the system was bought. The errors are identified as "ATI EEU Client event error", whatever that is supposed to mean.

Please update to the current Firefox 23.0 release.

• Help > About Firefox

• https://support.mozilla.org/kb/update-firefox-latest-version.
• https://support.mozilla.org/kb/Updating+Firefox

The Firefox 19 version that you currently run is no longer supported with security updates.

• It is important to update Firefox and add-ons to the latest version to get all security fixes.

Your crash report indicates a problem with Websense Endpoint that may have been fixed in the current release.

• https://crash-stats.mozilla.com/report/index/f86d069c-194c-4e97-b3b9-62e782130321
• bug 828184 - startup crash in nsPrefBranch::GetIntPref with QIPCAP.dll (Websense Endpoint)

I already had updated to Firefox 23.0 when experiencing the above. I don't remember if I Restart(ed) the computer however. There was no notice that it was necessary, since updates always seem to go into effect when Firefox is restarted.