X
Tap here to go to the mobile version of the site.

Support Forum

Firefox crashes

Posted

Crash ID: bp-4181bd74-7659-40eb-9e57-fc35a2150327

Crash ID: bp-4181bd74-7659-40eb-9e57-fc35a2150327

Additional System Details

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36

More Information

FredMcD
  • Top 10 Contributor
4254 solutions 59583 answers

The crash report flagged these programs;

interenetoptimizer.dll = interenet optimizer = Adware ?
http://www.spywareremove.com/file/interenetoptimizerdll-173141/

CouponMarvel32.dll = COUPON MARVEL = PUP.Optional.CouponMarvel.A ?

icudt52.dll = International Components for Unicode


Use most or all of the scanners listed; Troubleshoot Firefox issues caused by malware article.

The crash report flagged these programs; interenetoptimizer.dll = interenet optimizer = Adware ?<br> http://www.spywareremove.com/file/interenetoptimizerdll-173141/ CouponMarvel32.dll = COUPON MARVEL = PUP.Optional.CouponMarvel.A ? icudt52.dll = International Components for Unicode ------------------------------------- Use most or all of the scanners listed; [[Troubleshoot Firefox issues caused by malware]] article.
jscher2000
  • Top 10 Contributor
8758 solutions 71655 answers

Are you able to start Firefox in its Safe Mode?

If Firefox is not running, hold down the Shift key while clicking/double-clicking your Firefox desktop or task bar shortcut.

A small dialog should appear: click Start in Safe Mode.

Will it start up?

Are you able to start Firefox in its Safe Mode? If Firefox is not running, hold down the Shift key while clicking/double-clicking your Firefox desktop or task bar shortcut. A small dialog should appear: click Start in Safe Mode. Will it start up?
guigs 1072 solutions 11697 answers

The bug associated with the crash is a back out of a feature called HTTP cache v2, basically something to do with cache loading optimization. It was said to be fixed in 33, but this may be another issue.

Please first try the troubleshooting steps mentioned above, however in the meantime try a new profile if the previous steps do no work: Profile Manager - Create, remove, or switch Firefox profiles

The bug associated with the crash is a back out of a feature called HTTP cache v2, basically something to do with cache loading optimization. It was said to be fixed in 33, but this may be another issue. Please first try the troubleshooting steps mentioned above, however in the meantime try a new profile if the previous steps do no work: [[Use the Profile Manager to create and remove Firefox profiles]]