Hi Garrett,
You say have tried everything but obviously you haven't or you would have already fixed it.
We need data in order to help. What have you done besides what you listed above? The CLOCK_WATCHDOG_TIMEOUT error has many causes.
- Are you using Windows? If so which version?
- What model is your motherboard?
- Have you tried reseating RAM, video card, drive cables?
- Checked other cables?
- Updated drivers? Frequent cause of problem.
- Updated Windows?
- Did you install any apps just before the error started appearing?
Run DISM and then SFC from the Command Prompt:
- Type Command Prompt (Admin) in the Start menu search bar, then right-click and select Run as administrator to open an elevated Command Prompt.
- Type the following command and press Enter: DISM /online /cleanup-image /restorehealth
- Wait for the command to complete. The process can take up to 20 minutes, depending on your system's health. The process seems stuck at certain times, but wait for it to complete.
- When the process completes, type sfc /scannow and press Enter.
CHKDSK is another Windows system tool that checks your file structure. Unlike SFC, CHKDSK scans your entire drive for errors, whereas SFC scans your Windows system files specifically. Like SFC, run the CHKDSK scan from the Command Prompt to fix your machine.
- Type command prompt in your Start menu search bar, then right-click the best match and select Run as administrator. (Alternatively, press Windows Key + X, then select Command Prompt (Admin) from the menu.)
- Next, type chkdsk /r and press Enter. The command will scan your system for errors and fix any issues along the way.
Are you overclocking? Turn it off.
Run Windows Memory Diagnostics? - Type Windows Memory Diagnostic into your Start menu search bar. Set it to run on next boot.
Let us know how it goes or if you need further help with any of the above procedures.
crwdns2934105:0crwdne2934105:0
crwdns2934113:0crwdne2934113:0
crwdns2915270:0crwdne2915270:0
crwdns2889612:0crwdne2889612:0
1
crwdns2942205:01crwdne2942205:0
Unfortunately watchdog errors are... broad. They could be just about anything. You don't mention anything about your RAM?
Run a Memtest86 on them and see what the results tell you.
After that, I would recommend pulling your boot drive and use some other drive, even if just temporarily, and see if you crash again.
crwdns2934271:0crwdnd2934271:0 Justin Castle crwdne2934271:0