Page 2 of 3 First 123 Last
  1. #21

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Forgive if this shows my ignorance, but since those commands were done from 0: isn't that looking at processor 0 which was not the hung processor based on the prcb?


    • Ad Bot

      advertising
      Beep.

        
       

  2. #22
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    14,525

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    I would recommend Comodo removal and Broadcom driver update -

    Broadcom - http://www.sysnative.com/drivers/driver.php?id=k57nd60a.sys

    Comodo Internet Security removal - Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015

  3. #23
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    14,525

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    phylock.sys showed up on the stack in the last full kernel dump -

    Code:
    0: kd> lmvm phylock
    start             end                 module name
    fffff880`01123000 fffff880`0112f000   phylock    (no symbols)           
        Loaded symbol image file: phylock.sys
        Image path: \SystemRoot\system32\drivers\phylock.sys
        Image name: phylock.sys
        Timestamp:        Mon Oct 15 00:33:46 2012 (507B922A)
        CheckSum:         0000EE65
        ImageSize:        0000C000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    It comes back to TeraByte Inc.

    Do you have any of their products installed?

    http://www.terabyteunlimited.com/index.htm

    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\a1\AppData\Local\Temp\Temp1_MEMORY 2013-08-22.zip\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    
    Symbol search path is: SRV*C:\symbols*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.18205.amd64fre.win7sp1_gdr.130708-1532
    Machine Name:
    Kernel base = 0xfffff800`0341a000 PsLoadedModuleList = 0xfffff800`0365d6d0
    Debug session time: Thu Aug 22 03:04:00.257 2013 (UTC - 4:00)
    System Uptime: 0 days 2:38:41.459
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 000007ff`fffda018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    .............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 101, {31, 0, fffff88002f65180, 2}
    
    *** ERROR: Module load completed but symbols could not be loaded for phylock.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: fffff88002f65180, The PRCB address of the hung processor.
    Arg4: 0000000000000002, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  imagew64.exe
    
    CURRENT_IRQL:  d
    
    TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0
    
    STACK_TEXT:  
    fffff800`00ba2088 fffff800`034e6a3a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f65180 : nt!KeBugCheckEx
    fffff800`00ba2090 fffff800`034996f7 : 00000000`00000000 fffff800`00000002 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
    fffff800`00ba2120 fffff800`03a0a895 : fffff800`03a30460 fffff800`00ba22d0 fffff800`03a30460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
    fffff800`00ba2220 fffff800`0348c0d3 : 00000000`19f377ab fffff800`00ba22d0 fffff800`0360ae80 00000000`00000002 : hal!HalpHpetClockInterrupt+0x8d
    fffff800`00ba2250 fffff800`0349ea22 : fffff800`0360ae80 00000000`00000001 00000000`00000000 fffff980`4790efc0 : nt!KiInterruptDispatchNoLock+0x163
    fffff800`00ba23e0 fffff800`0353ec26 : 00000000`00000000 fffff800`0360ae80 fffff980`4790efc0 fffff800`034ba83b : nt!KiIpiSendRequestEx+0xb2
    fffff800`00ba2420 fffff800`03597a69 : 00000000`00000001 fffff800`00ba24e0 fffff6fc`c023c870 fffff980`4790efc0 : nt!KeFlushSingleTb+0x126
    fffff800`00ba24a0 fffff800`035c293b : fffff800`0341a000 00000000`5043524c ffffffff`ff849840 00000000`00000000 : nt!MmFreeSpecialPool+0x349
    fffff800`00ba25f0 fffff800`03937a3b : fffff980`4790efc0 00000000`00000000 fffffa80`0b50c1f0 ffffdb54`67526480 : nt!ExDeferredFreePool+0xf33
    fffff800`00ba26a0 fffff880`01125af6 : 00000000`00000034 00000000`00000000 fffff980`4790efc0 fffff980`4790efc0 : nt!VerifierExFreePool+0x1b
    fffff800`00ba26d0 fffff880`01125ebd : fffffa80`08731c10 00000000`00000000 fffff980`4790efc0 fffffa80`0b50c2f8 : phylock+0x2af6
    fffff800`00ba2700 fffff800`034935d1 : fffffa80`0883a853 fffff800`0349522a fffff880`02f65100 fffffa80`0a84bb02 : phylock+0x2ebd
    fffff800`00ba2780 fffff800`039332af : fffffa80`0883a6f0 00000000`ffffff01 fffffa80`08733001 00000000`00000000 : nt!IopfCompleteRequest+0x341
    fffff800`00ba2870 fffff880`010f4bce : 00000000`00000000 00000000`00000002 00000000`00000002 fffffa80`08733010 : nt!IovCompleteRequest+0x19f
    fffff800`00ba2940 fffff800`034935d1 : 00000000`00000000 fffffa80`0a933108 fffffa80`0a933108 fffff880`04210127 : CLASSPNP!TransferPktComplete+0x1ce
    fffff800`00ba29c0 fffff800`039332af : fffffa80`0822cb10 fffffa80`08262101 fffffa80`08262101 00000000`00000000 : nt!IopfCompleteRequest+0x341
    fffff800`00ba2ab0 fffff880`0114141a : fffffa80`0922c5c0 00000000`00000000 00000000`00000000 fffffa80`082621b0 : nt!IovCompleteRequest+0x19f
    fffff800`00ba2b80 fffff880`01141242 : fffffa80`08784010 fffffa80`09107ba8 fffffa80`0922c502 fffffa80`09107410 : ataport!IdeCompleteScsiIrp+0x62
    fffff800`00ba2bb0 fffff880`0113be32 : 00000000`00000002 00000000`00000000 00000000`00000000 000f8142`000f8141 : ataport!IdeCommonCrbCompletion+0x5a
    fffff800`00ba2be0 fffff880`01144805 : fffffa80`081fc1a0 fffffa80`08784010 00000000`00000000 fffffa80`08d7e5d0 : ataport!IdeTranslateCompletedRequest+0x236
    fffff800`00ba2d10 fffff880`01144104 : fffffa80`081fc1a0 00000000`00000000 fffffa80`081fc1a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
    fffff800`00ba2e40 fffff800`0349a30c : fffff800`0360ae80 fffffa80`00094e02 fffffa80`081fc050 fffffa80`081fc118 : ataport!IdePortCompletionDpc+0x1a8
    fffff800`00ba2f00 fffff800`03492d15 : 00000000`00000000 fffffa80`08785360 00000000`00000000 fffff880`01143f5c : nt!KiRetireDpcList+0x1bc
    fffff800`00ba2fb0 fffff800`03492b2c : fffff880`07ec6b60 00000000`00000014 00000000`00000001 00000001`00000000 : nt!KxRetireDpcList+0x5
    fffff880`07ec6aa0 fffff800`034dab53 : fffff800`0348b5c3 fffff800`0348b62f fffffa80`08785360 fffffa80`0b22f7c0 : nt!KiDispatchInterruptContinue
    fffff880`07ec6ad0 fffff800`0348b62f : fffffa80`08785360 fffffa80`0b22f7c0 00000000`00000000 fffffa80`087dc4f0 : nt!KiDpcInterruptBypass+0x13
    fffff880`07ec6ae0 00000001`4008a6d2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0x19f
    00000000`058cfa10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`4008a6d2
    
    
    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_VRF_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm phylock
    start             end                 module name
    fffff880`01123000 fffff880`0112f000   phylock    (no symbols)           
        Loaded symbol image file: phylock.sys
        Image path: \SystemRoot\system32\drivers\phylock.sys
        Image name: phylock.sys
        Timestamp:        Mon Oct 15 00:33:46 2012 (507B922A)
        CheckSum:         0000EE65
        ImageSize:        0000C000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0: kd> lmnt
    start             end                 module name
    fffff800`00bac000 fffff800`00bb6000   kdcom    kdcom.dll    Sat Feb 05 11:52:49 2011 (4D4D8061)
    fffff800`0341a000 fffff800`03a00000   nt       ntkrnlmp.exe Mon Jul 08 23:15:54 2013 (51DB806A)
    fffff800`03a00000 fffff800`03a49000   hal      hal.dll      Sat Nov 20 08:00:25 2010 (4CE7C669)
    fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Sat Nov 20 08:12:36 2010 (4CE7C944)
    fffff880`00cec000 fffff880`00d3b000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Nov 20 08:03:51 2010 (4CE7C737)
    fffff880`00d3b000 fffff880`00d4f000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
    fffff880`00d4f000 fffff880`00dad000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`00dad000 fffff880`00df9000   fltmgr   fltmgr.sys   Sat Nov 20 04:19:24 2010 (4CE7929C)
    fffff880`00e00000 fffff880`00e15000   partmgr  partmgr.sys  Sat Mar 17 01:06:09 2012 (4F641BC1)
    fffff880`00e15000 fffff880`00e1e000   compbatt compbatt.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6)
    fffff880`00e1e000 fffff880`00e2a000   BATTC    BATTC.SYS    Mon Jul 13 19:31:01 2009 (4A5BC3B5)
    fffff880`00e2a000 fffff880`00e3f000   volmgr   volmgr.sys   Sat Nov 20 04:19:28 2010 (4CE792A0)
    fffff880`00e75000 fffff880`00f37000   Wdf01000 Wdf01000.sys Wed Jul 25 22:25:13 2012 (5010AA89)
    fffff880`00f37000 fffff880`00f47000   WDFLDR   WDFLDR.SYS   Wed Jul 25 22:29:04 2012 (5010AB70)
    fffff880`00f47000 fffff880`00f9e000   ACPI     ACPI.sys     Sat Nov 20 04:19:16 2010 (4CE79294)
    fffff880`00f9e000 fffff880`00fa7000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`00fa7000 fffff880`00fb1000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
    fffff880`00fb1000 fffff880`00fbe000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
    fffff880`00fbe000 fffff880`00ff1000   pci      pci.sys      Sat Nov 20 04:19:11 2010 (4CE7928F)
    fffff880`01000000 fffff880`0100b000   amdxata  amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
    fffff880`0100b000 fffff880`01036000   nvstor   nvstor.sys   Fri Mar 19 16:45:11 2010 (4BA3E257)
    fffff880`01036000 fffff880`0104a000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
    fffff880`01055000 fffff880`010b1000   volmgrx  volmgrx.sys  Sat Nov 20 04:20:43 2010 (4CE792EB)
    fffff880`010b1000 fffff880`010cb000   mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299)
    fffff880`010cb000 fffff880`010f3000   nvraid   nvraid.sys   Fri Mar 19 16:59:20 2010 (4BA3E5A8)
    fffff880`010f3000 fffff880`01123000   CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B)
    fffff880`01123000 fffff880`0112f000   phylock  phylock.sys  Mon Oct 15 00:33:46 2012 (507B922A)
    fffff880`0112f000 fffff880`01138000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`01138000 fffff880`01162000   ataport  ataport.SYS  Sat Nov 20 04:19:15 2010 (4CE79293)
    fffff880`01162000 fffff880`0116d000   msahci   msahci.sys   Sat Nov 20 05:33:58 2010 (4CE7A416)
    fffff880`0116d000 fffff880`0117d000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`0117d000 fffff880`0119b000   amdsata  amdsata.sys  Thu Mar 18 20:45:17 2010 (4BA2C91D)
    fffff880`0119b000 fffff880`011fe000   storport storport.sys Thu Mar 10 23:30:23 2011 (4D79A55F)
    fffff880`01213000 fffff880`0121c000   cmderd   cmderd.sys   Wed Nov 07 17:06:57 2012 (509ADB81)
    fffff880`0121c000 fffff880`01246000   cdrom    cdrom.sys    Sat Nov 20 04:19:20 2010 (4CE79298)
    fffff880`0124a000 fffff880`013ec000   Ntfs     Ntfs.sys     Fri Apr 12 07:54:36 2013 (5167F5FC)
    fffff880`01408000 fffff880`01466000   msrpc    msrpc.sys    Sat Nov 20 04:21:56 2010 (4CE79334)
    fffff880`01466000 fffff880`01481000   ksecdd   ksecdd.sys   Fri Jun 01 22:50:23 2012 (4FC97F6F)
    fffff880`01481000 fffff880`014f3000   cng      cng.sys      Fri Aug 24 11:47:16 2012 (5037A204)
    fffff880`014f3000 fffff880`01504000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
    fffff880`01504000 fffff880`0150e000   Fs_Rec   Fs_Rec.sys   Wed Feb 29 22:41:06 2012 (4F4EEFD2)
    fffff880`0150e000 fffff880`01600000   ndis     ndis.sys     Wed Aug 22 11:11:46 2012 (5034F6B2)
    fffff880`01600000 fffff880`0163a000   rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E)
    fffff880`0163a000 fffff880`0164c000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
    fffff880`0164c000 fffff880`01655000   hwpolicy hwpolicy.sys Sat Nov 20 04:18:54 2010 (4CE7927E)
    fffff880`01655000 fffff880`0168f000   fvevol   fvevol.sys   Wed Jan 23 22:11:24 2013 (5100A65C)
    fffff880`0168f000 fffff880`016a5000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`016c3000 fffff880`01723000   NETIO    NETIO.SYS    Wed Aug 22 11:11:28 2012 (5034F6A0)
    fffff880`01723000 fffff880`0174e000   ksecpkg  ksecpkg.sys  Fri Aug 24 11:48:29 2012 (5037A24D)
    fffff880`0174e000 fffff880`01797000   fwpkclnt fwpkclnt.sys Wed Jan 02 22:06:48 2013 (50E4F5C8)
    fffff880`01797000 fffff880`017a7000   vmstorfl vmstorfl.sys Sat Nov 20 04:57:30 2010 (4CE79B8A)
    fffff880`017a7000 fffff880`017f3000   volsnap  volsnap.sys  Sat Nov 20 04:20:08 2010 (4CE792C8)
    fffff880`017f3000 fffff880`017fb000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
    fffff880`01800000 fffff880`01a00000   tcpip    tcpip.sys    Fri Jul 05 23:12:44 2013 (51D78B2C)
    fffff880`02c00000 fffff880`02c0c000   cmdhlp   cmdhlp.sys   Wed Nov 07 17:07:03 2012 (509ADB87)
    fffff880`02c0c000 fffff880`02c95000   afd      afd.sys      Tue Dec 27 22:59:20 2011 (4EFA9418)
    fffff880`02cae000 fffff880`02d41000   cmdguard cmdguard.sys Wed Nov 07 17:07:39 2012 (509ADBAB)
    fffff880`02d41000 fffff880`02d4a000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
    fffff880`02d4a000 fffff880`02d51000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
    fffff880`02d51000 fffff880`02d5f000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
    fffff880`02d5f000 fffff880`02d84000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
    fffff880`02d84000 fffff880`02d94000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
    fffff880`02d94000 fffff880`02d9d000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`02d9d000 fffff880`02da6000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`02da6000 fffff880`02daf000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
    fffff880`02daf000 fffff880`02dba000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`02dba000 fffff880`02dcb000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`02dcb000 fffff880`02ded000   tdx      tdx.sys      Sat Nov 20 04:21:54 2010 (4CE79332)
    fffff880`02ded000 fffff880`02dfa000   TDI      TDI.SYS      Sat Nov 20 04:22:06 2010 (4CE7933E)
    fffff880`03e00000 fffff880`03e2f000   SCSIPORT SCSIPORT.SYS Sat Nov 20 05:34:01 2010 (4CE7A419)
    fffff880`03e6a000 fffff880`03eaf000   netbt    netbt.sys    Sat Nov 20 04:23:18 2010 (4CE79386)
    fffff880`03eaf000 fffff880`03eb8000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff880`03eb8000 fffff880`03ede000   pacer    pacer.sys    Sat Nov 20 05:52:18 2010 (4CE7A862)
    fffff880`03ede000 fffff880`03ef8000   inspect  inspect.sys  Wed Nov 07 17:07:02 2012 (509ADB86)
    fffff880`03ef8000 fffff880`03f07000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff880`03f07000 fffff880`03f24000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
    fffff880`03f24000 fffff880`03f3f000   wanarp   wanarp.sys   Sat Nov 20 05:52:36 2010 (4CE7A874)
    fffff880`03f3f000 fffff880`03f53000   termdd   termdd.sys   Sat Nov 20 06:03:40 2010 (4CE7AB0C)
    fffff880`03f53000 fffff880`03fa4000   rdbss    rdbss.sys    Sat Nov 20 04:27:51 2010 (4CE79497)
    fffff880`03fa4000 fffff880`03fb0000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
    fffff880`03fb0000 fffff880`03fbb000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
    fffff880`03fbb000 fffff880`03fc7000   ElbyCDIO ElbyCDIO.sys Thu Dec 16 17:58:13 2010 (4D0A9985)
    fffff880`03fc7000 fffff880`03fd6000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
    fffff880`04000000 fffff880`0402f000   ndiswan  ndiswan.sys  Sat Nov 20 05:52:32 2010 (4CE7A870)
    fffff880`0402f000 fffff880`0404a000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
    fffff880`0404a000 fffff880`0406b000   raspptp  raspptp.sys  Sat Nov 20 05:52:31 2010 (4CE7A86F)
    fffff880`0406b000 fffff880`04085000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
    fffff880`04085000 fffff880`04090000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
    fffff880`04090000 fffff880`0409f000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`0409f000 fffff880`040ae000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`040ae000 fffff880`040bd000   VClone   VClone.sys   Sat Jan 15 11:21:04 2011 (4D31C970)
    fffff880`040dc000 fffff880`0415f000   csc      csc.sys      Sat Nov 20 04:27:12 2010 (4CE79470)
    fffff880`0415f000 fffff880`0417d000   dfsc     dfsc.sys     Sat Nov 20 04:26:31 2010 (4CE79447)
    fffff880`0417d000 fffff880`0418e000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
    fffff880`0418e000 fffff880`041b4000   tunnel   tunnel.sys   Sat Nov 20 05:51:50 2010 (4CE7A846)
    fffff880`041b4000 fffff880`041c4000   CompositeBus CompositeBus.sys Sat Nov 20 05:33:17 2010 (4CE7A3ED)
    fffff880`041c4000 fffff880`041da000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
    fffff880`041da000 fffff880`041fe000   rasl2tp  rasl2tp.sys  Sat Nov 20 05:52:34 2010 (4CE7A872)
    fffff880`04200000 fffff880`04246000   dxgmms1  dxgmms1.sys  Tue Apr 09 23:27:15 2013 (5164DC13)
    fffff880`04246000 fffff880`04257000   HECIx64  HECIx64.sys  Tue Oct 19 19:33:43 2010 (4CBE2AD7)
    fffff880`04257000 fffff880`04268000   usbehci  usbehci.sys  Thu Mar 24 23:29:04 2011 (4D8C0C00)
    fffff880`04268000 fffff880`042be000   USBPORT  USBPORT.SYS  Thu Mar 24 23:29:12 2011 (4D8C0C08)
    fffff880`042be000 fffff880`042e2000   HDAudBus HDAudBus.sys Sat Nov 20 05:43:42 2010 (4CE7A65E)
    fffff880`042e2000 fffff880`042e8c00   GEARAspiWDM GEARAspiWDM.sys Thu May 03 15:56:17 2012 (4FA2E2E1)
    fffff880`042e9000 fffff880`042ea480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
    fffff880`042eb000 fffff880`043df000   dxgkrnl  dxgkrnl.sys  Tue Apr 09 23:28:09 2013 (5164DC49)
    fffff880`043df000 fffff880`043eec00   EtronXHCI EtronXHCI.sys Fri Jan 28 16:46:43 2011 (4D433943)
    fffff880`043ef000 fffff880`043fc000   fdc      fdc.sys      Mon Jul 13 20:00:54 2009 (4A5BCAB6)
    fffff880`04600000 fffff880`04624000   mrxsmb20 mrxsmb20.sys Tue Apr 26 22:39:37 2011 (4DB781E9)
    fffff880`04624000 fffff880`0463b000   LEqdUsb  LEqdUsb.Sys  Wed Jun 17 12:49:54 2009 (4A391EB2)
    fffff880`04649000 fffff880`04656000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
    fffff880`04656000 fffff880`0465e000   LHidEqd  LHidEqd.Sys  Wed Jun 17 12:49:56 2009 (4A391EB4)
    fffff880`0465f000 fffff880`04728000   HTTP     HTTP.sys     Sat Nov 20 04:24:30 2010 (4CE793CE)
    fffff880`04728000 fffff880`04743000   USBSTOR  USBSTOR.SYS  Thu Mar 10 23:37:16 2011 (4D79A6FC)
    fffff880`04743000 fffff880`04761000   bowser   bowser.sys   Tue Feb 22 23:55:04 2011 (4D649328)
    fffff880`04761000 fffff880`04779000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
    fffff880`04779000 fffff880`047a6000   mrxsmb   mrxsmb.sys   Tue Apr 26 22:40:38 2011 (4DB78226)
    fffff880`047a6000 fffff880`047f4000   mrxsmb10 mrxsmb10.sys Fri Jul 08 22:46:28 2011 (4E17C104)
    fffff880`047f4000 fffff880`047fd000   cpuz135_x64 cpuz135_x64.sys Tue Nov 09 08:33:36 2010 (4CD94DB0)
    fffff880`04800000 fffff880`0480c000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
    fffff880`0480c000 fffff880`04815000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
    fffff880`04815000 fffff880`0482b000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
    fffff880`0482b000 fffff880`04837000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
    fffff880`04837000 fffff880`04d521a0   igdkmd64 igdkmd64.sys Wed Dec 12 19:42:26 2012 (50C92472)
    fffff880`04d53000 fffff880`04d91000   1394ohci 1394ohci.sys Sat Nov 20 05:44:56 2010 (4CE7A6A8)
    fffff880`04d91000 fffff880`04df8000   k57nd60a k57nd60a.sys Mon Feb 14 23:19:05 2011 (4D59FEB9)
    fffff880`04e00000 fffff880`04e13000   LHidFilt LHidFilt.Sys Wed Jun 17 12:49:39 2009 (4A391EA3)
    fffff880`04e13000 fffff880`04e27000   LMouFilt LMouFilt.Sys Wed Jun 17 12:49:43 2009 (4A391EA7)
    fffff880`04e9e000 fffff880`04ee1000   ks       ks.sys       Sat Nov 20 05:33:23 2010 (4CE7A3F3)
    fffff880`04ee1000 fffff880`04ef3000   umbus    umbus.sys    Sat Nov 20 05:44:37 2010 (4CE7A695)
    fffff880`04ef3000 fffff880`04f03000   busenum  busenum.sys  Fri Aug 03 05:32:04 2012 (501B9A94)
    fffff880`04f03000 fffff880`04f04f00   USBD     USBD.SYS     Thu Mar 24 23:28:59 2011 (4D8C0BFB)
    fffff880`04f05000 fffff880`04f5f000   usbhub   usbhub.sys   Thu Mar 24 23:29:25 2011 (4D8C0C15)
    fffff880`04f5f000 fffff880`04f68c00   EtronHub3 EtronHub3.sys Fri Jan 28 16:46:45 2011 (4D433945)
    fffff880`04f69000 fffff880`04f7e000   NDProxy  NDProxy.SYS  Sat Nov 20 05:52:20 2010 (4CE7A864)
    fffff880`04f7e000 fffff880`04f86080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
    fffff880`04f87000 fffff880`04f9c000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`04f9c000 fffff880`04fb4000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`04fb4000 fffff880`04fd1000   usbccgp  usbccgp.sys  Thu Mar 24 23:29:14 2011 (4D8C0C0A)
    fffff880`04fd1000 fffff880`04fe2000   usbscan  usbscan.sys  Mon Jul 13 20:35:32 2009 (4A5BD2D4)
    fffff880`04fe2000 fffff880`04fee000   usbprint usbprint.sys Mon Jul 13 20:38:18 2009 (4A5BD37A)
    fffff880`05800000 fffff880`0580c000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
    fffff880`0580c000 fffff880`0581a000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
    fffff880`0581a000 fffff880`0583d000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
    fffff880`0583d000 fffff880`0585a000   cdfs     cdfs.sys     Mon Jul 13 19:19:46 2009 (4A5BC112)
    fffff880`0585a000 fffff880`05868000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
    fffff880`05868000 fffff880`05874000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`05874000 fffff880`0587f000   dump_msahci dump_msahci.sys Sat Nov 20 05:33:58 2010 (4CE7A416)
    fffff880`0587f000 fffff880`05892000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    fffff880`058a0000 fffff880`058b9000   HIDCLASS HIDCLASS.SYS Sat Nov 20 05:43:49 2010 (4CE7A665)
    fffff880`058bb000 fffff880`05b3fb80   RTKVHD64 RTKVHD64.sys Tue Nov 30 04:03:19 2010 (4CF4BDD7)
    fffff880`05b40000 fffff880`05b7d000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
    fffff880`05b7d000 fffff880`05b9f000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
    fffff880`05b9f000 fffff880`05ba4200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
    fffff880`05ba5000 fffff880`05bf8000   IntcDAud IntcDAud.sys Fri Oct 15 04:28:17 2010 (4CB810A1)
    fffff880`06451000 fffff880`064f7000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
    fffff880`064f7000 fffff880`06502000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
    fffff880`06502000 fffff880`06533000   srvnet   srvnet.sys   Thu Apr 28 23:05:35 2011 (4DBA2AFF)
    fffff880`06533000 fffff880`06545000   tcpipreg tcpipreg.sys Wed Oct 03 12:07:26 2012 (506C62BE)
    fffff880`06545000 fffff880`065ae000   srv2     srv2.sys     Thu Apr 28 23:05:46 2011 (4DBA2B0A)
    fffff880`07200000 fffff880`0720b000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
    fffff880`0721a000 fffff880`07228000   hidusb   hidusb.sys   Sat Nov 20 05:43:49 2010 (4CE7A665)
    fffff880`0722c000 fffff880`072c4000   srv      srv.sys      Thu Apr 28 23:06:06 2011 (4DBA2B1E)
    fffff880`072c4000 fffff880`072d0000   NuidFltr NuidFltr.sys Fri Dec 28 06:15:22 2012 (50DD7F4A)
    fffff880`072d0000 fffff880`072de000   kbdhid   kbdhid.sys   Sat Nov 20 05:33:25 2010 (4CE7A3F5)
    fffff880`072de000 fffff880`072ef000   point64  point64.sys  Fri Apr 12 08:15:29 2013 (5167FAE1)
    fffff880`072fa000 fffff880`07306000   npf      npf.sys      Fri Jun 25 12:50:58 2010 (4C24DE72)
    fffff880`07306000 fffff880`07334000   rdpdr    rdpdr.sys    Sat Nov 20 06:06:41 2010 (4CE7ABC1)
    fffff880`07334000 fffff880`0733f000   tdtcp    tdtcp.sys    Thu Feb 16 23:57:32 2012 (4F3DDE3C)
    fffff880`0733f000 fffff880`0734e000   tssecsrv tssecsrv.sys Sat Jun 15 00:32:15 2013 (51BBEE4F)
    fffff880`0734e000 fffff880`07387000   RDPWD    RDPWD.SYS    Fri Apr 27 23:55:20 2012 (4F9B6A28)
    fffff880`07387000 fffff880`073a0000   WudfPf   WudfPf.sys   Wed Jul 25 22:26:45 2012 (5010AAE5)
    fffff880`073a0000 fffff880`073d6000   WUDFRd   WUDFRd.sys   Wed Jul 25 22:26:06 2012 (5010AABE)
    fffff880`073d6000 fffff880`073ed000   dc3d     dc3d.sys     Fri Apr 12 08:15:46 2013 (5167FAF2)
    fffff880`073f4000 fffff880`073fe000   umpass   umpass.sys   Mon Jul 13 20:06:52 2009 (4A5BCC1C)
    fffff960`00060000 fffff960`00377000   win32k   win32k.sys   Tue Jun 04 23:33:59 2013 (51AEB1A7)
    fffff960`00520000 fffff960`0052a000   TSDDD    TSDDD.dll    Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff960`00770000 fffff960`00797000   cdd      cdd.dll      Thu Feb 03 06:25:25 2011 (4D4A90A5)
    fffff960`00990000 fffff960`009f1000   ATMFD    ATMFD.DLL    Sun Dec 16 09:45:03 2012 (50CDDE6F)
    
    Unloaded modules:
    fffff880`04e27000 fffff880`04e98000   spsys.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00071000
    fffff880`073ed000 fffff880`073f4000   magdrvamd64.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00007000
    fffff880`072ef000 fffff880`072f6000   magdrvamd64.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00007000
    fffff880`073ed000 fffff880`073fb000   hidusb.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`07200000 fffff880`0720e000   kbdhid.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`0720e000 fffff880`0721a000   NuidFltr.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000C000
    fffff880`05892000 fffff880`058a0000   hidusb.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`0463b000 fffff880`04649000   kbdhid.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`072c4000 fffff880`072fa000   WUDFRd.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00036000
    fffff880`016a5000 fffff880`016b3000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`016b3000 fffff880`016bf000   dump_pciidex.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000C000
    fffff880`013ec000 fffff880`013f7000   dump_msahci.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000B000
    fffff880`01200000 fffff880`01213000   dump_dumpfve.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00013000

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015

  4. #24
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    14,525

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    STACK_TEXT:

    Apologies for another post, but the 161 MB download just completed (SLOW Verizon DSL here!).

    Quote Originally Posted by rockstream View Post
    Forgive if this shows my ignorance, but since those commands were done from 0: isn't that looking at processor 0 which was not the hung processor based on the prcb?
    Here are the stacks from the processors:

    proc 0
    Code:
    0: kd> !analyze -v
    
    BugCheck 101, {31, 0, fffff88002f65180, 2}
    
    *** ERROR: Module load completed but symbols could not be loaded for phylock.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: fffff88002f65180, The PRCB address of the hung processor.
    Arg4: 0000000000000002, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  imagew64.exe
    
    CURRENT_IRQL:  d
    
    TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0
    
    STACK_TEXT:  
    fffff800`00ba2088 fffff800`034e6a3a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f65180 : nt!KeBugCheckEx
    fffff800`00ba2090 fffff800`034996f7 : 00000000`00000000 fffff800`00000002 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
    fffff800`00ba2120 fffff800`03a0a895 : fffff800`03a30460 fffff800`00ba22d0 fffff800`03a30460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
    fffff800`00ba2220 fffff800`0348c0d3 : 00000000`19f377ab fffff800`00ba22d0 fffff800`0360ae80 00000000`00000002 : hal!HalpHpetClockInterrupt+0x8d
    fffff800`00ba2250 fffff800`0349ea22 : fffff800`0360ae80 00000000`00000001 00000000`00000000 fffff980`4790efc0 : nt!KiInterruptDispatchNoLock+0x163
    fffff800`00ba23e0 fffff800`0353ec26 : 00000000`00000000 fffff800`0360ae80 fffff980`4790efc0 fffff800`034ba83b : nt!KiIpiSendRequestEx+0xb2
    fffff800`00ba2420 fffff800`03597a69 : 00000000`00000001 fffff800`00ba24e0 fffff6fc`c023c870 fffff980`4790efc0 : nt!KeFlushSingleTb+0x126
    fffff800`00ba24a0 fffff800`035c293b : fffff800`0341a000 00000000`5043524c ffffffff`ff849840 00000000`00000000 : nt!MmFreeSpecialPool+0x349
    fffff800`00ba25f0 fffff800`03937a3b : fffff980`4790efc0 00000000`00000000 fffffa80`0b50c1f0 ffffdb54`67526480 : nt!ExDeferredFreePool+0xf33
    fffff800`00ba26a0 fffff880`01125af6 : 00000000`00000034 00000000`00000000 fffff980`4790efc0 fffff980`4790efc0 : nt!VerifierExFreePool+0x1b
    fffff800`00ba26d0 fffff880`01125ebd : fffffa80`08731c10 00000000`00000000 fffff980`4790efc0 fffffa80`0b50c2f8 : phylock+0x2af6
    fffff800`00ba2700 fffff800`034935d1 : fffffa80`0883a853 fffff800`0349522a fffff880`02f65100 fffffa80`0a84bb02 : phylock+0x2ebd
    fffff800`00ba2780 fffff800`039332af : fffffa80`0883a6f0 00000000`ffffff01 fffffa80`08733001 00000000`00000000 : nt!IopfCompleteRequest+0x341
    fffff800`00ba2870 fffff880`010f4bce : 00000000`00000000 00000000`00000002 00000000`00000002 fffffa80`08733010 : nt!IovCompleteRequest+0x19f
    fffff800`00ba2940 fffff800`034935d1 : 00000000`00000000 fffffa80`0a933108 fffffa80`0a933108 fffff880`04210127 : CLASSPNP!TransferPktComplete+0x1ce
    fffff800`00ba29c0 fffff800`039332af : fffffa80`0822cb10 fffffa80`08262101 fffffa80`08262101 00000000`00000000 : nt!IopfCompleteRequest+0x341
    fffff800`00ba2ab0 fffff880`0114141a : fffffa80`0922c5c0 00000000`00000000 00000000`00000000 fffffa80`082621b0 : nt!IovCompleteRequest+0x19f
    fffff800`00ba2b80 fffff880`01141242 : fffffa80`08784010 fffffa80`09107ba8 fffffa80`0922c502 fffffa80`09107410 : ataport!IdeCompleteScsiIrp+0x62
    fffff800`00ba2bb0 fffff880`0113be32 : 00000000`00000002 00000000`00000000 00000000`00000000 000f8142`000f8141 : ataport!IdeCommonCrbCompletion+0x5a
    fffff800`00ba2be0 fffff880`01144805 : fffffa80`081fc1a0 fffffa80`08784010 00000000`00000000 fffffa80`08d7e5d0 : ataport!IdeTranslateCompletedRequest+0x236
    fffff800`00ba2d10 fffff880`01144104 : fffffa80`081fc1a0 00000000`00000000 fffffa80`081fc1a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
    fffff800`00ba2e40 fffff800`0349a30c : fffff800`0360ae80 fffffa80`00094e02 fffffa80`081fc050 fffffa80`081fc118 : ataport!IdePortCompletionDpc+0x1a8
    fffff800`00ba2f00 fffff800`03492d15 : 00000000`00000000 fffffa80`08785360 00000000`00000000 fffff880`01143f5c : nt!KiRetireDpcList+0x1bc
    fffff800`00ba2fb0 fffff800`03492b2c : fffff880`07ec6b60 00000000`00000014 00000000`00000001 00000001`00000000 : nt!KxRetireDpcList+0x5
    fffff880`07ec6aa0 fffff800`034dab53 : fffff800`0348b5c3 fffff800`0348b62f fffffa80`08785360 fffffa80`0b22f7c0 : nt!KiDispatchInterruptContinue
    fffff880`07ec6ad0 fffff800`0348b62f : fffffa80`08785360 fffffa80`0b22f7c0 00000000`00000000 fffffa80`087dc4f0 : nt!KiDpcInterruptBypass+0x13
    fffff880`07ec6ae0 00000001`4008a6d2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0x19f
    00000000`058cfa10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`4008a6d2
    
    
    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_VRF_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm phylock
    start             end                 module name
    fffff880`01123000 fffff880`0112f000   phylock    (no symbols)           
        Loaded symbol image file: phylock.sys
        Image path: \SystemRoot\system32\drivers\phylock.sys
        Image name: phylock.sys
        Timestamp:        Mon Oct 15 00:33:46 2012 (507B922A)
        CheckSum:         0000EE65
        ImageSize:        0000C000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    proc 1
    Microsoft OS drivers fltmgr.sys & ntfs.sys listed on the stack - (BSOD cause may be HDD/SSD related...?) -
    Code:
    0: kd> ~1
    1: 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: fffff88002f65180, The PRCB address of the hung processor.
    Arg4: 0000000000000002, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  mysqld-nt.exe
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`02865090 fffff800`03494a1c : 00000000`00000000 fffff880`028651f8 00000000`00000000 fffff800`0349ee8c : nt!KxFlushEntireTb+0x7f
    fffff880`028650d0 fffff800`034a6a66 : 00000000`00000004 00000000`00000000 fffff6fc`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x28c
    fffff880`028651a0 fffff800`034a6ce2 : fffffa80`078dbe40 fffff980`57fc003f 00000000`00000000 00000000`00000000 : nt!MiObtainSystemCacheView+0x352
    fffff880`028652e0 fffff800`034a6027 : fffff8a0`1225f180 fffff880`009eb830 fffff880`02865488 fffff880`028654a8 : nt!MmMapViewInSystemCache+0xc2
    fffff880`02865450 fffff800`034a4f8f : fffff980`00000000 00000000`2cfe3e6c 00000000`2b870000 00000000`00000000 : nt!CcGetVacbMiss+0x177
    fffff880`02865510 fffff800`0377a9e2 : 00000000`00000000 00000000`2cfe3e6c fffff880`028655e0 fffff880`02865670 : nt!CcGetVirtualAddress+0x2e0
    fffff880`028655a0 fffff880`012e2dbf : fffff880`00000000 00000000`00000005 fffffa80`08779140 fffffa80`00000001 : nt!CcCopyRead+0x132
    fffff880`02865660 fffff880`00dae098 : fffffa80`09773800 fffffa80`087790d8 00000000`00000000 fffffa80`09773801 : Ntfs!NtfsCopyReadA+0x18f
    fffff880`02865840 fffff880`00db18ba : fffff880`02865910 00000000`0df4db03 00000000`0df4db00 fffffa80`09773800 : fltmgr!FltpPerformFastIoCall+0x88
    fffff880`028658a0 fffff880`00dcf630 : fffffa80`09773800 00000000`00000000 fffff880`02865a00 00000000`00000014 : fltmgr!FltpPassThroughFastIo+0xda
    fffff880`028658e0 fffff800`0377a569 : fffffa80`09773800 fffffa80`00000001 fffffa80`06d4f8a0 fffffa80`09773800 : fltmgr!FltpFastIoRead+0x1d0
    fffff880`02865980 fffff800`0348ee13 : 00000000`0002053c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x417
    fffff880`02865a70 00000000`76f4131a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0df4d968 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f4131a
    
    
    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_VRF_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE
    
    Followup: MachineOwner
    ---------


    proc 2 shows a zero stack -
    Code:
    1: kd> ~2
     2: 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: fffff88002f65180, The PRCB address of the hung processor.
    Arg4: 0000000000000002, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    BUCKET_ID:  ZEROED_STACK
    
    Followup: MachineOwner
    ---------

    proc 3
    inspect.sys (COMODO Firewall) appears on the stack -
    Code:
    2: kd> ~3
    3: 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: fffff88002f65180, The PRCB address of the hung processor.
    Arg4: 0000000000000002, 0.
    
    Debugging Details:
    ------------------
    
    *** ERROR: Module load completed but symbols could not be loaded for inspect.sys
    Page 1e21a5 not present in the dump file. Type ".hh dbgerr004" for details
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  imagew64.exe
    
    CURRENT_IRQL:  0
    
    TAG_NOT_DEFINED_c000000f:  FFFFF880009B0FB0
    
    STACK_TEXT:  
    fffff880`009af9e0 fffff800`0353ec26 : 00000000`00000000 fffff880`02fd7180 fffff980`47982ed0 fffff800`034ba83b : nt!KiIpiSendRequestEx+0xb2
    fffff880`009afa20 fffff800`03597a69 : 00000000`00000001 fffff880`009afae0 fffff6fc`c023cc10 fffff980`47982ed0 : nt!KeFlushSingleTb+0x126
    fffff880`009afaa0 fffff800`035c293b : 00000000`000003f8 00000000`31716552 00000000`00001fb0 fffff980`1d4b0f80 : nt!MmFreeSpecialPool+0x349
    fffff880`009afbf0 fffff800`03937a3b : fffff980`47982ed0 fffff980`1d4b0f80 fffff980`1f02ce10 00000000`00000000 : nt!ExDeferredFreePool+0xf33
    fffff880`009afca0 fffff880`03ee762c : fffff980`47982ed0 00000000`00000000 00000000`558c9400 fffffa80`08d1e148 : nt!VerifierExFreePool+0x1b
    fffff880`009afcd0 fffff880`03ee8f3c : fffff980`47982ed0 00000000`00000000 fffff980`1b017d4a fffff980`1f02a8c0 : inspect+0x962c
    fffff880`009afd00 fffff880`03ee9736 : fffff980`47982ed0 fffff980`1f02ce10 00000000`00000000 fffff980`47982ed0 : inspect+0xaf3c
    fffff880`009afd40 fffff880`03edf9b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : inspect+0xb736
    fffff880`009afd80 fffff880`015104d4 : fffff980`1d4b0f80 fffff980`479a2d30 fffff880`00000000 fffff880`009afc48 : inspect+0x19b4
    fffff880`009afdf0 fffff880`03eb9199 : 00000000`00000000 fffffa80`08dfb1a0 00000000`00000000 fffffa80`08855060 : ndis!NdisFSendNetBufferLists+0x64
    fffff880`009afe30 fffff880`01510419 : fffff880`009afeb0 fffff880`009afd78 00000000`00000000 fffff880`009b0720 : pacer!PcFilterSendNetBufferLists+0x29
    fffff880`009aff30 fffff880`015cc5d5 : 00000000`00000600 00000000`00000000 fffffa80`08dfb1a0 fffff880`018859e6 : ndis!ndisSendNBLToFilter+0x69
    fffff880`009aff90 fffff880`0185d35e : 00000000`00000000 00000000`0000000e fffffa80`09056ba0 00000000`00000000 : ndis!NdisSendNetBufferLists+0x85
    fffff880`009afff0 fffff880`0185af57 : fffff880`0196e9a0 00000000`00000000 fffffa80`091a0000 fffff980`01960800 : tcpip!IppFragmentPackets+0x39e
    fffff880`009b0110 fffff880`0185c985 : 00000000`00000000 00000000`00000000 fffffa80`091a9080 fffffa80`08577cec : tcpip!IppDispatchSendPacketHelper+0x87
    fffff880`009b01d0 fffff880`0185bc0e : fffffa80`08577c06 fffff880`009b0500 00000000`00000014 fffffa80`00000000 : tcpip!IppPacketizeDatagrams+0x2d5
    fffff880`009b02f0 fffff880`0185e52e : 00000000`00000000 fffff880`01903207 fffffa80`0797f010 fffffa80`07a6f010 : tcpip!IppSendDatagramsCommon+0x87e
    fffff880`009b0490 fffff880`01932060 : fffffa80`0797f010 00000000`00000004 00000000`00000004 fffffa80`0797f010 : tcpip!IpNlpSendDatagrams+0x3e
    fffff880`009b04d0 fffff880`018bd2f6 : 00000000`00000000 fffff880`01885358 00000000`00000000 fffffa80`0797f010 : tcpip!TcpTcbKeepAliveSend+0x490
    fffff880`009b0640 fffff880`018859e6 : 00000000`00000000 00000000`00000000 00000000`00000e88 00000000`000e852d : tcpip! ?? ::FNODOBFM::`string'+0x3b86d
    fffff880`009b0720 fffff800`0349a85c : fffff880`009b0830 fffffa80`00053071 00000000`0000fffe 00000000`00000001 : tcpip!TcpPeriodicTimeoutHandler+0x3f9
    fffff880`009b07a0 fffff800`0349a6f6 : fffffa80`0854df68 00000000`00094ea6 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff880`009b0810 fffff800`0349a5de : 00000016`27a0f94a fffff880`009b0e88 00000000`00094ea6 fffff880`02fdaa48 : nt!KiProcessExpiredTimerList+0xc6
    fffff880`009b0e60 fffff800`0349a3c7 : fffff880`02fd71c1 fffff880`00094ea6 00000000`00000001 00000000`000000a6 : nt!KiTimerExpiration+0x1be
    fffff880`009b0f00 fffff800`03492d15 : 00000000`00000000 fffffa80`0797e060 00000000`00000000 fffff800`035b0a80 : nt!KiRetireDpcList+0x277
    fffff880`009b0fb0 fffff800`03492b2c : fffff880`02fd7180 fffff800`0349b1b8 00000000`00000000 00000000`1bb08b82 : nt!KxRetireDpcList+0x5
    fffff880`075beb40 fffff800`034dab53 : fffff800`0349af4c fffff800`0349afb8 fffff6fc`8062f208 fffff880`075bec00 : nt!KiDispatchInterruptContinue
    fffff880`075beb70 fffff800`0349afb8 : fffff6fc`8062f208 fffff880`075bec00 00000000`000755ba 00000000`00000000 : nt!KiDpcInterruptBypass+0x13
    fffff880`075beb80 fffff800`034af302 : fffff800`0341a000 00000000`00000000 00001bcb`00000000 fffff880`075b3000 : nt!KiSecondaryClockInterrupt+0x1a8
    fffff880`075bed10 fffff800`034b1c98 : 00000000`0000000c fffff880`075bee80 fffff900`c5e41000 00000000`0002179c : nt!MiFlushTbAsNeeded+0x282
    fffff880`075bee20 fffff800`035c0f86 : 00000000`0000b200 fffff880`05c6dcc0 00000000`00000021 00000000`00000000 : nt!MiAllocatePagedPoolPages+0x4cc
    fffff880`075bef40 fffff800`034af9b0 : 00000000`0000b200 fffff880`05c6dcc0 00000000`00000021 00000000`00000000 : nt!MiAllocatePoolPages+0x906
    fffff880`075bf080 fffff800`035c443e : 00000000`00000000 fffff960`00060000 fffff900`00000020 00000000`0000b200 : nt!ExpAllocateBigPool+0xb0
    fffff880`075bf170 fffff960`00114c05 : fffff900`c49f5650 00000000`00000000 fffffa80`06cb10a0 fffff800`0392807d : nt!ExAllocatePoolWithTag+0x82e
    fffff880`075bf260 fffff960`001162be : 00000000`0000020a fffff880`075bf400 fffff900`c49f56c0 00000000`000020a0 : win32k!AllocateObject+0xdd
    fffff880`075bf2a0 fffff960`000ed0cc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x38a
    fffff880`075bf390 fffff960`000ecc3a : 00000017`000001e9 00000000`00000017 00000000`01080030 00000000`000001e9 : win32k!hsurfCreateCompatibleSurface+0x3bc
    fffff880`075bf460 fffff800`0348ee13 : fffffa80`0797e060 fffff880`075bf5c0 00000000`000001e9 fffff900`c00b8010 : win32k!GreCreateCompatibleBitmap+0x26e
    fffff880`075bf540 000007fe`fe4e2dea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0012e848 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fe4e2dea
    
    
    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_VRF_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE
    
    Followup: MachineOwner
    ---------
    Last edited by jcgriff2; 08-27-2013 at 01:05 AM.

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015

  5. #25

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Thanks for the detailed output. If I understand correctly the stack of the hung processor (2) is empty--does that suggest perhaps that this is a CPU issue?. In some of the other processor stacks you see a variety of drivers, which I will be happy to continue to keep erasing one by one as I have done so far for troubleshooting purposes, although the pattern appears to me that some driver appears in the stack, which then I delete/uninstall, only to crash again and then a different driver this time appears, so I delete that one, and then another crash shows yet another driver, and so on... Is there particular evidence that suggests these drivers are responsible, or simply their presence in the stack may or may not mean something?

    I will proceed with uninstalling Comodo as requested for troubleshooting purposes, but this means I will have to keep the computer disconnected from the network since I depend on the firewall with very particular software settings. After I remove the firewall and the inspect.sys driver, if I get another crash, does that mean I can go ahead and reinstall it?

    I will also update Broadcom driver as suggested. Finally regarding Terabyte (phylock.sys), that is software I use for making backup images of the Windows drive -- very useful to me particularly now since I can image the drive before I make a major change.

  6. #26
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    14,525

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Quote Originally Posted by rockstream View Post
    Thanks for the detailed output. If I understand correctly the stack of the hung processor (2) is empty--does that suggest perhaps that this is a CPU issue?. In some of the other processor stacks you see a variety of drivers, which I will be happy to continue to keep erasing one by one as I have done so far for troubleshooting purposes, although the pattern appears to me that some driver appears in the stack, which then I delete/uninstall, only to crash again and then a different driver this time appears, so I delete that one, and then another crash shows yet another driver, and so on... Is there particular evidence that suggests these drivers are responsible, or simply their presence in the stack may or may not mean something?
    0x101 is almost always a CPU issue. I have seen some 0x101 BSODs caused by 3rd party drivers; hence the reason why the ones listed on the stack should be looked at.

    System uptime:
    Code:
    System Uptime: 0 days 2:38:41.459
    Process listed:
    Code:
    PROCESS_NAME:  imagew64.exe
    I'm not sure if that is part of TeraByte or not. I can't say this process caused the BSOD either.

    In general, anytime a 3rd party driver is listed in a BSOD stack, it is a possible culprit.

    I'm not sure of the significance of proc 2's zero stack after running some additional Windbg commands on the full kernel dump. I've sent PMs requesting other analysts to review the info.

    I'm listing the Processor Control Region (PCR) info here for future reference.
    Code:
    0: kd> !pcr 0
    KPCR for Processor 0 at fffff8000360ad00:
        Major 1 Minor 1
    	NtTib.ExceptionList: fffff80000b95000
    	    NtTib.StackBase: fffff80000b96080
    	   NtTib.StackLimit: 00000000058cf8d8
    	 NtTib.SubSystemTib: fffff8000360ad00
    	      NtTib.Version: 000000000360ae80
    	  NtTib.UserPointer: fffff8000360b4f0
    	      NtTib.SelfTib: 000007fffffac000
    
    	            SelfPcr: 0000000000000000
    	               Prcb: fffff8000360ae80
    	               Irql: 0000000000000000
    	                IRR: 0000000000000000
    	                IDR: 0000000000000000
    	      InterruptMode: 0000000000000000
    	                IDT: 0000000000000000
    	                GDT: 0000000000000000
    	                TSS: 0000000000000000
    
    	      CurrentThread: fffffa8008785360
    	         NextThread: 0000000000000000
    	         IdleThread: fffff80003618cc0
    
    	          DpcQueue:
    
     
    0: kd> !pcr 1
    KPCR for Processor 1 at fffff880009eb000:
        Major 1 Minor 1
    	NtTib.ExceptionList: fffff880009f6540
    	    NtTib.StackBase: fffff880009eff40
    	   NtTib.StackLimit: 000000000df4d968
    	 NtTib.SubSystemTib: fffff880009eb000
    	      NtTib.Version: 00000000009eb180
    	  NtTib.UserPointer: fffff880009eb7f0
    	      NtTib.SelfTib: 000007fffff9a000
    
    	            SelfPcr: 0000000000000000
    	               Prcb: fffff880009eb180
    	               Irql: 0000000000000000
    	                IRR: 0000000000000000
    	                IDR: 0000000000000000
    	      InterruptMode: 0000000000000000
    	                IDT: 0000000000000000
    	                GDT: 0000000000000000
    	                TSS: 0000000000000000
    
    	      CurrentThread: fffffa800877b720
    	         NextThread: fffffa800985bb50
    	         IdleThread: fffff880009f5fc0
    
    	          DpcQueue:
    
     
    0: kd> !pcr 2
    KPCR for Processor 2 at fffff88002f65000:
        Major 1 Minor 1
    	NtTib.ExceptionList: fffff88002f70540
    	    NtTib.StackBase: fffff88002f69f40
    	   NtTib.StackLimit: 000000000872f4c8
    	 NtTib.SubSystemTib: fffff88002f65000
    	      NtTib.Version: 0000000002f65180
    	  NtTib.UserPointer: fffff88002f657f0
    	      NtTib.SelfTib: 000007fffff8c000
    
    	            SelfPcr: 0000000000000000
    	               Prcb: fffff88002f65180
    	               Irql: 0000000000000000
    	                IRR: 0000000000000000
    	                IDR: 0000000000000000
    	      InterruptMode: 0000000000000000
    	                IDT: 0000000000000000
    	                GDT: 0000000000000000
    	                TSS: 0000000000000000
    
    	      CurrentThread: fffff88002f6ffc0
    	         NextThread: fffffa8008cb8660
    	         IdleThread: fffff88002f6ffc0
    
    	          DpcQueue:
    
     
    0: kd> !pcr 3
    KPCR for Processor 3 at fffff88002fd7000:
        Major 1 Minor 1
    	NtTib.ExceptionList: fffff88002fe2540
    	    NtTib.StackBase: fffff88002fdbf40
    	   NtTib.StackLimit: 000000000615f0f8
    	 NtTib.SubSystemTib: fffff88002fd7000
    	      NtTib.Version: 0000000002fd7180
    	  NtTib.UserPointer: fffff88002fd77f0
    	      NtTib.SelfTib: 000007fffffde000
    
    	            SelfPcr: 0000000000000000
    	               Prcb: fffff88002fd7180
    	               Irql: 0000000000000000
    	                IRR: 0000000000000000
    	                IDR: 0000000000000000
    	      InterruptMode: 0000000000000000
    	                IDT: 0000000000000000
    	                GDT: 0000000000000000
    	                TSS: 0000000000000000
    
    	      CurrentThread: fffffa800797e060
    	         NextThread: 0000000000000000
    	         IdleThread: fffff88002fe1fc0
    
    	          DpcQueue:
    Quote Originally Posted by rockstream View Post
    I will proceed with uninstalling Comodo as requested for troubleshooting purposes, but this means I will have to keep the computer disconnected from the network since I depend on the firewall with very particular software settings. After I remove the firewall and the inspect.sys driver, if I get another crash, does that mean I can go ahead and reinstall it? .
    I am anti-3rd party firewalls in general for Vista, Windows 7 & Windows 8 because I often see 0xc5 memory access violations associated with them. However, given your situation with a server, a properly configured firewall should not necessarily be an issue. Have you tried other firewalls? Comodo seems to appear on my radar too often in BSODs (my personal experience).

    I would uninstall COMODO until the BSODs are solved.

    Quote Originally Posted by rockstream View Post
    I will also update Broadcom driver as suggested. Finally regarding Terabyte (phylock.sys), that is software I use for making backup images of the Windows drive -- very useful to me particularly now since I can image the drive before I make a major change.
    I understand about Terabyte, but seeing phylock.sys on the stack means it too is a possible cause.

    Unfortunately, BSOD dumps are incapable of telling us the exact piece of hardware that is/has failed and can at best point us in a direction. I try and rule out possible software causes unless a dump lists a probable cause like "I/O error" or multiple bugchecks are found.

    Have you run Driver Verifier yet?

    http://www.sysnative.com/forums/bsod...h-related.html

    Regards. . .

    John
    Patrick says thanks for this.

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015

  7. #27

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Update on this thread - I was out of town for 1 week so I was unable to do any further troubleshooting. While I was out, I left the computer on but not logged in (stayed in the log on screen) to maximize the chances that it would not crash. It stayed without crashing for the entire week, and I was even able to remotely (via Chrome Remote Desktop) log on briefly and then log back out.

    When I arrived yesterday, following the recommendations here, I removed all traces of Comodo Firewall and Antivirus and I installed MSE and configured Windows Firewall instead. I turned on Driver Verifier again and left it all day yesterday and all night with heavy activity, and woke up this morning to find that it had not crashed -- I believe this is the first time time it survived overnight with Driver Verifier on. I will wait a few more days before I declare any victories, but so far removing Comodo appears promising.

  8. #28

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Hi,

    Keep us updated, sounds like we're in the clear.

    Regards,

    Patrick

  9. #29

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Ok not quite there yet. Had another x101 error today after about 24 hours on Driver Verifier. Kernel dump is at:

    https://www.dropbox.com/s/8nvffvgse2...2013-09-03.zip

    I briefly looked at the !analyze -v output and all I see is networking related drivers, such as afd.sys, netio.sys, tcpip.sys. The processes running heavily during the crash were performing lots of network download.

    FYI - following advice from the thread, I had updated by network card driver to Broadcom v15.6.0.2 - 10/15/2012 (k57nd60a.sys) directly from the Broadcom site -- my motherboard site only had v.14.6.4.2 available (4/29/2011).

  10. #30

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    FYI - following advice from the thread, I had updated by network card driver to Broadcom v15.6.0.2 - 10/15/2012 (k57nd60a.sys) directly from the Broadcom site -- my motherboard site only had v.14.6.4.2 available (4/29/2011).
    Keep me updated after doing so. You don't have any 3rd party antivirus or firewall software installed, do you?

    Regards,

    Patrick

  11. #31

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    The Broadcom update had been done before the last crash. I had also removed the Comodo antivirus and firewall and I only have Microsoft Security Essentials.

  12. #32

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Hi,

    Have you had any crashes since making the above adjustments?

    Regards,

    Patrick

  13. #33

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Sorry if I wasn't clear. The crash at:
    https://www.dropbox.com/s/8nvffvgse2...2013-09-03.zip

    happened *after* all the adjustments I mentioned (upgrading Broadcom, removing Comodo). There have not been any other changes since then.

  14. #34

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Okay, let's go through this... *101's are fairly difficult so bear with me.

    As usual, it's a CLOCK_WATCHDOG_TIMEOUT (101) bugcheck.

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

    31 clock ticks in regards to the timeout.

    fffff88002fd7180 is the PRCB address of the hung processor, let's keep this address in mind.

    Running a !prcb on processor 0:
    Code:
    0: kd> !prcb 0
    PRCB for Processor 0 at fffff80003643e80:
    Current IRQL -- 13
    Threads--  Current fffffa800c5cab50 Next 0000000000000000 Idle fffff80003651cc0
    Processor Index 0 Number (0, 0) GroupSetMember 1
    Interrupt Count -- 1e52881e
    Times -- Dpc    0001a981 Interrupt 0000e408 
             Kernel 00524e0a User      0010e2e0
    No match for address, let's try processor 1 this time:

    Code:
    0: kd> !prcb 1
    PRCB for Processor 1 at fffff880009eb180:
    Current IRQL -- 0
    Threads--  Current fffffa800c2a0060 Next fffffa8009b7d060 Idle fffff880009f5fc0
    Processor Index 1 Number (0, 1) GroupSetMember 2
    Interrupt Count -- 1acd8bf2
    Times -- Dpc    000000c3 Interrupt 00000640 
             Kernel 0050afcc User      0012810b
    Nope, no match either. I'll spare you the space in the post and tell you that processor #3 is the one we're looking for :+)

    Code:
    0: kd> !prcb 3
    PRCB for Processor 3 at fffff88002fd7180:
    Current IRQL -- 0
    Threads--  Current fffff88002fe1fc0 Next fffffa800b289640 Idle fffff88002fe1fc0
    Processor Index 3 Number (0, 3) GroupSetMember 8
    Interrupt Count -- 18eaff17
    Times -- Dpc    000000ee Interrupt 000006b3 
             Kernel 004d01ad User      00162c9c
    As this matches the 3rd parameter of the bugcheck, processor #3 is the responsible processor. Now with the information we have here thus far, we know that processor #3 reached 31 clock ticks without responding, therefore the system BSOD'd. Before we go further, what is a clock tick? A clock_interrupt is a form of interrupt which involves counting the the cycles of the processor core, which is running a clock on the processors to keep them all in sync. A clock interrupt is handed out to all processors and then they must report in, and when one doesn't report in, you then crash.

    Now how and why did this take place? Let's check the IRQL of each one of the processors before the system crash:

    Code:
    0: kd> !irql 0
    Debugger saved IRQL for processor 0x0 -- 13
    0: kd> !irql 1
    Debugger saved IRQL for processor 0x1 -- 0 (LOW_LEVEL)
    
    0: kd> !irql 2
    Debugger saved IRQL for processor 0x2 -- 0 (LOW_LEVEL)
    
    0: kd> !irql 3
    Debugger saved IRQL for processor 0x3 -- 0 (LOW_LEVEL)
    The IRQL of the processor 1 is 13, which is CLOCK for x64 processors. The rest are at 0.

    Let's see the call stacks of the processors:

    Processor 0:

    Code:
    0: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff880`0d3d1328 fffff800`0351fa3a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02fd7180 : nt!KeBugCheckEx
    fffff880`0d3d1330 fffff800`034d26f7 : 00000000`00000000 fffff800`00000003 00000000`00002710 fffff880`0d3d1450 : nt! ?? ::FNODOBFM::`string'+0x4e3e
    fffff880`0d3d13c0 fffff800`03414895 : fffff800`0343a460 fffff880`0d3d1570 fffff800`0343a460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
    fffff880`0d3d14c0 fffff800`034c50d3 : fffff800`03643e80 00000000`00000001 00000000`00000001 fffff800`03453000 : hal!HalpHpetClockInterrupt+0x8d
    fffff880`0d3d14f0 fffff800`0349d8e7 : fffff6fc`0001bea0 fffff800`034e5c8f 00000000`00000000 74a00000`037d4860 : nt!KiInterruptDispatchNoLock+0x163 (TrapFrame @ fffff880`0d3d14f0)
    fffff880`0d3d1680 fffff800`037d566f : 00000000`00000000 fffff880`0d3d1b60 00000000`00000000 fffff800`034f86c4 : nt!KeFlushProcessWriteBuffers+0x63
    fffff880`0d3d16f0 fffff800`037d5ccd : 00000000`06ae0a90 fffff800`037c05ee 00000000`00000000 00000000`00010246 : nt!ExpQuerySystemInformation+0x13af
    fffff880`0d3d1aa0 fffff800`034c7e13 : 00000000`00000000 fffff880`0d3d1b60 ffffffff`fffe7960 000007fe`fbfc0b48 : nt!NtQuerySystemInformation+0x4d
    fffff880`0d3d1ae0 00000000`777a161a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0d3d1ae0)
    00000000`0461f028 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777a161a
    Processor 1:

    Code:
    1: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff880`0cd33320 fffff800`03577c26 : 00000000`00000000 fffff880`009eb180 fffff980`37980d10 fffff800`034f383b : nt!KiIpiSendRequestEx+0xb2
    fffff880`0cd33360 fffff800`035d0a69 : 00000000`00000001 fffff880`0cd33420 fffff6fc`c01bcc00 fffff980`37980d10 : nt!KeFlushSingleTb+0x126
    fffff880`0cd333e0 fffff800`035fb93b : fffff800`03453000 00000000`6c624e54 00000000`097cb740 00000000`00000100 : nt!MmFreeSpecialPool+0x349
    fffff880`0cd33530 fffff880`01635232 : fffff980`37980d30 fffff980`37980d30 fffff980`0149ac80 fffff980`0149aa00 : nt!ExDeferredFreePool+0xf33
    fffff880`0cd335e0 fffff880`0186756a : 00000000`00000000 fffff980`37980e60 00000000`00000000 00000000`ea94000f : ndis!NdisFreeNetBufferList+0x112
    fffff880`0cd33610 fffff880`01727872 : fffffa80`082f5bc8 00000000`00000001 00000000`00000001 fffffa80`08688800 : tcpip!TcpSendDatagramsComplete+0x9a
    fffff880`0cd33650 fffff880`01885e6f : 00000000`00000000 00000000`00000001 fffff880`0cd33700 00000000`00000000 : NETIO!NetioDereferenceNetBufferListChain+0x132
    fffff880`0cd33720 fffff880`01861d75 : fffff980`37980f00 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpFlushDelay+0x13f
    fffff880`0cd33800 fffff880`0183e2ba : fffffa80`084f3880 fffffa80`0000ea0c fffff880`000020fe fffff880`0cd320fe : tcpip!TcpPreValidatedReceive+0x3e5
    fffff880`0cd338d0 fffff800`034d4878 : fffff880`0196e9a0 fffff800`034f3a06 00000000`00000000 fffff880`0cd33ae0 : tcpip!IppLoopbackTransmit+0x11a
    fffff880`0cd33980 fffff880`0183ebcf : fffff880`0188e4b4 fffff880`0000000c fffff880`0cd33b02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`0cd33a60 fffff880`01860357 : fffff980`378f8d30 00000000`00000004 fffff880`0cd33f01 fffffa80`0b9e6010 : tcpip!IppLoopbackEnqueue+0x22f
    fffff880`0cd33b10 fffff880`01866a85 : fffffa80`084f3820 00000000`00000001 fffffa80`00000001 00000000`00000080 : tcpip!IpNlpFastSendDatagram+0xb77
    fffff880`0cd33ec0 fffff880`01867640 : fffff880`00000000 fffffa80`06d324d8 00000000`00000000 00000000`00004800 : tcpip!TcpTcbSend+0x495
    fffff880`0cd34140 fffff880`01866398 : 00000000`00000000 000000ec`1711a9e9 fffff880`0cd34360 fffff880`0cd34470 : tcpip!TcpEnqueueTcbSendOlmNotifySendComplete+0xa0
    fffff880`0cd34170 fffff880`0186655b : fffffa80`08d69000 00000000`fffffffe 00000000`00004800 fffff800`036d6b10 : tcpip!TcpEnqueueTcbSend+0x258
    fffff880`0cd34220 fffff800`034d4878 : 00000000`00000001 fffff880`00000000 00000000`00000404 00000000`0cd34ae0 : tcpip!TcpTlConnectionSendCalloutRoutine+0x1b
    fffff880`0cd34250 fffff880`0186741a : fffff880`01866540 00000000`00000000 00000000`00000000 fffff880`02d47601 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`0cd34330 fffff880`02d61b2b : fffffa80`083dbcf0 fffff880`0cd34b60 00000000`0000003c fffffa80`0c2303b0 : tcpip!TcpTlConnectionSend+0x7a
    fffff880`0cd343a0 fffff880`02d46469 : fffffa80`094b0000 fffffa80`094b0000 00000000`00000000 00000000`00000000 : afd!AfdFastConnectionSend+0x38b
    fffff880`0cd34560 fffff800`037e6a33 : 00000000`0000003c fffffa80`0bb7ba10 00000000`00b7f5ec fffff880`00000001 : afd!AfdFastIoDeviceControl+0x459
    fffff880`0cd348d0 fffff800`037e7526 : 00000000`00000000 00000000`00000114 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x373
    fffff880`0cd34a00 fffff800`034c7e13 : 00000000`73b82450 00000000`001feb30 00000000`001ffd20 fffff880`0cd34ae0 : nt!NtDeviceIoControlFile+0x56
    fffff880`0cd34a70 00000000`73b82e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0cd34ae0)
    00000000`001feab8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73b82e09
    Processor 2:

    Code:
    2: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff880`02748cc0 fffff800`03529188 : 0000007f`fffffff8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x266
    fffff880`02748d90 fffff800`035d060d : fffff800`03703b00 fffff880`02748fa0 fffff8a0`00000000 fffff8a0`00000006 : nt! ?? ::FNODOBFM::`string'+0x204ce
    fffff880`02748f80 fffff800`035d1bd7 : fffffa80`09b91060 00000000`00000000 00000000`00000000 00000000`00000008 : nt!MiEmptyWorkingSet+0x27d
    fffff880`02749030 fffff800`0396d371 : 00000000`00000000 fffff980`0149aa02 fffff980`0149ad00 fffff880`02d470e2 : nt!MiTrimAllSystemPagableMemory+0x218
    fffff880`02749090 fffff800`0396d4cf : fffff980`0149aa02 fffffa80`06c90578 fffffa80`06c90578 fffff6fc`40016a38 : nt!MmVerifierTrimMemory+0xf1
    fffff880`027490c0 fffff800`0396dc24 : fffff980`0149aa08 fffff980`0149aa00 00000000`000001f1 00000000`00000000 : nt!ViKeRaiseIrqlSanityChecks+0xcf
    fffff880`02749100 fffff880`01635206 : 00000000`00000000 fffff980`378f8d30 fffff980`0149ad00 fffff980`378f8d30 : nt!VerifierKeAcquireSpinLockRaiseToDpc+0x54
    fffff880`02749160 fffff880`0186718f : fffff980`378f8f70 fffff980`378f8d30 fffff980`378f8e60 fffff8a0`12fda0b0 : ndis!NdisFreeNetBufferList+0xe6
    fffff880`02749190 fffff880`01727872 : fffffa80`07a56d70 fffff880`02749650 00000000`00000001 00000000`00000001 : tcpip!TcpTcbSendDatagramsComplete+0x12f
    fffff880`027491f0 fffff880`0187c731 : 00000000`00000038 00000000`00000000 fffff880`02749238 00000000`00000000 : NETIO!NetioDereferenceNetBufferListChain+0x132
    fffff880`027492c0 fffff880`02d1d44d : fffff880`02749650 fffff980`378f8d30 fffff880`02749b60 fffffa80`0b1387b0 : tcpip!TcpTlProviderReleaseIndicationList+0x81
    fffff880`027492f0 fffff880`02d60a01 : 00000000`02e7fd70 fffff880`02749650 fffff880`02749650 00000000`00000000 : afd!AfdTLReleaseIndications+0x2d
    fffff880`02749340 fffff880`02d467bb : fffff880`02749560 fffff880`02749560 fffffa80`00000000 00000000`00000000 : afd!AfdFastConnectionReceive+0x8d1
    fffff880`02749560 fffff800`037e6a33 : 00000000`00000038 fffffa80`0885f090 00000000`02e7fc58 fffffa80`0861eb01 : afd!AfdFastIoDeviceControl+0x7ab
    fffff880`027498d0 fffff800`037e7526 : fffff880`02749ab8 00000000`000204c8 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x373
    fffff880`02749a00 fffff800`034c7e13 : fffff880`02749b60 fffffa80`098fe530 fffff880`02749ab8 fffff8a0`0e1b4001 : nt!NtDeviceIoControlFile+0x56
    fffff880`02749a70 00000000`777a132a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`02749ae0)
    00000000`02e7fba8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777a132a
    Processor 3

    Code:
    3: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    From the above, we can see that processor 0 was the processor that performed the bugcheck. In processors 1-2 we can see various network related routines and such being called, tcpip... netio, etc.

    We can also see that processor 3 fails to do anything at all. It's a 0x0, as John mentioned above earlier. *101's are very difficult to debug and analyze, and I am tongue in cheek as I type this, but at this point I very well believe this is a processor issue (if not motherboard). This is two times now we've seen the culprit processor 0x0. Do you happen to have a wireless adapter of some sort or something connected? If so, I would recommend directly connecting to the onboard NIC if possible to circumvent possible adapter issues (just throwing that out there given the network routines being called).

    Regards,

    Patrick

  15. #35

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    I do not have any kind of wireless adapter. My Ethernet is directly connected to the onboard NIC.

    I searched about this issue in my specific MB, and see some reports of 101 BSODs. Since there are many different variables it's difficult to tell whether we are talking about the same issue, but it is very much possible that we are seeing this MB instability. What is interesting is that I have been using this MB since I built the system in 2011 without this, but there is a possible explanation: for most of that time when it was stable I was overclocking, which meant that I had a higher Vcore setting in the BIOS. A few months ago, I had some issues with Windows 7 which made me reinstall the OS and I stopped overcloking to troubleshoot that, and it appears that problems with BSOD started around that time (hard to pinpoint exactly what came first).

    The reports in forums regarding my motherboard suggest that leaving it happens when Vcore is left at the default "Auto" setting (which is where it has been during all these troubleshooting incidents). Apparently the voltage ends up dropping down too low which can cause the 101 errors. Some suggest making the Vcore a bit higher (1.19V for example) even though there is no overclock solves the 101 instability. So I moved the Vcore to 1.19 V and also per recommendation also disabled the "Sata Aggressive link power management option in BIOS. We'll try that for a couple of days to see if it does the trick. Next if that doesn't work would be to upgrade BIOS to a newer version advertised specifically to address BSOD instability.

  16. #36

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Sounds great, and good detective work :+)

    Keep us updated.

    Regards,

    Patrick

  17. #37

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Three full days on Driver Verifier and constant load without a crash...best so far.

  18. #38

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Hi,

    You can definitely disable verifier now since it's been 3 days. Keeping verifier enabled for any longer may actually CAUSE issues.

    Regards,

    Patrick

  19. #39

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    I turned Driver Verifier off and rebooted. Still good going on 4th day.

  20. #40

    Re: Recurrent BSODs (every 1-2 days) clock interrupt

    Hi,

    96 hours without a crash as opposed to before and having Verifier enabled for half of it sounds like solved to me. If you're comfortable, you can go ahead and mark it solved. If not and you'd like to wait a few more days, that's fine too.

    Regards,

    Patrick

Page 2 of 3 First 123 Last

Similar Threads

  1. [SOLVED] BSOD Clock interrupt was not receieved on a secondary processor
    By fuller10e in forum BSOD, Crashes, Kernel Debugging
    Replies: 9
    Last Post: 09-14-2015, 06:00 AM
  2. BSOD Clock interrupt was not receieved on a secondary processor
    By djeby in forum BSOD, Crashes, Kernel Debugging
    Replies: 10
    Last Post: 07-29-2013, 11:35 AM
  3. Constant Clock Interrupt BSODs
    By Lateralus in forum BSOD, Crashes, Kernel Debugging
    Replies: 30
    Last Post: 10-25-2012, 05:01 AM
  4. Replies: 3
    Last Post: 06-14-2012, 01:10 AM
  5. 0x101 "A clock interrupt was not received on a secondary processor..."
    By oatcoatedstoat in forum BSOD, Crashes, Kernel Debugging
    Replies: 89
    Last Post: 06-08-2012, 08:49 AM

Log in

Log in