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


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

Symbol search path is: srv*c:\programfiler\Debugging Tools for Windows\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Sun May  4 13:17:47.156 2008 (GMT+2)
System Uptime: 1 days 4:49:20.727
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.......................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffff, 2, 0, ffff}



Probably caused by : ntoskrnl.exe ( nt!KiTrap0E+233 )

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

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

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




READ_ADDRESS:  0000ffff 

CURRENT_IRQL:  2

FAULTING_IP: 
+ffff
0000ffff ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  f78a6e18 -- (.trap 0xfffffffff78a6e18)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=00000041 edx=80559f40 esi=f78a6eb0 edi=0000ffff
eip=0000ffff esp=f78a6e8c ebp=f78a6fa4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00050246
0000ffff ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 0000ffff to 804e187f

FAILED_INSTRUCTION_ADDRESS: 
+ffff
0000ffff ??              ???

STACK_TEXT:  
f78a6e18 0000ffff badb0d00 80559f40 ba2c854e nt!KiTrap0E+0x233
WARNING: Frame IP not in any known module. Following frames may be wrong.
f78a6e88 804dc4fd 20000000 000000b8 7b335704 0xffff
f78a6fa4 804dc378 96368b7f 000000f1 ffdff000 nt!KiTimerListExpire+0x122
f78a6fd0 804dbbd4 80559480 00000000 0065542e nt!KiTimerExpiration+0xaf
f78a6ff4 804db89e af4d3d44 00000000 00000000 nt!KiRetireDpcList+0x46
f78a6ff8 af4d3d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
f78a6ffc 00000000 00000000 00000000 00000000 0xaf4d3d44


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTrap0E+233
804e187f f7457000000200  test    dword ptr [ebp+70h],20000h

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiTrap0E+233

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  45e54711

FAILURE_BUCKET_ID:  0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+233

BUCKET_ID:  0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+233

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