ROG CROSSHAIR X670E EXTREME - Marvell aqnic650 10g on mobo crashes

[Teletha]

Hi i have some major problem with the 10G connection on the mobo 

it did hold up a bit longer but it happened again now 2 times but the first time was a light disconnect but the 2nd one a couple of days later was a hard lockup and i needed to reset the adapter for it to start working again.

while it was being locked up i checked ipconfig;

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell AQtion 10Gbit Network Adapter
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::907e:64b5:586:cc61%10(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.167.190(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
really weird it looks like it reverted to another IP cause it can't reach the DHCP server?  i tried to force the IP it should have from the router since it is a static ip set on the router for the MAC 

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell AQtion 10Gbit Network Adapter

DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::907e:64b5:586:cc61%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.119(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 192.168.1.1
1.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

it managed to apply it but it still wont connect, not even the LAN since i still can't reach my router:

------

ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.

.....

tracert  192.168.1.1

Tracing route to 192.168.1.1 over a maximum of 30 hops

  1  mainPC [192.168.1.119]  reports: Destination host unreachable.

Trace complete.

-----

I'm out of ideas. i can only get it to work again if i disable and re-enable the adapter then it starts working again.... 

im wondering if it is a bad windows install since i did just move my nvme disk from my AM4 5950x build to this am5 and then upgraded from win10 to win11 on the am5 system via the windows update thing so not a clean install or anything. But i am sceptical to that since everything else is working great. 
its either that or a bad network chip? 

[Devar]

I have exactly the same issue with the marvell 10g on my ROG Crosshair X670E Extreme. The NIC will crash and you have to disable/enable to get it working again. I can't pin any root cause. It seems to be common across not only this board but other ASUS boards with the marvell 10g NIC. ASUS is silent on the issue.

[Teletha · Accepted solution]

i talked to asus rma support:

Windows 11 have had some issues after some recent Windows updates unfortunately, but one thing that can be worthwhile to check here is a certain setting called EEE (Energy Efficient Ethernet) which sometimes works as a "sleep function" in certain scenarios. 

Go to the device manager, go to network adapters then rightclick on your ethernet adapter and choose "properties". In the pop-up window go to the "advanced" tab. You should then turn the EEE to off as shown in the picture below (there might be a different worded ethernet adapter unit in this picture, but you choose your ethernet adapter for this):

[Devar]

I turned EEE off a while ago as I searched it being a potential fix. Unfortunately, it does not make any difference.

[loudbob]

I have the same issue with the  ASUS X670E Extreme Mobo and the 10G connector dropping connection. It's connected to an ASUS-AX89X router via a 10G switch. I have no issue with any other device (2 servers & 2 desktop) all using 10G ASUS NIC's.

I have tried to disable Energy-Efficient Ethernet (EEE) and Recv Segment Coalescing (IPv4) but the issue still persists.

[sbehring]

My 10 GB disappeared from system after 1 month of use - the hardware could not be detected in Windows & Linux. In BIOS I could switch it ON/OFF, but without success. Lates BIOS uploaded, tried downgrade to older BIOS too. Probably hardware fault and need to RMA.