This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

C: drive keeps filling up due to Mozilla Crash Reports

  • 6 การตอบกลับ
  • 6 คนมีปัญหานี้
  • 1 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย cor-el

more options

Hello,

Recently my C: Drive keeps filling up due to tremendous amounts of Crash Reports being generated by Mozilla. Within a couple of hours use I am filling up 2-3Gb of space.

I identified that the culprits are '*.dmp' files located in c:\Documents and Settings\Myusername\Application Data\Mozilla\Firefox\Crash Reports\pending.

I uninstalled and re-installed Firefox but the issue is still there. I never had this problem before but noticed that my C: Drive started to experience this problem when I added 'Ghostery' and 'Script Blocker' as Add-on's.

I have disabled the Script Blocker but this has not helped either. Can someone please advise as to why Firefox has started to create thousands of dump files all of a sudden?

Thanks

Hello, Recently my C: Drive keeps filling up due to tremendous amounts of Crash Reports being generated by Mozilla. Within a couple of hours use I am filling up 2-3Gb of space. I identified that the culprits are '*.dmp' files located in c:\Documents and Settings\Myusername\Application Data\Mozilla\Firefox\Crash Reports\pending. I uninstalled and re-installed Firefox but the issue is still there. I never had this problem before but noticed that my C: Drive started to experience this problem when I added 'Ghostery' and 'Script Blocker' as Add-on's. I have disabled the Script Blocker but this has not helped either. Can someone please advise as to why Firefox has started to create thousands of dump files all of a sudden? Thanks

วิธีแก้ปัญหาที่เลือก

Ok well first off, remove your anti-virus. I'm not sure why it's showing up in there but iolo isn't a good anti-virus. Let's use something like Microsoft security essentials.

After that, uninstall the Google Talk plugin. You should be able to do this from the windows control panel.

Now, restart your computer, do you still have crashes? If not, try re-installing google talk and see if this happens again.

อ่านคำตอบนี้ในบริบท 👍 4

การตอบกลับทั้งหมด (6)

more options

If you go to about:crashes in your address bar, do you have crash reports listed there? Click the "Remove all Reports" button to clear them.

more options

Fastback said

Hello, Recently my C: Drive keeps filling up due to tremendous amounts of Crash Reports being generated by Mozilla. Within a couple of hours use I am filling up 2-3Gb of space. I identified that the culprits are '*.dmp' files located in c:\Documents and Settings\Myusername\Application Data\Mozilla\Firefox\Crash Reports\pending. I uninstalled and re-installed Firefox but the issue is still there. I never had this problem before but noticed that my C: Drive started to experience this problem when I added 'Ghostery' and 'Script Blocker' as Add-on's. I have disabled the Script Blocker but this has not helped either. Can someone please advise as to why Firefox has started to create thousands of dump files all of a sudden? Thanks

Tyler Downer said

If you go to about:crashes in your address bar, do you have crash reports listed there? Click the "Remove all Reports" button to clear them.

Hello,

Thanks for getting back to me. There are literally thousands of crash reports being logged; several dozen every minute it seems.

I can clear them but they just keep coming back as I stated everytime I use Mozilla. Here is an extract from one of the reports:

Report ID: 654a089f-c23f-4b6e-9bab-85b6b2150422

Process Type: plugin Filename:npgoogletalk.dll

Crash Reason: EXCEPTION_ILLEGAL_INSTRUCTION

iolo AntiVirus LSP over [MSAFD Tcpip [TCP/IP]] : 2 : 1 : C:\WINDOWS\system32\iavlsp.dll

iolo AntiVirus LSP over [MSAFD Tcpip [UDP/IP]] : 2 : 2 : C:\WINDOWS\system32\iavlsp.dll 
MSAFD Tcpip [TCP/IP] : 2 : 1 : %SystemRoot%\system32\mswsock.dll 
MSAFD Tcpip [UDP/IP] : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
MSAFD Tcpip [RAW/IP] : 2 : 3 : %SystemRoot%\system32\mswsock.dll 
RSVP UDP Service Provider : 6 : 2 : %SystemRoot%\system32\rsvpsp.dll 
RSVP TCP Service Provider : 6 : 1 : %SystemRoot%\system32\rsvpsp.dll 
iolo AntiVirus LSP : 2 : 0 : C:\WINDOWS\system32\iavlsp.dll 
MSAFD NetBIOS [\Device\NetBT_Tcpip_{BCB44314-7EB5-4D54-A8FE-F3CB162C8A59}] SEQPACKET 0 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
MSAFD NetBIOS [\Device\NetBT_Tcpip_{BCB44314-7EB5-4D54-A8FE-F3CB162C8A59}] DATAGRAM 0 : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
MSAFD NetBIOS [\Device\NetBT_Tcpip_{F462DE4C-7037-463C-B65B-4D4EB70D041E}] SEQPACKET 1 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
MSAFD NetBIOS [\Device\NetBT_Tcpip_{F462DE4C-7037-463C-B65B-4D4EB70D041E}] DATAGRAM 1 : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
MSAFD NetBIOS [\Device\NetBT_Tcpip_{2D080F18-8BBB-4EA9-9024-45650D78D9ED}] SEQPACKET 2 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
MSAFD NetBIOS [\Device\NetBT_Tcpip_{2D080F18-8BBB-4EA9-9024-45650D78D9ED}] DATAGRAM 2 : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
MSAFD NetBIOS [\Device\NetBT_Tcpip_{79ADD270-C3E6-4E35-AFED-8500DC90F8E9}] SEQPACKET 3 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
MSAFD NetBIOS [\Device\NetBT_Tcpip_{79ADD270-C3E6-4E35-AFED-8500DC90F8E9}] DATAGRAM 3 : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
MSAFD NetBIOS [\Device\NetBT_Tcpip_{49D6DB57-0255-4929-81A1-CCAD04954C7E}] SEQPACKET 4 : 2 : 5 : %SystemRoot%\system32\mswsock.dll 
MSAFD NetBIOS [\Device\NetBT_Tcpip_{49D6DB57-0255-4929-81A1-CCAD04954C7E}] DATAGRAM 4 : 2 : 2 : %SystemRoot%\system32\mswsock.dll

In the Crashing Thread Table the following is highlighted in RED

Ø 0 npgoogletalk.dll npgoogletalk.dll@0x1814 Ø 1 npgoogletalk.dll npgoogletalk.dll@0x1c6b4 Ø 2 npgoogletalk.dll npgoogletalk.dll@0x14bae Ø 3 npgoogletalk.dll npgoogletalk.dll@0xc48e Ø 4 npgoogletalk.dll npgoogletalk.dll@0xcb72

It's obvious that there is an Issue with the Google Talk application; not sure if the AntiVirus package I have installed in causing problems as well.

more options

Hello,

Thanks for getting back to me. There are literally thousands of crash reports being logged; several dozen every minute it seems.

I can clear them but they just keep coming back as I stated everytime I use Mozilla. Here is an extract from one of the reports:

Report ID: 654a089f-c23f-4b6e-9bab-85b6b2150422

Process Type: plugin Filename:npgoogletalk.dll

Crash Reason: EXCEPTION_ILLEGAL_INSTRUCTION

iolo AntiVirus LSP over [MSAFD Tcpip [TCP/IP]] : 2 : 1 : C:\WINDOWS\system32\iavlsp.dll

iolo AntiVirus LSP over [MSAFD Tcpip [UDP/IP]] : 2 : 2 : C:\WINDOWS\system32\iavlsp.dll MSAFD Tcpip [TCP/IP] : 2 : 1 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [UDP/IP] : 2 : 2 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [RAW/IP] : 2 : 3 : %SystemRoot%\system32\mswsock.dll RSVP UDP Service Provider : 6 : 2 : %SystemRoot%\system32\rsvpsp.dll RSVP TCP Service Provider : 6 : 1 : %SystemRoot%\system32\rsvpsp.dll iolo AntiVirus LSP : 2 : 0 : C:\WINDOWS\system32\iavlsp.dll MSAFD NetBIOS [\Device\NetBT_Tcpip_{BCB44314-7EB5-4D54-A8FE-F3CB162C8A59}] SEQPACKET 0 : 2 : 5 : %SystemRoot%\system32\mswsock.dll MSAFD NetBIOS [\Device\NetBT_Tcpip_{BCB44314-7EB5-4D54-A8FE-F3CB162C8A59}] DATAGRAM 0 : 2 : 2 : %SystemRoot%\system32\mswsock.dll MSAFD NetBIOS [\Device\NetBT_Tcpip_{F462DE4C-7037-463C-B65B-4D4EB70D041E}] SEQPACKET 1 : 2 : 5 : %SystemRoot%\system32\mswsock.dll MSAFD NetBIOS [\Device\NetBT_Tcpip_{F462DE4C-7037-463C-B65B-4D4EB70D041E}] DATAGRAM 1 : 2 : 2 : %SystemRoot%\system32\mswsock.dll MSAFD NetBIOS [\Device\NetBT_Tcpip_{2D080F18-8BBB-4EA9-9024-45650D78D9ED}] SEQPACKET 2 : 2 : 5 : %SystemRoot%\system32\mswsock.dll MSAFD NetBIOS [\Device\NetBT_Tcpip_{2D080F18-8BBB-4EA9-9024-45650D78D9ED}] DATAGRAM 2 : 2 : 2 : %SystemRoot%\system32\mswsock.dll MSAFD NetBIOS [\Device\NetBT_Tcpip_{79ADD270-C3E6-4E35-AFED-8500DC90F8E9}] SEQPACKET 3 : 2 : 5 : %SystemRoot%\system32\mswsock.dll MSAFD NetBIOS [\Device\NetBT_Tcpip_{79ADD270-C3E6-4E35-AFED-8500DC90F8E9}] DATAGRAM 3 : 2 : 2 : %SystemRoot%\system32\mswsock.dll MSAFD NetBIOS [\Device\NetBT_Tcpip_{49D6DB57-0255-4929-81A1-CCAD04954C7E}] SEQPACKET 4 : 2 : 5 : %SystemRoot%\system32\mswsock.dll MSAFD NetBIOS [\Device\NetBT_Tcpip_{49D6DB57-0255-4929-81A1-CCAD04954C7E}] DATAGRAM 4 : 2 : 2 : %SystemRoot%\system32\mswsock.dll

In the Crashing Thread Table the following is highlighted in RED

Ø 0 npgoogletalk.dll npgoogletalk.dll@0x1814 Ø 1 npgoogletalk.dll npgoogletalk.dll@0x1c6b4 Ø 2 npgoogletalk.dll npgoogletalk.dll@0x14bae Ø 3 npgoogletalk.dll npgoogletalk.dll@0xc48e Ø 4 npgoogletalk.dll npgoogletalk.dll@0xcb72

It's obvious that there is an Issue with the Google Talk application; not sure if the AntiVirus package I have installed in causing problems as well.

more options

วิธีแก้ปัญหาที่เลือก

Ok well first off, remove your anti-virus. I'm not sure why it's showing up in there but iolo isn't a good anti-virus. Let's use something like Microsoft security essentials.

After that, uninstall the Google Talk plugin. You should be able to do this from the windows control panel.

Now, restart your computer, do you still have crashes? If not, try re-installing google talk and see if this happens again.

more options

PENDING (file under Mozilla) Crash Reports not yet sent, how do I send them to Mozilla? If Mozilla doesn't want Crash Reports and you want me/world to delete them. What is the purpose of these reports after all? I have 3,000+ reports pending Deleting Crash Report log is not an issue here.

เปลี่ยนแปลงโดย wvelovich เมื่อ

more options

You can delete the pending folder or possibly only leave some recent crash reports.

You can find the report ID of recent crash reports on the "Help > Troubleshooting Information" page (about:support).

  • Click the "All Crash Reports" button on this page to open the about:crashes page and see all crash reports.

Alternatively you can open about:crashes via the location/address bar.

If a line on the about:crashes page doesn't start with "bp-" then click the line to submit the report and the link will be updated and gets a "bp-" prefix if the report is submitted successfully.