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


  1. Posts : 1
    windows 7 professional sp1
       #1

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


    Hi guys,

    First of all, thanks for reading this.

    I switched my computer on 3 days a go and encountered the above BSOD. It happens as soon as I sign in or when I open a web browser. Previously I had no known issues with the computer and made no changes to cause this problem, no added hardware or software. I followed the instructions on this site and used the application for getting system information. I have attached the files to this post if anyone has any time to look through them that would be much appreciated.

    Many thanks

    (just to add, I am posting this from the computer in question, using safe mode)
      My Computer


  2. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #2

    henryg40 said:
    Hi guys,

    First of all, thanks for reading this.

    I switched my computer on 3 days a go and encountered the above BSOD. It happens as soon as I sign in or when I open a web browser. Previously I had no known issues with the computer and made no changes to cause this problem, no added hardware or software. I followed the instructions on this site and used the application for getting system information. I have attached the files to this post if anyone has any time to look through them that would be much appreciated.

    Many thanks

    (just to add, I am posting this from the computer in question, using safe mode)
    Hello there!

    Follow this article STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg and do the tests.

    BSOD BUGCHECK SUMMARY

    Code:
    
    Loading Dump File [C:\Documents and Settings\Shyam\_jcgriff2_\dbug\__Kernel__\080612-11419-01.dmp]
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Tue Aug  7 00:04:55.642 2012 (GMT+6)
    System Uptime: 0 days 0:01:37.875
    BugCheck 101, {31, 0, fffff88003565180, 2}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
    Bugcheck code 00000101
    Arguments 00000000`00000031 00000000`00000000 fffff880`03565180 00000000`00000002
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Loading Dump File [C:\Documents and Settings\Shyam\_jcgriff2_\dbug\__Kernel__\080512-9828-01.dmp]
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Sun Aug  5 19:20:40.509 2012 (GMT+6)
    System Uptime: 0 days 0:00:37.352
    BugCheck 101, {31, 0, fffff88003565180, 2}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
    Bugcheck code 00000101
    Arguments 00000000`00000031 00000000`00000000 fffff880`03565180 00000000`00000002
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Loading Dump File [C:\Documents and Settings\Shyam\_jcgriff2_\dbug\__Kernel__\080512-9547-01.dmp]
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Sat Aug  4 14:32:55.912 2012 (GMT+5)
    System Uptime: 0 days 0:10:42.755
    BugCheck 101, {31, 0, fffff88003565180, 2}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  MsMpEng.exe
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
    Bugcheck code 00000101
    Arguments 00000000`00000031 00000000`00000000 fffff880`03565180 00000000`00000002
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Loading Dump File [C:\Documents and Settings\Shyam\_jcgriff2_\dbug\__Kernel__\080512-10155-01.dmp]
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Sun Aug  5 19:21:48.261 2012 (GMT+6)
    System Uptime: 0 days 0:00:24.494
    BugCheck 101, {31, 0, fffff88003565180, 2}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
    Bugcheck code 00000101
    Arguments 00000000`00000031 00000000`00000000 fffff880`03565180 00000000`00000002
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    
    
      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 17:24.
Find Us