I'm a bit worried my hard drive is dying at the moment, and I was hoping to get some other views on the matter before I tear my P.C apart.
A few days ago, I decided to partition my C drive in order to install ubuntu on to the new partition. I shrunk the volume, made a new one, and all was fine. When I went to restart the P.C, Windows wouldn't start, not matter what I did (boot priorities, system clean up, system restore, etc.)
I installed Ubuntu, found my Windows 7 installation CD, then reinstalled Windows 7 (Ultimate). At the custom installation screen, I deleted and formatted previous partitions - I am now left with my C Drive (100gb), D drive (10gb), F Drive (360gb), and the Systems partition.
Everything went well. However, when I went to download a game from Steam, the game randomly stops downloading - the 'Disk Write Error' status pops up. At the same time, my browser stops working (I use Google Chrome) and shows an "oops!" screen. After a few moments, I can use it again.
I can re-initiate the download in Steam, but it just repeats after a few moments of downloading...
Initially, the Steam folder was located on the C Drive. I thought it was an issue with disk space. I removed and reinstalled steam, deleted all game content, and saved the new content to my F Drive - the issue still repeats.
Be honest. Does this sound like my hard drive is dying? Has anyone had this issue before?
Disk Write Error - Browser Crashes/Steam stops downloading
|TSR's new app is coming! Sign up here to try it first >>||17-10-2016|
- 11-04-2016 03:45
- 100 followers
- 3 badges
- 11-04-2016 04:23
Well the first thing you can do is run the Error Check on your HDD. If that comes out clean you can navigate to the folder where steam is installed, most probably C drive, within program files. In there you're gonna find steamapps and then common. You'll find a file by the name of the game you're downloading. Make sure it's the one which is 0 KB in size. Delete that and you should be all goodTagged:
(Original post by Hamoody)
- 11-04-2016 05:55
Well the first thing you can do is run the Error Check on your HDD. If that comes out clean you can navigate to the folder where steam is installed, most probably C drive, within program files. In there you're gonna find steamapps and then common. You'll find a file by the name of the game you're downloading. Make sure it's the one which is 0 KB in size. Delete that and you should be all good
My steam is currently installed in my F drive. There is no dota in the steam apps commons folder, because it is doing this mid download - dota only move to commons once it has finished downloading, as I understand.
What else could it be?
- 11-04-2016 14:14
In order to determine if it is an issue with my HD, I installed Steam on to my external HD, and am now downloading dota on to it.
If there is, again, a disk write error, then it's probably not to do with the hard drives....
- 11-04-2016 14:35
Just did a hard drive/system check using the cmd prompt - my HD is listed as healthy...
- 11-04-2016 14:57
The download to my external hard drive just showed 'Disk Write Error'.
I am now at a loss. What do I do? It's not an issue with my hard drive (I think).... what else can it be?
(Original post by Meteora636)
- 11-04-2016 15:29
Try a download manager. Big files are easily corrupted when they are downloaded as one chunk
Oh wait... is this game downloaded *through* Steam? I'm not familiar with Steam...
I'm beginning to think it's an issue with my network - my p.c might be dropping off every now and again.
I'm going to install Steam onto my F Drive, and download Dota again. I'll monitor via the pinging in CMD to see if the signal drops.
- 11-04-2016 16:30
- I'm monitoring the ping in the Command Prompt while using the p.c.
Between the many 'Reply from 126.96.36.199: bytes=32 time=17ms TIL=57' lines, I can the occasional
"Request Time Out"
What can this mean!!Last edited by Kagutsuchi; 11-04-2016 at 16:37.
- 14-04-2016 10:09
A network boo boo. This probably isn't the cause of your disk write error. Internet protocols are designed to be resilient to a certain amount of lost packets. If they weren't it just wouldn't work.