蓝屏.........郁闷中啊，， 已经解析过里，，帮忙解决下。
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\zh\Desktop\Minidump\Minidump\Mini102313-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Windows\symbols
Executable search path is:
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (8 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a8ec8
Debug session time: Wed Oct 23 19:09:03.460 2013 (GMT+8)
System Uptime: 9 days 8:02:24.227
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
............................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 51, {3, 4, d7490a80, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
Probably caused by : ntkrnlpa.exe ( nt!KeDelayExecutionThread+1f7 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 00000003, (reserved)
Arg2: 00000004, (reserved)
Arg3: d7490a80, depends on where Windows bugchecked, may be pointer to hive
Arg4: 00000000, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x51
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 808bd5da to 80827dc1
STACK_TEXT:
f791ad18 808bd5da 00000051 00000003 00000004 nt!KeDelayExecutionThread+0x1f7
f791ad3c 808c52a7 d7490a01 8d1a3b40 808a6710 nt!CmMoveKey+0x290
f791ad58 808c0121 00000000 d7490d78 f791ad78 nt!HvpBuildMapAndCopy+0xeb
f791ad80 80881e89 00000000 00000000 8d1a3b40 nt!CmpCleanUpKCBCacheTable+0x137
f791adac 8094bf62 00000000 00000000 00000000 nt!CpInitialize+0x3f
f791addc 8088fabe 80881d9e 00000001 00000000 nt!RtlUpcaseUnicodeToMultiByteN+0x218
00000000 00000000 00000000 00000000 00000000 nt!KdPitchDebugger+0x1216
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeDelayExecutionThread+1f7
80827dc1 5d pop ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KeDelayExecutionThread+1f7
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlpa.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 49e86572
FAILURE_BUCKET_ID: 0x51_nt!KeDelayExecutionThread+1f7
BUCKET_ID: 0x51_nt!KeDelayExecutionThread+1f7
Followup: MachineOwner
---------
