Need help analyzing minidump

You say "usually", have you got only one crash file so far?


101510-11762-01.dmp
Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT
BugCheck 101, {31, 0, fffff88002f63180, 2}

The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\101510-11762-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image Unknown_Module_662a7502`6b396630, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_662a7502`6b396630
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_662a7502`6b396630
Debugger can not determine kernel base address
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03267000 PsLoadedModuleList = 0xfffff800`034a4e50
Debug session time: Fri Oct 15 10:17:41.522 2010 (GMT-5)
System Uptime: 0 days 5:15:38.927
Unable to load image Unknown_Module_662a7502`6b396630, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_662a7502`6b396630
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_662a7502`6b396630
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002f63180, 2}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

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: fffff88002f63180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff800`0481d7f8 fffff800`03285453 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f63180 : 0xfffff800`032d7740
fffff800`0481d800 00000000`00000101 : 00000000`00000031 00000000`00000000 fffff880`02f63180 00000000`00000002 : 0xfffff800`03285453
fffff800`0481d808 00000000`00000031 : 00000000`00000000 fffff880`02f63180 00000000`00000002 fffff800`0481d8c0 : <Unloaded_Unknown_Module_00000000`00000050>+0xb1
fffff800`0481d810 00000000`00000000 : fffff880`02f63180 00000000`00000002 fffff800`0481d8c0 00000002`00000000 : 0x31


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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


662a7502`6b396630 662a7503`6b27d919   Unknown_Module_662a7502_6b396630 Unknown_Module_662a7502`6b396630 unavailable (00000000)
Missing image name, possible paged-out or corrupt data.

Unloaded modules:
00000000`00000050 00000001`00000000   Unknown_Module_00000000`00000050
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Missing image name, possible paged-out or corrupt data.
000003c0`0000067e 000003c1`00000001   Unknown_Module_000003c0`0000067e
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Missing image name, possible paged-out or corrupt data.
00000000`7226014a 00000001`00000000   Unknown_Module_00000000`7226014a
    Timestamp: unavailable (00000000)
    Checksum:  00000000