dump file help classpnp.sys

Hi there

I have had a server unexpectedly reboot over the weekend,

the dump file is below, can anyone help with what the issue maybe?

is there a hotfix for this? or is it hardware related?

thank you

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


Loading Dump File [c:\dump\memory.dmp]
Kernel Complete Dump File: Full address space is available

************************************************************
WARNING: Dump file has been truncated. Data may be missing.
************************************************************
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
;C:\WINNT\symbols;C:\WINNT\symbols\dll
Executable search path is: c:\winnt\i386
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatib
le
Product: Server, suite: TerminalServer SingleUserTS
Kernel base = 0x80400000 PsLoadedModuleList = 0x80485b40
Debug session time: Mon Mar 17 01:13:01.572 2008 (GMT+0)
System Uptime: 11 days 18:26:23.296
Loading Kernel Symbols
................................................................................
..................
Loading User Symbols

Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {73746e65, 2, 0, bff73932}

*** ERROR: Module load completed but symbols could not be loaded for naiavf5x.sy
s




Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClasspSendTestUnitIrp+99 )

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: 73746e65, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: bff73932, address which referenced memory

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






READ_ADDRESS: 73746e65

CURRENT_IRQL: 2

FAULTING_IP:
SCSIPORT!SpAllocateSrbExtension+156
bff73932 8b03 mov eax,dword ptr [ebx]

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: f5c774cc -- (.trap 0xfffffffff5c774cc)
ErrCode = 00000000
eax=88ff60e8 ebx=73746e65 ecx=00000000 edx=8902b030 esi=88585ea8 edi=8902b0e8
eip=bff73932 esp=f5c77540 ebp=f5c77550 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
SCSIPORT!SpAllocateSrbExtension+0x156:
bff73932 8b03 mov eax,dword ptr [ebx] ds:0023:73746e65=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from bff73932 to 8046b19c

STACK_TEXT:
f5c774cc bff73932 8902c802 f5c7750c bff72e4f nt!KiTrap0E+0x210
f5c77550 bff719d4 8902b0e8 88ff60e8 8902b1e4 SCSIPORT!SpAllocateSrbExtension+0x1
56
f5c77580 80420781 8902b030 885ace08 885ace08 SCSIPORT!ScsiPortStartIo+0x3f6
f5c775a4 bff714ec 8902b030 885ace08 00000000 nt!IoStartPacket+0x6f
f5c775d8 bff721d0 8902b030 885ace08 88585ea8 SCSIPORT!ScsiPortFdoDispatch+0x26c
f5c775f0 bff742f7 88ff60e8 885ace08 88ff6030 SCSIPORT!SpDispatchRequest+0x70
f5c7760c bff70390 88ff6030 885ace08 885ace08 SCSIPORT!ScsiPortPdoScsi+0xef
f5c7761c 8041eec9 88ff6030 885ace08 00000fff SCSIPORT!ScsiPortGlobalDispatch+0x1
a
f5c77630 f5820c66 88dae630 885ace08 88dae278 nt!IopfCallDriver+0x35
f5c7764c 8041eec9 88dae630 0001e000 88dae480 CLASSPNP!ClasspSendTestUnitIrp+0x99

f5c77660 f5c142db 8041eec9 88dae480 885ace08 nt!IopfCallDriver+0x35
f5c77664 8041eec9 88dae480 885ace08 885acf2c PartMgr!PmPassThrough+0x1b
f5c77678 f5d00480 88dae1c0 885ace08 885ace08 nt!IopfCallDriver+0x35
f5c77698 8041eec9 88dae1c0 885ace08 00000000 Diskperf!DiskPerfReadWrite+0xb4
f5c776ac bffbbb70 88daca10 885ace08 88daaed8 nt!IopfCallDriver+0x35
f5c776c8 8041eec9 88dacac8 885ace08 885acf74 ftdisk!FtDiskReadWrite+0x142
f5c776dc f5d00480 88daae20 885ace08 885ace00 nt!IopfCallDriver+0x35
f5c776fc 8041eec9 88daae20 885ace08 88b0d470 Diskperf!DiskPerfReadWrite+0xb4
f5c77710 bfe9e123 86988a28 885ace08 f5c778e8 nt!IopfCallDriver+0x35
f5c77720 bfe9e970 86988a28 88daae20 742fc000 Ntfs!NtfsSingleAsync+0x6b
f5c778e8 bfea1366 86988a28 885ace08 e82550d8 Ntfs!NtfsNonCachedIo+0x220
f5c77c74 bfe9f33e 86988a28 885ace08 88b0d3a0 Ntfs!NtfsCommonWrite+0x1d90
f5c77cdc 8041eec9 88b0d3a0 885ace08 885ace08 Ntfs!NtfsFsdWrite+0xee
f5c77cf0 bdae64a0 8804e840 8804ea68 8905b618 nt!IopfCallDriver+0x35
WARNING: Stack unwind information not available. Following frames may be wrong.
f5c77d28 bdae1520 885ace08 8804e840 885ace08 naiavf5x+0x74a0
f5c77d3c 8041eec9 8804e840 885ace08 87f93818 naiavf5x+0x2520
f5c77d50 8041e8ea 80065634 8905b608 8905b618 nt!IopfCallDriver+0x35
f5c77d64 8043f86b 8804e840 8905b640 8905b610 nt!IoAsynchronousPageWrite+0x96
f5c77da8 804578c2 00000000 00000000 00000000 nt!MiMappedPageWriter+0xc9
f5c77ddc 8046c956 8043f7a2 00000000 00000000 nt!PspSystemThreadStartup+0x54
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP!ClasspSendTestUnitIrp+99
f5820c66 b803010000 mov eax,103h

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: CLASSPNP!ClasspSendTestUnitIrp+99

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 3e25b9bb

FAILURE_BUCKET_ID: 0xD1_CLASSPNP!ClasspSendTestUnitIrp+99

BUCKET_ID: 0xD1_CLASSPNP!ClasspSendTestUnitIrp+99

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

0: kd>