First BSOD dump

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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.100216-1441
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Jul 16 03:14:11.687 2012 (UTC + 2:00)
System Uptime: 0 days 3:45:09.416
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {2, 9, 0, 8a59b000}

Probably caused by : ntkrpamp.exe ( nt!KiIdleLoop+10 )

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

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


READ_ADDRESS: GetUlongFromAddress: unable to read from 80560f30
 00000002

CURRENT_IRQL:  9

FAULTING_IP:
+0
8a59b000 0203            add     al,byte ptr [ebx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

LAST_CONTROL_TRANSFER:  from 80544fdc to 8a59b000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b84d3d50 80544fdc 00000000 0000000e 00000000 0x8a59b000
b84d3d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiIdleLoop+10
80544fdc f390            pause

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiIdleLoop+10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b7a91dc

FAILURE_BUCKET_ID:  0xD1_nt!KiIdleLoop+10

BUCKET_ID:  0xD1_nt!KiIdleLoop+10

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