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


Loading Dump File [C:\WINDOWS\Minidump\Mini120910-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.100216-1301
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Thu Dec  9 00:12:25.031 2010 (GMT-5)
System Uptime: 0 days 0:50:11.031
Loading Kernel Symbols
...............................................................
..................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, d0000002, 8, 0}

Unable to load image sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : storport.sys ( storport!RaidpAdapterDpcRoutine+28 )

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

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

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


READ_ADDRESS:  00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
+37
00000000 ??              ???

PROCESS_NAME:  Idle

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from f7833768 to 00000000

FAILED_INSTRUCTION_ADDRESS: 
+37
00000000 ??              ???

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
f78b6c9c f7833768 8a3366c0 f78b6cfc f78b6ce8 0x0
f78b6cac f72a4894 8aac0a8c 8aac0a18 00000000 storport!RaidpAdapterDpcRoutine+0x28
f78b6cf8 8083211c 8aac0a8c 8aac0a18 00000000 sptd+0x11894
f78b6d50 8088de7f 00000000 0000000e 00000000 nt!KiRetireDpcList+0xca
f78b6d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x37


STACK_COMMAND:  kb

FOLLOWUP_IP: 
storport!RaidpAdapterDpcRoutine+28
f7833768 85f6            test    esi,esi

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  storport!RaidpAdapterDpcRoutine+28

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: storport

IMAGE_NAME:  storport.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45d69bb4

FAILURE_BUCKET_ID:  0xD1_CODE_AV_NULL_IP_storport!RaidpAdapterDpcRoutine+28

BUCKET_ID:  0xD1_CODE_AV_NULL_IP_storport!RaidpAdapterDpcRoutine+28

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