Computer BSOD - clock_watchdog_timeout error

Anonymous

I have updated my cpu, gpu, ram, psu, and still have an unknown crash. I have amd ryzen 5700xt, rog strix x570 - e gaming wifi II, and msi 850w psu.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------

BUGCHECK_CODE:  0

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  EngHost.exe

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

FAILURE_BUCKET_ID:  0x0_ANALYSIS_INCONCLUSIVE!unknown_function

FAILURE_ID_HASH:  {c1cb3be3-2935-5af0-8ba5-f15df2c5aaf2}

Followup:     MachineOwner

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

43 answers

Jonathan Deives 81,795 Reputation points Independent Advisor

2025-04-23T02:21:12+00:00

The minidump files do not indicate any driver or hardware causes, only memory corruption.
Was this answer helpful?

0 comments No comments
Anonymous

2025-04-23T02:27:38+00:00

haha. hmmm so just replace ram then?
Was this answer helpful?

0 comments No comments
Jonathan Deives 81,795 Reputation points Independent Advisor

2025-04-23T02:28:43+00:00

Memory corruption is not necessarily related to RAM.

Try forcing Windows to show failed drivers and produce minidump files, enable Driver Verifier for this;

https://answers.microsoft.com/en-us/windows/for...

Let the BSOD happen 3 times and then see if the files were created.

Before running Driver Verifier, create a new system restore point.

If you have problems starting Windows after enabling Driver Verifier, follow these steps:

Start your PC, as soon as Windows tries to load (spinning dots appear), press and hold the power button for 5 to 10 seconds to perform a forced shutdown

Do this two or three times.

Windows will boot into the Recovery Environment.

Go to Troubleshoot > Advanced Option > Startup Settings and click Restart.

When restarting, press 4 to enter safe mode.

Open command prompt as administrator, run these two commands and restart your PC.

verifier /reset

verifier /bootmode resetonbootfail
Was this answer helpful?

0 comments No comments
Anonymous

2025-04-23T04:22:23+00:00

here is the new minidump after all that. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Showed up each BSOD

https://www.dropbox.com/scl/fi/nghn9phvdf78p9h3400u2/042325-5703-01.dmp?rlkey=pvt4e50rjsm4uxv622xrjc22d&st=1635u34y&dl=0
Was this answer helpful?

0 comments No comments
Jonathan Deives 81,795 Reputation points Independent Advisor

2025-04-23T04:27:12+00:00

The minidump file indicates that the cause of the BSOD is "igovsd.sys"

It is usually related to the Asus audio driver, try downloading this driver and see if the problem persists.

https://dlcdnets.asus.com/pub/ASUS/mb/01AUDIO/D...

___________________________________________________________

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

___________________________________________________________
Was this answer helpful?

0 comments No comments