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

I350-t2 Windows 10 bluescreen

NM2
Beginner
8,102 Views

Windows version: Windows 10 Pro

Version: 1703

OS Build: 15063.608

Intel Proset: 22.6

Network card: Intel I350-t2

Driver version: 12.15.184.0

Driver date: 2017-03-29

I have been trying for weeks to get Nic Teaming working on my Windows 10 machine. However, whenever I try setup a new teaming, Windows 10 would blue screen with error code Bad_pool_caller.

Any suggestion or help is greatly appreciated.

Thank you

Nelson

0 Kudos
31 Replies
idata
Employee
1,317 Views

HI Logic,

 

 

Thank you for the update and I am sorry to hear the issue still persist. Let me further check.

 

 

Regards,

 

Sharon

 

0 Kudos
idata
Employee
1,317 Views

Hi Logic,

 

 

Can you try disable the Jumbo frame setting? Do let me know the result. Thanks.

 

 

Regards,

 

Sharon

 

0 Kudos
idata
Employee
1,317 Views

Hi Logic,

 

 

Please feel free to update me. Thank you.

 

 

Regards,

 

Sharon

 

0 Kudos
idata
Employee
1,317 Views

Hi Logic,

 

 

Please try installing driver version 22.9 https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10 if you are still using Windows 10 (1709).

 

 

Thanks,

 

Sharon

 

0 Kudos
idata
Employee
1,317 Views

Hi Logic,

 

 

Please feel free to update me if you have installed version 22.9?

 

 

Thanks,

 

Sharon

 

0 Kudos
ssean3
Beginner
1,500 Views

I actually had/have this same problem on Windows 10E x64 1703 with the 1219V and 1211. It DOES bluescreen with BAD_POOL_CALLER, but then the PC reboots, but in my case the actual team is still created and is operational after the reboot.

It also happens once you create the team, but then change any settings on the teamed NICs.

0 Kudos
NM2
Beginner
1,500 Views

SeanVree,

unfortunately, for my situation, after the reboot the team is created. But one nic is turned off. So I can't set the team properly.

Nelson M

0 Kudos
ssean3
Beginner
1,317 Views

FYI:

I updated my windows 10 x64 box to FC 1709. I thought I'd lose all teaming functionality like the previous releases.

However, to my surprise, I was actually able to install the team with NO BSOD.

Not sure if this is relevant to your environment, but I've been fussing with this for over a year now, and after I installed FCU, it was the first time that I got straight thru the process.

0 Kudos
idata
Employee
1,317 Views

Hi SeanVree,

 

 

Thank you for sharing the update, this is indeed a good news.

 

 

Regards,

 

Sharon

 

0 Kudos
NM2
Beginner
1,317 Views

SeanVree,

What driver are you using? My windows 10 x64 is still running 1703. I will update tonight and give it a shot.

If teaming doesn't work, I will just using SMB3 instead with multiple Nic to accomplish the additional bandwidth.

Nelson M

0 Kudos
ssean3
Beginner
1,317 Views

@logic ,

both of them are on the latest.

1219-v: 12.15.25.6712

1211: 12.15.184.0

Here's the network info from the intel SSU application:

```

# SSU Scan Information

Scan Info:

Version:"2.5.0.12"

Date:"10/21/2017"

Time:"00:00:03.7491501"

# Scanned Hardware

Computer:

- "Networking"

Intel ® Network Connections Install Options:"ANS,DMIX,SNMP"

Intel ® Network Connections Version:"22.7.18.0"

Intel ® PROSet/Wireless Software Version:"19.50.1.0"

- "TEAM: team01"

Availability:"Running or Full Power"

Caption:"TEAM: team01"

CoInstallers:"NicCo36.dll,NicCoInstallerEntry"

Default IP Gateway:"192.168.1.1;fe80::e6f4:c6ff:fe1d:885b"

DHCP Enabled:"Yes"

DHCP Lease Expires:"01/18/2038 07:14 PM"

DHCP Lease Obtained:"12/31/1969 04:00 PM"

DHCP Server:"192.168.1.1"

Driver:"iansw60e.sys"

Driver Date:"05/10/2017 12:00 AM"

Driver Path:"C:\WINDOWS\system32\DRIVERS\iansw60e.sys"

Driver Provider:"Intel"

Driver Version:"9.9.0.55"

Index:"0018"

INF:"oem12.inf"

INF Section:"iANSMP.ndi.NTamd64.6.0"

Install Date:"Not Available"

Installed:"Yes"

IP Address:"192.168.1.20;fe80::39fb:7b5c:cafe:adf8;2601:602:9a00:196d:a888:46e0:a01b:82c2;2601:602:9a00:196d:1d7b:ac85:5d2a:8aaf;2601:602:9a00:196d:39fb:7b5c:cafe:adf8"

IP Subnet:"255.255.255.0;64;128;128;64"

Last Error Code:"Not Available"

Last Error Code Description:"Not Available"

Last Reset:"10/19/2017 04:12 AM"

Location:"Not Available"

MAC Address:"40:8D:5C:B7:2C:7B"

Manufacturer:"Intel"

Media Type:

Net Connection ID:"Ethernet 2"

NetCfgInstanceId:"{5322B462-F2AC-43B0-9D1C-26E560E5A15A}"

Number of VLANs:"0"

PNP Device ID:"ROOT\IANSMINIPORT\0000"

Port:"Not Available"

Power Management (Low Power):"Not Available"

Power Management (Wake On LAN):"Not Available"

Power Management (Wake on Magic Packet):"Not Available"

Power Management Capabilities:"Not Available"

Power Management Supported:"No"

Product Type:"Intel(R) Advanced Network Services Virtual Adapter"

Service Name:"iANSMiniport"

Status:"Enabled"

Team Members:"Intel(R) I211 Gigabit Network Connection;Intel(R) Ethernet Connection (2) I219-V"

Team Mode:"StaticLinkAggregation"

Team Name:"team01"

Temperature:

Type:"Ethernet 802.3"

- "Service Bindings"

Client for Microsoft Networks:

File and Printer Sharing for Microsoft Networks:

Internet Protocol Version 4 (TCP/IPv4):

Internet Protocol Version 6 (TCP/IPv6):

Link-Layer Topology Discovery Mapper I/O Driver:

Link-Layer Topology Discovery Responder:

Microsoft LLDP Protocol Driver:

Microsoft Network Monitor 3 Driver:

QoS Packet Scheduler:

WinpkFilter LightWeight Filter:

- "Settings"

BalanceInterval:Load Balance Refresh Rate:"10 (10)"

CheckTime:Check Time (in Seconds):"1000 (1000)"

ConnectionName:ConnectionName:"Ethernet 2 (Ethernet 2)"

UserSelectedAddress:Locally Administered Address:

- "TEAM: team01 - Intel(R) Ethernet Connection (2) I219-V"

Availability:"Running or Full Power"

- "Caption":"Intel(R) Ethernet Connection (2) I219-V"

Link:" http://www.intel.com/content/www/us/en/search.html?keyword=Ethernet+Connection+(2)+I219+V"

CoInstallers:"NicCo4.dll,NicCoInstallerEntry"

Default IP Gateway:"Not Available"

DHCP Enabled:"Yes"

DHCP Lease Expires:"Not Available"

DHCP Lease Obtained:"Not Available"

DHCP Server:"Not Available"

Driver:"e1d65x64.sys"

Driver Date:"07/12/2017 12:00 AM"

Driver Path:"C:\WINDOWS\system32\DRIVERS\e1d65x64.sys"

Driver Provider:"Intel"

Driver Version:"12.15.25.6712"

ETrackID:"0x00000000"

Index:"0015"

INF:"oem15.inf"

INF Section:"E15B8.10.0.1"

Install Date:"Not Available"

Installed:"Yes"

IP Address:"Not Available"

IP Subnet:"Not Available"

Last Error Code:"Not Available"

Last Error Code Description:"Not Available"

Last Reset:"10/19/2017 04:12 AM"

Location:"PCI bus 0, device 31, function 6"

MAC Address:"40:8D:5C:B7:2C:7B"

Manufacturer:"Intel"

Media Type:"Copper"

Net Connection ID:"i1219v"

NetCfgInstanceId:"{C7A1707C-4B15-43BA-8CC4-596C9B313A36}"

NVM Version:"0x00000000"

Part Number:"FFFFFF-0FF"</...

0 Kudos
Reply