My brother is getting this really annoying BSOD quite often.
How the ***** do I solve that?
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [\\SERVER\Random\090811-21153-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03018000 PsLoadedModuleList = 0xfffff800`0325d670
Debug session time: Thu Sep 8 19:28:33.573 2011 (UTC + 2:00)
System Uptime: 0 days 0:30:04.791
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff880031d7180, 3}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880031d7180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: dllhost.exe
CURRENT_IRQL: d
STACK_TEXT:
fffff880`0be20d38 fffff800`030ec8c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`031d7180 : nt!KeBugCheckEx
fffff880`0be20d40 fffff800`0309f497 : 00000000`00000000 fffff800`00000003 00000000`00002710 fffff800`030a1618 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0be20dd0 fffff800`0360b895 : fffff800`03631460 fffff880`0be20f80 fffff800`03631460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0be20ed0 fffff800`03091173 : 00000000`720ab1f0 00000000`00000000 00000006`0000000e fffffa80`0b3e89b0 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0be20f00 fffff800`030cb361 : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0be21090 fffff800`0309a7cc : 00000000`00000000 fffff880`0be211f8 fffff880`00163000 fffffa80`00000000 : nt!KxFlushEntireTb+0xcd
fffff880`0be210d0 fffff800`030ac5c6 : 00000000`00000004 00000000`00000000 fffff6fc`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`0be211a0 fffff800`030ac842 : fa80072f`43d004c0 fffff980`2714003f 00000000`00000000 fa80072f`43d004c0 : nt!MiObtainSystemCacheView+0x352
fffff880`0be212e0 fffff800`030abb87 : fffff8a0`0a509d70 fffff800`0320b530 fffff880`0be21488 fffff880`0be214a8 : nt!MmMapViewInSystemCache+0xc2
fffff880`0be21450 fffff800`030aaaef : fffff980`00000000 00000000`176c0000 00000000`17680000 00000000`00000000 : nt!CcGetVacbMiss+0x177
fffff880`0be21510 fffff800`0337edc2 : 00000000`00000000 00000000`176c0000 fffff880`0be215e0 fffff880`0be21670 : nt!CcGetVirtualAddress+0x2e0
fffff880`0be215a0 fffff880`012b0f08 : fffff880`00000001 00000000`00000005 fffffa80`00040000 fffffa80`00163001 : nt!CcCopyRead+0x132
fffff880`0be21660 fffff880`01041098 : fffffa80`0b69fa20 fffffa80`090e9df8 00000000`00120089 fffffa80`0b69fa01 : Ntfs!NtfsCopyReadA+0x1a8
fffff880`0be21840 fffff880`010448ba : fffff880`0be21910 00000000`0b11b403 00000000`0b11b400 fffffa80`0b69fa00 : fltmgr!FltpPerformFastIoCall+0x88
fffff880`0be218a0 fffff880`01062630 : fffffa80`0b69fa20 00000000`00000000 fffff880`0be21a00 00000000`00163000 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`0be218e0 fffff800`0337e949 : fffffa80`0b69fa20 fffff800`00000001 fffffa80`067199f0 fffffa80`0b69fa20 : fltmgr!FltpFastIoRead+0x1d0
fffff880`0be21980 fffff800`03093ed3 : 00000000`000002e4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x417
fffff880`0be21a70 00000000`7764137a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0200f768 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7764137a
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: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
How the ***** do I solve that?
