Ethernet Products
Determine ramifications of Intel® Ethernet products and technologies
4810 Discussions

i210 blue screen on install and during operation

ASpec
Beginner
4,226 Views

Hello,

I'm running Windows Server 2016 on a Asus P10 WS mainboard. This MB has two i210 network interfaces on-board. Currently, I'm using only one of them, the second one is disabled in Windows device manager.

The driver installed has a date of 08.12.2016 and a version of 12.15.184.0 (as shown in device manager.)

For the interface in use I have enabled teaming in Windows to use different VLANs. For a while now, there were two virtual adapters "Microsoft Network Adapter Multiplexor Driver # X" in my system, each configured with a different VLAN ID. This has been working quite well for some time now.

Recently, I tried to add a third VLAN. During configuration, the machine crashed with a blue screen. After reboot, the third virtual interface was there regardless. Now, I'm experiencing (seemingly) random crashes (blue screens) every once in a while. They seem to be more frequent when the new, third virtual adapter is being used a lot, but I can't really put my finger on it.

However, when I run the executable of the latest Intel driver package PROWinx64.exe v22.7.1, there is a reproducible blue screen as soon as the new driver is being installed. There is an additional popup by the installer that says something like "installing driver for i210 Gigabyte connection...". That's when the machine crashes consistently.

The memdump analysis says the following (first example is a "random" crash, second one is the "driver install" crash:)

***

Probably caused by : e1r65x64.sys ( e1r65x64+150ad )

[...]

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 0000000000000028, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff8099451abdf, address which referenced memory

***

***

Probably caused by : NdisImPlatform.sys ( NdisImPlatform!implatReturnNetBufferLists+1d6 )

[...]

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 0000000000000010, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff806566040b3, address which referenced memory

***

(Complete analysis logfile is available if anyone is interested.)

How can I fix this?

Regards

0 Kudos
16 Replies
idata
Employee
1,241 Views

Hi VGER,

Thank you for posting in Wired Communities. I will further check on this. For the meantime,can you provide more information below:

1) Running memory test to check on the memory

2) Try use drivers from Asus* the board vendor to see if this will make any changes

3) What is the teaming mode you enabled?

4) What is the other network adapter model you team with the I210? You mentioned the second I210 is disabled.

Regards,

 

Sharon

 

0 Kudos
ASpec
Beginner
1,241 Views

Memory: The System is running ECC Memory. If there was an error, there should have been a different error message.

Asus Driver: I can do that, but apparently this is just an (older) Intel driver (v21.1). Of course, can't hurt to try.

Mode of installation: I'm not using "teaming" as such. I'm using the teaming feature of the OS (Windows Server 2016) to create virtual interfaces that can use seperate VLAN IDs. There is only one physical Adapter in use (at the moment).

While browsing the Asus site I came across a BIOS update as well. This may just be that ME-engine-issue, but maybe it will do something for the issue at Hand, too. I'll report back.

Regards

0 Kudos
idata
Employee
1,241 Views

Hi VGER,

Thank you for the information. Please do update me about the BIOS and driver from Asus (in case you want to try). I will furher check.

Regards,

 

Sharon
0 Kudos
idata
Employee
1,241 Views

HI VGER,

 

 

I run a test in our lab using another NIC model (I350-T4) driver version 12.15.22.6. These are the steps performed:

 

1) Create a Team interface first using single port (as I understand you only use one I210 onboard NIC)

 

2) After creating the team, add the interface to create VLAN 1

 

3) Add another interface to create VLAN 2

 

4) Another interface to create VLAN 3

 

After creating the third VLAN, no issue occur. Can you share more information how you did the

 

team and adding of VLAN?

 

 

Are you creating a Team interface using single port on the I210?

 

 

Please feel free to update me.

 

 

Thanks,

 

Sharon

 

0 Kudos
ASpec
Beginner
1,241 Views

Hi,

your description:

Yes, this is exactly what I did. Except that I already had the two virtual interfaces (VLAN ID 1 and 2) and only added the third. After the last step, when the change was actually applied, the system crashed with a blue screen. After reboot, the third virtal interface was there nevertheless.

my earlier, reg. manufacturer BIOS:

The updated system BIOS did not improve things. BSOD still occur.

my earlier, reg. trace:

Looking at the bugcheck stack trace, I see the following:

STACK_TEXT:

fffff801`850d6108 fffff801`83373929 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff801`850d6110 fffff801`83371f07 : ffffc183`b6b4a000 ffffc183`c28e5102 00000000`00000000 00000000`0089d583 : nt!KiBugCheckDispatch+0x69

fffff801`850d6250 fffff801`83a32486 : ffffc183`ffffffff fffff80e`9af6d26a 00000000`00000000 ffffc183`b637e740 : nt!KiPageFault+0x247

fffff801`850d63e0 fffff80e`9689ddf8 : ffffc183`cdd17f50 ffffc183`c29bdf00 00000000`000001fe 00000000`000001fe : hal!HalPutScatterGatherList+0x26

fffff801`850d6440 fffff80e`9af43f81 : ffffc183`c28e51a0 00000000`00000000 ffffc183`c29b6000 fffff801`850d66d0 : NDIS!NdisMFreeNetBufferSGList+0x38

fffff801`850d6480 fffff80e`9af4e31a : ffffc183`b0c2ed50 ffffc183`c29b6000 ffffc183`c29b6001 ffffc183`c29b6000 : e1r65x64+0x13f81

fffff801`850d6550 fffff80e`9af4e5eb : ffffc183`b0c2ad50 00000001`00000000 00000001`00000000 ffffc183`c2a24000 : e1r65x64+0x1e31a

fffff801`850d65c0 fffff80e`9af4dd7c : 00000000`00000015 ffffc183`00000000 00000000`00000000 00000000`00000000 : e1r65x64+0x1e5eb

fffff801`850d6650 fffff80e`96894e69 : ffffc183`c40b0180 fffff80e`9750c3b8 ffffc183`c40b0030 00000000`00000000 : e1r65x64+0x1dd7c

fffff801`850d6690 fffff801`8324fc05 : ffffc183`c2a24000 0001e6dd`a8346cc0 00000000`00000000 fffff801`83554180 : NDIS!ndisInterruptDpc+0x1c9

fffff801`850d6810 fffff801`8324f18f : ffffc183`c3d2e900 ffffc183`c3d2e900 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x335

fffff801`850d6960 fffff801`8336b81a : 00000000`00000000 fffff801`83554180 fffff801`835ce940 ffffc183`c3d2e800 : nt!KiRetireDpcList+0x8df

fffff801`850d6be0 00000000`00000000 : fffff801`850d7000 fffff801`850d0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

Can you interpret anything further from that? The driver does appear to be involved for certain.

my earlier, reg. manufacturer drivers:

I'm hesitant to use the (older) drivers offered by Asus. They seem to be derived from Intel v21.1. Will drivers "that old" even offer the virtual interfaces that I need? Could you please check if this feature is supported by this version already?

other observations:

On the machine there is Virtualbox installed. One of the VMs is running in "bridged" network mode, accessing one of the virtual interfaces (# 2, not the newly created # 3). Unfortunatly, I can't very well just uninstall this for a while to check things since that VM is accessed in daily use. However, since Virtualbox's drivers are not mentioned in the bugcheck log in any way, does that make their involvement in the problem seem likly?

Regards

0 Kudos
ASpec
Beginner
1,241 Views

After some more work, I now believe that I'm looking at two sperate issues here:

1) Crash (BSOD) on driver installation:

When the setup PROWINx64.EXE starts to install the drivers, the system drops to a blue screen. This is completly consistent, reproducible, and cannot be avoided in any way (that I can think of.) Running or having installed Virtualbox makes no difference at all.

2) Crashes during operation:

As mentioned, on the machine there was a Virtualbox VM with its network configuration "bridged" to one of the i210's virtual interfaces. While this setup was working in principle, the machine crashed randomly multiple times during the day. As a test, I have now moved this VM to a different machine. Since then I have not experienced any more BSODs. I have then reintroduced the VM to the machine, but now set it to "host-only" networking and am now activly routing between the network segments. So far, still no new crashes.

Conclusions:

The Intel driver package v22.7.1 just won't install without causing a blue screen crash. Were you able to look into the bugcheck logs to trace this?

The random crashes may have been caused by Virtualbox "bridged" networking. Is there even a chance to get this fixed, or should I just try to make the workaround into a permanent solution?

Regards

0 Kudos
idata
Employee
1,241 Views

Hi VGER,

 

 

Thank you for sharing the information, I will have to check on this.

 

 

Regards,

 

Sharon

 

0 Kudos
idata
Employee
1,241 Views

Hi VGER,

 

 

Please help providing the SSU log, go to https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-, download and run the tool, attach the log generated.

 

 

Thanks,

 

Sharon

 

0 Kudos
idata
Employee
1,241 Views

HI VGER,

 

 

Please feel free to provide the SSU log.

 

 

Thanks,

 

Sharon

 

0 Kudos
ASpec
Beginner
1,241 Views

Hi,

could you give me an email address to send the report file to?

Regards

0 Kudos
idata
Employee
1,241 Views

Hi VGER,

 

 

You can attach the SSU log here. If you prefer email, I will PM you.

 

 

Thanks,

 

Sharon

 

0 Kudos
idata
Employee
1,241 Views

Hi VGER,

 

 

Please feel free to update me.

 

 

Thanks,

 

Sharon

 

0 Kudos
idata
Employee
1,241 Views

Hi VGER,

 

 

Please try installing driver version 22.9 https://downloadcenter.intel.com/download/26092/Intel-Network-Adapter-Driver-for-Windows-Server-2016-. Do let me know the result. Thank you.

 

 

Regards,

 

Sharon

 

0 Kudos
idata
Employee
1,241 Views

Hi VGER,

 

 

Please feel free to update if you have tried driver version 22.9.

 

 

Thanks,

 

Sharon

 

0 Kudos
idata
Employee
1,241 Views

Hi VGER,

 

 

You may tried our recently released driver 22.10 at

 

https://downloadcenter.intel.com/download/26092/Ethernet-Intel-Network-Adapter-Driver-for-Windows-Server-2016-?product=64399 https://downloadcenter.intel.com/download/26092/Ethernet-Intel-Network-Adapter-Driver-for-Windows-Server-2016-?product=64399

 

Another thing you can try is to install without using the exe. Just unpacking the drivers and then installing the inf from Device Manager.

 

 

Since this is an onboard NIC, it is recommended you contact Asus* for further support. Thank you.

 

 

Regards,

 

Sharon

 

0 Kudos
idata
Employee
1,241 Views

Hi VGER,

 

 

Please feel free to update if further assistance needed.

 

 

Thanks,

 

Sharon

 

0 Kudos
Reply