Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows 10 hanging at random


  • Please log in to reply
3 replies to this topic

#1 xii4obear

xii4obear

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:12:29 AM

Posted 10 April 2016 - 01:26 AM

Hi guys, 

 

Windows 10 Pro retail 64 bits.

i5-6600K, 16GB Kingston 2133mhz DDR4, MSI GTX970, Asus Z170 Pro Gaming, EVGA Supernova 650W, Samsung 840 240GB, Sandisk Extreme PRO 480GB, 

 

The graphics card and SSDs are from my build before I moved. I'm booting off the Samsung SSD. I put the build together a few weeks back, worked fine until recently. Problems began with a BSOD, machine check exception. After it restarted itself it got stuck at automatic repairs. Then it refused to even boot, no video signal etc.

 

I turned it off, reseated the gpu and RAM, and it worked again. After this, sometimes the system will just freeze up, audio cuts out. No blue screen, no error messages, but I am able to restart just fine. I thought it might be a windows problem, so I reinstalled Windows. Problem persists. I'm not sure where to go from here. 

 

The hangs happen at about random, when I'm playing a game, or when I'm browsing the web. Sometimes it hangs right after windows loads, after I enter my password. The screen doesn't blackout, but remains at what it was displaying when the hang occurs. Unable to move cursor or CTRL-ALT-DEL. 


Edited by xii4obear, 10 April 2016 - 06:35 AM.


BC AdBot (Login to Remove)

 


#2 xii4obear

xii4obear
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:12:29 AM

Posted 10 April 2016 - 06:33 AM

Update: I've started getting BSODs, they tell me clock_watchdog_timeout. These BSODs took lesser and lesser time before appearing from when I put my password in. Then every time I boot into windows I'll get a BSOD. I turned off the power at the source and waited for a bit before turning it back on, and I did not get a BSOD. I'm attaching the files below. I am unable to get a performance monitor report, it's stuck at collecting data for 60 seconds. 

 

Update Update: The freezing without BSOD is back now. arghwhy.

Attached Files


Edited by xii4obear, 10 April 2016 - 08:59 AM.


#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:29 AM

Posted 10 April 2016 - 05:07 PM

Your UEFI/BIOS (version 1206) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a recent update.

Only 5 Windows Update hotfixes installed.  Most build 10586 (TH2/1511) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

You have 3 hard drives.  What is the age of your 650 watt EVGA Power Supply?

 

CLOCK_WATCHDOG_TIMEOUT is frequently a hardware problem - as is the MACHINE_CHECK_EXCEPTION

Please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

 

Of the 7 memory dumps, 6 are the CLOCK_WATCHDOG_TIMEOUT and one is a STOP 0xA

The STOP 0xA blames your Intel video drivers. (it's the 3rd one from the bottom in the following list)

Is it possible for you to disable the Intel video in the BIOS/UEFI and see if that helps?

 

 

Analysis:
The following is for informational purposes only.
**************************Sun Apr 10 06:42:53.531 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\041016-6531-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
System Uptime: 0 days 0:02:12.196
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, ffffd00058718180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd00058718180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Apr 10 06:38:46.522 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\041016-5671-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
System Uptime: 0 days 0:00:48.188
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, ffffd001d2d18180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd001d2d18180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Apr 10 06:33:06.535 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\041016-5640-02.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
System Uptime: 0 days 0:00:18.201
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, ffffd001b6318180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd001b6318180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  lsass.exe
FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Apr 10 06:28:27.525 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\041016-7375-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
System Uptime: 0 days 0:01:18.189
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, ffffd00193318180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd00193318180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Apr 10 06:26:30.128 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\041016-7984-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
System Uptime: 0 days 0:23:27.793
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : igdkmd64.sys ( igdkmd64+3c90d )
BugCheck A, {0, f, 0, fffff800d77a12b9}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 000000000000000f, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800d77a12b9, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  AV_igdkmd64!Unknown_Function
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  1206
  BIOS Release Date             03/07/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Apr 10 05:26:30.538 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\041016-5640-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
System Uptime: 0 days 0:00:42.203
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, ffffd00147718180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd00147718180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Apr 10 05:25:09.539 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\041016-7031-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
System Uptime: 0 days 0:01:36.203
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, ffffd00184118180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd00184118180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
**************************Sun Apr 10 06:42:53.531 2016 (UTC - 4:00)**************************
e1d64x64.sys                Thu Jun 18 12:44:38 2015 (5582F576)
nvhda64v.sys                Mon Sep 21 05:44:17 2015 (55FFD171)
TeeDriverW8x64.sys          Thu Oct  8 14:13:00 2015 (5616B22C)
intelppm.sys                Thu Oct 29 22:09:51 2015 (5632D16F)
iaStorA.sys                 Wed Nov  4 05:27:49 2015 (5639DDA5)
IntcDAud.sys                Tue Jan 26 06:46:55 2016 (56A75CAF)
idmwfp.sys                  Wed Jan 27 11:45:02 2016 (56A8F40E)
igdkmd64.sys                Tue Feb  2 21:18:16 2016 (56B16368)
asmtxhci.sys                Thu Feb  4 02:22:05 2016 (56B2FC1D)
asmthub3.sys                Thu Feb  4 02:22:26 2016 (56B2FC32)
nvlddmkm.sys                Mon Mar 21 21:44:53 2016 (56F0A395)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Apr 10 06:33:06.535 2016 (UTC - 4:00)**************************
sshid.sys                   Tue Jan 26 11:51:40 2016 (56A7A41C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Apr 10 05:26:30.538 2016 (UTC - 4:00)**************************
IntcDAud.sys                Thu Nov 12 07:58:35 2015 (56448CFB)
igdkmd64.sys                Mon Jan 25 16:18:24 2016 (56A69120)

 

http://www.carrona.org/drivers/driver.php?id=e1d64x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=idmwfp.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=sshid.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys



 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#4 xii4obear

xii4obear
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:12:29 AM

Posted 11 April 2016 - 02:08 AM

Hi, thanks for the analysis. Windows update shows no updates available. The PSU is brand new, along with my CPU, RAM, motherboard and case. The only old components in my build are the GPU and storage devices. 

 

I'm pretty certain that the root cause of my problems is my processor. There has been several reports from other forums that hanging and freezing isn't uncommon to the new Skylake platform. 

 

After my second post, the problem had become so bad that I would get a freeze about 1-5 minutes after I put in my password, then I was unable to boot into windows at all. I disabled all but a single core on my processor, and I'm able to boot into windows successfully, and there has been no freezing so far. Others have reported luck with disabling C-states in BIOS. I'm currently trying out different options so I can still use the computer in the meantime. I have contacted my retailer, MSY, whom were less than enthusiastic, and bounced me to the online department. I have also put in a warranty request with Intel. 

 

Anyone finding this thread from Google, who thinks you might have the same problem as I do, try disabling your cores. Intel also has a nifty cpu diagnostic tool available on their website. 






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users