BSOD A clock interrupt was not received on a secondary processor...


  1. Posts : 373
    Windows 7 Ultimate x6
       #1

    BSOD A clock interrupt was not received on a secondary processor...


    I just had a BSOD with my Clevo W860CU laptop with GTX 285M and 920XM OEM CPU.

    The BSOD contained this error message: A clock interrupt was not received on a secondary processor within an allocated time

    What could be the cause of it?
    Last edited by kevindd992002; 17 Sep 2010 at 08:59.
      My Computer


  2. Posts : 17,796
    Windows 10, Home Clean Install
       #2

    Post the Mini Dump and you will be helped.

    https://www.sevenforums.com/crashes-d...tructions.html
      My Computer


  3. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #3

    I have a Clevo W860CU Laptop with these specs:

    NVIDIA GeForce GTX285M Vidcard
    i7 920XM OEM CPU
    4GB Kingston HyperX Memory 1333 MHz
    500GB Hitachi 7200RPM HDD
    LG Hitachi GBW-T10N Blu-Ray Combo Drive
    Intel 6300AGN WiF Mini PCI-E WiFi Card
    Realtek 1Gbps LAN Ethernet Mini PCI-E Card
    Sentelic Touchpad

    Is Windows 7 . . .
    - x86 (32-bit) or x64 ? x64
    - the original installed OS on the system? Yes
    - an OEM or full retail version? OEM
    - OEM = came pre-installed on system
    - Full Retail = you purchased it from retailer

    - What is the age of system (hardware)? The hardware is around 1 month old and I just reinstalled Windows 7 3 days ago with the latest drivers but I sticked with Nvidia version 186.81 drivers since I know they are so much stable.
    - What is the age of OS installation (have you re-installed the OS?) 3 days

    Attached is the necessary zip file. Thanks for the help.
      My Computer


  4. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #4

    bump!
      My Computer


  5. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #5

    Here's another instance of my problem, I attached the files needed. Please help me
      My Computer


  6. Posts : 17,796
    Windows 10, Home Clean Install
       #6

    Sorry that so much time has gone by without an answer. The probable reason is that no one has a definitive answer for you. You show BC 101, which is inconclusive.
    Here is our classic answer for the particular BC
    STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_crash[1].zip\Windows7_BSOD_jcgriff2\082910-20233-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50
    Debug session time: Sun Aug 29 11:19:48.909 2010 (GMT-4)
    System Uptime: 0 days 9:59:24.986
    Loading Kernel Symbols
    ................................................
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 101, {19, 0, fffff880032a3180, 5}
    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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff880032a3180, The PRCB address of the hung processor.
    Arg4: 0000000000000005, 0.
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  d
    STACK_TEXT:  
    fffff800`04211a28 fffff800`02c33453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`032a3180 : nt!KeBugCheckEx
    fffff800`04211a30 fffff800`02c8dde7 : 00000000`00000000 fffff800`00000005 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe
    fffff800`04211ac0 fffff800`031fb895 : fffff800`03220460 fffff800`04211c70 fffff800`03220460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
    fffff800`04211bc0 fffff800`02c81c33 : fffffa80`04a09c00 fffffa80`0730e001 fffff800`02e03580 00000000`00000002 : hal!HalpHpetClockInterrupt+0x8d
    fffff800`04211bf0 fffff800`02c8dec2 : fffff800`02dffe80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
    fffff800`04211d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32
    
    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_8_PROC_ANALYSIS_INCONCLUSIVE
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    Followup: MachineOwner
    ---------
      My Computer


  7. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #7

    Does that mean my video card driver can cause this BSOD problem?
      My Computer


  8. Posts : 17,796
    Windows 10, Home Clean Install
       #8

    Yes, that can be a possible cause. Those posts give a lot of suggestions and tests. You can start with them to elimiante other causes, before you spend money on a new card.
      My Computer


  9. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #9

    Hmm. I'm not sure where to start first because I already have all updated drivers including the BIOS. But I may have to take time read those posts.

    Thanks.
      My Computer


  10. Posts : 17,796
    Windows 10, Home Clean Install
       #10

    Take your time. Tell us what test you want to take next and we will give you any information about the correct way that the test should be given.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 23:16.
Find Us