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

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: c0000005, The exception code that was not handled
Arg2: 80638451, The address that the exception occurred at
Arg3: ba2b796c, Trap Frame
Arg4: 00000000

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"

FAULTING_IP:
nt!HvpGetCellMapped+5f
80638451 8b4304          mov     eax,dword ptr [ebx+4]

TRAP_FRAME: ba2b796c -- (.trap ffffffffba2b796c)
ErrCode = 00000000
eax=00000560 ebx=00000560 ecx=89de0190 edx=00000003 esi=e1037008 edi=00000369
eip=80638451 esp=ba2b79e0 ebp=ba2b7a28 iopl=0         nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000             efl=00010246
nt!HvpGetCellMapped+0x5f:
80638451 8b4304          mov     eax,dword ptr [ebx+4] ds:0023:00000564=????????
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: services.exe

LAST_CONTROL_TRANSFER: from 804ff827 to 804faf43

STACK_TEXT:
ba2b7534 804ff827 0000008e c0000005 80638451 nt!KeBugCheckEx+0x1b
ba2b78fc 805430a5 ba2b7918 00000000 ba2b796c nt!KiDispatchException+0x3b1
ba2b7964 80543056 ba2b7a28 80638451 badb0d00 nt!CommonDispatchException+0x4d
ba2b796c 80638451 badb0d00 00000003 00000004 nt!Kei386EoiHelper+0x18a
ba2b7a28 80638362 e1037008 00656369 e1037008 nt!HvpGetCellMapped+0x5f
ba2b7a3c 8063c7f6 e1037008 00656369 e1037008 nt!HvpGetHCell+0x10
ba2b7a58 80630bc8 e1037008 00656369 e1037008 nt!HvMarkCellDirty+0x30
ba2b7a74 80639cae e1037008 d82e6f6c e1037008 nt!CmpMarkValueDataDirty+0xf2
ba2b7a90 80639f53 e1037008 0032d9d8 d838cb04 nt!CmpMarkKeyValuesDirty+0xcc
ba2b7aac 80639ff0 e1037008 0032d9d8 d82ee9dc nt!CmpFreeKeyValues+0x17
ba2b7ae8 8063a82e e1037008 0013c8a0 d80fd8a4 nt!CmpSyncKeyValues+0x26
ba2b7b2c 8063a9a1 e2d2f000 00000400 00000003 nt!CmpCopySyncTree2+0x1f4
ba2b7b5c 806270a2 e1037008 000001b8 e1037008 nt!CmpCopySyncTree+0x4f
ba2b7ccc 8062299a 00010002 ba2b7d64 ba2b7ce8 nt!CmpSaveBootControlSet+0x2b0
ba2b7cdc 8054263c 00000004 ba2b7d64 8050147d nt!NtInitializeRegistry+0x5e
ba2b7cdc 8050147d 00000004 ba2b7d64 8050147d nt!KiFastCallEntry+0xfc
ba2b7d58 8054263c 00000004 0007fe8c 7c92e514 nt!ZwInitializeRegistry+0x11
ba2b7d58 7c92e514 00000004 0007fe8c 7c92e514 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0007fe8c 00000000 00000000 00000000 00000000 0x7c92e514

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!HvpGetCellMapped+5f
80638451 8b4304          mov     eax,dword ptr [ebx+4]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!HvpGetCellMapped+5f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b1e8f8a

FAILURE_BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f

BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f

Followup: MachineOwner

-----------------------

可能得修复方式：chkdsk /r