Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Windows 7 Action Center reports that Plugin Container for Firefox Stopped working

  • 4 antwurd
  • 6 hawwe dit probleem
  • 3 werjeftes
  • Lêste antwurd fan sonardog

more options

On 10/31/2015 and 11/09/2015 Firefox has reported a problem with a script on Comcast/Xfinity's http://my.xfinity.com/ home page to browse my email using Windows 7 Home. Clicking any of the options provided in the debugger window results in Firefox shutting down and a report was being sent. Checking Firefox Health Report there are no indications of a crash.

Here is what the Action Center reported: Source Plugin Container for Firefox

Summary Stopped working

Date ‎10/‎31/‎2015 9:59 PM

Status Report sent

Description Faulting Application Path: C:\Program Files (x86)\Mozilla Firefox\plugin-container.exe

Problem signature Problem Event Name: APPCRASH Application Name: plugin-container.exe Application Version: 41.0.2.5765 Application Timestamp: 561ef9f1 Fault Module Name: mozglue.dll Fault Module Version: 41.0.2.5765 Fault Module Timestamp: 561ee53f Exception Code: 80000003 Exception Offset: 0000ec91 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Extra information about the problem Bucket ID: 285859499

Source Plugin Container for Firefox

Summary Stopped working

Date ‎11/‎9/‎2015 10:43 AM

Status Report sent

Description Faulting Application Path: C:\Program Files (x86)\Mozilla Firefox\plugin-container.exe

Problem signature Problem Event Name: APPCRASH Application Name: plugin-container.exe Application Version: 41.0.2.5765 Application Timestamp: 561ef9f1 Fault Module Name: mozglue.dll Fault Module Version: 41.0.2.5765 Fault Module Timestamp: 561ee53f Exception Code: 80000003 Exception Offset: 0000ec91 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Extra information about the problem Bucket ID: 285859499

On 10/31 I discovered that Firefox needed an update and until today I would make a manual check for updates before using Firefox. After the reported crash by Windows Action Center I manually checked for updates which were applied.

The Action Center reports appear to be identical to me can anyone please help me with the problem.

On 10/31/2015 and 11/09/2015 Firefox has reported a problem with a script on Comcast/Xfinity's http://my.xfinity.com/ home page to browse my email using Windows 7 Home. Clicking any of the options provided in the debugger window results in Firefox shutting down and a report was being sent. Checking Firefox Health Report there are no indications of a crash. Here is what the Action Center reported: Source Plugin Container for Firefox Summary Stopped working Date ‎10/‎31/‎2015 9:59 PM Status Report sent Description Faulting Application Path: C:\Program Files (x86)\Mozilla Firefox\plugin-container.exe Problem signature Problem Event Name: APPCRASH Application Name: plugin-container.exe Application Version: 41.0.2.5765 Application Timestamp: 561ef9f1 Fault Module Name: mozglue.dll Fault Module Version: 41.0.2.5765 Fault Module Timestamp: 561ee53f Exception Code: 80000003 Exception Offset: 0000ec91 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789 Extra information about the problem Bucket ID: 285859499 Source Plugin Container for Firefox Summary Stopped working Date ‎11/‎9/‎2015 10:43 AM Status Report sent Description Faulting Application Path: C:\Program Files (x86)\Mozilla Firefox\plugin-container.exe Problem signature Problem Event Name: APPCRASH Application Name: plugin-container.exe Application Version: 41.0.2.5765 Application Timestamp: 561ef9f1 Fault Module Name: mozglue.dll Fault Module Version: 41.0.2.5765 Fault Module Timestamp: 561ee53f Exception Code: 80000003 Exception Offset: 0000ec91 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789 Extra information about the problem Bucket ID: 285859499 On 10/31 I discovered that Firefox needed an update and until today I would make a manual check for updates before using Firefox. After the reported crash by Windows Action Center I manually checked for updates which were applied. The Action Center reports appear to be identical to me can anyone please help me with the problem.

Alle antwurden (4)

more options

Try using safe mode https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

If nothing changes attempt to reinstall Firefox.

more options
  • see if there are updates for your graphics drive drivers

https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration

  • disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later)

https://forums.adobe.com/message/4468493#TemporaryWorkaround

  • disable hardware acceleration in the Flash plugin

https://forums.adobe.com/thread/891337 See also:

more options

Hello LostGod and FredMcD,

Thank-you for the help and I will try the solutions you have suggested.

more options

Hello again LostGod and FredMcD,

I have tried the suggested solutions and the problem still occurs when Firefox indicates that there is a script issue on my ISP's home page. My conclusion is that there is a programming error in the coding of the web page that does not like Firefox. Of course with the ISP's continual coding updates this is another little issue to add to the mix.

Again thank you very much for the help, hopefully the ISP will accidentally fix the problem.