Problems with smart array and cpqcissm.sys

Hi,

I have an Compaq ML350 with a 6400 smart array running 6 x 72GB drives. The server hangs regularly when under high stress. For example when running full backups etc. I have run the debugger on the .dmp file it produces, but I don't really know what it means.

Can someone help?

Thanks in advance.....



Symbol search path is: C:\websymbols

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


Loading Dump File [H:\My Documents\Mini011205-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\websymbols
Executable search path is:
Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 1.1289) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer
Kernel base = 0x80800000 PsLoadedModuleList = 0x808aba08
Debug session time: Tue Jan 11 23:55:06 2005
System Uptime: 0 days 3:11:30.570
Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................................
Loading unloaded module list
...
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {260, 8, 0, f78a3f77}

Unable to load image cpqcissm.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for cpqcissm.sys
Unable to load image \WINDOWS\system32\drivers\SCSIPORT.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for SCSIPORT.SYS
Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : cpqcissm.sys ( cpqcissm!DriverEntry <PERF> (cpqcissm+0xf77)+0 )

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

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

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: 00000260, memory referenced
Arg2: 00000008, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f78a3f77, address which referenced memory

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


READ_ADDRESS: 00000260

CURRENT_IRQL: 55

FAULTING_IP:
cpqcissm!DriverEntry <PERF> (cpqcissm+0xf77)+0
f78a3f77 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f78a3f77 to 8082d535

STACK_TEXT:
808a0490 f78a3f77 badb0d00 00000000 00000000 nt!CcScheduleReadAhead+0xec
808a0534 f73401d5 89b45004 808a0600 89ba6008 cpqcissm!DriverEntry <PERF> (cpqcissm+0xf77)
808a054c 808300c5 89ba6008 89ba4a40 00010008 SCSIPORT!ScsiPortFdoDispatch+0x2d1
808a0570 f7639d72 badb0d00 00001ff1 f6b18dbd nt!RtlpStatusTable+0x7e5
WARNING: Stack unwind information not available. Following frames may be wrong.
808a0600 80830632 00000000 0000000e 00000000 intelppm+0x2d72
808a3bc0 00000000 808a3bc8 808a3bc8 808a3bd0 nt!MmUnlockPagableImageSection+0x161


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
cpqcissm!DriverEntry <PERF> (cpqcissm+0xf77)+0
f78a3f77 ?? ???

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: cpqcissm!DriverEntry <PERF> (cpqcissm+0xf77)+0

MODULE_NAME: cpqcissm

IMAGE_NAME: cpqcissm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 401eac8c

BUCKET_ID: 0xD1_cpqcissm!DriverEntry__PERF__(cpqcissm+0xf77)+0

Followup: MachineOwner

 

The debugger is a harsh mistress. Use the tool in my signature to feed the debugger the 17 things it needs to function properly and post a new log.


You say 'Hangs regularly' but then post a dump from a bugcheck crash dump file. I am confused. When i see the word hang, i think, the machine is taking a nap, and unresponsive. When i see a bugcheck, i think 'shazbot, thats a blue screen of death'. Explain your scenario with more precision please.