Network adapter disables by itself

[test019]

Well, after quite a lot of research I can't really find any reason or solution why, and you'll bunch of pros probably figure it better than me.

 

There are two issues, mainly one.

 

A) The network adapter for ethernet, stops working after a few hours. Not always same time and seems not related with anything either gaming or watching just random youtube or twitch it disables itself down.

Sometimes takes 4hrs some other times 6hrs maybe even less than 2hrs. The adapter stays in disabled mode, and there is no option to turn it on again. Usually before that point, I can turn on or off without any issues. Then I found out, -Let's connect via wifi, onto the same network, and the wifi connection works fine for quite long hours. Once I had same issue in both adapters, but I believe it had to do with the ethernet adapter coming back alive after unknown time since that happens also sometimes, but it takes quite long time. Temps don't go above like 70Cº? And a pc reset will just make everything working fine once again.

 

B) Second issue is a black screen and followed by a ramping up of fans of my GPU to max and it wont stop until I force restart manually. Happened twice already, maybe related?

 

- Q-Codes that I've seen, 47, 41(after initialization it keeps on 41), 49, 45?, 42

- I already clean all drivers and re-installed manually from Asus directly the correct divers

- the nvme was in a laptop previously, and I just hard swapped and cleaned devices and stuff

- stress tested memory/cpu/gpu/psu and results showed no issues

- cables of the PSU reach but not with much slack, but they are neither into stress conditions

- armoury crate is fully updated 

• WIN Windows 10 Home x64 bit
• CPU AMD Ryzen 7 9800X3D 4.7 GHz 8-Core
• MOBO Asus ROG STRIX B650E-E GAMING WIFI ATX AM5 (bios ver.3222)
• RAM Crucial Pro 64 GB (2 x 32 GB) DDR5-6000 CL40 (XMP activated)
• M2 Samsung 980 Pro 2 TB M.2-2280 PCIe 4.0 X4
• GPU Asus TUF GAMING OC GeForce RTX 5070Ti 16gb
• PSU Asus ROG LOKI 1000W SFX

 

Ideas are welcome. Or solutions! :)

[OddOod]

2 hours ago, test019 said:

Second issue is a black screen and followed by a ramping up of fans of my GPU to max and it wont stop until I force restart manually. Happened twice already, maybe related?

That sounds like NV driver plague. Since the 50 series launch they've been terrible
 

2 hours ago, test019 said:

The network adapter for ethernet, stops working after a few hours

Honestly, that's probably just a dying NIC. It should qualify for RMA, but TBH, when faced with the option of a mobo swap (which in my experience takes longer than building a whole PC though YMMV) or shelling out for a 20$ NIC (or 60$ for a 10G NIC), I'm pretty much always gonna go for the NIC. I was gonna make a caveat about SFF PCs, but it seems that while you have a SFX PSU, you have a full sized mobo.
There is a chance that transplanting the Windows install to new hardware messed something up. First you should definitely do runs of SFC and DISM and check for any microcode optional updates. If that doesn't fix anything, one option would be to try booting a linux LiveUSB and see if you get the same problems on that. If so, it's definitely a hardware problem. If not, you may be in luck and only need to reinstall windows.

[Timme]

6 hours ago, test019 said:

a black screen and followed by a ramping up of fans of my GPU to max

Just the fans or the GPUs doing some work? 

[test019]

13 hours ago, Timme said:

Just the fans or the GPUs doing some work? 

From the two times once was gameing I believe and the second was super in chill mode

[test019]

16 hours ago, OddOod said:

That sounds like NV driver plague. Since the 50 series launch they've been terrible
 

Honestly, that's probably just a dying NIC. It should qualify for RMA, but TBH, when faced with the option of a mobo swap (which in my experience takes longer than building a whole PC though YMMV) or shelling out for a 20$ NIC (or 60$ for a 10G NIC), I'm pretty much always gonna go for the NIC. I was gonna make a caveat about SFF PCs, but it seems that while you have a SFX PSU, you have a full sized mobo.
There is a chance that transplanting the Windows install to new hardware messed something up. First you should definitely do runs of SFC and DISM and check for any microcode optional updates. If that doesn't fix anything, one option would be to try booting a linux LiveUSB and see if you get the same problems on that. If so, it's definitely a hardware problem. If not, you may be in luck and only need to reinstall windows.

Just to be safe, NIC is network interface card, right? And I believe so too, at least by the looks.

 

I can claim RMA asap and swap it for the same in like a week (or any MB better in that fact), but im doing some hopefully a last test next week swapping the MB for the 'ASUS ROG Strix X870E-E Gaming' a little overkill but should give me answers.

For the PSU i saw that it was powerful and reliable enough even for SFX to beat my other options non SFX, so far it goes golden, only like I said cables are not the longest but maybe cablemod in the future..

 

I forgot to say I did SFC and DISM already, but I did it again just in case. The linux idea is great, I'll try to test with the upcoming x870 first and then linux, as I have also the potential doubt that could be the cpu not sitting properly and that might show why all those codes, now btw showing 40, 41, 42. Cause from these codes comes to my mind bad sitting cpu, faulty ram, faulty cpu or wrong bios ram config. But I believe the ram works flawless and sits fine, and the cpu is fine but maybe not sitting properly, still will not make the network adapter disable itself just randomly for what I know.

 

Yesterday I had the issue once again, here is what I did or happened.

 

I was watching twitch while having a call in discord and friend told me to play Star Citizen, updated the game started playing, like 2hrs in, ethernet disables itself, I go wifi, after like 4 hrs? The wifi adapter still working but shows as it can't find any network (on but not showing) I run win troubleshoot on wifi and immediately finds and 'resets' itself and shows me all networks and auto connects, funny is that it restarted also the ethernet and I got both adapters up and running again I run the troubleshoot again on the working ehternet again and shows as 'ethernet does not have a valid IP address' but I'm connected and working in ethernet. To mention that I run cloudflare 1.1.1.1, but it causes no issues in my eyes.

 

[NanoBleed]

This doesn’t look like a simple driver issue. Since both Ethernet and Wi-Fi eventually fail and come back only after a reboot or troubleshooting, it’s likely a chipset or firmware problem. I’d boot a Linux live USB and leave it running for a few hours to see if it happens there too. If it does, it’s hardware. If not, it’s Windows or BIOS-related. You can also try disabling C-States or ASPM in BIOS. If nothing changes, swapping to the X870 board will confirm if the current motherboard is the culprit.

[test019]

40 minutes ago, NanoBleed said:

This doesn’t look like a simple driver issue. Since both Ethernet and Wi-Fi eventually fail and come back only after a reboot or troubleshooting, it’s likely a chipset or firmware problem. I’d boot a Linux live USB and leave it running for a few hours to see if it happens there too. If it does, it’s hardware. If not, it’s Windows or BIOS-related. You can also try disabling C-States or ASPM in BIOS. If nothing changes, swapping to the X870 board will confirm if the current motherboard is the culprit.

I believe the same is onto the chipset or NIC, I'm running the 3.4.2.1046 driver for the MediaTek Wireless LAN card (mediatek wifi 6e mt7922 rz616) which I believe is the culprit, but interestingly those are Asus drivers (and should be stable?), and I found that 3.4.2.1123 (from CCleaner) is the newest version, and still would not explain why I'm getting 40/41/42 codes...

 

Edit. I just searched for that specific NIC card and seems to be an interesting similar point, and also I found in some library the 3.4.0.1268 as the newest driver

• Similar issue, other MB but same NIC controller
• Library with NIC list with the 'new' driver (trustable?) (no idea how to install the driver manually like this)

[OddOod]

7 hours ago, test019 said:

NIC is network interface card, right?

Yes

[test019]

Small update after looking up for those drivers, the crashes of the NIC have been reduced significantly to the point that only happened once so far (today, and perhaps a second time, maybe also after installing the drivers, but substantially less) there is still some 'spikes' so to say where the network feels like it's losing itself.

 

I received the MB mentioned previously, but yet tests are coming soon.

[Allan B]

I had this with my asus tuf B650, it was the NIC drivers and Windows 11.  I dont recall the old\new version, but getting the latest drivers from the website resolved it for me about 6 months ago.

[test019]

UPDATE.

So after installing those found drivers manually, the crashes reduced substantially. But never disappeared and kept increasing, and shortening (instead of 2hrs they started happening like 15min to 30 which never happened previously)

AND the MOBO swap finally happened. (gotta say I've never seen such a chunk of aluminum for m2 drives, like wtf.) So far network crashes seems to 0, and only using ethernet so far.

But.. I had two crashes by now.

After setting my computer to sleep, this new MB seems to behave way better than the old one. Today when I tried to wake it up showed 47 / 48 code and did not wake up at all. Searching this, shows some post that is related with cpu temps? But it was sleeping mode and the cooling even at stress test never passed over 70C / 158F, so I have no clue on that? After forced manual restart, like 1h later the Issue B happened again. (is that even normal now with the new MB?) and like mentioned if I don't manually turn it off after that issue it keeps at that ramped mode endlessly.

 

• Now I have questionable questions, is my cpu the culprit of all this too?
• Sounds like the NIC was the clear issue of that motherboard, but was it the only thing broken?
• Does even the RAM have anything to do with this? It's supposed to be supported, but it won't show as it is a new part pcpartpicker or anywhere else, but it's official.

 

To my own questions, I feel that first MB was guilty and perhaps now the cpu too? But the ram seems to be fine and not related, and the GPU should only ramp up because something sends a signal to it, therefore I feel again pointing fingers to cpu/MB.

 

Hope to find a clear solution soon.

[test019]

So after much much testing, internet issues are gone. I tested in the ASUS ROG Strix X870E-E and at some point look like everything was fixed, sadly issue B arise more than before, but still in that new board was quite okay. I got a new unit of my first MB Asus ROG STRIX B650E-E and like mentioned all NIC issues are gone, but now it crashes constantly (even only writing this, it crashed) and now somehow when starting my pc I get a msn page open all the time.

In short words, I will open a new post with only issue B, but the solution for this, was clearly a damaged NIC or dying NIC.