Loading Dump File 
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Wed Dec 28 02:21:08.187 2005 (GMT-5)
System Uptime: 0 days 1:18:35.151
Unable to load image 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 100000D1, {71a5df52, 2, 0, 71a5df52}

Probably caused by : Unknown_Image

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

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


READ_ADDRESS:  71a5df52 

CURRENT_IRQL:  2

FAULTING_IP: 
+71a5df52
71a5df52 ??               ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from 00000000 to 71a5df52

STACK_TEXT:  
0079f078 00000000 00666df8 00000000 00000000 0x71a5df52


FAILED_INSTRUCTION_ADDRESS: 
+71a5df52
71a5df52 ??               ???

FOLLOWUP_IP: 
+71a5df52
71a5df52 ??               ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME:  Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  kb

BUCKET_ID:  INVALID_KERNEL_CONTEXT