F5F Stay Refreshed Hardware Desktop Unusual 10GbE network card issue detected, system utilization at 12,600 k.

Unusual 10GbE network card issue detected, system utilization at 12,600 k.

Unusual 10GbE network card issue detected, system utilization at 12,600 k.

O
Ob22007
Member
121
10-20-2021, 06:11 PM
#1
I installed two Mellanox cards for higher speeds between Unraid and Windows 11. The first card worked well on the server, but the second caused blue screens on my Windows 11 PC with a 12600k chipset. After cleaning up the Windows 10 installation, the issue disappeared. I tried disabling the E cores on the 12600k, which fixed the problem. Now I’m restoring my Windows 11 build. Disabling the E cores helped, but turning them back on caused instability. The motherboard is a Z690 M. AORUS ELITE with DDR4 (rev 1.0) and four E-cores. Blue screen errors appeared when handling system threads and MLX4eth63.sys. File transfer tests showed issues with irql less or equal.
O
Ob22007
10-20-2021, 06:11 PM #1

I installed two Mellanox cards for higher speeds between Unraid and Windows 11. The first card worked well on the server, but the second caused blue screens on my Windows 11 PC with a 12600k chipset. After cleaning up the Windows 10 installation, the issue disappeared. I tried disabling the E cores on the 12600k, which fixed the problem. Now I’m restoring my Windows 11 build. Disabling the E cores helped, but turning them back on caused instability. The motherboard is a Z690 M. AORUS ELITE with DDR4 (rev 1.0) and four E-cores. Blue screen errors appeared when handling system threads and MLX4eth63.sys. File transfer tests showed issues with irql less or equal.

S
SnazzyMeow
Junior Member
45
10-21-2021, 02:47 PM
#2
Also having 2 processors helps resolve the blue screen issue. Now I'm even more puzzled.
S
SnazzyMeow
10-21-2021, 02:47 PM #2

Also having 2 processors helps resolve the blue screen issue. Now I'm even more puzzled.

D
daviesoj
Member
70
10-21-2021, 03:53 PM
#3
ConnectX-2 is outdated. The V3 version is already becoming outdated, but V2 has significant problems internally. I've noticed errors and complaints about the V2 line for years. UEFI support on newer boards is at best uncertain, and it seems unlikely that any OS newer than Win8.1 would properly boot or utilize the V2 series. You might attempt a firmware upgrade, but I have no certainty if such firmware exists for V2 cards anymore.
D
daviesoj
10-21-2021, 03:53 PM #3

ConnectX-2 is outdated. The V3 version is already becoming outdated, but V2 has significant problems internally. I've noticed errors and complaints about the V2 line for years. UEFI support on newer boards is at best uncertain, and it seems unlikely that any OS newer than Win8.1 would properly boot or utilize the V2 series. You might attempt a firmware upgrade, but I have no certainty if such firmware exists for V2 cards anymore.

J
jaap220
Senior Member
369
10-23-2021, 09:31 AM
#4
It seems like you're dealing with some unusual results. Disabling two CPU cores seems to resolve the issue, which is odd. You mentioned finding firmware for the V2 card, but updating it didn't help. Considering a V3 card might be worth exploring for your 12600K build.
J
jaap220
10-23-2021, 09:31 AM #4

It seems like you're dealing with some unusual results. Disabling two CPU cores seems to resolve the issue, which is odd. You mentioned finding firmware for the V2 card, but updating it didn't help. Considering a V3 card might be worth exploring for your 12600K build.

C
ClumsySky
Senior Member
526
10-23-2021, 06:51 PM
#5
I have this same issue with my connect-x 3 card after upgrading from my 3rd gen to a 12600k. I've tried all different versions of drivers I can find. Tried different combinations of disabling the P and E cores. Ensured my bios is up to date. Made sure windows was up to date. Looked all over the bios for a setting I might be missing but didn't find anything. Even with no drivers installed, if the card is plugged in it will boot and about 10 seconds later it blue screens. Sorry for the poor image but I get this error. This is on a fresh install of windows since I installed fresh with the new build, so I have not tried doing a reinstall. I confirmed the card works on another machine that is running truenas. Wondering if it's just not compatible with this new hardware or maybe it's a windows issue. Could try booting Ubuntu to see if it works there with this hardware. Any other ideas?
C
ClumsySky
10-23-2021, 06:51 PM #5

I have this same issue with my connect-x 3 card after upgrading from my 3rd gen to a 12600k. I've tried all different versions of drivers I can find. Tried different combinations of disabling the P and E cores. Ensured my bios is up to date. Made sure windows was up to date. Looked all over the bios for a setting I might be missing but didn't find anything. Even with no drivers installed, if the card is plugged in it will boot and about 10 seconds later it blue screens. Sorry for the poor image but I get this error. This is on a fresh install of windows since I installed fresh with the new build, so I have not tried doing a reinstall. I confirmed the card works on another machine that is running truenas. Wondering if it's just not compatible with this new hardware or maybe it's a windows issue. Could try booting Ubuntu to see if it works there with this hardware. Any other ideas?

X
Xikam20
Member
65
10-31-2021, 04:13 PM
#6
Disabling four cores brought stability once I discovered two would experience blue screens during file transfers. Any updates or experiences would be appreciated. Curious about the motherboard—I'm using a Z690 M.2 with DDR4. Are you running DDR5? What differences make my older chipset function while yours doesn't?
X
Xikam20
10-31-2021, 04:13 PM #6

Disabling four cores brought stability once I discovered two would experience blue screens during file transfers. Any updates or experiences would be appreciated. Curious about the motherboard—I'm using a Z690 M.2 with DDR4. Are you running DDR5? What differences make my older chipset function while yours doesn't?