有时候开机就蓝屏报0X00000101，有时候看视频蓝屏，开机什么也不做同样蓝屏，请教这是什么问题导致的？？
还在保内，去找了三次联想的售后他们叫我安装原版系统，用官网的驱动，我这样做了还是蓝屏
完整dump文件有1.66G，我传了几个mini的麻烦帮忙分析一下，万分感谢！
dump 地址：http://pan.baidu.com/s/1dDGcdrz
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\蓝屏文件\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available
Symbol search path is: SRV*e:\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x83c14000 PsLoadedModuleList = 0x83d5e850
Debug session time: Sun Mar 9 20:38:41.108 2014 (GMT+8)
System Uptime: 0 days 0:03:51.621
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 807c0120, The PRCB address of the hung processor.
Arg4: 00000001, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 1c
STACK_TEXT:
807f998c 83c8fa6f 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
807f99c8 83c8f0be 00026160 00000000 00003900 nt!KeAccumulateTicks+0x242
807f9a08 83c8ef6b 83c4bc1e d65bed8e 00000000 nt!KeUpdateRunTime+0x145
807f9a60 83c93c17 94c2731b 94c2731b 000000d1 nt!KeUpdateSystemTime+0x613
807f9a60 83c4bc1e 94c2731b 94c2731b 000000d1 nt!KeUpdateSystemTimeAssist+0x13
807f9b04 83c94df9 8d980000 00000000 807f9b5c nt!KeFlushMultipleRangeTb+0x2c0
807f9b18 83c72670 00001000 869c2348 00000000 nt!MiFlushPteList+0x22
807f9be0 83c9c86c 8d981000 00001000 00000001 nt!MmSetAddressRangeModified+0x205
807f9c70 83c9f96e 869c289c 00000000 00000001 nt!CcFlushCache+0x294
807f9ca8 83cae33b 807f9cc4 99a8cd90 859fe0d0 nt!CcWriteBehind+0x105
807f9d00 83c91aab 859fe0d0 00000000 85a0fd48 nt!CcWorkerThread+0x164
807f9d50 83e1df5e 00000000 99a8cd00 00000000 nt!ExpWorkerThread+0x10d
807f9d90 83cc5219 83c9199e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
