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

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

loss of network connection (socket loss/crash)

  • 3 valiny
  • 1 manana an'ity olana ity
  • 13 views
  • Valiny farany nomen'i cor-el

more options

When I'm running speed test (Shaw ca) from firefox I get loss/crash of socket connection. I have no problem when running same test from chrome. I get random crashes on firefox which crashes my network socket and i have to reboot. 300 Mbps connection. window 7

When I'm running speed test (Shaw ca) from firefox I get loss/crash of socket connection. I have no problem when running same test from chrome. I get random crashes on firefox which crashes my network socket and i have to reboot. 300 Mbps connection. window 7

All Replies (3)

more options

What is the site you used for the test and what sites did it connect to that was different from chrome? I know I done the test and they connect to two different places.

more options

speedtest.shaw.ca same place for both browsers. the speed test is from modem to main plant and back to my modem. chrome gets 276 Mbps down and 16 Mbps up. firefox crashes inside 10 seconds. lastest drivers for nic. windows is up to date. firefox has default settings and is the latest version.

more options

Does Firefox crash or does a Windows network component crash?

If you have submitted crash reports then please post the IDs of one or more recent crash reports that start with "bp-".

  • bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

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

  • 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.

See also:

You can also check the Windows event log.