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
I left CS:GO (one of the games with this issue) to download overnight.
Rule out the following possible causes:
1. A third party program messing with Steam (Norton, in example, is notorious)
2. Disk defects
One thing I forgot to mention, before I left for school, I was able to install the game 'receiver' and really big Sky, two games I had never installed before. I then tried to install castle crasher as a test, but it still wouldn't install and only gave me the Installscript.vdf. Why would those two games install perfectly, but not castle crashers?
I recently ran a disk defragment but I've been having bsods on startup recently (waiting to reinstall Windows on an ssd when I get one). I'll run chkdsk after I get home from school.
Those sort of errors seem to be saying that there's errors or issues with your disk drive.
That would certainly explain why you're having download issues, and why you can download certain games and not others - note that the ones you downloaded are small compared to what you can't download.
That might suggest some buggered sectors.
How should i go about fixing it? Is there a way to repair windows without deleting all my files?
You can't, basically. If your disk drive is having such serious issues, it is ONLY ever going to worsen and probably quickly.
All you can do is go to your drive manufacturer's website and download one of their disk checking utilities - it SHOULD be able to check and then mark the bad sectors so you can at least use SOME of your disk drive for now.
Of course, if it's the drive controller or something else, then it might even have troubles with this.
But give that a go - your best bet is to get any data on there that's important backed up ASAP.
Western Digital's utility is probably only useful if your drive IS WD. This is why I told you to go to your drive manufacturer's website.
If it IS WD, then try and look a little more to see if there's a utility that's a bit more intensive.
I'm afraid that's HIGHLY unlikely.
The BSOD errors are DIRECTLY related to your hard drive. That's how we both spotted it straight away. If it were driver related, you wouldn't likely have such errors.
Do note that testing utilities aren't exact either. Each hard drive has it's OWN "in-built" utilities to mark duff sectors as they're detected, as ALL hard drives are built with faults (none are perfect).
So, it's entirely likely that as each sector fails on your hard drive, it gets marked. Then when you run a check, it report nothing untoward. This is why I asked if you could find an INTENSIVE scanner, which goes into great detail.
It's also incredibly likely for you to THINK the issue is down to Steam alone, for the simple reason Steam was most likely installed with it's games at that time on a certain area of the disk. Likewise Origin, etc. If those sectors and those surrounding for Origin are OK, they wouldn't cause any issue.
However, depending on how much space there is on the drive, etc, it could easily be that the games you're trying to install on Steam are being installed (in part or full) on dodgy sectors. That's often how it goes. I realise I probably haven't explained this very well, though.
This is why I suggested that those games you succesfully installed were small and the ones you couldn't were larger - this would back that hypothesis up.
So, I'm afraid there seems to be a fair amount of evidence for hard drive failure, and nothing I can see for anything else.
EDIT: Also to add, those BSODs - NTFS is the disk filing system, and the other is an OS file that should obviously NOT be deleted or disappeared shows as not working.