locked
Blue Screen of Death RRS feed

  • Question

  • Hello. I keep receiving a BSOD. I ran WinDbg on the minidump file and here are the results. Any help would be appreciated.

     

     

     

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

     

     

    Loading Dump File [C:\Users\xxx\Desktop\112011-65707-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: 

    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`02c0f000 PsLoadedModuleList = 0xfffff800`02e54670

    Debug session time: Sun Nov 20 23:47:19.560 2011 (UTC - 8:00)

    System Uptime: 0 days 1:29:36.106

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ..........................

    Loading User Symbols

    Loading unloaded module list

    ........

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    Use !analyze -v to get detailed debugging information.

     

    BugCheck 101, {31, 0, fffff88002fd5180, 3}

     

    Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for Rt64win7.sys

    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys

    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for nvlddmkm.sys

    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

    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: fffff88002fd5180, 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:  VIRTUA~1.EXE

     

    CURRENT_IRQL:  d

     

    STACK_TEXT:  

    fffff800`00ba2098 fffff800`02ce38c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02fd5180 : nt!KeBugCheckEx

    fffff800`00ba20a0 fffff800`02c96497 : fffff800`00000000 fffff800`00000003 00000000`00026160 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4e2e

    fffff800`00ba2130 fffff800`03202895 : fffff800`03228460 fffff800`00ba22e0 fffff800`03228460 00000000`00000000 : nt!KeUpdateSystemTime+0x377

    fffff800`00ba2230 fffff800`02c88173 : 00000000`ff73d080 fffffa80`0798d000 fffff880`018459a0 00000000`0864d001 : hal!HalpHpetClockInterrupt+0x8d

    fffff800`00ba2260 fffff800`02c917a6 : fffff800`02e01e80 0000057f`00000001 00000000`00000000 fffff800`00ba2518 : nt!KiInterruptDispatchNoLock+0x163

    fffff800`00ba23f0 fffff800`02c29fbd : 00000000`00000014 fffff880`070f3000 00000000`00000000 fffff880`070f3068 : nt!KeFlushMultipleRangeTb+0x266

    fffff800`00ba24c0 fffff800`02c2a6e3 : fffff880`070f3068 00000000`00000004 00000000`00000001 00000000`00000001 : nt!MiRemoveIoSpaceMap+0xe9

    fffff800`00ba25f0 fffff880`03fd591b : 00000000`70110040 00000000`00000001 fffffa80`082ee8d8 fffffa80`082eb000 : nt!MmUnmapIoSpace+0x83

    fffff800`00ba2640 00000000`70110040 : 00000000`00000001 fffffa80`082ee8d8 fffffa80`082eb000 fffffa80`082eb068 : Rt64win7+0x7c91b

    fffff800`00ba2648 00000000`00000001 : fffffa80`082ee8d8 fffffa80`082eb000 fffffa80`082eb068 fffff880`03fd5987 : 0x70110040

    fffff800`00ba2650 fffffa80`082ee8d8 : fffffa80`082eb000 fffffa80`082eb068 fffff880`03fd5987 fffff880`02d7f300 : 0x1

    fffff800`00ba2658 fffffa80`082eb000 : fffffa80`082eb068 fffff880`03fd5987 fffff880`02d7f300 fffff880`130a794e : 0xfffffa80`082ee8d8

    fffff800`00ba2660 fffffa80`082eb068 : fffff880`03fd5987 fffff880`02d7f300 fffff880`130a794e fffff880`03316c20 : 0xfffffa80`082eb000

    fffff800`00ba2668 fffff880`03fd5987 : fffff880`02d7f300 fffff880`130a794e fffff880`03316c20 fffff800`00ba2860 : 0xfffffa80`082eb068

    fffff800`00ba2670 fffff880`02d7f300 : fffff880`130a794e fffff880`03316c20 fffff800`00ba2860 00000000`00000068 : Rt64win7+0x7c987

    fffff800`00ba2678 fffff880`130a794e : fffff880`03316c20 fffff800`00ba2860 00000000`00000068 00000000`00000007 : rdbss!RxDispatcherWorkQueues+0x1a0

    fffff800`00ba2680 fffff880`03316c20 : fffff800`00ba2860 00000000`00000068 00000000`00000007 fffffa80`082eb040 : nvlddmkm+0x7e94e

    fffff800`00ba2688 fffff800`00ba2860 : 00000000`00000068 00000000`00000007 fffffa80`082eb040 fffff880`03fd5ddc : 0xfffff880`03316c20

    fffff800`00ba2690 00000000`00000068 : 00000000`00000007 fffffa80`082eb040 fffff880`03fd5ddc fffff800`00000000 : 0xfffff800`00ba2860

    fffff800`00ba2698 00000000`00000007 : fffffa80`082eb040 fffff880`03fd5ddc fffff800`00000000 00000000`00000000 : 0x68

    fffff800`00ba26a0 fffffa80`082eb040 : fffff880`03fd5ddc fffff800`00000000 00000000`00000000 fffff800`00ba2770 : 0x7

    fffff800`00ba26a8 fffff880`03fd5ddc : fffff800`00000000 00000000`00000000 fffff800`00ba2770 00000000`00000000 : 0xfffffa80`082eb040

    fffff800`00ba26b0 fffff800`00000000 : 00000000`00000000 fffff800`00ba2770 00000000`00000000 00000000`00000068 : Rt64win7+0x7cddc

    fffff800`00ba26b8 00000000`00000000 : fffff800`00ba2770 00000000`00000000 00000000`00000068 fffffa80`0984dd01 : 0xfffff800`00000000

     

     

    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

    ---------

     

     


    • Edited by Artifaxx Monday, November 21, 2011 4:50 PM
    Monday, November 21, 2011 4:50 PM

Answers

  • Hi,
     
    Can you post the minidumps to skydrive for further analysis and post a link,
     
     
    Based on the type of error (CLOCK_WATCHDOG_TIMEOUT), please try a CPU
    stress test to help determine if there is a hardware issue occurring
    with the processor,
     
     

    -- Mike Burr
    Technology
    • Marked as answer by Miya Yao Friday, December 2, 2011 5:53 AM
    Monday, November 21, 2011 7:20 PM
  • Bug Check Code 0x101: http://msdn.microsoft.com/en-us/library/ff557211(v=VS.85).aspx

    The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

    Please start by updating your processor driver and check again. If this does not help, consider contacting your manufacturer Technical Support.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Marked as answer by Miya Yao Friday, December 2, 2011 5:53 AM
    Wednesday, November 23, 2011 10:12 PM

All replies

  • Hi,
     
    Can you post the minidumps to skydrive for further analysis and post a link,
     
     
    Based on the type of error (CLOCK_WATCHDOG_TIMEOUT), please try a CPU
    stress test to help determine if there is a hardware issue occurring
    with the processor,
     
     

    -- Mike Burr
    Technology
    • Marked as answer by Miya Yao Friday, December 2, 2011 5:53 AM
    Monday, November 21, 2011 7:20 PM
  • Bug Check Code 0x101: http://msdn.microsoft.com/en-us/library/ff557211(v=VS.85).aspx

    The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

    Please start by updating your processor driver and check again. If this does not help, consider contacting your manufacturer Technical Support.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Marked as answer by Miya Yao Friday, December 2, 2011 5:53 AM
    Wednesday, November 23, 2011 10:12 PM