Segmentation fault

[trishitchar]

Node.js Version

v22.18.0

NPM Version

11.5.2

Operating System

windows, (tried linux too same issue happened before)

Subsystem

path

Description

Random Network Issues on Windows – c/Program Files/nodejs/npm: line 65: 1374 Segmentation fault "$NODE_EXE" "$NPM_CLI_JS" "$@"

I'm facing a recurring and highly inconsistent issue on my new Windows machine. When accessing websites or running development servers (Node.js or otherwise). The errors appear randomly and sometimes resolve on their own without any clear reason.

Symptoms

When trying to load web pages in the browser or connect to local servers, I often see:

• net::ERR_BLOCKED_BY_CLIENT
• net::ERR_SSL_PROTOCOL_ERROR
• net::ERR_CONNECTION_CLOSED

Sometimes it works fine, but other times these errors block access entirely. This inconsistency makes it very difficult to pin down the root cause.

Environment

• OS: Windows 11 (fully updated)
• Node.js: Latest LTS (also tested with earlier versions)
• Browser: Chrome / Edge (both show similar issues)
• Antivirus/Firewall: Windows Defender (no third-party AV installed)
• Network: Stable wifi connection, working fine in another device

Observations

• The issue sometimes resolves itself
• These errors happen both in the browser and occasionally in development tools (e.g. when Node.js tries to connect to services or APIs).
• But working fine in some native apps like telegram or xbox.

Things I’ve Tried

• Flushed DNS (ipconfig /flushdns), Disabled/enabled network adapter, Restarted router, Cleared SSL state, Tried different browsers, Reinstalled Node.js, Checked system time/date, Ran sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth (no issues found), Temporarily disabled Windows Defender Firewall

Possible Theories

• Misconfigured or faulty network driver?
• System-level proxy or firewall settings interfering?
• Malware or misbehaving app blocking secure connections?
• Hardware (NIC or motherboard) issues?

What I’m Looking For

• Any ideas for deeper network troubleshooting steps
• Ways to diagnose faulty network adapters or drivers
• Whether this might be related to Node.js, even if indirectly
• Tools or scripts to monitor/debug low-level network errors on Windows

---

---

---

---

Minimal Reproduction

No response

Output

No response

Before You Submit

• I have looked for issues that already exist before submitting this
• My issue follows the guidelines in the README file, and follows the 'How to ask a good question' guide at https://stackoverflow.com/help/how-to-ask

[avivkeller]

(Node.js or otherwise)

If this is happening on multiple clients and platforms, it's likely not an issue with Node.js, but rather some system-level configuration

[trishitchar]

Thanks for your reply, Aviv.

• I was wondering if you know any workaround to fix this issue, since your team encounters similar issues often. I asked for help because I haven’t been able to run my Node.js app for quite some time.

Thanks again 👍🏻

[avivkeller]

This is likely either a problem with the machine (ERR_SSL_BAD_RECORD_MAC_ALERT), or the website you are connecting to (ERR_SSL_BAD_PROTOCOL).

Regardless, this isn't something Node.js is responsible for, nor equipped to provide support on.