Internet randomly disconnects

[✪Rich&Nuts]

Reddit communities have not responded to my question so I hope here I'll find a solution. I've been getting internet issues the past few months, occasionally the internet would disconnect after waking it up from a sleep state. I am hard wired and when I check the intel(R) ethernet Controller 1226-V device I get the error code 43. I try to update the drivers, but I have the latest versions already. I am wondering if this is a windows 11 issue or is there something wrong with my hardware? Searching hasn't been helping me pin point my specific issue. To fix it I have to disable and re-enable it again, but it gets annoying after a few times.

[Bad 💀 Motha]

Uninstall the driver, reboot the PC.
Go to your web browser > Google search > Intel Driver Assist.
Go to the link (make sure it's intel offical website) let it detect your PC and update any Intel related drivers.

Stop using Sleep Modes.
Just set the Display to turn off after X amount of idle time.

[✪Rich&Nuts]

Messaggio originale di Bad 💀 Motha:

Uninstall the driver, reboot the PC.
Go to your web browser > Google search > Intel Driver Assist.
Go to the link (make sure it's intel offical website) let it detect your PC and update any Intel related drivers.

Stop using Sleep Modes.
Just set the Display to turn off after X amount of idle time.

I uninstalled the driver and rebooted my pc, looks like it reinstalled itself after startup? Hopefully this is a perma solution and won't randomly disconnect

[Illusion of Progress]

It sounds like Windows update chose one of its choosing (or it reinstalled the prior one since it found it still). Windows update forced updates on my i225V a lot early in its life.

Both the i225V (which has three revisions of varying behavior) and i226V Intel NICs are both known to be problematic to some extents, yes. I'm not sure of the severity of the issues with the latter but it's amazing Intel turned around and messed up right after having just done so with the former one, and multiple revisions of it at that. I've made it a point to avoid either of these NICs after having issues with the i225V (second revision) on my previous motherboard.

Randomly cutting out is one of the known issues, yes. So this might be a "hardware issue that isn't faulty hardware" so to speak, or maybe some driver or NIC settings can work around it.

If I'm remembering right from the i225V, it was mostly 2.5 Gbps link speeds that worsened some of the issues. I'm not sure if this is the case for the i226V, but I would try that if I was in that spot. Are you using a 2.5 Gbps link speed between yourself and the router? And if so, do you need it to get the most out of either your home network or internet connection? It might be worth trying 1 Gbps to see if that helps.

[Bad 💀 Motha]

This is why I find myself having to use Win10/11 PRO; never Home
As the device manager option for NO to fetching drivers through WU does not appear to have any effect. I can force that off via Group Policy. You should be able to do this in Home Edition with a Registry edit.

[plat]

I recently had this issue so I'll share some things, one of which successfully resolved my Interent-disconnected issue and prevented a costly service visit from the rip-off of an iSP I have to tolerate.

Disconnect the co-axial cable from the modem. It's the one with the metallic connector in the back, you unscrew it. Wait maybe 30 seconds, then screw it back in. Do you have extra yellow cables? Swap in new ones, one at a time. Make sure they are all blinking--the back of the PC, as well as the backs of the router and modem. if there is no activity, nothing is being routed from the outside in. So that needs to checked as well and it'll help you narrow down what may be defective equipment.

[Illusion of Progress]

Messaggio originale di Bad 💀 Motha:

This is why I find myself having to use Win10/11 PRO; never Home
As the device manager option for NO to fetching drivers through WU does not appear to have any effect. I can force that off via Group Policy. You should be able to do this in Home Edition with a Registry edit.

Having a certain Windows version is not going to help if the issue is with known flawed NIC hardware. The drivers were probably being pushed because the issues with the NIC at the time were just that bad and Intel was desperately trying to fix a number of issues in software.

Also when I say "forced updates" it may have been simply presenting them through the optional list and I was choosing them, or maybe they were in the priority updates. I can't remember honestly, but I noticed it was being updated only when I was choosing to do the usual batch of Windows updates and not randomly on its own.

The only driver I remember for sure that forced itself to update on its own time was nVidia's drivers and it decided to do it while I was playing a game and I thought I was having a failure somewhere. Likewise, some of nVidia's older drivers were making headlines for having security issues in them so I took it that might be part of why.

I'm not a fan of forced updates but one way or another we all eventually get forced to the newer stuff and older stuff increasingly has more security issues (seemingly more often these days).

[Bad 💀 Motha]

Almost every time I use a system that has Realtek LAN or WiFi based chipsets it has these issues. It's like the chip gets too hot and then restarts itself, resulting it device disappearing from the system, then after a minute or so, comes back again. Like a driver restart.

When I use Killer or Intel based chipsets I don't experience these kinds of issues.

I grabbed a TP-Link USB 3.0 WiFi-6 adapter for a friend at work cause his Desktop had an outdated Wireless-G card. This adapter while when working gets great signal due to being external with 2 antennas and is getting 350Mbps over WiFi from a Tmobile 5G box; the adapter is junk. No matter the network adapter settings we've tried, it keeps randomly rebooting. Can't narrow down the actual reasons. You could be downloading a Steam game @ 350Mbps and it will be fine, or it may drop out after a while, it's so random. Then you could also be nearly idle, loading up text based forum and posting and such and it'll randomly cut out.

Realtek chipsets are complete junk.

[Bad 💀 Motha]

Messaggio originale di Illusion of Progress:

Messaggio originale di Bad 💀 Motha:

This is why I find myself having to use Win10/11 PRO; never Home
As the device manager option for NO to fetching drivers through WU does not appear to have any effect. I can force that off via Group Policy. You should be able to do this in Home Edition with a Registry edit.

Having a certain Windows version is not going to help if the issue is with known flawed NIC hardware. The drivers were probably being pushed because the issues with the NIC at the time were just that bad and Intel was desperately trying to fix a number of issues in software.

Also when I say "forced updates" it may have been simply presenting them through the optional list and I was choosing them, or maybe they were in the priority updates. I can't remember honestly, but I noticed it was being updated only when I was choosing to do the usual batch of Windows updates and not randomly on its own.

The only driver I remember for sure that forced itself to update on its own time was nVidia's drivers and it decided to do it while I was playing a game and I thought I was having a failure somewhere. Likewise, some of nVidia's older drivers were making headlines for having security issues in them so I took it that might be part of why.

I'm not a fan of forced updates but one way or another we all eventually get forced to the newer stuff and older stuff increasingly has more security issues (seemingly more often these days).

Sorry for that quote I was referring to the setting in Windows 10/11 that is related to the user telling the OS + WU not to auto install/update drivers through WU. It does not appear to work at all.

With Win10 Pro + Group Policy you can go in there and set...

Optional Driver Updates through Windows Updates = Disable

and it works 100%

[✪Rich&Nuts]

Messaggio originale di Illusion of Progress:

It sounds like Windows update chose one of its choosing (or it reinstalled the prior one since it found it still). Windows update forced updates on my i225V a lot early in its life.

Both the i225V (which has three revisions of varying behavior) and i226V Intel NICs are both known to be problematic to some extents, yes. I'm not sure of the severity of the issues with the latter but it's amazing Intel turned around and messed up right after having just done so with the former one, and multiple revisions of it at that. I've made it a point to avoid either of these NICs after having issues with the i225V (second revision) on my previous motherboard.

Randomly cutting out is one of the known issues, yes. So this might be a "hardware issue that isn't faulty hardware" so to speak, or maybe some driver or NIC settings can work around it.

If I'm remembering right from the i225V, it was mostly 2.5 Gbps link speeds that worsened some of the issues. I'm not sure if this is the case for the i226V, but I would try that if I was in that spot. Are you using a 2.5 Gbps link speed between yourself and the router? And if so, do you need it to get the most out of either your home network or internet connection? It might be worth trying 1 Gbps to see if that helps.

I believe that I am using a router up to 2.5 gbps speeds. I currently have fiber internet that is 1 gig. But so far uninstalling the device and restarting the pc has fixed the issue, no internet drop so far

[Bad 💀 Motha]

Please keep in mind that whenever you install a network adapter driver, the device then has various settings avaiable, some might need to be changed from whatever the defaults are.

Device Manager > Network Adapter > Adapter Name > Properties
First disable all power management options.
Click OK to apply changes.
Then go back into Properties > Advanced and within here are your network adapter settings.

For example you can disable 2.4Ghz altogether so it never hops on or switches to that mode if you prefer to use 5Ghz. Then there are options in there for Roaming and Power Output. Try setting Roaming to the lowest setting and set the Power to the Max.

Also keep in mind if you update this device driver over time, all the settings might go back to defaults after such an update.

[✪Rich&Nuts]

Messaggio originale di Bad 💀 Motha:

Please keep in mind that whenever you install a network adapter driver, the device then has various settings avaiable, some might need to be changed from whatever the defaults are.

Device Manager > Network Adapter > Adapter Name > Properties
First disable all power management options.
Click OK to apply changes.
Then go back into Properties > Advanced and within here are your network adapter settings.

For example you can disable 2.4Ghz altogether so it never hops on or switches to that mode if you prefer to use 5Ghz. Then there are options in there for Roaming and Power Output. Try setting Roaming to the lowest setting and set the Power to the Max.

I've turned off the option where the network device is in power safe mode. I am assuming this should fix the issue if I put the pc to sleep. I am hard wire so I shouldn't be too concerned with the wireless setting

[Bad 💀 Motha]

Sleep Mode is just a problem all on its own; it never really works very well in Win10/11

Best option is simply never use it. What is even the point? This is something I can't understand about PC users. Sleep Mode on PC is pointless, since the PC can boot into your OS and be ready to go in 10-15 seconds, WTF is the point of sleep mode? Just leave the PC on and press WINKEY+L when you walk away from it. The Display(s) will go to sleep this way regardless of your Power Options settings.

And unless you are forcing CPU clocks 100% those will go idle and auto downclock all on their own.

[✪Rich&Nuts]

Messaggio originale di Bad 💀 Motha:

Sleep Mode is just a problem all on its own; it never really works very well in Win10/11

Best option is simply never use it. What is even the point? This is something I can't understand about PC users. Sleep Mode on PC is pointless, since the PC can boot into your OS and be ready to go in 10-15 seconds, WTF is the point of sleep mode? Just leave the PC on and press WINKEY+L when you walk away from it. The Display(s) will go to sleep this way regardless of your Power Options settings.

And unless you are forcing CPU clocks 100% those will go idle and auto downclock all on their own.

Mainly to save power from what I hear in the pc community

[Bad 💀 Motha]

You are either using the PC, or you are not.

If you are going to walk away from it for a long period, turn it off.

If you configure your PC properly, it shouldn't use much power at idle.

If you leave it on however, you can have it do things for you while you walk away and do other real-life stuff, like go to the store, wash dishes, do laundry, clean the house, etc. You could easily que up various downloads before you walk away. Then start those when ready to take a break. Having it download stuff while you are off doing other things.

If you are going to give it a break for a few hours and not have it doing anything, might as well turn it off. Sleep Mode is totally worthless because it can't do anything in the background when you put it in sleep mode.

[Illusion of Progress]

Messaggio originale di Bad 💀 Motha:

Realtek chipsets are complete junk.

Not sure why you have an axe to grind against Realtek here. This thread isn't about any one of our NIC preferences or our empirical anecdote evidence of why something is good or bad. It's about someone using a particular NIC and having issues, issues which are known with said NIC, so it was relevant to bring up. I know from experience the i225V also had issues. Realtek NICs also have their own issues yes, but that's neither here nor there.

Messaggio originale di ✪Rich&Nuts:

I believe that I am using a router up to 2.5 gbps speeds. I currently have fiber internet that is 1 gig. But so far uninstalling the device and restarting the pc has fixed the issue, no internet drop so far

Hopefully this fixed it! It might have been a corrupt driver install, or the reinstall gave a different (newer or older) version which is behaving better in the circumstances the other one was not.

The flurry of updates Intel released for the i225V fixed some of the issues I had with my i225V, but one was never fixed. Going to another motherboard (not for that reason) with a different NIC and I don't have that issue anymore. Hopefully you have better luck here.