asked on

Windows Server 2003 - Blue Screens/Dump Log Analysis

I have a set of matching Windows 2003 Servers that have recently gone into production (very recently) and have both decided to start blue screening. If anyone can take a look at this analysis of the dump log and give me any suggestions it would be greatly appreciated.

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000121a, (reserved)
Arg3: 00e40015, Memory contents of the pool block
Arg4: 858d78e8, Address of the block of pool being deallocated

Debugging Details:
------------------

POOL_ADDRESS: 858d78e8

FREED_POOL_TAG: NTID

BUGCHECK_STR: 0xc2_7_NTID

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

LAST_CONTROL_TRANSFER: from 8089c8ff to 8087c480

STACK_TEXT:
808a3140 8089c8ff 000000c2 00000007 0000121a nt!ObpUnsecureGlobalNamesBuffer+0x20
808a31a8 f716bee6 858d78e8 00000000 808a31cc nt!MiMapViewOfDataSection+0x195
808a31b8 ba47c9a5 858d78e8 00000714 00000000 NDIS!ndisReadBindPaths+0x140
WARNING: Stack unwind information not available. Following frames may be wrong.
808a31cc ba47d7d9 858d78e8 866937d8 808a31ec cpqteam+0x149a5
808a31dc ba47d7c3 865a0b50 866937d8 808a3260 cpqteam+0x157d9
808a31ec ba47dacb 866937d8 87f5d008 89167f7c cpqteam+0x157c3
808a3260 f7174c8a 01ee44f8 00000008 87f4a008 cpqteam+0x15acb
808a3274 b9f694a7 87f5d008 866937d8 88d10628 NDIS!ndisMInitializeAdapter+0x21e
808a32bc b9f6cd1f 00000000 00000000 867b38d4 tcpip!RouteTableLock+0x27
808a32f8 b9f71ffe 00000000 b9fa4f68 89167ef0 tcpip!g_NTECtxtMapBuffer+0x17bf
808a332c b9f5d7bf 89167ef0 808a3460 b9f7c200 tcpip!PortBitmapBufferTcp+0x1cde
808a346c b9f3c61a b9f3c75c 808a350c 00000000 tcpip!SendICMPMsg+0x10a
808a348c 00000000 000000e1 808a34d0 87aa3780 tcpip!IPSecRcvFWPacketDummy+0x1

STACK_COMMAND: kb

FOLLOWUP_IP:
cpqteam+149a5
ba47c9a5 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: cpqteam+149a5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: cpqteam

IMAGE_NAME: cpqteam.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46d7035b

FAILURE_BUCKET_ID: 0xc2_7_NTID_VRFK_cpqteam+149a5

BUCKET_ID: 0xc2_7_NTID_VRFK_cpqteam+149a5

Followup: MachineOwner
---------

TG Tran

Are these servers HP Proliant with Win2003 64bit?
I had BSOD on DL580 and this was the fix:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01102958&jumpid=reg_R1002_USEN

PlaceboC6

tgtran is probably right. It is crashing in the Compaq Teaming driver for the network card.

PJohnso

ASKER

Thanks for the responses guys.

It's a HP Proliant 385 running 2003 Enterprise (not 64bit).
Our SAS/SATA controller driver is already version 6.8.0.32 and the support pack is 7.91

ASKER CERTIFIED SOLUTION

TG Tran

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

PlaceboC6

I would considering uninstalling and reinstalling the latest nic software. The dump file is pointing to the teaming driver.

PJohnso

ASKER

We've gone ahead and unteamed the nic's (which didn't work via software so we had to brute force/safe mode remove the team) and it seems to have solved the problem for now. We'll have to work with HP on finding the exact piece of the problem/solution.

Thanks