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

Symbol search path is: *c:/symbols/*srvhttp://msdl.microsoft.com/downloads/symbols
Executable search path is: http://msdl.microsoft.com/downloads/symbols
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81800000 PsLoadedModuleList = 0x81908ad0
Debug session time: Mon Mar  3 12:53:06.249 2008 (GMT+1)
System Uptime: 0 days 0:01:53.862
Loading Kernel Symbols
.........................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8a685000, 2, 0, 8b17c7a0}

Unable to load image \SystemRoot\system32\drivers\nvmcp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmcp.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmcp.sys


Probably caused by : nvmcp.sys ( nvmcp+5c7a0 )

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

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




READ_ADDRESS: GetPointerFromAddress: unable to read from 819275a0
Unable to read MiSystemVaType memory at 819086a0
 8a685000 

CURRENT_IRQL:  2

FAULTING_IP: 
nvmcp+5c7a0
8b17c7a0 ??              ???

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

TRAP_FRAME:  8761db24 -- (.trap 0xffffffff8761db24)
ErrCode = 00000000
eax=000000b3 ebx=86a9fc28 ecx=8a685000 edx=86aa7360 esi=00000002 edi=86aa6b20
eip=8b17c7a0 esp=8761db98 ebp=00000001 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nvmcp+0x5c7a0:
8b17c7a0 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8b17c7a0 to 818493d4

STACK_TEXT:  
8761db24 8b17c7a0 badb0d00 86aa7360 83e410c4 nt!KiTrap0E+0x2ac
WARNING: Stack unwind information not available. Following frames may be wrong.
8761db94 00000000 86a9fc28 0000cc00 86a9ff58 nvmcp+0x5c7a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvmcp+5c7a0
8b17c7a0 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nvmcp+5c7a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvmcp

IMAGE_NAME:  nvmcp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4179548d

FAILURE_BUCKET_ID:  0xD1_nvmcp+5c7a0

BUCKET_ID:  0xD1_nvmcp+5c7a0

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