F5F Stay Refreshed Power Users Networks Windows 11 gaming PC experiences Ethernet connectivity loss within a day.

Windows 11 gaming PC experiences Ethernet connectivity loss within a day.

Windows 11 gaming PC experiences Ethernet connectivity loss within a day.

G
gormatadon
Junior Member
Find
31
08-21-2021, 04:55 PM
#1
I'm facing a problem with my gaming PC's Ethernet connection. After a few days online, it suddenly loses network access—even though the high power plan is active. I've updated the networking and chipset drivers on my motherboard, and the static IP is set correctly. It still works fine when connected to 192.168.0.1. Could this be because the DHCP request failed at some point? When it can't connect, it stops responding to pings and even fails to reach my router (192.168.0.1). I can ping the loopback address but not other devices on the network. Connecting wirelessly fixes it, so the issue is likely with the physical or DHCP connection. I'm unsure if changing the Ethernet cable path or switching networks would help.
Reply
Reply
G
gormatadon
08-21-2021, 04:55 PM #1

I'm facing a problem with my gaming PC's Ethernet connection. After a few days online, it suddenly loses network access—even though the high power plan is active. I've updated the networking and chipset drivers on my motherboard, and the static IP is set correctly. It still works fine when connected to 192.168.0.1. Could this be because the DHCP request failed at some point? When it can't connect, it stops responding to pings and even fails to reach my router (192.168.0.1). I can ping the loopback address but not other devices on the network. Connecting wirelessly fixes it, so the issue is likely with the physical or DHCP connection. I'm unsure if changing the Ethernet cable path or switching networks would help.

Reply
Reply
F
FanvonLOGO
Member
Find
61
08-22-2021, 12:06 AM
#2
The static IP configuration is likely managed on the router. The specific settings for PC would depend on the device, but it’s usually handled through its network settings. Whether it uses a static or DHCP assignment isn’t clear from the context. You’ve already considered tools like Windows Network Troubleshooter and changing to DHCP—those are good steps to take during the outage.
Reply
Reply
F
FanvonLOGO
08-22-2021, 12:06 AM #2

The static IP configuration is likely managed on the router. The specific settings for PC would depend on the device, but it’s usually handled through its network settings. Whether it uses a static or DHCP assignment isn’t clear from the context. You’ve already considered tools like Windows Network Troubleshooter and changing to DHCP—those are good steps to take during the outage.

Reply
Reply
A
ArceusHD
Member
Find
154
08-22-2021, 08:51 AM
#3
The static IP configurations were applied on both routers (new and existing). I also experimented with another IP address, but the same problem persisted. Additionally, regarding the DHCP range of 100-255, the IPs assigned to this device fall below that threshold, preventing duplicate conflicts. On the PC side, I've used both DHCP and static settings with varying addresses compared to the router's configuration. While it occasionally receives an IP via DHCP, it doesn't consistently connect or function properly. It also fails to renew its DHCP lease in this region. I ran the network troubleshooter, which pointed to the modem/router as the issue. All other devices on the network are working fine.
Reply
Reply
A
ArceusHD
08-22-2021, 08:51 AM #3

The static IP configurations were applied on both routers (new and existing). I also experimented with another IP address, but the same problem persisted. Additionally, regarding the DHCP range of 100-255, the IPs assigned to this device fall below that threshold, preventing duplicate conflicts. On the PC side, I've used both DHCP and static settings with varying addresses compared to the router's configuration. While it occasionally receives an IP via DHCP, it doesn't consistently connect or function properly. It also fails to renew its DHCP lease in this region. I ran the network troubleshooter, which pointed to the modem/router as the issue. All other devices on the network are working fine.

Reply
Reply
R
RYAANOO
Member
Find
52
08-22-2021, 10:55 AM
#4
I received another 2.5GB NIC and haven’t experienced any problems yet. It seems the original issue was related to the Intel NIC on my motherboard, possibly due to a driver problem or hardware fault.
Reply
Reply
R
RYAANOO
08-22-2021, 10:55 AM #4

I received another 2.5GB NIC and haven’t experienced any problems yet. It seems the original issue was related to the Intel NIC on my motherboard, possibly due to a driver problem or hardware fault.

Reply
Reply
T
ttj_16
Member
Find
116
08-23-2021, 02:16 PM
#5
Intel continues refining the I225-V series, yet it remains unreliable due to ongoing hardware and driver problems. Swapping it out seems like the best course of action. Disappointing for everyone who has these NICs integrated into their motherboards!
Reply
Reply
T
ttj_16
08-23-2021, 02:16 PM #5

Intel continues refining the I225-V series, yet it remains unreliable due to ongoing hardware and driver problems. Swapping it out seems like the best course of action. Disappointing for everyone who has these NICs integrated into their motherboards!

Reply
Reply
L
levo14
Member
Find
247
09-11-2021, 04:35 PM
#6
I’m not sure if Intel is responsible here. Many users report Aquantia cards failing on Windows, and I’ve seen my AQC107 crash the entire Windows network stack right after a Steam download begins. Yet the same card runs flawlessly on Linux. Interestingly, switching to an i225-V B3 resolved the issue completely. There were no problems with the B3 version on a pfSense device either. Unless there’s some unusual manufacturing defect, I believe the problem lies with Windows itself.
Reply
Reply
L
levo14
09-11-2021, 04:35 PM #6

I’m not sure if Intel is responsible here. Many users report Aquantia cards failing on Windows, and I’ve seen my AQC107 crash the entire Windows network stack right after a Steam download begins. Yet the same card runs flawlessly on Linux. Interestingly, switching to an i225-V B3 resolved the issue completely. There were no problems with the B3 version on a pfSense device either. Unless there’s some unusual manufacturing defect, I believe the problem lies with Windows itself.

Reply
Reply