BSOD playing No Man's Sky : Clock_Watchdog_Timeout

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 10 Family 64-bit
       #1

    BSOD playing No Man's Sky : Clock_Watchdog_Timeout


    Hey,

    I'm having recurent Clock_Watchdog_Timeout BSOD while playing No Man's Sky.

    I tried to go through the MEMORY.DMP with WinDbg but it tells me that the dump is corrupted. Actually when the BSOD occurs it blocks on 15% (I let it there for more than an hour with no progression).

    You will find attached the V2 log. The dump weighs 15Go, I'll upload it if you need !


    Thanks

    Pump'
      My Computer


  2. Posts : 1,538
    Windows 8.1 Enterprise x64
       #2

    Code:
    Crash dump found at C:\WINDOWS\MEMORY.DMP
    Creation date: 12/04/2019 17:57:52
    Size on disk: 14569 MB
    Can you upload full memory dump?
      My Computer


  3. Posts : 41,475
    windows 10 professional version 1607 build 14393.969 64 bit
       #3

    Hi PumpkinVS,

    Welcome to the BSOD forum.

    The logs were in a foreign language and could not be scanned.

    Please change the default language to English and upload each a new V2 and DM:


    https://www.tenforums.com/tutorials/...dows-10-a.html
    Change Display Language in Windows 10

    BSOD - Posting Instructions


    After modifying the default language please perform the following steps:


    1) Uninstall Driver Easy 5.6.10 and any drivers that were installed with this software.
    If you are unable to identify the drivers installed by this software please install new drivers from the MSI website.

    2) Update the specs in the "My Computer" section:

    System Specs - Fill in at Ten Forums
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)



    3) Open administrative command prompt and type or copy and paste:
    4) sfc /scannow
    5) dism /online /cleanup-image /scanhealth
    6) dism /online /cleanup-image /restorehealth
    7) sfc /scannow
    8) chkdsk /scan
    9) wmic recoveros set autoreboot = false
    10) wmic recoveros set DebugInfoType = 7
    11) bcdedit /enum {badmemory}

    12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    13) Make sure that there is no over clocking while troubleshooting.

    14) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    15) Were you planning to upgrade Windows or were there problems upgrading?
      My Computer


  4. Posts : 8
    Windows 10 Family 64-bit
    Thread Starter
       #4

    Sure ! Here it is : Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

    EDIT : Ok I'm going through your instructions, Zbook.
      My Computer


  5. Posts : 1,538
    Windows 8.1 Enterprise x64
       #5

    Unfortunately, this memory dump cannot be read because it did not save properly. You have to crash again
      My Computer


  6. Posts : 8
    Windows 10 Family 64-bit
    Thread Starter
       #6

    You'll find attached the V2 and DM log generated after switching the display language to english.

    Concerning the other instructions :

    1) Done
    2) Done
    3-12) See results below :

    Microsoft Windows [Version 10.0.17763.864]
    (c) 2018 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files but was unable to fix some of them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.17763.771

    Image Version: 10.0.17763.864

    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.17763.771

    Image Version: 10.0.17763.864

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files and successfully repaired them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.
    Volume label is SSD.

    Stage 1: Examining basic file system structure ...
    948992 file records processed.
    File verification completed.
    20486 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    1037 reparse records processed.
    1179178 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    1037 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    115094 data files processed.
    CHKDSK is verifying Usn Journal...
    34211088 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    487806975 KB total disk space.
    347156276 KB in 698771 files.
    372420 KB in 115095 indexes.
    0 KB in bad sectors.
    1069967 KB in use by the system.
    65536 KB occupied by the log file.
    139208312 KB available on disk.

    4096 bytes in each allocation unit.
    121951743 total allocation units on disk.
    34802078 allocation units available on disk.

    C:\WINDOWS\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\DESKTOP-C0CIRM8\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Famille|C:\\WINDOWS|\\Device\\Harddisk1\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\DESKTOP-C0CIRM8\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Famille|C:\\WINDOWS|\\Device\\Harddisk1\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}

    C:\WINDOWS\system32>

    14) See attached

    15) Nope !

    I'll try to generate a new memory.dmp for tomorrow.


    Thanks
      My Computer


  7. Posts : 1,538
    Windows 8.1 Enterprise x64
       #7

    Check "Automatically manage paging file size for all drives" option
      My Computer


  8. Posts : 8
    Windows 10 Family 64-bit
    Thread Starter
       #8

    It was on automatic two days ago (BSOD were already occuring), I tried setting the sizes manually because of the corrupted memory.dmp.
    I'll change it back.

    And I don't know how, but a new BSOD (after seconds in the game) just passed over the 15%, here is the - I hope - complete dump : Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
      My Computer


  9. Posts : 41,475
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    1) First scannow:
    Code:
    Windows Resource Protection found corrupt files but was unable to fix some of them.
    2) Second scannow:
    Code:
    Windows Resource Protection found corrupt files and successfully repaired them.


    3) For Virtual Memory:
    a) move the dot from custom size to system managed size
    b) check the box to Automatically manage paging size for all drives
    c) reboot to save settings

    4) Turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10

    5) Run the Avast uninstall tool:
    Avast Uninstall Utility | Download aswClear for Avast Removal
    Avast Removal Tool - Avast Remover

    6) List and uninstall all non-Microsoft antivirus software
    (This includes always on and manual software.)
    (This includes running the applicable antivirus uninstall tools for any AV that could have been incompletely uninstalled)

    7) List and uninstall all non-Microsoft firewall software

    8) List all Microsoft and non-Microsoft drive encryption software.
    Uninstall all non-Microsoft disk encryption software

    9) Uninstall Malwarebytes using the applicable uninstall tool:
    https://downloads.malwarebytes.com/file/mb_clean

    10) Open administrative command prompt and type or copy and paste:
    chkdsk /r /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /r /v
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot


    11) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
    Read Chkdsk Log in Event Viewer in Windows 10


    12) For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

    13) The latest log collector displayed:
    Code:
    Driver Easy 5.6.10                                                                                               5.6.10           Easeware                           20190524
    Please make sure that the Driver Easy software is uninstalled

    14) Reinstall all drivers displayed on the MSI website
      My Computer


  10. Posts : 1,538
    Windows 8.1 Enterprise x64
       #10

    The crash dump you sent is also damaged. Therefore test your RAM with HCI memtest Test RAM with HCIDesign Memtest | Sysnative Forums and disks with SeaTools SeaTools for DOS - Hard Drive Diagnostic
      My Computer


 

  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 03:48.
Find Us




Windows 10 Forums