Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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.

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.

Learn More

kernel panic / "bluescreen" re: tcpip.sys when firefox is launched repeatedly or open for several hours

  • 1 odgovor
  • 2 ima ovaj problem
  • 27 views
  • Posljednji odgovor poslao Shadow110

more options

I support several users having this reoccurring problem (All Windows 10 w/ creators update, running webroot secureanywhere, but problem persists if webroot realtime protection + firewall is disabled)

Periodically when firefox is running, but usually immediately on the second or third time firefox is launched after the computer starts up, a kernel panic occurs with the reference mentioning tcpip.sys. Examining the minidump with bluescreenview shows ntoskrnl.sys involved as well.

I would not normally suspect this issue to be caused by firefox, but since switching the affected users to chrome or edge, not a single bluescreen has occurred. Out of curiosity I created a fresh firefox profile on one user's computer which had not bluescreened in days, launched firefox with the new profile, browsed to a website, closed firefox, launched it again, and immediately got another bluescreen referencing tcpip.sys.

The users' firefox profile folders are normally in shares on a fileserver (in "my documents" via folder redirection) but the issue persists with profiles stored locally, fresh profiles, "refresh firefox", updating to "quantum" beta, and creating a shortcut for the users that always starts firefox in safe mode.

The problem started roughly 2 weeks ago (week of march 12-16, reports were slow to come in) and all of the firefox installations have been kept up to date since then.

I support several users having this reoccurring problem (All Windows 10 w/ creators update, running webroot secureanywhere, but problem persists if webroot realtime protection + firewall is disabled) Periodically when firefox is running, but usually immediately on the second or third time firefox is launched after the computer starts up, a kernel panic occurs with the reference mentioning tcpip.sys. Examining the minidump with bluescreenview shows ntoskrnl.sys involved as well. I would not normally suspect this issue to be caused by firefox, but since switching the affected users to chrome or edge, not a single bluescreen has occurred. Out of curiosity I created a fresh firefox profile on one user's computer which had not bluescreened in days, launched firefox with the new profile, browsed to a website, closed firefox, launched it again, and immediately got another bluescreen referencing tcpip.sys. The users' firefox profile folders are normally in shares on a fileserver (in "my documents" via folder redirection) but the issue persists with profiles stored locally, fresh profiles, "refresh firefox", updating to "quantum" beta, and creating a shortcut for the users that always starts firefox in safe mode. The problem started roughly 2 weeks ago (week of march 12-16, reports were slow to come in) and all of the firefox installations have been kept up to date since then.

All Replies (1)

more options

I think this is where your issue is : webroot secureanywhere I would suggest checking into the appropriate Community forum as there are several listed : https://tinyurl.com/y9n454uc and check if others are having the issue.

If you have a bug, file a bug report. https://bugzilla.mozilla.org/ Bug Writing Guidelines : https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines