DaHeng CCV halt

dump

3: 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: c0000017, The exception code that was not handled
Arg2: 842dbf96, The address that the exception occurred at
Arg3: a4d6a668, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000017 - {

FAULTING_IP: 
nt!MiMapLockedPagesInUserSpace+52
842dbf96 684d6d7076      push    76706D4Dh

TRAP_FRAME:  a4d6a668 -- (.trap 0xffffffffa4d6a668)
ESP EDITED! New esp=a4d6aa18
ErrCode = 00000000
eax=8b6892a0 ebx=00036000 ecx=00030004 edx=00030003 esi=8bce74b8 edi=8c0f0de8
eip=842dbf96 esp=a4d6a6dc ebp=a4d6aa44 iopl=0         nv up ei pl zr na po cy
cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000243
nt!MiMapLockedPagesInUserSpace+0x52:
842dbf96 684d6d7076      push    76706D4Dh
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  CCV.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 84095fb7 to 842dbf96

STACK_TEXT:  
a4d6aa44 84095fb7 87594f08 00000001 00000000 nt!MiMapLockedPagesInUserSpace+0x52
a4d6aaa8 8407dc0e 87594f08 00000001 00000001 nt!MmMapLockedPagesSpecifyCache+0x29
a4d6aac8 8e983731 87594f08 00000001 8c336740 nt!MmMapLockedPages+0x18
WARNING: Stack unwind information not available. Following frames may be wrong.
a4d6aae8 8e9833b0 8b268d68 8b9c41a8 8c336740 DVCServ+0x731
a4d6ab14 8423999f 8c336740 8b9c41a8 8b9c4218 DVCServ+0x3b0
a4d6ab34 8423cb71 8b268cb0 8c336740 00000000 nt!IopSynchronousServiceTail+0x1f8
a4d6abd0 842833f4 8b268cb0 8b9c41a8 00000000 nt!IopXxxControlFile+0x6aa
a4d6ac04 8404c1ea 00000238 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
a4d6ac04 76e070b4 00000238 00000000 00000000 nt!KiFastCallEntry+0x12a
0574fe10 00000000 00000000 00000000 00000000 0x76e070b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
DVCServ+731
8e983731 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  DVCServ+731

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: DVCServ

IMAGE_NAME:  DVCServ.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  3fcd3a8c

FAILURE_BUCKET_ID:  0x8E_DVCServ+731

BUCKET_ID:  OLD_IMAGE_DVCServ.sys

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