HP NCU Team Rename Causes Bluescreen

[PaulY_4]

Hi, I have an issue with renaming team names using the HP NCU (9.90.1.0). Whenever I rename the team I get a BSOD. The O/S is Windows 2003 and the NIC's in the team are NC371i's (5.2.17.0). I have tried both renaming the team via RDP and ILO but both bluescreen.

Any ideas would be gratefully received.

[LuckyP_1]

There were few issues with old version of NCU. NCU version 10.20 or 10.30 does not have blue screen/ Hang issue.

If possible, please use new version of NCU.

[PaulY_4]

Thanks LuckyP for your reply but I'm not sure that upgrading the NCU will be possible at this momemnt in time as we have just upgraded to version 9.90.1.0 across our server estate (8000+ servers). I will put your suggestion to our engineering team and see what they say. Any other idea's will be welcomed.

[LuckyP_1]

Paul,

Were you able to rename the Team name earlier without issues?

or is this something you are doing first time.

Ideally it should not cause a BSOD, however the BSOD is happening. This means Teaming driver ia having some issue with underlying OS and NIC driver/ SP.

please attach the screen shots of BSOD. Also if possible, please enable server to generate mini dumps. This will give us more insight about cause of issue.

[PaulY_4]

This is the first time we have had a need to do this.

The server is a PROLIANT DL585 G2 running
WINDOWS 2003 ENTERPRISE EDITION WITH SP2

Here is part of the memory.dmp file.

********************************************
DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 8088a7c0 to 8088e65b

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b936b2c0 8088a7c0 badb0d00 00000000 8082ee87 nt!Kei386EoiHelper+0x28f3
b936b358 b487a0e2 97f71000 b936b370 9767e640 nt!KefAcquireSpinLockAtDpcLevel
b936b37c f7a30705 97f74010 9767e640 9767e640 bxnd52x+0x30e2
b936b3a4 b484463b b936b3c4 00000001 97fec130 NDIS!NdisReturnPackets+0xb7
b936b3b8 f7a30705 968c6008 9767e640 93b62ef0 cpqteam+0x663b
b936b3e0 b42c2105 95f84ef8 00000001 93b62ef0 NDIS!NdisReturnPackets+0xb7
b936b3f8 b42c799b 95f84eec 922b8dd8 b42c799b afd+0x10105
b936b42c b432aa3b 93b62ef0 c000013c 00000000 afd+0x1599b
b936b464 b4353e77 93b62ef0 00000000 c0000241 tcpip!ARPRcv+0x108e
b936b498 b4359309 b4353daa b936b4b8 00000000 tcpip!SendICMPErr+0x9107
b936b4b0 f7609a7f 2d928c0a 980350d0 9844ec48 tcpip!SendICMPErr+0xe599
b936b4dc f7609f97 f760c188 980350b0 00000000 TDI!TdiPnPPowerComplete+0x92b
b936b500 f760a3b0 00000000 00eb3c58 00000000 TDI!TdiPnPPowerComplete+0xe43
b936b53c f760a62b 980350b0 0000000c b936b58c TDI!TdiPnPPowerComplete+0x125c
b936b54c b4335520 980350b0 96588288 97ae55b8 TDI!TdiDeregisterNetAddress+0xf
b936b58c b43356af 2d928c0a 00ffffff 984ae5a8 tcpip!tcpxsum+0x475f
b936b5c4 b434a334 97ae55b8 b4346727 00000000 tcpip!tcpxsum+0x48ee
b936b5fc b434a751 97ae0002 b936b653 00000000 tcpip!UnSetIPSecSendPtr+0x1c0
b936b648 b4343bba 00ae55b8 00000001 96583860 tcpip!IPDelInterface+0xe5
b936b664 f7a29e83 b936b730 965835e0 b936b684 tcpip!tcpxsum+0x12df9
b936b738 f7a2b441 96583860 b936b75c 97fec130 NDIS!NdisCompleteUnbindAdapter+0x2b8
b936b78c f7a2c7bc 97fdf628 97fec130 c0000001 NDIS!NdisUnmapFile+0x37f
b936b8b8 f7a2cbbd 968c6325 968c6008 00000000 NDIS!NdisMPciAssignResources+0x288
b936b8cc b4840598 97fec130 968c6008 975ec000 NDIS!NdisIMDeInitializeDeviceInstance+0x44
b936b8e8 b4848155 968c6008 975ec000 983d8000 cpqteam+0x2598
b936b904 b48464ac 983d8000 968ad118 97fdf510 cpqteam+0xa155
b936b920 f7a29e83 b936b9ec 968ae498 b936b940 cpqteam+0x84ac
b936b9f4 f7a2b441 968ad118 b936ba18 97fd7ab0 NDIS!NdisCompleteUnbindAdapter+0x2b8
b936ba48 f7a2c7bc 94194008 00000000 97fd7ab0 NDIS!NdisUnmapFile+0x37f
b936bb74 f7a28bd9 941940e4 97ffd410 94194008 NDIS!NdisMPciAssignResources+0x288
b936bba4 8081e0f5 97fd79b0 94194008 b936bc34 NDIS!NdisRegisterTdiCallBack+0x235b
b936bbb8 8090fafe 98354030 98354030 98354dc8 nt!IofCallDriver+0x45
b936bbe4 8090fd7b 97fd79b0 b936bc10 00000000 nt!IoReportResourceUsage+0xbf6c
b936bc38 80823b6a 98354030 00000002 00000000 nt!IoReportResourceUsage+0xc1e9
b936bc60 8091196c e00a7e78 00000016 da76c918 nt!IoTranslateBusAddress+0xde6
b936bc78 809119d3 98354dc8 00000002 da76c918 nt!IoReportResourceUsage+0xddda
b936bcac 80913931 98354030 0276c918 00000002 nt!IoReportResourceUsage+0xde41
b936bd40 80913c02 b936bd7c 984aec74 e5cf4f28 nt!IoReportResourceUsage+0xfd9f
b936bd5c 80913e30 b936bd7c 984858d0 808b065c nt!IoReportResourceUsage+0x10070
b936bd80 80882107 9229a260 00000000 984858d0 nt!IoReportResourceUsage+0x1029e
b936bdac 8094c0ac 9229a260 00000000 00000000 nt!ExQueueWorkItem+0x1e3
b936bddc 8088fd5e 8088201c 00000001 00000000 nt!PsRemoveCreateThreadNotifyRoutine+0x21e
00000000 00000000 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x57e


STACK_COMMAND: kb

FOLLOWUP_IP:
bxnd52x+30e2
b487a0e2 5f pop edi

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: bxnd52x+30e2

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: bxnd52x.sys
********************************************

[LuckyP_1]

I would suggest you to disable RSS and TCP Chimney by making below changes in registry:


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
EnableTCPA REG_DWORD 0x0
EnableRSS REG_DWORD 0x0
EnableTCPChimney REG_DWORD 0x0

Note: Please have registry backup before doing these changes.

Please update me the status.

Thanks,
Lucky

[PaulY_4]

Thanks for your continued support.

I have checked the regkeys and they are already set as per your recommendations

[LuckyP_1]

Please check if below hotfix is installed on your machine:
http://support.microsoft.com/kb/948496

Note: As a work-around this hotfix also suggest to disable TCP Chimney and RSS, Those are already disabled on your server.

This Hotfix resolve below issue with NICs:

1. The TCP/IP Offload-enabled network adapter may consume lots of nonpaged pool memory. This may cause other problems in the operating system.
2. In some cases, the TCP/IP Offload-enabled network adapter may request large blocks of contiguous memory. This makes the computer stop responding when it tries to free the memory.

if this patch is also installed, then i would suggest you to send the dumps to Microsoft for detailed analysis.

[LuckyP_1]

Note: After applying the patch, Enable the TCP/IP Offload from registry and then check for the issue.