[blue screen] IMAGE_NAME: kisknl.sys

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


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

Symbol search path is: SRV*D:\down\TEMP*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x8424d000 PsLoadedModuleList = 0x84395810
Debug session time: Sun Jul  3 11:40:29.424 2011 (GMT+8)
System Uptime: 0 days 0:13:32.502
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000006, 84494c31, a1c0f5bc, 0}

*** WARNING: Unable to verify timestamp for kisknl.sys
*** ERROR: Module load completed but symbols could not be loaded for kisknl.sys
Probably caused by : kisknl.sys ( kisknl+aa58 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000006, The exception code that was not handled
Arg2: 84494c31, The address that the exception occurred at
Arg3: a1c0f5bc, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - 0x%p

FAULTING_IP: 
nt!ObfDereferenceDeviceMap+37
84494c31 ff4b0c          dec     dword ptr [ebx+0Ch]

TRAP_FRAME:  a1c0f5bc -- (.trap 0xffffffffa1c0f5bc)
ErrCode = 00000002
eax=8438eb60 ebx=acdd35f8 ecx=00000001 edx=00000000 esi=8438eb60 edi=860bed48
eip=84494c31 esp=a1c0f630 ebp=a1c0f63c iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!ObfDereferenceDeviceMap+0x37:
84494c31 ff4b0c          dec     dword ptr [ebx+0Ch]  ds:0023:acdd3604=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8446e5e3 to 84494c31

STACK_TEXT:  
a1c0f63c 8446e5e3 acdd35f8 884ba1a0 884ba300 nt!ObfDereferenceDeviceMap+0x37
a1c0f694 84494729 00000000 a1c0f6e8 00000240 nt!ObpLookupObjectName+0x562
a1c0f6f0 8448ca7b a1c0f818 86141040 a1c0f800 nt!ObOpenObjectByName+0x165
a1c0f76c 844c4279 a1c0f8a4 00100080 a1c0f818 nt!IopCreateFile+0x673
a1c0f7c8 917d3a58 a1c0f8a4 00100080 a1c0f818 nt!IoCreateFileEx+0x9e
WARNING: Stack unwind information not available. Following frames may be wrong.
a1c0f84c 917d4021 a1c0f89c 00100080 00000001 kisknl+0xaa58
a1c0f86c 917d465a a1c0f89c 00100080 00000001 kisknl+0xb021
a1c0f8a8 917d0516 a1c0fa28 a1c0f8c8 00000000 kisknl+0xb65a
a1c0f8f0 917d1360 a1c0f928 a1c0fa38 a1c0fa34 kisknl+0x7516
a1c0fa70 842894ac 88069688 860cf358 88315e6c kisknl+0x8360
00000000 00000000 00000000 00000000 00000000 nt!IofCallDriver+0x63


STACK_COMMAND:  kb

FOLLOWUP_IP: 
kisknl+aa58
917d3a58 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  kisknl+aa58

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kisknl

IMAGE_NAME:  kisknl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ddf6083

FAILURE_BUCKET_ID:  0x8E_kisknl+aa58

BUCKET_ID:  0x8E_kisknl+aa58

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