✕ BSOD Stop Codes
TCPIP_AOAC_NIC_ACTIVE_REFERENCE_LEAK BSOD on Windows 11 — Fix the stop code (2026)
TCPIP_AOAC_NIC_ACTIVE_REFERENCE_LEAK (stop code 0x0000017E) is one of the most reported Windows blue screen stop codes. In most cases it's a recent driver update, a failing storage device, or a corrupted Windows file — not a bricked PC. Follow the steps in order and you will isolate the cause without reinstalling Windows.
- Time
- 25 min
- Difficulty
- medium
- Applies to
- Windows 11, Windows 10
- Updated
- May 25, 2026
Error message
Your PC ran into a problem and needs to restart. Stop code: TCPIP_AOAC_NIC_ACTIVE_REFERENCE_LEAK (stop code 0x0000017E)
Symptoms
- ▸Blue screen with the message "TCPIP_AOAC_NIC_ACTIVE_REFERENCE_LEAK" and stop code 0x0000017E
- ▸PC reboots automatically a few seconds after the blue screen appears
- ▸Boot loop where Windows fails before reaching the desktop
- ▸Minidump files appear in
C:\Windows\Minidump\after each crash
Likely causes
- ▸TCP/IP stack reference leak on a network adapter (often after sleep / wake)
- ▸Outdated Wi-Fi or Bluetooth driver
- ▸Buggy VPN client
- ▸Recent Windows network stack update
How to fix it — step by step
- 01
Boot into Safe Mode
Hold Shift while clicking Restart, then choose
Troubleshoot → Advanced options → Startup Settings → Restart → 4 (Safe Mode). If the system is stuck in a boot loop, force three power-cycles during boot to trigger Automatic Repair, which gives you the same menu. - 02
Roll back recent driver updates
TCPIP_AOAC_NIC_ACTIVE_REFERENCE_LEAK (stop code 0x0000017E) most commonly fires after a driver change. Open
Device Manager, right-click any device updated in the last week →Properties → Driver → Roll Back Driver. Focus on GPU, storage controller and chipset drivers first. - 03
Run SFC and DISM
Repair the Windows system files that the kernel needs at every boot.
sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth - 04
Check disk and memory hardware
Run
chkdsk C: /f /rin an elevated PowerShell (a reboot is required). For RAM, openmdsched.exeand choose the standard test, or run MemTest86 from USB for at least 4 passes. - 05
Look up the failing driver in the minidump
Install WinDbg Preview from the Microsoft Store and open
C:\Windows\Minidump\. The first !analyze -v output names the failing module — search for it and update or roll back specifically that driver.!analyze -v - 06
Use System Restore as a clean reset
From the same Advanced options menu, choose
System Restoreand pick a restore point from before the BSOD started. This is safer than reinstalling Windows and keeps your files intact.