Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
To add, ensure there no 3rd party app that hooks into Steam app, that causing the problems. There an anti virus that scans unnecessary causing high usage, and huge delay launching anything via Steam client, so ensure nothing causing problems for Steam.
I've tested closing Steam every time (about 6 times now), and I'm sure it's the source of the issue. I don't have any third party programs the interact with steam.
Do you have your OS updated?
What motherboard do you have, and do you have the latest bios for it?
ASUS Rampage IV and yes my bios is up to date.
Test running Steam under Windows safe mode with network enable, don't run any other app, and see if you get same issue. When under safe mode, no other app should be running at start up so make your job isolating easier.
i did not say ypu had old pc , should be fast enough and a desktop as i understand it..
but again we cant mind read here. what if its 1 HD that update both OS , and partion the disk and steam doing checkup. ( through in Laptop in top of this, and you do have worst possible setup and in Balance mode or battry mode ) i did not say you had laptop, it was more a worst case sametime. and OS doing backup sametime. then all will feel just like you said in topic
If you have a quad core however or more, it can very well be due to the GPU Accelerated Webrendering setting. (yes, I know it shouldn't be related, but unfortunately in my own tests in october this year I found out it was. Disabling this setting at least allowed Steam to use multiple CPU physical cores on my own PC. Ask CEF I guess, or the programmers at Valve who... only do web development as of late.)
Anyway I recommend disabling that setting and tuning to low bandwidth low performance mode and see if that helps any. You can leave directwrite on, unless this too causes problems.
i can only agree with Elucidator, it seem we are at a point with user own faulth for not knowing steam settings can effect such, but even i look that sandy bridge E processor, the 3930k
it should be fine. so something else could be the cause. (steam own settings, maybe ? )
its almost come to that no one ask about it , we assume it cant be that ofc.
I did delay the trouble shooting: After a restart the other day I had forgot to close Steam because of its core #0 problem. I didn't notice any issues for 2.5 days. Tonight the problem came back, and once again the solution was simply to close steam.
I will resuming trouble shooting tomorrow, first thing I'll do is Safe Mode with Networking and leaving it running for a long time.
The system is unchanged, and I hadn't downloaded or installed any new software or programs.