Torch Browser Main Errors – Solution

If Torch pages crash, fail to load, or show DNS/network codes, the same fixes used for Chrome typically resolve them in Torch because both share the Chromium engine, so this guide consolidates the most reliable steps for each error code.

Aw, Snap! page crash

This is a generic page crash usually tied to low memory, corrupted profile data, bad extensions, security software conflicts, or outdated builds in Chromium-based browsers like Torch. Close heavy tabs/apps, update Torch, and disable extensions or security software temporarily to isolate the cause.

Solution Steps

• Close other apps and tabs, then try the page again to free memory.
• Update Torch to the latest build and reboot Windows.
• Disable all extensions, test, then re-enable one by one to find conflicts.
• Temporarily pause antivirus/firewall to test, then re-enable if the page works.
• Reset browser settings to defaults if crashes persist.
• Optional advanced check: Windows SFC/DISM to repair system files.

Error 101 ERR_CONNECTION_RESET

Connection was dropped before data exchange, commonly by unstable networks. The fix path is to rule out local network and browser data, then reset TCP/IP and DNS.

Solution Steps

• Restart router and PC to refresh the connection.
• Clear browser cache/cookies for “All time.”
• Disable VPN/proxy and try again.
• Temporarily pause firewall/AV to test, then re-enable.
• Flush DNS and renew IP.
• Change to public DNS.
• Disable extensions and retest the page.

Error 102 ERR_CONNECTION_REFUSED

This indicates the target server or local stack refused the connection, often due to proxy misconfig, extensions, cache, or router/DNS issues.

Solution Steps

• Check site status from another device or network.
• Restart the router and PC.
• Clear cache/cookies and retest.
• Turn off any proxy in system/Chrome network settings.
• Change DNS to Google or Cloudflare.
• Disable all extensions, then re-enable one by one.
• Reinstall/update the browser if nothing else helps.

Error 104 ERR_CONNECTION_FAILED

This generic failure often follows prolonged uptime or driver/stack issues and can be cleared by Winsock/TCP resets, cache clears, and driver updates. If it recurs, audit extensions and security tools.

Solution Steps

• Power-cycle router and PC.
• Clear browser cache/cookies for “All time.”
• Reset Winsock/TCP/IP, then reboot.
• Disable VPN/proxy and test direct connection.
• Disable extensions and retest, then re-enable selectively.
• Update network adapter drivers and Windows.

Error 105 ERR_NAME_NOT_RESOLVED

Common fixes include flushing OS and Chrome DNS caches, switching DNS, clearing cache, and checking hosts.

Solution Steps

• Flush OS DNS cache and reboot.
• Clear Chrome DNS cache at chrome://net-internals/#dns.
• Switch to public DNS.
• Clear cache/cookies for “All time.”
• Review hosts file entries for the domain.
• Disable DNS preloading/prefetch temporarily and retest.

You can find more browsers and other useful programs for Windows in our Office & Productivity section.

Error 15 ERR_SOCKET_NOT_CONNECTED

This typically points to stale/broken socket pools or network stack hitches. Flushing Chrome socket pools and clearing cache usually helps, alongside standard network hygiene. If it persists, restart devices, disable VPN/proxy, and update Torch/Chromium core.

Solution Steps

• Restart the browser and test the site.
• Go to chrome://net-internals/#sockets and click “Flush socket pools.”
• Clear cache/cookies for “All time.”
• Disable VPN/proxy and try again.
• Reboot modem/router and PC.
• Disable extensions and test and re-enable selectively.
• Update or reinstall the browser if needed.

Conclusion

Chromium-grade hygiene solves most Torch issues: clear cache, disable extensions, pause security tools briefly, reset network stacks, and refresh DNS or socket pools, escalating to router/driver updates or a clean profile only if simpler steps fail. With these targeted checklists for each code, you can quickly eliminate local causes before assuming a remote server problem and restore stable browsing in Torch.