Windows 8 and 8.1 Forums

BSOD & Clock_Watchdog_Timeout

  1. #1

    Posts : 1
    Windows 8

    BSOD & Clock_Watchdog_Timeout

    Hello fellas,

    Barely new windows 8 user on my 3.5 years old Dell Studio 1557 (not the least problematic series, for sure).

    So, I like Windows 8 so far, but I have been having BSOD lately with the Clock_Watchdog_Timeout error.

    Even though I have no clue, I suspect it could be something with the graphics card since it usually happens when I watch a video or movie.

    Anyway, I don't want to make you biased towards that, so let's keep an open mind!

    I have also attached a latest copy of the Minidump folder contents.



      My System SpecsSystem Spec

  2. #2

    Posts : 5,139
    Win8.1Pro - Finally!!!

    Please provide this information so we can provide a complete analysis: Blue Screen of Death (BSOD) Posting Instructions

    The error appears to be in the networking sub-system, other than that we'll need the rest of the reports. Update your wired and wireless network drivers for starters.

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    SSPORT.sys Thu Aug 11 19:07:32 2005 (42FBDA34)
    Samsung printer driver

    NETwNs64.sys Thu Oct 6 10:45:03 2011 (4E8DBEEF)
    Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7

    Rt630x64.sys Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    Realtek PCI/PCIe Adapters

    If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings

    The following is for informational purposes only.
    **************************Sun Jul 14 13:32:39.687 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\071413-51043-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:2 days 6:30:51.443
    *** ERROR: Module load completed but symbols could not be loaded for mslldp.sys
    Probably caused by :ntkrnlmp
    BugCheck 9F, {4, 12c, fffffa8004921800, fffff803f0e98950}
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    Arg2: 000000000000012c, Timeout in seconds.
    Arg3: fffffa8004921800, The thread currently holding on to the Pnp lock.
    Arg4: fffff803f0e98950, nt!TRIAGE_9F_PNP on Win7
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_4_IMAGE_ntkrnlmp
    CPUID:        "Intel(R) Core(TM) i7 CPU       Q 720  @ 1.60GHz"
    MaxSpeed:     1600
    CurrentSpeed: 1596
      BIOS Version                  A09
      BIOS Release Date             03/30/2011
      Manufacturer                  Dell Inc.
      Product Name                  Studio 1557
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    **************************Sun Jul 14 13:32:39.687 2013 (UTC - 4:00)**************************
    SSPORT.sys                  Thu Aug 11 19:07:32 2005 (42FBDA34)
    NETwNs64.sys                Thu Oct  6 10:45:03 2011 (4E8DBEEF)
    Rt630x64.sys                Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
    atikmpag.sys                Mon Jun 18 16:41:29 2012 (4FDF9279)
    atikmdag.sys                Mon Jun 18 17:21:01 2012 (4FDF9BBD)
    intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
    acsock64.sys                Tue Nov  6 21:27:25 2012 (5099C70D)
    dump_storahci.sys           Fri Mar  1 21:15:44 2013 (513160D0)
    acsock64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
      My System SpecsSystem Spec

BSOD & Clock_Watchdog_Timeout
Related Threads
So yeah, iดm "new" here. Actually been using Seven forums for a while. Friend of mine been having a lot of bluescreens lately and unfortunately i have been unable pinpoint what the problem is so iดm asking your help and assistance. There have been several different bluescreen which come up while...
Solved Clock_watchdog_timeout in BSOD Crashes and Debugging
Blue screen started yesterday, both times I was playing a game. This is the first time I have had any bsod/lockups. Let me know if you need anymore info. Thanks for your time.
Clock_watchdog_timeout in BSOD Crashes and Debugging
I get this blue screen every so often (it happened when I first tried typing this too, haha) and they started about a day ago. From other threads on this it looks like a driver problem, but I have no idea WTF I'm doing so any help would be appreciated.
Solved Clock_watchdog_timeout in BSOD Crashes and Debugging
Hey, got some problems with my PC for 2 weeks now, I receive random BSOD with CLOCK_WATCHDOG_TIMEOUT error caused by hal.dll and ntoskrnl.exe. I reinstalled windows from scratch, 2 days worked fine, now I get the blue screen again and I cannot solve this :/ I attached W8 log collector archive,...
Clock_watchdog_timeout in BSOD Crashes and Debugging
I saw another thread on this, but couldn't find the files GMan indicated to delete. Once or twice per night, my computer will freeze completely. Sometimes, I'll see a BSOD which briefly shows CLOCK_WATCHDOG_TIMEOUT. DxDiag is here: MGA dxdiag -
Bsod: Clock_watchdog_timeout in BSOD Crashes and Debugging
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: 00000030, Clock interrupt time out interval in...
clock_watchdog_timeout in BSOD Crashes and Debugging
Every now and then my system stops working and I get a screen with this message before I need to turn off and restart. Anyone have any ideas what this message might mean? I never saw it at all in windows 7 which ran as stable as a rock.
Eight Forums Android App Eight Forums IOS App Follow us on Facebook