Hello Max,
Thank you for posting question on Microsoft Windows Forum!
I would like to share my insight with you about the possible causes for this symptom. The primary suspect might be the network stack flooding on boot. When Windows boots, multiple services (OneDrive synchronization, Windows Update peer-to-peer delivery optimization, telemetry reporting, and cloud apps) initialize simultaneously. If a recent patch or a corrupted Winsock/TCP stack mismanages socket pooling, it can fire thousands of concurrent connection requests or local multicast/broadcast packets instantly, choking the router's state table. On the other hand, Steam utilizes aggressive multi-connection peer downloads and UDP content distribution. If your network adapter's Large Send Offload (LSO) or Receive Side Scaling (RSS) is misbehaving due to an updated driver, your PC will dump raw packet chunks faster than the router can queue them, filling the router's hardware buffers and starving every other device on the LAN.
The suggestion here is to try disabling Delivery Optimization by navigating to Settings > Windows Update > Advanced options > Delivery Optimization and toggle "Allow downloads from other PCs" to Off. Then, restart your PC and see if the network still crashes.
Since Network adapter drivers updated automatically via Windows Update frequently enable aggressive hardware offloading that crashes consumer router buffers during heavy throughput. It is suggested to adjust network adapter offload settings by opening Device Manager. Expand Network adapters, right-click your primary Ethernet or Wi-Fi adapter, and select Properties. Go to the Advanced tab and modify these settings. Large Send Offload v2 (IPv4 & IPv6) Set to Disabled (This frequently fixes router crashes during high-speed downloads like Steam). Receive Side Scaling (RSS) making sure it is enabled and Energy Efficient Ethernet / Green Ethernet Set to Disabled. Then Go to the Power Management tab and uncheck "Allow the computer to turn off this device to save power".
Another suggestion is to reset the local Windows network stack. Since corrupted TCP/IP parameters or Winsock catalogs often cause packets to loop or stall after major cumulative updates. Open Command Prompt as Administrator and run the following commands one by one
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Then restart your computer immediately after running the above commands.
Until this moment, there is no single confirmed KB update to blame for this specific symptom. If the issue started roughly a week ago, look into your update history for any recent cumulative updates or out-of-band patches installed around the time the issue began. If a problematic update lines up precisely with when your desktop began crashing the network, use the Uninstall updates option to roll it back temporarily.
If the provided information is helpful! It is appreciated to consider clicking "Accept Answer". Should you have more questions, feel free to leave a message. Have a nice day!