Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
Even after a Windows re-install, it's still doing it.
When a 240GB model is sold for about 20 bucks, you know you're buying cheap.
There are also reports of SSDs failing less than half a year after purchase.
It's cheap chinese SSD, I know what you're gonna say, "that's the cause". But no, that can't be the cause, especially when my second SSD (PNY) has the exact problem that doesn't happen on linux. Both of my SSD used for gaming were tested on linux with the same method.
Install a game and see if it blocks, that doesn't happen on linux.
The cause is somewhere between Windows and my SSD (technically, both), but where?
For the DRAM, if you know any software that could help me see if i have any, I'm all ears
But a question still remains for me (if DRAM was the issue). Why would it happen on Windows only?
In this case, it might be the difference in the way the OSes interface with hardware.
Different OS'es may handle storage differently would be one obvious possibility. If you can show that every setting and feature is configured and functions identically between linux and windows, then that's something. If you're just assuming it's all the same and it's not, well obvious flaw with the assumption.
Your screenshot literally shows the issue. Your disk is 100% utilized. It has no IO left to download things.
The reason is becuase as steam patches files it is both cpu and disk IO intensive. As such steam stops downloading patch files while a file is being patched. Because, as your screenshot shows, the disk can become IO saturated. If yout ry to download files in this state, it just takes longer for everything to complete.
Why would it behave this way tho?
My two options are:
- DRAM-less SSD so less performance. Could be the issue since since Windows and Linux don't handle files the same way.
- Faulty SSD, tho I don't really believe it.
There is also this issue, but as he said, it's hard to see what's wrong. And I also have zero knowledge on that
A faulty SSD could still run "fine"? Because that's the only issue I have. If it was burned, it would completely stop, no?