BSOD Clock watchdog error while playing doing anything like Games or video editing.

[andy3831]

hi all

was hoping i could get some help before i spend some money on a new cooling system that i may not need,

i started experiencing this issue about a month ago, when i played any games or did any video edit (during its compiling stage)

it seems to happen at random intervals and if im not gaming and just streaming or watching movies is fine, no overclocking done (no idea how and dont need too)

i just learn how to export a mini dump file, please let me know if there is more information required.

really appreciate any help in pointing me in the right direction

CPU i5-4690K CPU @ 3.50GHz
8GB RAM
win 10 64bit
nvidia GeForce GTX 760

==================================================
Dump File : 050217-3265-01.dmp
Crash Time : 2/05/2017 9:19:43 PM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000030
Parameter 2 : 00000000`00000000
Parameter 3 : ffffcb01`0898b180
Parameter 4 : 00000000`00000002
Caused By Driver : hal.dll
Caused By Address : hal.dll+4e490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14e7c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\050217-3265-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 14393
Dump File Size : 510,972
Dump File Time : 2/05/2017 9:20:11 PM
==================================================

==================================================
Dump File : 041217-3140-01.dmp
Crash Time : 12/04/2017 9:38:36 PM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000030
Parameter 2 : 00000000`00000000
Parameter 3 : ffffbd80`22f8b180
Parameter 4 : 00000000`00000002
Caused By Driver : hal.dll
Caused By Address : hal.dll+4e490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14e7c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\041217-3140-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 14393
Dump File Size : 235,820
Dump File Time : 12/04/2017 9:39:25 PM
==================================================

 

[johnbl]

you have to change the memory dump type from minidump to kernel memory dump, then provide the actual memory dump file from c:\windows\memory.dmp so it can be loaded into the windows debugger and read.
the file will be large over 500MB. You have to put it on a cloud server like microsoft onedrive, share the file for public access and post a link.

the mini memory dump could also be useful but will not contain proper debug info for this particular bugcheck.

all i can get form the text provided was that some hardware did not respond within the timeout period of 30 clock ticks.

as a generic fix, you would update the BIOS, remove any overclock drivers from the CPU and GPU
and install the current motherboard drivers from the motherboard vendors website.

since you have a nvidia card, make sure you update the ethernet drivers and motherboard sound drivers.
you might want to disable shadowplay if you are not using it. You might want to disable your gpu high def sound drivers if you do not get sound from your monitor via a hdmi cable.

hi all

was hoping i could get some help before i spend some money on a new cooling system that i may not need,

i started experiencing this issue about a month ago, when i played any games or did any video edit (during its compiling stage)

it seems to happen at random intervals and if im not gaming and just streaming or watching movies is fine, no overclocking done (no idea how and dont need too)

i just learn how to export a mini dump file, please let me know if there is more information required.

really appreciate any help in pointing me in the right direction

CPU i5-4690K CPU @ 3.50GHz
8GB RAM
win 10 64bit
nvidia GeForce GTX 760

==================================================
Dump File : 050217-3265-01.dmp
Crash Time : 2/05/2017 9:19:43 PM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000030
Parameter 2 : 00000000`00000000
Parameter 3 : ffffcb01`0898b180
Parameter 4 : 00000000`00000002
Caused By Driver : hal.dll
Caused By Address : hal.dll+4e490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14e7c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\050217-3265-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 14393
Dump File Size : 510,972
Dump File Time : 2/05/2017 9:20:11 PM
==================================================

==================================================
Dump File : 041217-3140-01.dmp
Crash Time : 12/04/2017 9:38:36 PM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000030
Parameter 2 : 00000000`00000000
Parameter 3 : ffffbd80`22f8b180
Parameter 4 : 00000000`00000002
Caused By Driver : hal.dll
Caused By Address : hal.dll+4e490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14e7c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\041217-3140-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 14393
Dump File Size : 235,820
Dump File Time : 12/04/2017 9:39:25 PM
==================================================

 

[saint19]

Hi and welcome to Tom's forum.

What driver version do you have? Did you install something new recently?

 

[JackNaylorPE]

One of the main causes of STOP: 0x00000101 is corrupted or missing system files... try running SFC scan

https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files

 

[andy3831]

my driver is
Driver date 29/12/2016
driver version 21.21.13.7653

i also installed davinci resolve (video editor) and mass effect andromeda

Hi and welcome to Tom's forum.

What driver version do you have? Did you install something new recently?

Ill try that now as well and check back in 24hrs too see if i get a crash during play
Edit: i got "Windows Resource Protection did not find any integrity violations."

One of the main causes of STOP: 0x00000101 is corrupted or missing system files... try running SFC scan

https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files

Edit: Might take me tomorrow to do as i need to wait for the system to crash first to overwrite my existing dump to a kernal memory one correct ?

i got one right now thats about 650mb called memory.dmp would that one be sufficient ?

you have to change the memory dump type from minidump to kernel memory dump, then provide the actual memory dump file from c:\windows\memory.dmp so it can be loaded into the windows debugger and read.
the file will be large over 500MB. You have to put it on a cloud server like microsoft onedrive, share the file for public access and post a link.

the mini memory dump could also be useful but will not contain proper debug info for this particular bugcheck.

all i can get form the text provided was that some hardware did not respond within the timeout period of 30 clock ticks.

as a generic fix, you would update the BIOS, remove any overclock drivers from the CPU and GPU
and install the current motherboard drivers from the motherboard vendors website.

since you have a nvidia card, make sure you update the ethernet drivers and motherboard sound drivers.
you might want to disable shadowplay if you are not using it. You might want to disable your gpu high def sound drivers if you do not get sound from your monitor via a hdmi cable.

 

[johnbl]

yep, that would be a kernel memory dump. go ahead and put it on a server and post a link

 

[andy3831]

here it is

https://1drv.ms/u/s!AkdoUxUd_p1TlX9kgt_NU4AJ-HXh

yep, that would be a kernel memory dump. go ahead and put it on a server and post a link

 

[johnbl]

overall, i suspect the system used too much power and the cpu reset
I would expect that the updated bios will help.
I would ignore the bugcheck until you get the bios update and driver updates.

the bugcheck was caused because of pending writes to your registry did not complete before the motherboard reset the CPU. The power supply should have prevented the restart of the cpu but a lot of them fake the signal to the motherboard. When the system booted, the CPU power was too low, the file system was marked dirty and had to run chkdsk, the CPU power was just coming up to level and it had to flush its cache. All in a 6 second window and the electronics dropped a signal between the CPUs. The updated bios will have better voltage/clock tables than the old version and should work much better.

do the updates and retest to see if you still get a bugcheck.

------
note: cpu launch date Q2'14
and your BIOS is dated 05/09/2014

go here and install the updated bios and drivers
https://www.asus.com/us/Motherboards/SABERTOOTH_Z97_MARK_2/HelpDesk_Download/

also pick up the new asus probe in the utilities directory to get rid of the bad version you have installed.

------------

your machine rebooted, it was up for 6 seconds and was dealing with various problems because of a CPU reset.

I would just look into why the machine rebooted (power problem)

you also have various other issues with the machine:

old drivers:
old logitech drivers, get updates
\SystemRoot\system32\DRIVERS\lvrs64.sys Mon Oct 22 19:11:24 2012
\SystemRoot\system32\DRIVERS\lvuvc64.sys Mon Oct 22 19:12:08 2012

netlimiter 4 installed:
C:\Program Files\Locktime Software\NetLimiter 4\nldrv.sys Sat Oct 10 01:31:36 2015

old intel drivers installed.
generic microsoft drivers running rather than the motherboard vendors driver updates.

old asus probe installed:
SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012
(update should be in the asus utilites on the motherboard website)

HUAWEI Mobile Connect - Bus Enumerate Device
\SystemRoot\System32\drivers\ew_jubusenum.sys Sat Nov 30 01:10:19 2013
(i would check for a update)


machine info:
BIOS Version 0902
BIOS Starting Address Segment f000
BIOS Release Date 05/09/2014
Manufacturer ASUSTeK COMPUTER INC.
Product SABERTOOTH Z97 MARK 2
Processor Version Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 3500MHz

 

[andy3831]

awesome, i just updated bios and Asus Probe, ill test this for 24-48hr and report back
Edit
i think it worked no crashes for 2 days!

thanks everyone !