locked
BSOD win7 64bit RRS feed

  • Question

  • hi

     

    i am often getting BSODs and need help to read the minidump files to troubleshoot the problem.

    the dump file is located at https://skydrive.live.com/redir.aspx?cid=3558bec2d94242df&resid=3558BEC2D94242DF!144

     


    new sharepoint user
    Tuesday, August 9, 2011 2:55 AM

Answers

  • Hi,

     

    After check your dump file:

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

    *                                                                             *

    *                        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: fffff880035d7180, 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:  System

     

    CURRENT_IRQL:  d

     

    STACK_TEXT: 

    fffff880`0391d268 fffff800`02ed78f9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`035d7180 : nt!KeBugCheckEx

    fffff880`0391d270 fffff800`02e8a4b7 : 00000000`00000000 fffff800`00000003 00000000`00002711 00000000`0000000c : nt! ?? ::FNODOBFM::`string'+0x4e2e

    fffff880`0391d300 fffff800`033f3895 : fffff800`03419460 fffff880`0391d4b0 fffff800`03419460 00000000`00000000 : nt!KeUpdateSystemTime+0x377

    fffff880`0391d400 fffff800`02e7c233 : 00000000`408c9fc3 fffff800`02ff2e80 00000000`00000000 fffff880`0391d630 : hal!HalpHpetClockInterrupt+0x8d

    fffff880`0391d430 fffff800`02eb637b : fffff800`02ff2e80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163

    fffff880`0391d5c0 fffff800`02eb52ed : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x83

    fffff880`0391d600 fffff800`02ed9850 : 00000000`00000001 fffff6fc`4003d320 00000000`00000001 00000000`00000004 : nt!KeFlushTb+0x119

    fffff880`0391d680 fffff800`02e9054f : fffff6fc`4003d320 fffff880`0391d700 fffff800`030b2500 fffff800`030b2500 : nt! ?? ::FNODOBFM::`string'+0xae02

    fffff880`0391d6c0 fffff800`02e9d7be : 00000000`00000001 fffff880`07a64000 00000000`00000002 fffff6fc`4003d320 : nt!MiResolveDemandZeroFault+0x1ff

    fffff880`0391d7b0 fffff800`02e8da2b : fffff880`02c12c70 fffff800`030b2a80 00000000`00000206 fffff800`02e9f533 : nt!MiDispatchFault+0x8ce

    fffff880`0391d8c0 fffff800`02eb44e0 : 00000000`00000001 fffff880`07a64000 fffffa80`0babeb00 fffff6fc`4003d300 : nt!MmAccessFault+0xe1b

    fffff880`0391da20 fffff800`02eb46d0 : fffffa80`0b36c710 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiInPageSingleKernelStack+0x134

    fffff880`0391db30 fffff800`02eb465f : 00000000`00000000 00000000`00000001 fffffa80`06ca2890 00000000`00000080 : nt!MmInPageKernelStack+0x40

    fffff880`0391db90 fffff800`02eb43a4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`06ca2800 : nt!KiInSwapKernelStacks+0x1f

    fffff880`0391dbc0 fffff800`0311c32e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x84

    fffff880`0391dc00 fffff800`02e71666 : fffff880`03565180 fffffa80`06d3eb60 fffff880`0356ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

    fffff880`0391dc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

     

     

    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

    ---------

     

    One of your CPU may corrupted or overclocking. Please contact your PC manufacturer to check.

     

     

    Regards,

    Leo   Huang

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Leo Huang Wednesday, August 17, 2011 7:06 AM
    Thursday, August 11, 2011 6:14 AM

All replies

  • The zip file is empty
    Tuesday, August 9, 2011 5:25 AM
  • Hi Craig

     

    sorry for the missing files.

    i have tried to reload it again.

    there should be a zip file 310kb in size.

     


    DTTL
    Tuesday, August 9, 2011 5:44 AM
  • Hi,

     

    After check your dump file:

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

    *                                                                             *

    *                        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: fffff880035d7180, 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:  System

     

    CURRENT_IRQL:  d

     

    STACK_TEXT: 

    fffff880`0391d268 fffff800`02ed78f9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`035d7180 : nt!KeBugCheckEx

    fffff880`0391d270 fffff800`02e8a4b7 : 00000000`00000000 fffff800`00000003 00000000`00002711 00000000`0000000c : nt! ?? ::FNODOBFM::`string'+0x4e2e

    fffff880`0391d300 fffff800`033f3895 : fffff800`03419460 fffff880`0391d4b0 fffff800`03419460 00000000`00000000 : nt!KeUpdateSystemTime+0x377

    fffff880`0391d400 fffff800`02e7c233 : 00000000`408c9fc3 fffff800`02ff2e80 00000000`00000000 fffff880`0391d630 : hal!HalpHpetClockInterrupt+0x8d

    fffff880`0391d430 fffff800`02eb637b : fffff800`02ff2e80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163

    fffff880`0391d5c0 fffff800`02eb52ed : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x83

    fffff880`0391d600 fffff800`02ed9850 : 00000000`00000001 fffff6fc`4003d320 00000000`00000001 00000000`00000004 : nt!KeFlushTb+0x119

    fffff880`0391d680 fffff800`02e9054f : fffff6fc`4003d320 fffff880`0391d700 fffff800`030b2500 fffff800`030b2500 : nt! ?? ::FNODOBFM::`string'+0xae02

    fffff880`0391d6c0 fffff800`02e9d7be : 00000000`00000001 fffff880`07a64000 00000000`00000002 fffff6fc`4003d320 : nt!MiResolveDemandZeroFault+0x1ff

    fffff880`0391d7b0 fffff800`02e8da2b : fffff880`02c12c70 fffff800`030b2a80 00000000`00000206 fffff800`02e9f533 : nt!MiDispatchFault+0x8ce

    fffff880`0391d8c0 fffff800`02eb44e0 : 00000000`00000001 fffff880`07a64000 fffffa80`0babeb00 fffff6fc`4003d300 : nt!MmAccessFault+0xe1b

    fffff880`0391da20 fffff800`02eb46d0 : fffffa80`0b36c710 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiInPageSingleKernelStack+0x134

    fffff880`0391db30 fffff800`02eb465f : 00000000`00000000 00000000`00000001 fffffa80`06ca2890 00000000`00000080 : nt!MmInPageKernelStack+0x40

    fffff880`0391db90 fffff800`02eb43a4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`06ca2800 : nt!KiInSwapKernelStacks+0x1f

    fffff880`0391dbc0 fffff800`0311c32e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x84

    fffff880`0391dc00 fffff800`02e71666 : fffff880`03565180 fffffa80`06d3eb60 fffff880`0356ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

    fffff880`0391dc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

     

     

    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

    ---------

     

    One of your CPU may corrupted or overclocking. Please contact your PC manufacturer to check.

     

     

    Regards,

    Leo   Huang

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Leo Huang Wednesday, August 17, 2011 7:06 AM
    Thursday, August 11, 2011 6:14 AM