Minidump Analysis PCIIDEX.SYS Crash

Hello,

I recently had a server crash on me.  I ran the WinDbg program on the Minidump file, and it said that PCIIDEX.SYS caused the crash.

Here is the actual Minidump file:  http://www.box.net/shared/uhc5uttryb

The server is running Windows Server 2003, and the computer is about a year old.  I have no idea what PCIIDEX.SYS does....Please help...thanks!


Here are the results that I got:

Microsoft (R) Windows Debugger  Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\rgutwein\My Documents\Randy\MMSDump\Mini050307-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: Server, suite: TerminalServer
Built by: 3790.srv03_sp1_gdr.070304-2232
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af988
Debug session time: Thu May  3 12:30:05.766 2007 (GMT-4)
System Uptime: 12 days 21:26:25.578
Loading Kernel Symbols
.......................................................................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 88574348, 88574b70, b05a236}

Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmFlush+29 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 88574348, The pool entry we were looking for within the page.
Arg3: 88574b70, The next pool entry.
Arg4: 0b05a236, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  88574348

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

PROCESS_NAME:  Idle

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 8089c8f4 to 8087b71e

STACK_TEXT:  
808a3498 8089c8f4 00000019 00000020 88574348 nt!KeBugCheckEx+0x1b
808a3500 80a7a330 88574350 00000000 80a76230 nt!ExFreePoolWithTag+0x477
808a3518 f74a8911 89f21bd8 88574350 00000001 hal!HalpAddAdapterToList+0x14
808a3538 f738ba7f 89f24d48 ffdffa40 89f6409c PCIIDEX!BmFlush+0x29
808a35a8 8083eaff 89f6409c 89f64028 00000000 atapi!IdePortCompletionDpc+0x75
808a3600 8083ac1f 00000000 0000000e 00000000 nt!KiRetireDpcList+0xca
808a3604 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x37


STACK_COMMAND:  kb

FOLLOWUP_IP:
PCIIDEX!BmFlush+29
f74a8911 891f            mov     dword ptr [edi],ebx

SYMBOL_STACK_INDEX:  3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PCIIDEX

IMAGE_NAME:  PCIIDEX.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  42435b40

SYMBOL_NAME:  PCIIDEX!BmFlush+29

FAILURE_BUCKET_ID:  0x19_20_PCIIDEX!BmFlush+29

BUCKET_ID:  0x19_20_PCIIDEX!BmFlush+29

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

Start Free Trial