none
[BSOD] WATCHDOG_TIMEOUT RRS feed

  • Общие обсуждения

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

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


    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_IPI_EARLY

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  1c

    STACK_TEXT: 
    82706890 826c9321 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
    827068c4 826c902d 0000001b 000000d1 82706984 nt!KeUpdateRunTime+0xd5
    827068c4 826c8ca2 0000001b 000000d1 82706984 nt!KeUpdateSystemTime+0xed
    82706950 82617671 0000000e 82617712 838a0982 nt!KiIpiSendPacket+0x8e
    82706984 838a0b3e 838a0982 8270699c 00040000 nt!KeIpiGenericCall+0x6e
    WARNING: Stack unwind information not available. Following frames may be wrong.
    827069d4 838a126a 0000001f 838a084e 827069f8 spyq+0x14b3e
    82706a04 8389b5e3 01000001 89c19150 89ce0f20 spyq+0x1526a
    82706a1c 8389cf6d 00000103 89c609d0 89c82008 spyq+0xf5e3
    82706a48 8389f8c4 89c19098 82706aa0 8389c8ec spyq+0x10f6d
    82706ab8 826cd053 89be3030 89c19098 89c19190 spyq+0x138c4
    82706ad0 83dc1b11 841ec1f4 89c4ced0 841ee000 nt!IofCallDriver+0x63
    82706ae4 826cd053 89c4ced0 89c19098 89c19098 iviaspi+0x2b11
    82706afc 841df264 89c60b70 89c609b0 89c60ab8 nt!IofCallDriver+0x63
    82706b10 841df45d 89c60b70 89c609c8 00000000 CLASSPNP!ClasspSendMediaStateIrp+0x2ec
    82706b28 841df2af 89c60b70 89bd8be4 82745cc0 CLASSPNP!ClassCheckMediaState+0x54
    82706b48 8264b598 89c60ab8 00000000 82706b94 CLASSPNP!ClasspTimerTick+0x41
    82706b68 826c7d00 82745ca0 02745c44 3c29efe0 nt!IopTimerDispatch+0x49
    82706c88 826c78c0 82706cd0 893cdb02 82706cd8 nt!KiTimerListExpire+0x367
    82706ce8 826c7483 00000000 00000000 0054fe6c nt!KiTimerExpiration+0x22a
    82706d50 826c5f9d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
    82706d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


    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:  CLOCK_WATCHDOG_TIMEOUT_IPI_EARLY_ANALYSIS_INCONCLUSIVE

    BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_IPI_EARLY_ANALYSIS_INCONCLUSIVE

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



    Устал уже блин, появление совершенно рендомное, но последнее время участилось.
    Как бороться? Стоит заметить, что на Win7/Ubuntu не наблюдается...


    "When there's something strange in the neighborhood... WHO YA GONNA CALL?"
    • Изменен тип Igor LeykoModerator 18 октября 2010 г. 18:00 давность и отсутствие активности в теме
    27 февраля 2009 г. 22:32