(riješeno) Win 10 error - novo računalo

[Mr.Black]

Amd Ryzen 3, 1300X, gigabyte ga-a320m.ds2, patriot 4 gb, toshiba 1 tb, gigabyte rx 550, mission 550W....kod instalacije win10 baca error clock_watchdog_timeout....??

[Mommistake]

Simply put, it’s your processor. Or, as you often hear it referred to, your CPU.

The CLOCK_WATCHDOG_TIMEOUT error means that your processor is having trouble with cooperation from its cores and threads. Threads are tasks taken by cores, and some cores can take many threads simultaneously. The problem here is that a thread is waiting for a proper response from another thread — or a core is waiting for a response from another core — and those responses aren’t coming. Therefore, you get this BSoD error.

Home Resources BlogA Guide to the CLOCK_WATCHDOG_TIMEOUT Blue Screen of Death Error

Search here...
A Guide to the CLOCK_WATCHDOG_TIMEOUT Blue Screen of Death Error
By Steve Horton January 22, 2013 Blue Screen of Death, bsod, CLOCK_WATCHDOG_TIMEOUT 35 Comments
Error Name: CLOCK_WATCHDOG_TIMEOUT

Before I explain what this error means and how to fix it, I’m going to give you a little background information. First off, you’ve now encountered one of many infamous “Blue Screen of Death” errors.
You may have encountered them before. Depending on which version of Windows you’re using, you’re either seeing something that looks like this:

CLOCK_WATCHDOG_TIMEOUT
Blue Screen of the Past
Or this:

CLOCK_WATCHDOG_TIMEOUT
Clock Watchdog Timeout in Windows 8
What’s causing my problem?

Simply put, it’s your processor. Or, as you often hear it referred to, your CPU.
Graphics cards — or GPUs — determine the visual elements of what you see on your screen, while memory — or RAM — determines how much you can be doing at once. Hard drives serve as storage for your files and folders, and your processor is the raw power behind everything being done in your computer.
The CLOCK_WATCHDOG_TIMEOUT error means that your processor is having trouble with cooperation from its cores and threads. Threads are tasks taken by cores, and some cores can take many threads simultaneously. The problem here is that a thread is waiting for a proper response from another thread — or a core is waiting for a response from another core — and those responses aren’t coming. Therefore, you get this BSoD error.
While this is a processor problem, this can be caused by two things: a driver error, which is very likely if you’re using Windows 8, or the OS itself isn’t playing nice with the processor. First question: how long have you had this computer? Has it been working fine until now?
How do I fix it?

If so, just use System Restore to go back to a point where the system worked. Be wary of using any new devices that may have caused the problem.
If you’re able to boot into Safe Mode when your computer starts, run Driver Reviver to update all your drivers to their latest version. There’s a good chance this will clear up the problem.
You should also use Windows Update, and if you aren’t already using the latest device driver, install that as well.
Drivers are what is used to get your devices like your keyboard to interact with your computer, and while some misconfigured drivers can result in bad performance, bad drivers overwhelmingly result in BSoDs like CLOCK_WATCHDOG_TIMEOUT.
Windows Update can usually solve these problems, but installing new drivers is always advised if you don’t already have the latest version. You should also update your BIOS, which you can find at your motherboard manufacturer’s website, and install from there.
If, however, you can’t boot into your computer at all or this error is still occuring, you’re going to have to get personal help from Microsoft or your manufacturer.
Good luck.

[Mr.Black]

Znači neispravan procesor?

[Mommistake]

A ne znam da li je neispravan, ali uglavnom do njega je, da.
Dobivaš BSOD ili kad se dignu windowsi ti javi error?

[Mr.Black]

Autor Mommistake

A ne znam da li je neispravan, ali uglavnom do njega je, da.
Dobivaš BSOD ili kad se dignu windowsi ti javi error?

Da, nakon instalacije..čista..bez drivera i bez programa..kad krene instalacija nečega isto se pojavi..i tako u krug

[Mommistake]

Možeš u safe mode?

[SaleFFS]

Da li si probao update na zadnji bios? Čisto da eliminiraš tu mogućnost. Piše za zadnji F4 bios "Fix P2-state hanged issue while adjusting CPU Vcore of Ryzen 3" pa bi možda to riješilo problem. Vrijedi pokušati.

https://www.gigabyte.com/Motherboard...-10#support-dl

[Mr.Black]

Ne znam jel smijem flashati mbo, kad je nova i pod garancijom?

[SaleFFS]

Ne vidim razloga zašto bi to bio problem. Slobodno flešaj ako znaš što radiš. Neće ti nitko odbiti zbog toga jamstvo.

[Mr.Black]

Autor SaleFFS

Ne vidim razloga zašto bi to bio problem. Slobodno flešaj ako znaš što radiš. Neće ti nitko odbiti zbog toga jamstvo.

Dakle, nakon flasha na F4 i dalje se događa isto..

[SaleFFS]

Jesi napravio clear cmos nakon updejta za svaki slučaj? Ako nakon toga neće onda ili je ploča defektna ili te potrefio defektan cpu. Ja bi još probao za svaki slučaj ako si u mogućnosti drugo napajanje kao i memtest da vidiš da li je ram ok. Greška upućuje na cpu ali ne mora značiti da je problem u njemu.

[Mommistake]

Procesor je nov? Garancija?

[Mr.Black]

Sve je ispod čekića..stavio sam sad FSP Raidera 550W..za sad radi..tak da je moguće da je Mission Q550 šrot..

[QuidZz]

"Stari" Win 10? Skini novi Windows 10 Pro build 1709 i radit ce ti.

[Mommistake]

Autor Mr.Black

Sve je ispod čekića..stavio sam sad FSP Raidera 550W..za sad radi..tak da je moguće da je Mission Q550 šrot..

Teško da bi ti napajanje bacalo error, ali ako radi, super

[alengrosevic]

Autor Mr.Black

Sve je ispod čekića..stavio sam sad FSP Raidera 550W..za sad radi..tak da je moguće da je Mission Q550 šrot..

vrlo moguće da je do napajanja. Za ovo napajanje Mission još nisam čuo Očito neki low end kinez.

Ali uvijek preporučujem da si ljudi nabave kvalitetno napajanje, malo veća investicija u startu, no kasnije nema glavobolja kao što si ti npr imao.

Ovo FSP je kvalitetnije napajanje i trebalo bi biti OK.

[Mr.Black]

Flash biosa i update win10 je rješilo problem..i dalje radi sa Mission-om...