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.



  • Please log in to reply
1 reply to this topic

#1 Kris Toph

Kris Toph

  • Members
  • 1 posts
  • Local time:08:19 AM

Posted 20 June 2015 - 11:41 AM

I had read another thread that dealt with this issue with the CLOCK_WATCHDOG_TIMEOUT error. Since that thread was locked, I thought I might repost it here with my info and see if I can't get some help.


Here was what the thread asked for:



:welcome:  to the forum.


CLOCK_WATCHDOG_TIMEOUT is generally considered as a hardware BSOD. Although rare, some faulty drivers can also cause this error. Before jumping to any conclusion, please follow the below instructions to collect some basic info.


1 ) A Speccy snapshot of your system.


 Read the instructions in the below guide and post the web link Speccy gives.





2 ) Open C:\Windows\Minidump folder. If there are any files with .dmp extension, zip the entire folder and upload to any free file hosting site like Mediafire - http://www.mediafire.com/

If you are getting a permission error, disable UAC and restart the system.
Post the download link to it in next reply. 



3 ) Download and run Minitoolbox from http://www.bleepingcomputer.com/download/minitoolbox/

    Run the tool and only select the following tick boxes.
    -List last 10 Event viewer errors
    -List installed programs
    -List devices
    -List users, partition and memory size
Now click "Go" and post the output in next reply  (or upload the result.txt with dump files) 
4 ) Also post the exact model number of your system. If you can find specific pattern for the crash, that will also be helpful (ie playing videos, games or a specific app )

Edited by Anshad Edavana, 01 July 2013 - 11:36 PM.



And the links to my info


1: http://speccy.piriform.com/results/XTEeWfiYMnJpCJOmAgRgnMW

2: http://www.mediafire.com/download/c3rbencrhhyvz5n/Minidumpcopy.zip

3: http://www.mediafire.com/view/ru8z74u2al628ue/Result.txt

4: Unsure of any model number, but as for a pattern it seems to happen when I play online games (World of Warcraft, Final Fantasy XIV: ARR) and may have happened once or twice while watching videos/running a bunch of open tabs.


Thanks for the help!

BC AdBot (Login to Remove)


#2 usasma


    Still visually handicapped (avatar is memory developed by my Dad

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

Posted 22 June 2015 - 04:34 AM

When I try to access your data at MediaFire, it wants me to login.  I won't do that.

A second attempt actually let me access the dump files.

FYI - I will not accept MediaFire links in the future - as this is a scam to get more "clicks" on their website.

Please use another online file hosting service (I prefer OneDrive or even DropBox) if you are unable to upload things to this forum.


Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum):  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

As STOP 0x101 errors are frequently hardware (but not always), please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html


Early on in this series of errors you had differing errors that seemed to point to hardware or low-level drivers.  The system has now settled on a series of STOP 0x101 errors.

I strongly suggest running the hardware diagnostics I mentioned above.  We'll still work on low-level drivers (and other things that may pop up in the reports) - but the hardware diagnostics are essential at this point.


Please be sure to visit the Gigabyte support website and:\

- update your BIOS/UEFI  It currently dates from 2014 and is version F2

- update the rest of the drivers from the website, particularly any that date from after the release of Win8.1 (17 Oct 2013)


Also, get ALL available Windows Updates.  You may have to go back several times - so just keep going back and updating until the system shows no further updates are available.


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! :

wanatw64.sys                Mon Apr 11 18:07:10 2005 (425AF50E)
Wan Miniport (ATW) America Online}http://www.aol.com
lv302a64.sys                Sat Jul 26 11:06:31 2008 (488B3D77)
Logitech Camera driver}http://www.logitech.com/index.cfm/support_downloads/downloads/&cl=us,en
LVUSBS64.sys                Sat Jul 26 11:06:36 2008 (488B3D7C)
Logitech Camera driver}http://www.logitech.com/index.cfm/support_downloads/downloads/&cl=us,en
lvrs64.sys                  Sat Jul 26 11:09:02 2008 (488B3E0E)
Logitech Camera driver}http://www.logitech.com/index.cfm/support_downloads/downloads/&cl=us,en
LV302V64.SYS                Sat Jul 26 11:09:08 2008 (488B3E14)
Logitech Camera driver}http://www.logitech.com/index.cfm/support_downloads/downloads/&cl=us,en
tscusb2a.sys                Fri Jun 18 13:43:29 2010 (4C1BB041)
 Tascam US122MKII USB Audio/Midi Interface

tscusb2a.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.
tascusb2.sys                Fri Jun 18 13:44:51 2010 (4C1BB093)
  Tascam US122MKII USB Audio/Midi Interface
tascusb2.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.
Please remove (uninstall) this one:
VKbms.sys                   Thu Sep 30 12:16:33 2010 (4CA4B7E1)
HID mini driver for USB Fx2 Device  (Razer driver)}http://www.razersupport.com/index.php?_m=downloads&_a=view
tap0901.sys                 Thu Nov 24 13:50:27 2011 (4ECE91F3)
TAP-Win32 Adapter V9 or[br]OpenVPN driver or COMODO}http://openvpn.net/index.php/open-source/downloads.html or http://forums.comodo.com/index.php?action=dlattach;topic=17220.0;attach=17692  Requires registration
Please remove (uninstall) this one:
Abyssus.sys                 Wed Jan  9 00:31:18 2013 (50ED00A6)
Razer Abyssus - BSOD issues with 2009 and earlier versions (Win7/Win8)}http://www.razersupport.com/index.php?_m=downloads&_a=view
Please remove (uninstall) this one:
RTCore64.sys                Mon Mar 11 01:32:06 2013 (513D6C56)
RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)}http://www.guru3d.com/category/rivatuner/

AppleCharger.sys            Sun Oct 27 21:59:21 2013 (526DC4F9)
GIGABYTE On/Off Charge driver. See here for details -

Here's my analysis.  I've only copied the latest memory dump (in order to save space)


The following is for informational purposes only.

[font=lucida console]**************************Sat Jun 20 11:48:37.043 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\062015-7062-01.dmp]
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: [B]9600[/B].17085.amd64fre.winblue_gdr.140330-1035
System Uptime:[B]0 days 0:56:48.813[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]101, {20, 0, ffffd00020640180, 4}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000101]CLOCK_WATCHDOG_TIMEOUT (101)[/url]
Arg1: 0000000000000020, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd00020640180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
PROCESS_NAME:  ffxiv.exe
  BIOS Version                  F2
  BIOS Release Date             11/25/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-78LMT-USB3 6.0
[B][U]3rd Party Drivers:[/U][/B]
[COLOR=BLUE][B]The following is for information purposes only.[/B][/COLOR]
[COLOR=RED][B]Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.[/B][/COLOR]
[code][font=lucida console]**************************Sat Jun 20 11:48:37.043 2015 (UTC - 4:00)**************************
[COLOR=RED][B]wanatw64.sys                Mon Apr 11 18:07:10 2005 (425AF50E)[/B][/COLOR]
[COLOR=RED][B]LVUSBS64.sys                Sat Jul 26 11:06:36 2008 (488B3D7C)[/B][/COLOR]
[COLOR=RED][B]VKbms.sys                   Thu Sep 30 12:16:33 2010 (4CA4B7E1)[/B][/COLOR]
ScpVBus.sys                 Sun May  5 17:31:26 2013 (5186CFAE)
Rt630x64.sys                Fri May 10 05:59:08 2013 (518CC4EC)
rtwlanu.sys                 Wed Jul 10 10:48:31 2013 (51DD743F)
[COLOR=RED][B]AppleCharger.sys            Sun Oct 27 21:59:21 2013 (526DC4F9)[/B][/COLOR]
xusb22.sys                  Tue Mar 18 04:18:41 2014 (53280161)
RTKVHD64.sys                Wed May 14 06:28:52 2014 (53734564)
nvhda64v.sys                Thu Oct  9 13:02:27 2014 (5436BFA3)
rzpnk.sys                   Fri Oct 17 15:38:10 2014 (54417022)
nvvad64v.sys                Thu Nov 20 10:33:54 2014 (546E09E2)
NvStreamKms.sys             Tue Mar 17 02:19:52 2015 (5507C788)
nvlddmkm.sys                Wed Apr  8 16:32:37 2015 (55259065)
**************************Sat Jun 20 01:42:13.028 2015 (UTC - 4:00)**************************
[COLOR=RED][B]RTCore64.sys                Mon Mar 11 01:32:06 2013 (513D6C56)[/B][/COLOR]
**************************Thu Apr 30 12:45:11.753 2015 (UTC - 4:00)**************************
[COLOR=RED][B]lv302a64.sys                Sat Jul 26 11:06:31 2008 (488B3D77)[/B][/COLOR]
[COLOR=RED][B]lvrs64.sys                  Sat Jul 26 11:09:02 2008 (488B3E0E)[/B][/COLOR]
[COLOR=RED][B]LV302V64.SYS                Sat Jul 26 11:09:08 2008 (488B3E14)[/B][/COLOR]
[COLOR=RED][B]tscusb2a.sys                Fri Jun 18 13:43:29 2010 (4C1BB041)[/B][/COLOR]
[COLOR=RED][B]tascusb2.sys                Fri Jun 18 13:44:51 2010 (4C1BB093)[/B][/COLOR]
[COLOR=RED][B]tap0901.sys                 Thu Nov 24 13:50:27 2011 (4ECE91F3)[/B][/COLOR]
Rt630x64.sys                Tue Jun 12 09:37:53 2012 (4FD74631)
[COLOR=RED][B]Abyssus.sys                 Wed Jan  9 00:31:18 2013 (50ED00A6)[/B][/COLOR]
rzpmgrk.sys                 Thu Apr 17 15:36:12 2014 (53502D2C)
xspltspk.sys                Wed Jun 11 16:59:54 2014 (5398C34A)
rzendpt.sys                 Tue Dec 30 04:32:47 2014 (54A2713F)
rzudd.sys                   Tue Dec 30 04:32:50 2014 (54A27142)
cpuz138_x64.sys             Thu Feb 26 02:04:34 2015 (54EEC582)
tscusb2a.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.
tascusb2.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 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.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users