E610-XT2 – BSOD / NIC hang (firmware vs driver mismatch?)

[CraigOZ]

I’ve got a Beelink AI 395 with an Intel Ethernet Network Adapter E610-XT2 (PCI\VEN_8086&DEV_57B0).

• NIC firmware: NVM 1.10, Option ROM 1.3786.0

• Driver: ixw.sys 1.2.43.0 from Intel Ethernet Pack 30.0.1

• OS: Windows 11 (build 26100)

Problem:
After a couple of minutes under load the system hits a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E) in ixw.sys. When it crashes the NIC LED stays solid green, Windows no longer sees the adapter, and only a full power cycle brings it back.

I tried disabling offloads (RSS, LSO, checksum, interrupt moderation) and rolling back drivers, but it still happens. Dumps consistently show null pointer deref inside ixw.sys.

Issue: I have run the "nvmupdate64e.exe -i" did not return any firmware details, which make me think the firmware maybe OEM locked. I confirmed the firmware version in the bios.

Ask:
Does anyone have a driver ↔ firmware (NVM) compatibility table for the E610 series? I’m on NVM 1.10 and it looks like newer packs (30.4?) ship with NVM 1.30. Wondering if my firmware is simply too old for the current drivers.

[Azhari_Intel]

Hello CraigOZ,

Thank you for posting in Intel Community!

We appreciate you reaching out to us regarding the reported issue.

Kindly to confirm if it is an onboard controller or was this purchase separately?

Meanwhile, we suggest looking into information available as per URL below.

https://www.intel.com/content/www/us/en/content-details/857714/intel-ethernet-controller-e610-feature-support-matrix.html

Looking forward to your update on this.

Best Regards,

Azhari_Intel

[CraigOZ]

Hiya,

The device is a Beelink GTR9 Pro AMD Ryzen™ AI Max+ 395, which has listed the Intel Ethernet Controller FUE610XAT2 SLPMM TW. The device is all on one board internally.

Beelink provide a bios update for the main board, but it did not update the NIC firmware. Here is what I see in the bios for the card. I can reproduce the issue by simple connect the cable, have a you tube video running and start a game of minecraft. This places load on the network, cpu and gpu for me. Within 5 minutes i have a crash/bsod.

What I have been told so far by Beelink is that its a driver fault and intel need to release the next driver. However I assume that the issue will remain as the firmware on the NIC is still very old.

[Sachinks]

Hello CraigOZ,

Thank you for your reply and thank you for the details.

Would you be able to provide us an image of the ethernet card that you are using with the badge details visible? This is to check if the card is an Intel retail one or if it is an OEM card. Based on this, we can recommend the NVM and driver updates.

Regards,

Sachin KS

Intel Customer Support Technician

[CraigOZ]

Hiya,

The nic is onboard the mainboard, its a beelink mini pc so everything is on one board. If you let me know what you want from a screenshot or export of a command I can get those. I can not open the PC just yet only had it for less then 48 hours.

Here is what i have in hwinfo

This is what the intel assistance report shows.

Cheers

Craig

[Sachinks]

Hello CraigOZ,

Thank you for your reply and thank you for the images.

As you have mentioned that this network card came along with the system and as you are not able to provide the pictures of the card to check the markings, we request you to contact the OEM (Beelink) regarding this.

From our end, the latest NVM firmware available for the 610 ethernet series is NVM version 1.3.

You can access the latest NVM file in the below link :

https://www.intel.com/content/www/us/en/download/845347/non-volatile-memory-nvm-update-package-for-intel-ethernet-e610-series.html

As you are on NVM 1.10 version, you can try updating the NVM to 1.3 however, If you are unable to update the NVM as you have stated that the firmware might be OEM locked, we request you to directly check once with the OEM regarding the NVM update.

Regards,

Sachin KS

Intel Customer Support Technician

[CraigOZ · Accepted solution]

Hiya,

I worked with Bee-Link and got a firmware update tot he NIC to 1.3. the BSOD have now stopped the and system is stable. I did write up the process here in case anyone needs it later. 

These were the fixes:

• System BIOS: v1.08 (Firmware supplied by Bee-Link Support)
• NIC Firmware: Intel E610 NVM 1.30 (Supplied by Bee-Link Support, appears the same as Intel version)
• Driver Pack: Intel Ethernet 30.4 (Intel and Bee-Link supplied drivers both worked)

https://craigwilson.blog/post/2025/2025-09-25-beelink395bsod/

Cheers

Craig

[Simon-Intel]

Hi CraigOZ,

Thank you for the confirmation.

We will proceed to archive the case associated with this query.

Your confirmation will help us manage the case effectively.

Regards,

Simon

Intel Customer Support Technician

[CraigOZ]

Yes we can its all resolved now.

Thanks for the support.

Cheers

Craig

[LukeD_NC]

Dear Intel,

I have the same machine and I followed the same exact process and while it improves stability. It doesn't solve the problem.

After updating to the latest firmware and drivers I still get instability and crashes. Even in Batocera Linux I get the following in dmesg

[Christosds]

The problem with the Intel Ethernet Controller E610-XT2 on the Beelink GTR9 Pro (Ryzen AI Max+ 395) has not been resolved.

Even after updating to the latest firmware from Beelink (System BIOS v1.08),
installing the NIC firmware NVM Version 1.30,
and using the latest Intel Ethernet Driver Pack 30.4,
the issue still persists.

Whenever the system is under moderate to heavy load and the temperature rises, both network adapters suddenly stop working. Windows immediately loses both NICs, and they only come back after a full power cycle (unplugging the machine from the power outlet).

This behavior clearly points to a firmware or thermal stability issue affecting the E610-XT2 controller on Beelink’s implementation.

There are hundreds of Beelink customers reporting the exact same issue, yet it seems that neither Beelink nor Intel is taking ownership or providing a proper fix.

Please escalate this internally to the Intel Ethernet engineering team this is not an isolated case, and it needs an official firmware and driver resolution.

[LukeD_NC]

+1 to Christosds post. I am still having issues despite latest firmware (system + Nic card) and driver updates.