Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
I have seen odd things like this occurring with a flaky controller board on another drive, even a cd/dvd/blue ray drive causing issues with another storage device. That was difficult to find.
These sorts of things can be right bastards to find as you say (especially if they're temperamental).
Hopefully the have abash and get back to us for further help
we have told this so many times , then you hit last 200gb you can feel a lost performance its diffrent then it happend on every brand and model ( cache size matter on my old WD 1,6TB its was apox 160gb, then its felt like someone drop a anchor and drag it around on the I/O task then it write to disk( wasteing to much time looking for free pocket to write in and and time defragmentation matter , but in the end still same problem no free room, and yes we are tired of explan this, and turn this around you did not have the issue then disk was new and empty.
no steam user has ever complain over it there, you need a faulthy disk or cable for that to happend.
i have said it so many times, im sure some day steam will make a "resevation disk pool size that warn people becausesteam users they will never learn "how things actual work" they are gamers not harddisk technician, then its dayli that steam user keep ask this, then its a problem, there is a diffrence in other that know better and casual pc gamer.
there is nothing wrong with what you dont know , problem is system aient going to tell you this anymore. thats user own problem , and now its been seen steam problem. all disk samller then 2TB is the issue and lack of respect with 10% free rule that was seen as recommedation in the old previous OS = 200gb kept free , lost disk performance then you do and it still stands today and we will never get ride of it.
this is know by many previous windows system users, and that rule was removed because TB disk larger then 2TB that 10% rule look like a joke. 10TB thats 1TB kept free % dont work
im pretty sure most here can see a issue looking for free space on 10tb then lesser then 1TB free left disk system is in trouble ( aka lost disk performance. )
ps.
and thats why steam might in the furture make a popup warning then ppl install, you run out of space and your pc performance can be effect by this in DL to write and its all about disk throughput. in I/O
this is common knowledge for harddisk experts.
For the record guys steams main EXE is installed on my OS drive, which is a NVME SSD guess i should have mentioned that. And i have a steam library on the OS drive for only a select few games that i tend to switch around, 1 HDD a 4TB WD black HDD as well as another library on a Samsung EVO SATA SSD 1TB
EDIT not trying to bark up the wrong tree but can it be something like windows directx Shader cache that could potentially be an issue under those temporary files?
They're just small files to do with well, shader pre-caching in games so very unlikely to do anything like this.
Yes Crystaldisk is for health checking, but it'll give you a start. If it reports anything you can then do further scanning using a different utility if you wish.
EDIT: problems returned so doing this some easy way without actually deleting my libraries i renamed them on the other drives so that steam loses them. Despite the HDD being healthy it looks like one of the huge libraries is causing the issue despite there being sufficient disk space. I'm going to run a few more tests but like you guys said might have to trim the damn thing down. Shouldn't be too hard bunch for games i don't play anymore and gotta get rid of the hoarder mindset now that i actually have decent net...
What you should be doing when installing or copying to a new drive is this:
First off install download Steam anew and install it on your new drive.
Then copy across both your steamapps folder contents (or the games you wish to) plus the appmanifest files.
It should then start seeing them when you run Steam.
The moment i remove the F: drive library it works again. Theres something in that library folder thats causing the issue but i got no idea. If i keep both my SSD libraries works fine its only the HDD one that seems to have the issue. Maybe a corrupted download/file in there somewhere?
Also double checked fragmentation/trim and the like, its set to weekly which i guess is its default setting so its definitely not an issue there.. At least i've nailed it down somewhat...