搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Firefox crashes

  • 1 回覆
  • 2 有這個問題
  • 4 次檢視
  • 最近回覆由 philipp

more options

Crash ID: bp-37149764-ea6c-497b-925d-dc40d2161225

Whenever I try to open firefox, the "Mozilla Crash Reporter" pops up. Already tried using Malwarebyte and superantispyware and the problem still occur. How do I fix this?

Crash ID: bp-37149764-ea6c-497b-925d-dc40d2161225 Whenever I try to open firefox, the "Mozilla Crash Reporter" pops up. Already tried using Malwarebyte and superantispyware and the problem still occur. How do I fix this?

被選擇的解決方法

hi, thanks for providing a crash id. unfortunately these crashes are probably triggered by malware that's present on your system and hooking into firefox (a lsp monitoring your network traffic labelled "chtbrkg.dll").

please go to the windows control panel / programs and remove all toolbars or potentially unwanted software from there (especially anything dubbed "adskip" or other programs you haven't installed intentionally). then please also try running security scans with various other tools like the free version of malwarebytes, adwcleaner & eset online one-time scanner.

finally you may also refer to this blog entry on how to proceed with malicious lsp-modules: https://blog.malwarebytes.com/cybercrime/2014/10/changes-in-the-lsp-stack/

從原來的回覆中察看解決方案 👍 0

所有回覆 (1)

more options

選擇的解決方法

hi, thanks for providing a crash id. unfortunately these crashes are probably triggered by malware that's present on your system and hooking into firefox (a lsp monitoring your network traffic labelled "chtbrkg.dll").

please go to the windows control panel / programs and remove all toolbars or potentially unwanted software from there (especially anything dubbed "adskip" or other programs you haven't installed intentionally). then please also try running security scans with various other tools like the free version of malwarebytes, adwcleaner & eset online one-time scanner.

finally you may also refer to this blog entry on how to proceed with malicious lsp-modules: https://blog.malwarebytes.com/cybercrime/2014/10/changes-in-the-lsp-stack/