Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
Now the tailored reply: useplatformclock is a developer setting that should be off. Or deleted. Unless you're a low-level developer.
So SOMETHING on your computer changes this setting. ZA might in fact he the culprit, but something else might be as well. Uninstall it, see if the problem repeats. If yes, uninstall the next potentially problematic program.
Remember to reboot after uninstalling.
But before we continue this talk, uninstall it, reboot, see if the problem persists. If yes, you can install it again, if you wish.
But id like you to monitor the state of the boot variable as well. Maybe, just maybe, ZA wasn't the one to mess it up.
I didn't know exactly if it did, it just seemed to me as though it did, based on the high cpu usage coming back when something would download on steam, and battlenet, and I would do the process over again and it would go back to normal when downloading from steam and battlenet.