Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

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.

Latest News: Loud Sound From Fire Alarm System Shuts Down Nasdaq's Scandinavian Data Center

Featured Deal: Get 96% off the MCSA SQL Server Training Deal

Clock Watchdogs Timeout BSOD

Started by ChurroVape , Jan 15 2017 10:53 PM

Please log in to reply

1 reply to this topic

#1 ChurroVape

Members
1 posts
OFFLINE

Local time:07:52 AM

Posted 15 January 2017 - 10:53 PM

I just got the BSOD with the error being "Clock Watchdog Timeout"

I have the SysnativeFileCollectionApp.zip attached but the perfmon report wasn't doing anything for about 2 mins.

· System Manufacturer - ASUS
· Exact model number - M Series M11BB

· Video Card - GeForce GT 640

· OS - Windows 10 Home

· x64 Bit

(Not sure what OS this computer came with off the shelf but when i bought it Windows 10 Home was installed)

I bought this computer a few months ago from someone off craigslist as a temporary PC, when i got it home i did a fresh install and everything has been just fine until now. I use it for low-mid graphic gaming and basic internet browsing.

Attached Files

SysnativeFileCollectionApp.zip 1.45MB 1 downloads

Back to top

BC AdBot (Login to Remove)

BleepingComputer.com
Register to remove ads

#2 usasma

Still visually handicapped (avatar is memory developed by my Dad

BSOD Kernel Dump Expert
25,089 posts
OFFLINE

Gender:Male
Location:Southeastern CT, USA
Local time:10:52 AM

Posted 17 January 2017 - 09:13 AM

Your UEFI/BIOS (version 0307) dates from 2013. Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system. If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it. WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Only 5 Windows Update hotfixes installed. Most build 14393 (1607) 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.

This is most likely a hardware problem - although it can also be a compatibility issue or a low-level driver problem

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

Please run ALL of the tests and let us know the results.

More info on the STOP 0x101 errors: http://www.carrona.org/bsodindx.html#0x00000101

More info on the STOP 0x124 errors: http://www.carrona.org/bsodindx.html#0x00000124

If all of the diagnostics pass, then try running Driver Verifier according to these instructions: http://www.carrona.org/verifier.html

~~More to follow in this spot after I post this reply......~~

Update your networking drivers (wired and wireless) as some of them date from 2013

Update your USB Dual Shock controller as it's drivers date from 2013 (or, uninstall it's software and physically remove the device from your system for testing)

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Sun Jan 15 21:45:11.309 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011517-23203-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 10:34:36.031
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 101, {30, 0, ffffa5810ce55180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffa5810ce55180, 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: MEMORY_CORRUPTION_LARGE
BIOS Version                  0307
BIOS Release Date             08/07/2013
Manufacturer                  ASUSTeK COMPUTER INC.
Product Name                  M11BB
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 13 11:18:30.067 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121316-41015-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.479.amd64fre.rs1_release.161110-2025
System Uptime:0 days 0:00:06.788
Probably caused by :AuthenticAMD
BugCheck 124, {0, ffffd70f7f8bb8f8, 0, 0}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffd70f7f8bb8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR: 0x124_AuthenticAMD
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 28 10:05:03.301 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\112816-32828-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 0:00:05.022
Probably caused by :AuthenticAMD
BugCheck 124, {0, ffffa78389f528f8, 0, 0}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffa78389f528f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR: 0x124_AuthenticAMD
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below. Click on "Show" to reveal them.

Spoiler

3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Sun Jan 15 21:45:11.309 2017 (UTC - 5:00)**************************
amd_sata.sys                Fri Nov 30 04:00:42 2012 (50B875BA)
amd_xata.sys                Fri Nov 30 04:00:46 2012 (50B875BE)
au630x64.sys                Thu Mar 14 05:44:07 2013 (51419BE7)
ScpVBus.sys                 Sun May  5 17:31:26 2013 (5186CFAE)
netr28x.sys                 Fri Jun 13 07:50:31 2014 (539AE587)
RTKVHD64.sys                Tue Jun 16 06:55:05 2015 (55800089)
 

**Windows 10 released on 29 July 2015**
 

rzpnk.sys                   Wed Sep 16 20:16:35 2015 (55FA0663)
rzpmgrk.sys                 Thu Sep 17 14:42:44 2015 (55FB09A4)
RzSurroundVAD.sys           Mon Feb 15 02:57:35 2016 (56C184EF)
rzendpt.sys                 Wed Jun 15 23:43:23 2016 (5762205B)
rzudd.sys                   Wed Jun 15 23:43:26 2016 (5762205E)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
nvvad64v.sys                Tue Oct  4 03:20:09 2016 (57F35829)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 13 11:18:30.067 2016 (UTC - 5:00)**************************
avgloga.sys                 Tue Feb 16 09:04:03 2016 (56C32C53)
avgrkx64.sys                Wed Jun  1 07:16:31 2016 (574EC40F)
avguniva.sys                Mon Jun 20 09:22:11 2016 (5767EE03)
avgmfx64.sys                Mon Sep 26 12:19:13 2016 (57E94A81)
avgidsha.sys                Wed Oct  5 10:01:00 2016 (57F5079C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov 26 12:04:41.865 2016 (UTC - 5:00)**************************
rzendpt.sys                 Tue Aug 11 07:13:46 2015 (55C9D8EA)
rzudd.sys                   Tue Aug 11 07:13:50 2015 (55C9D8EE)
avgdiska.sys                Fri May 13 01:52:02 2016 (57356B82)
avgwfpa.sys                 Wed Jul 27 09:24:37 2016 (5798B615)
nvvad64v.sys                Thu Sep 22 12:46:30 2016 (57E40AE6)
avgidsdrivera.sys           Mon Oct 17 12:19:07 2016 (5804F9FB)
avgfwd6a.sys                Wed Oct 19 09:07:00 2016 (58076FF4)
avgldx64.sys                Wed Oct 19 09:13:30 2016 (5807717A)
nvlddmkm.sys                Thu Nov 10 17:01:49 2016 (5824EE4D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Nov  3 11:29:04.263 2016 (UTC - 5:00)**************************
nvlddmkm.sys                Tue Oct 25 15:38:31 2016 (580FB4B7)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 28 17:38:39.060 2016 (UTC - 5:00)**************************
nvlddmkm.sys                Sat Oct 22 00:55:42 2016 (580AF14E)

Edited by usasma, 17 January 2017 - 09:16 AM.

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.