*******************************************************************************
*                                                                             *
*                        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: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 8e700120, The PRCB address of the hung processor.
Arg4: 00000002, 0.

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

*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 8384f000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78a09

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
935ec44c 838caa6f 00000101 00000031 00000000 nt+0xdef20
935ec488 838ca0be 00002711 00000000 0000a900 nt+0x7ba6f
935ec4c8 838c9f6b 838cbe7b 06e499cf 00000000 nt+0x7b0be
935ec524 838cec17 905f501b 905f501b 000000d1 nt+0x7af6b
935ec538 838cbe7b badb0d00 00000000 2073664c nt+0x7fc17
935ec5f4 838cfdf9 935ec648 00000000 935ec648 nt+0x7ce7b
935ec6d0 838d786c a29c2000 00001000 a380b0f8 nt+0x80df9
935ec760 8c6e4d0f 8816b808 935ec97c 00001000 nt+0x8886c
935ec9dc 8c6b7df8 935ecadc 870320d8 00000000 Ntfs+0xb7d0f
935eca30 8c6b7c19 935ecadc 870320d8 935ecbff Ntfs+0x8adf8
935eca90 8c6b7f03 935ecadc 00000000 8c6b7dbd Ntfs+0x8ac19
935ecc00 838ccaab 00000000 00000000 88069720 Ntfs+0x8af03
935ecc50 83a58f5e 80000000 ab1fbc0b 00000000 nt+0x7daab
935ecc90 83900219 838cc99e 80000000 00000000 nt+0x209f5e
00000000 00000000 00000000 00000000 00000000 nt+0xb1219


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntkrnlpa.exe

BUCKET_ID:  WRONG_SYMBOLS

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