Overclocking BSOD bringing down network for all devices.

Toggle sidebar Toggle sidebar
Faux_Grey

Faux_Grey

Honorable
Sep 1, 2012
747
1
11,360
Long story short, my main desktop occasionally bluescreens. (I love messing around with voltages)

at home I have many other devices on the network (switches, router, firewall, wireless access points, VMware servers, etc)

The weird/unexplainable thing is, whenever my computer bluescreens, ALL of the above devices suddenly stop working.

When my desktop BSODs, everything stops, no device can ping any other device (even if I directly cable them together)

From my other computers, I then can't get into any web management page of any other device, or access the internet.

If I plug my other pc directly into the router, internet doesn't work until I reboot the router.
When I re-connect my access points into the (now working) router, their network doesn't work until I reboot them.

Same story with all the other appliances, it's not just one device that fails and stops network connectivity, it's all of my devices failing at the exact same time as a BSOD.


WTF is going on here? Even my VIRTUAL machines hosted on my VMware server are affected by this, and don't inter-communicate until I reboot them.

Could a overclocking-related BSOD cause some form of electromagnetic interference which is affecting my entire house and somehow specifically breaking the network adapters of all my devices?
 
Solution
J
when you plug your new computer to the router, you should start cmd.exe as an admin and run
ipconfig.exe /release
ipconfig.exe /renew
(so you don't have to reboot the router or the computer.)

and see if the router will give you a proper address.

- the overclocking would not cause any electromagnetic interference with other devices outside the case.

it is hard to imagine one computer going down breaking the other computers network access unless they are being routed through the first computer.
if that is the case, you would have the same effect if you just unplugged the network cable from the machine that gets the bugcheck.

the bugcheck is a windows doing a forced shutdown of the computer. There might be some strange exceptions...
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
when you plug your new computer to the router, you should start cmd.exe as an admin and run
ipconfig.exe /release
ipconfig.exe /renew
(so you don't have to reboot the router or the computer.)

and see if the router will give you a proper address.

- the overclocking would not cause any electromagnetic interference with other devices outside the case.

it is hard to imagine one computer going down breaking the other computers network access unless they are being routed through the first computer.
if that is the case, you would have the same effect if you just unplugged the network cable from the machine that gets the bugcheck.

the bugcheck is a windows doing a forced shutdown of the computer. There might be some strange exceptions if your motherboard is using some networking BIOS extensions or if you have a very fancy network card with its own processor. (they are pretty expensive)
basically, if the transport is being supported by the BIOS it could keep connections open until the cable is unplugged for 300 seconds or the machine power is turned off.


you might wait 3.5 minutes after a crash to see if your network starts up again.
(it might be 300 seconds, I forget which. it is the tcp/ip timeout value)

-you might want to update the firmware in your router also.





 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom