Brand new Build. BSod CLock_Watchdog_Timeout and Freezes.

Page 1 of 15 12311 ... LastLast

  1. Posts : 75
    Windows 10
       #1

    Brand new Build. BSod CLock_Watchdog_Timeout and Freezes.


    I spent all weekend building up a new computer:
    CPU: Intel Core i7-6700K 4.0GHz Quad-Core Processor
    CPU Cooler: NZXT Kraken X41 106.1 CFM Liquid CPU Cooler
    Motherboard: Gigabyte GA-Z170X-Gaming 7 ATX LGA1151 Motherboard
    Memory: G.Skill Ripjaws V Series 32GB (4 x 8GB) DDR4-2400 Memory
    Storage: Western Digital BLACK SERIES 4TB 3.5" 7200RPM Internal Hard Drive
    Storage: Western Digital BLACK SERIES 4TB 3.5" 7200RPM Internal Hard Drive
    Storage: Crucial MX200 250GB
    Storage: Crucial MX200 500GB
    Video Card: EVGA GeForce GTX 750 Ti 2GB Superclocked Video Card
    Case: Fractal Design Define R5 w/Window (Black) ATX Mid Tower Case
    Power Supply: SeaSonic 650W 80+ Gold Certified Semi-Modular ATX Power Supply
    Monitor: Dell P2715Q 60Hz 27.0" Monitor

    Build went fine. Bios looked fine. installed OS, went fine.
    installed newest online drivers
    added a WD green 3TB drive form my exitsing PC with data - Started migrating large amounts of data and got a couple freezes.
    Once data was transferred everything seemed OK
    Browsing online - nothing CPU intensive and got BSoD with the clock_watchdog_timeout error
    started getting random freezes and the same cwt BSod here and there.

    Loaded Adobe Lightroom 6 and tried to process a photo. Within 30 seconds of entering in develop module I get either a complete freeze or the BSoD clock watchdog error.

    Talked to a friend at MS who said all she could find on that error was that it was possibly hardware related.

    Looking for some help please.

    Thanks!
      My Computer

  2. axe0's Avatar
    Posts : 14,785
    Windows 10 Pro
       #2

    Hi nosamk,

    Welcome to the 10forums.

    It seems your system has sometimes problems with generating a minidump from the memory dump.
    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
    Code:
    Event[2362]:
      Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2015-10-12T17:27:07.000
      Event ID: 1005
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-AVDU8OD
      Description: 
    Unable to produce a minidump file from the full dump file.
    If the Sound Blaster Recon3Di device is a headset, please disable every other sound device in sound manager (search sound).
    The program is causing lots of trouble, code below is just 1 error of the several errors.
    Code:
    10/13/2015 2:01 AM    Application Error    
    Faulting application name: CtHdaSvc.exe, version: 6.0.101.1042, time stamp: 0x55892600
    Faulting module name: CtHdaSvc.exe, version: 6.0.101.1042, time stamp: 0x55892600
    Exception code: 0xc0000005
    Fault offset: 0x0000367b
    Faulting process id: 0x1ec
    Faulting application start time: 0x01d1055b1689f6ac
    Faulting application path: C:\Windows\sysWow64\CtHdaSvc.exe
    Faulting module path: C:\Windows\sysWow64\CtHdaSvc.exe
    Report Id: 570a3e86-9e04-4b00-9d8c-a1f2bb3315d5
    Faulting package full name: 
    Faulting package-relative application ID:
      My Computers


  3. Posts : 75
    Windows 10
    Thread Starter
       #3

    Thanks axe. I'm running memtest currently. on 5th pass 16+ hours - trying to get to 8. I'll try this when its complete
      My Computer

  4. axe0's Avatar
    Posts : 14,785
    Windows 10 Pro
       #4

    Can you explain why you are running memtest?
    What memtest are you running?
      My Computers


  5. Posts : 75
    Windows 10
    Thread Starter
       #5

    found another thread on here with some getting random freezes and one of the suggestions was to run it.

    memtest86+ 5.01
      My Computer

  6. axe0's Avatar
    Posts : 14,785
    Windows 10 Pro
       #6

    nosamk said:
    found another thread on here with some getting random freezes and one of the suggestions was to run it.

    memtest86+ 5.01
    There is a problem with BSOD's, freezes and crashes, there are many causes for them, what for another solves the problem doesn't have to solve it for you and sometimes makes it only worse.

    I will check the dump now as I couldn't do it earlier due to internet problems.
    The internet speed at school isn't as good as home.
      My Computers


  7. Posts : 75
    Windows 10
    Thread Starter
       #7

    OK. I'll kill the test and run the sfc/scannow
      My Computer

  8. axe0's Avatar
    Posts : 14,785
    Windows 10 Pro
       #8




    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


  9. Posts : 75
    Windows 10
    Thread Starter
       #9

    Ran sfc/scannow twice. both results were "Windows Resource Protection did not find any integrity violations"

    also.
    soundblaster recon is not a headset
      My Computer


  10. Posts : 75
    Windows 10
    Thread Starter
       #10

    restarting now running driver verifer as instructed
      My Computer


 
Page 1 of 15 12311 ... LastLast

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

Designer Media Ltd
All times are GMT -5. The time now is 19:37.
Find Us




Windows 10 Forums