[SOLVED] Computer BSOD with CLOCK_WATCHDOG_TIMEOUT when opening Opera GX ?

[wfwcowboys]

Basically the title, I don't know what the issue could be all I know is that it is the CLOCK_WATCHDOG_TIMEOUT BSOD and it happens around once a month when opening up Opera GX. I ran CHKDSK and it was fine, the computer is not overheating.

Specs:

B450 I AORUS PRO WIFI, Gigabyte Technology Co., Ltd., B450 I AORUS PRO WIFI-CF
CPU: AuthenticAMD AMD Ryzen 7 1700 Eight-Core Processor 8664, level: 23
16 logical processors, active mask: 65535
RAM: 17125695488 bytes (15.9GB)

Information:

Crash info from WhoCrashed:
On Tue 5/11/2021 11:30:09 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051121-10203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x293348)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFF8E00EE136180, 0xA)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 5/11/2021 11:30:09 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (ntfs+0x1ff87)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFF8E00EE136180, 0xA)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

 

[Colif]

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

try running https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html to update lan & WIFI drivers. (Your lan is made by Intel even though you have an AMD cpu, same as mine)

 

[wfwcowboys]

Alright here is the link. Will updating the LAN and wifi drivers using the downloads on the motherbaord website be fine? I updated the chipset and GPU drivers.

 

[Colif]

Will updating the LAN and wifi drivers using the downloads on the motherbaord website be fine?

the ones on the gigabyte website are 2 years old, the ones on Intel should be this year

 

[wfwcowboys]

the ones on the gigabyte website are 2 years old, the ones on Intel should be this year

Ok I will install them when I get the chance. I’m still using the drivers from 2019, I probably should have updated them earlier

 

[Colif]

i don't update drivers for most of my stuff, unless its auto. If it works, why fix it? Only ones I might look for are Nvidia. Or if I am bored.

The intel updater runs enough for me not to look for intel updates. I know better than to use the Gigabyte app centre as it isn't really helpful, there aren't that many drivers that change. It mostly updates un necessary apps.

I have an Aorus X570 elite WIFI so I sort of guessed what drivers you had. I did check though.

 

[Colif]

oh, I should have said, I sent dump files to a friend to convert, he will reply later with a conversion I can use to see if dumps show us anything useful.

 

[wfwcowboys]

oh, I should have said, I sent dump files to a friend to convert, he will reply later with a conversion I can use to see if dumps show us anything useful.

Sounds good, I looked through them with a few programs but I’m not experienced with them so I could only really find the information I originally provided. I tried to also do some detective work in event viewer but I don’t think I found anything that would point to something causing the crash.

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/nv4kz91h/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	051121-10203-01.dmp (May 11 2021 - 11:30:09)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	memory_corruption (Process: opera.exe)
Uptime:	0 Day(s), 4 Hour(s), 05 Min(s), and 00 Sec(s)

File information:	041321-10031-01.dmp (Apr 13 2021 - 16:56:34)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	memory_corruption (Process: python.exe)
Uptime:	0 Day(s), 9 Hour(s), 12 Min(s), and 37 Sec(s)

Motherboard MANUFACTURER: Gigabyte Technology Co., Ltd.
Motherboard PRODUCT: B450 I AORUS PRO WIFI-CF
There may be a BIOS update for your motherboard. I'm not sure if you are using Revision 1.0 of your motherboard or not. Let us know if you are.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[wfwcowboys]

I should be using the revision 1.0 of the board. Hopefully those results could help me figure this out.

 

[PC Tailor]

I know Colif will add to this when he returns but just some input:

A CLOCK_WATCHDOG_TIMEOUT (bugcheck 101) is better known as a CPU hang - as it means the CPU hasn't responded to a clock interrupt within a certain clock tick timeframe. These are CPU errors in MANY cases, and if you have dump files for these, consistent messages across all of them can often be more indicative that it is indeed the CPU faulting. But overall CLOCK_WATCHDOGs are almost exclusively CPU errors.

In the vast majority of cases, these are hardware faults (like said CPU), but in a small proportion they can be driver related. Minidumps aren't that useful for analysing 101 bugchecks due to the information it captures. Minidumps only save the processor context for the processor core that was awake and able to successfully run KeBugCheckEx and dump the crashdump, so you can't run any detailed analysis on it.

I will let Colif elaborate on what to try - as I know most prefer not to run Driver Verifier, but generally I'd go through the below - however do not do any of these until Colif states as such as he will be better placed to give next steps and will likely work through potential driver issues first:

• Run Driver Verifier as per these instructions. If you encounter another BSOD, please post the dump files / Sysnative Info so that we can review them.

If the dump files from Driver Verifier do not shed any more light or indicate any third party drivers then I would then do the following:

• Test your CPU by running Prime95 as per these instructions. and then feedback on the results.

 

[wfwcowboys]

I know Colif will add to this when he returns but just some input:

A CLOCK_WATCHDOG_TIMEOUT (bugcheck 101) is better known as a CPU hang - as it means the CPU hasn't responded to a clock interrupt within a certain clock tick timeframe. These are CPU errors in MANY cases, and if you have dump files for these, consistent messages across all of them can often be more indicative that it is indeed the CPU faulting. But overall CLOCK_WATCHDOGs are almost exclusively CPU errors.

In the vast majority of cases, these are hardware faults (like said CPU), but in a small proportion they can be driver related. Minidumps aren't that useful for analysing 101 bugchecks due to the information it captures. Minidumps only save the processor context for the processor core that was awake and able to successfully run KeBugCheckEx and dump the crashdump, so you can't run any detailed analysis on it.

I will let Colif elaborate on what to try - as I know most prefer not to run Driver Verifier, but generally I'd go through the below - however do not do any of these until Colif states as such as he will be better placed to give next steps and will likely work through potential driver issues first:

Thank you for the information. It would suck if the CPU is going, but it is a preowned ryzen 7 1700 that was heavily used for 2 years and possibly longer by the first owner so I guess it could happen. Also worth noting this board broke around a year ago and had some weird BIOS problem according to Gigabyte. I think they just say that for everything because I have never seen a board RMA not fixed with "new bios chip/re flashed bios" listed as the fix.

Driver Verifier scares me lol but I am willing to give it a shot. This problem only happens when I open Opera GX so I will reinstall it when testing.

 

[Colif]

Did you update the Intel drivers like I suggested? Have you crashed since?

Oct 16 2019

Netwtw08.sys

Intel(R) Wireless Networking driver

Jun 15 2020

e1r68x64.sys

Intel(R) Gigabit Adapter driver https://downloadcenter.intel.com/

not that bad but might be newer

your wingman drivers leave a lot to be desired, mainly as they from 2010. I don't think they involved, I just look at dates of drivers as often old ones can be cause
Logmein is getting old

Mar 30 2015

Hamdrv.sys

LogMeIn Hamachi Virtual Miniport driver http://www.logmein.com/

dumps don't tell me a great deal, and I wouldn't run Driver Verifer yet, its too soon.
if you have Ryzen master, go into its options and update it, there is a newer version than what you have.

try updating chipset drivers - https://www.amd.com/en/support/chipsets/amd-socket-am4/b450
not sure if bios update would help, its more for the 5000 series CPU

 

[wfwcowboys]

Did you update the Intel drivers like I suggested? Have you crashed since?

Oct 16 2019

Netwtw08.sys

Intel(R) Wireless Networking driver

Jun 15 2020

e1r68x64.sys

Intel(R) Gigabit Adapter driver https://downloadcenter.intel.com/

not that bad but might be newer

your wingman drivers leave a lot to be desired, mainly as they from 2010. I don't think they involved, I just look at dates of drivers as often old ones can be cause
Logmein is getting old

Mar 30 2015

Hamdrv.sys

LogMeIn Hamachi Virtual Miniport driver http://www.logmein.com/

dumps don't tell me a great deal, and I wouldn't run Driver Verifer yet, its too soon.
if you have Ryzen master, go into its options and update it, there is a newer version than what you have.

try updating chipset drivers - https://www.amd.com/en/support/chipsets/amd-socket-am4/b450
not sure if bios update would help, its more for the 5000 series CPU

The crashes are rare, about a month spacing, I updated the drivers you recommended. Ryzen master is not on my pc. I am currently installing the chipset drivers and the log me in drivers.

 

[Colif]

rare... great... so we won't know until it stops happening.

hmm, so its something that only happens every 20 days or so. Finding needles is easier. How to find it... maybe shows in scheduled tasks. Event viewer not the ideal place to search for causes of bsod.

can you run this, it makes a zip file, can you upload it to same place as dumps and give me a link, I see if it gives any clues - https://www.sysnative.com/forums/pages/bsodcollectionapp/

chipset drivers might help if its a cpu action

both errors are identical so what ever cause is, its the same both times. What I mean is, its not just the error codes, the actions during error are the same

Below is the stack text, the actions occurring just as error was recorded and in both errors its the same locations. the characters after the + are the memory locations.

fffff8027347ac88 fffff8027003ab42 : 0000000000000101 000000000000000c 0000000000000000 ffffc900dbe00180 : nt!KeBugCheckEx
fffff8027347ac90 fffff8026fe7541d : 0000000000000000 fffff8026af5a180 0000000000000246 0000000000206142 : nt!KeAccumulateTicks+0x1c8942
fffff8027347acf0 fffff8026fe759c1 : 0000000000205f00 0000000000134cc8 fffff8026af5a180 0000000000000001 : nt!KiUpdateRunTime+0x5d
fffff8027347ad40 fffff8026fe6f833 : fffff8026af5a180 0000000000000000 fffff80270831aa0 0000000000000000 : nt!KiUpdateTime+0x4a1
fffff8027347ae80 fffff8026fe781f2 : fffff58963b9c090 fffff58963b9c110 fffff58963b9c100 000000000000000c : nt!KeClockInterruptNotify+0x2e3
fffff8027347af30 fffff8026ff27f55 : 0000004d3345d468 fffff802708f3ba0 fffff802708f3c50 0000000000000000 : nt!HalpTimerClockInterrupt+0xe2
fffff8027347af60 fffff8026fff76fa : fffff58963b9c110 fffff802708f3ba0 0000000000000001 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff8027347afb0 fffff8026fff7c67 : 0000000000000000 fffff8027092e3b8 ffffc900db6cb078 fffff8026ff5950a : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff58963b9c090 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
STACK_COMMAND: kb

the only variance is the memory location after nt!KeAccumulateTicks is different.
I don't expect you to understand it, I don't myself but sometimes the actual driver responsible will show its face in stack text... sometimes, like 5% of the time at most.
I can tell its a cpu operation that stalled.

but it must be the same thing both times as every other line in error is the same. including memory locations.

 

[wfwcowboys]

rare... great... so we won't know until it stops happening.

hmm, so its something that only happens every 20 days or so. Finding needles is easier. How to find it... maybe shows in scheduled tasks. Event viewer not the ideal place to search for causes of bsod.

can you run this, it makes a zip file, can you upload it to same place as dumps and give me a link, I see if it gives any clues - https://www.sysnative.com/forums/pages/bsodcollectionapp/

chipset drivers might help if its a cpu action

both errors are identical so what ever cause is, its the same both times. What I mean is, its not just the error codes, the actions during error are the same

Below is the stack text, the actions occurring just as error was recorded and in both errors its the same locations. the characters after the + are the memory locations.

fffff8027347ac88 fffff8027003ab42 : 0000000000000101 000000000000000c 0000000000000000 ffffc900dbe00180 : nt!KeBugCheckEx
fffff8027347ac90 fffff8026fe7541d : 0000000000000000 fffff8026af5a180 0000000000000246 0000000000206142 : nt!KeAccumulateTicks+0x1c8942
fffff8027347acf0 fffff8026fe759c1 : 0000000000205f00 0000000000134cc8 fffff8026af5a180 0000000000000001 : nt!KiUpdateRunTime+0x5d
fffff8027347ad40 fffff8026fe6f833 : fffff8026af5a180 0000000000000000 fffff80270831aa0 0000000000000000 : nt!KiUpdateTime+0x4a1
fffff8027347ae80 fffff8026fe781f2 : fffff58963b9c090 fffff58963b9c110 fffff58963b9c100 000000000000000c : nt!KeClockInterruptNotify+0x2e3
fffff8027347af30 fffff8026ff27f55 : 0000004d3345d468 fffff802708f3ba0 fffff802708f3c50 0000000000000000 : nt!HalpTimerClockInterrupt+0xe2
fffff8027347af60 fffff8026fff76fa : fffff58963b9c110 fffff802708f3ba0 0000000000000001 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff8027347afb0 fffff8026fff7c67 : 0000000000000000 fffff8027092e3b8 ffffc900db6cb078 fffff8026ff5950a : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff58963b9c090 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
STACK_COMMAND: kb

the only variance is the memory location after nt!KeAccumulateTicks is different.
I don't expect you to understand it, I don't myself but sometimes the actual driver responsible will show its face in stack text... sometimes, like 5% of the time at most.
I can tell its a cpu operation that stalled.

but it must be the same thing both times as every other line in error is the same. including memory locations.

It seemed identical both times, the first time I opened Opera GX, freeze for a second, BSOD. The next time I was playing Pokemon trading card game online, it opened a window in Opera GX and same process followed by a BSOD. I uninstalled Opera GX but I really liked it, I will probably reinstall it and keep using it until I get the issue... or it just never happens again. I am running that program I will upload the results when I can.

 

[wfwcowboys]

Here is the file.

Edit: Also worth noting I ran the Opera GX installer while this was running, I don't know if that matters but I wanted to add it.

 

[Colif]

I know Colif will add to this when he returns but just some input:

A CLOCK_WATCHDOG_TIMEOUT (bugcheck 101) is better known as a CPU hang - as it means the CPU hasn't responded to a clock interrupt within a certain clock tick timeframe. These are CPU errors in MANY cases, and if you have dump files for these, consistent messages across all of them can often be more indicative that it is indeed the CPU faulting. But overall CLOCK_WATCHDOGs are almost exclusively CPU errors.

In the vast majority of cases, these are hardware faults (like said CPU), but in a small proportion they can be driver related. Minidumps aren't that useful for analysing 101 bugchecks due to the information it captures. Minidumps only save the processor context for the processor core that was awake and able to successfully run KeBugCheckEx and dump the crashdump, so you can't run any detailed analysis on it.

I will let Colif elaborate on what to try - as I know most prefer not to run Driver Verifier, but generally I'd go through the below - however do not do any of these until Colif states as such as he will be better placed to give next steps and will likely work through potential driver issues first:

I just noticed who replied... i know you said you replied to one today but I didn't notice it was this one

I see you ran prime95? or tried to. Did it succeed?

the error on the 11th is different. Its showing as a Trap Frame Recursion and I can't find anything on this in Google searches. The other clock watchdog timeout was a Zereod stack

lots of radar pre leaks. Radar is another badly named acronym but its essentially windows Memory leak detector. A lot of the errors I see in this report may be one offs and they work perfectly fine every other time.

 

[wfwcowboys]

I just noticed who replied... i know you said you replied to one today but I didn't notice it was this one

I see you ran prime95? or tried to. Did it succeed?

the error on the 11th is different. Its showing as a Trap Frame Recursion and I can't find anything on this in Google searches. The other clock watchdog timeout was a Zereod stack

lots of radar pre leaks. Radar is another badly named acronym but its essentially windows Memory leak detector. A lot of the errors I see in this report may be one offs and they work perfectly fine every other time.

Prime 95 was fine running for about 20 min but I can run it longer if needed this weekend.

 

[Colif]

yeah, let it run its stress test
You probably already know this - Prime 95 Guide: http://www.playtool.com/pages/prime95/prime95.html

I can find a few people reporting GX causing BSOD but none of them specify which bsod and its not like there is only 1 code. but its not normal for programs to cause bsod, they often just the victim.

 

[wfwcowboys]

yeah, let it run its stress test
You probably already know this - Prime 95 Guide: http://www.playtool.com/pages/prime95/prime95.html

I can find a few people reporting GX causing BSOD but none of them specify which bsod and its not like there is only 1 code. but its not normal for programs to cause bsod, they often just the victim.

Alright I will get Prime 95 running when I have a few hours. I assumed Opera GX was just triggering a fault in my system I never noticed before. I will probably try running prime 95 overnight.

 

[wfwcowboys]

Quick update. Since installing all the new drivers my pc has stopped doing a weird thing where after shutting down the screen goes blank and it stays on for a few seconds. This started happening after a major windows update but I just assumed it was always there.

 

[Colif]

Quick update. Since installing all the new drivers my pc has stopped doing a weird thing where after shutting down the screen goes blank and it stays on for a few seconds. This started happening after a major windows update but I just assumed it was always there.

well, thats something.