Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Rohkem teavet

Crashing every time I access Pogo.com

  • 17 vastust
  • 1 on selline probleem
  • 4 views
  • Viimati vastas Blysse

more options

All day today, as soon as I try to access Pogo.com, FireFox crashes before the page can even finish loading.

I've turned off hardware acceleration; turned off Flash's protected mode; cleared my browser, Java, and Flash caches. I used FireFox in Safe Mode and it STILL crashed instantly.

It's crashed dozens of times in only a couple of hours, and only when I access Pogo.com. I could access the site perfectly fine even as recently as four hours ago and I didn't change anything on my end before the crashing started.

Here's the crash details copied from one of the last crashes: http://pastebin.com/Hf2Wu6tB

All day today, as soon as I try to access Pogo.com, FireFox crashes before the page can even finish loading. I've turned off hardware acceleration; turned off Flash's protected mode; cleared my browser, Java, and Flash caches. I used FireFox in Safe Mode and it STILL crashed instantly. It's crashed dozens of times in only a couple of hours, and only when I access Pogo.com. I could access the site perfectly fine even as recently as four hours ago and I didn't change anything on my end before the crashing started. Here's the crash details copied from one of the last crashes: http://pastebin.com/Hf2Wu6tB

Muudetud Blysse poolt

All Replies (17)

more options

hello, could you provide your latest few submitted crash reports? please enter about:crashes into the location bar, copy the latest few report ids from there starting with bp- & paste them here into a forum reply. this will give us a better understanding what may be triggering those crashes.

more options

bp-60249773-4537-4c3c-9e4e-8c4212170101 01/01/2017 1:51 PM bp-2589a057-b515-452f-a67a-8db8f2170101 01/01/2017 1:48 PM bp-0dd9c7e3-dceb-41e3-a117-99e042170101 01/01/2017 1:43 PM bp-0a8a39bd-9ec9-4942-a1ae-0d1f12170101 01/01/2017 1:38 PM bp-d19c3357-354d-444c-a1e6-4d2aa2170101 01/01/2017 1:36 PM bp-892fdde3-7661-4016-afaa-af0192170101 01/01/2017 1:35 PM bp-9d349d65-facb-4b9b-9faf-2db812170101

There's been more crashes than this, but I haven't selected to report them all.

Muudetud Blysse poolt

more options

thanks. can you test if those crashes can be reproduced when you use a 64bit build of firefox as well?: https://www.mozilla.org/en-US/firefox/all/

if yes, please also try how it is behaving with a new profile: Profile Manager - Create, remove or switch Firefox profiles

more options

Do I need to uninstall my current version of FireFox before installing the 64-bit build?

more options

yes, please uninstall it beforehand to avoid confusion, as the 64bit installer will install to a different patch by default...

more options

It appears to be working in the 64-bit version, thank you.

For my own curiosity [I work doing tech support for a website, these problems intrigue me], did the crash reports show any specific thing was going wrong/weird? How come simply changing to 64-bit worked? And why did the other version of FireFox work just fine until this morning?

more options

Okay, not fixed. FireFox is now crashing on even more pages with no rhyme or reason as to which ones.

bp-16a66821-cc53-447d-a8f4-936782170101 01/01/2017 2:33 PM bp-18a5f7a7-90a7-441f-a4af-2c57d2170101 01/01/2017 2:27 PM

Am trying the new profile thing right now.

more options

i'm no developer myself, so i can only give you an amateurish view ;-) you where very persistently crashing with the same crash signature. however, data from the past few days shows that no other firefox user has experienced this kind of crash or submitted a report about it. so this could either mean that something changed on the pogo website and you are the first to notice this crash (in this case i'd expect many more reports to follow), or something has gone wonky on your machine (more likely, if you stay the sole user to see this type of crash). your crash reports showed that the exception happened around the code that is responsible for accessing the npapi plugins on your system, and since win64-bit firefox versions come with limited plugin support (only flash) this was a candidate for a possible workaround.

more options

I made a new profile and Pogo still crashes it immediately.

bp-8767165f-b58a-4ea3-8c86-e4e5a2170101 01/01/2017 2:46 PM

I contacted Pogo tech support and they just told me to re-install FireFox and/or use a different browser. But now that this is happening with more and more pages, it can't be on Pogo's end.

more options

bp-569ead1d-edcc-4c6e-bb8b-b97492170101 01/01/2017 2:50 PM

Doing it on all kinds of pages still.

Any other suggestions?

more options

thanks, now the crashing reasons seem to become more random which would also make me suspect faulty hardware as a cause. can you check the integrity of your system's memory/RAM with a tool like from www.memtest.org or the ms tool that should come with your operating system: https://technet.microsoft.com/en-us/library/ff700221.aspx

more options

Windows says it's a memory problem, but that's all it says.

more options

Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen or hold down the Shift key) to see if that has effect.


Do a malware check with several malware scanning programs on the Windows computer.

Please scan with all programs because each program detects different malware. All these programs have free versions.

Make sure you update each program to get the latest version of their databases before doing a scan.

You can also do a check for a rootkit infection with TDSSKiller.

See also:

more options

Do I run those programs IN Safe Mode?

more options

And did you see that Windows says it's a memory problem? Can Malware do that?

more options

each memory error is one to many and you should exchange faulty RAM modules in order to avoid instability in firefox and other programs/your os (this won't be triggered by malware). the details depend on your configuration: if there are multiple ram modules in your device, you could take out one of the modules and run the test again, until you find the faulty part. if your device is still covered under the warranty by its manufacturer you should get in contact with their support to get the part replaced.

more options

Alright, thank you.

I just purchased this computer on the 21st and it IS under warranty, but by the company who refurbished it. I contacted the manufacturers and they can't help, but I'm waiting for a response from the refurb company.