Having a Disk Write Error Problem

[FlameArrow57]

I am having trouble reinstalling Doom, during pre-allocation. It says disk write error, I've noticed specifically for a few files. I have tried many solutions, clearing download cache, repairing game folder, changing regions, verifying game files for integrity, repairing the install drive C:, removing read-only on the Program Files (x86) install directory, and running Windows Memor Diagnostic. Steam is allowed through my firewall, the only anti-virus software I have is Windows Defender, which allows the game, I don't have any overclocking enabled, and I have latest version of Windows. This is the first time I've had any disk write error, and had it with some other games that I tried installing once it was happening with Doom to see if it was only Doom, and they had some trouble installing with disk write errors too, but were able to install. I do have enough download space.

I tried to message steam support, but it was only automated messages that already suggested what I did, and ended with suggesting to go to forums.

Edit: Fixed. Had something to do with power supply/bad cable, which messed with hard drive.

[RICK 100]

Disable the antivirus

[FlameArrow57]

Didn't work

[The Giving One]

So you said the install directory is your C drive. So that is an internal drive, just to make sure, right ?

You did say "repairing" the drive. Did the drive actually need reparing or did you run a disk check and it reported no issues ?

What did the disk check report, if you did that, please ?

[FlameArrow57]

Yeah, it's internal drive.

Sorry, I should've specified more. When I say repair drive, I mean going into its properties, going to tools, and checking for errors, not knowing if there are any or not. It has repaired errors 3 times now, recently, each time appearing successful.

Event viewer report:
Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x41c30f for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0xa615 is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0xA615.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x597d3ac for possibly 0x19a clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xa62a is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0xA62A.
602368 file records processed. File verification completed.
8286 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
A downpointer (VCN 0x0) was found in index $I30 in file 0xa615 but the index has no index allocation attribute.
Removing corrupt index $I30 in file A615.
Recreating deleted index $I30 in file A615.
806030 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file DOOM_D~1.BNK (A61F) into directory file A615.
Recovering orphaned file doom_dlc2_vo.bnk (A61F) into directory file A615.
Recovering orphaned file doom_vo.bnk (A62A) into directory file A615.
Recovering orphaned file STREAM~1.PCK (A62B) into directory file A615.
Recovering orphaned file streamed_vo.pck (A62B) into directory file A615.
Recovering orphaned file STREAM~2.PCK (A62D) into directory file A615.
Recovering orphaned file streamed_vo_dlc1.pck (A62D) into directory file A615.
Recovering orphaned file STREAM~3.PCK (A62E) into directory file A615.
Recovering orphaned file streamed_vo_dlc2.pck (A62E) into directory file A615.
6 unindexed files scanned. Recovering orphaned file STREAM~4.PCK (A632) into directory file A615.
Skipping further messages about recovering orphans.
6 unindexed files recovered to original directory.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 694 unused index entries from index $SII of file 0x9.
Cleaning up 694 unused index entries from index $SDH of file 0x9.
Cleaning up 694 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file A62A.
101833 data files processed. CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

468336639 KB total disk space.
361246416 KB in 349104 files.
187420 KB in 101832 indexes.
0 KB in bad sectors.
687679 KB in use by the system.
65536 KB occupied by the log file.
106215124 KB available on disk.

4096 bytes in each allocation unit.
117084159 total allocation units on disk.
26553781 allocation units available on disk.

Internal Info:
00 31 09 00 44 e1 06 00 7f ac 0b 00 00 00 00 00 .1..D...........
51 02 00 00 5d 00 00 00 00 00 00 00 00 00 00 00 Q...]...........

Windows has finished checking your disk.
Please wait while your computer restarts.

[tacoshy]

sound like your HDD is dying. It is annoying but not dramatic if it not occurs to often.

You should start considering to replace it. Take a quality WD, Seagate or Hitachi. WD is by far the best with WD Gold > WD Black > WD Purple > WD Cavier Blue > WD Blue (5400 rpm). Seagate the FireCuda > BarraCuda.

[The Giving One]

I have to agree with the helpful user above. It sounds like the drive is going out. I highly suggest you now backup any important data, before doing further troubleshooting.

[FlameArrow57]

Ok, thank you guys!

[The Giving One]

Save your steamapps folder now also. Then, you will not have to redownload all your games if and when you install a new drive. The whole steamapps folder, please.

[FlameArrow57]

Ok

[FlameArrow57]

Ok, I dunno what happened, but we switched out power supply and one of the power cables, and it started working, game is installing, getting past pre-allocation. We don't know know exactly which one was causing the problem, it somehow affected the hard drive.

[x537t]

you hit both of the biggie's PS internal component failure (low voltage/high volt)
or just a flacky connection with cable.
I have had PS cables go bad, tried cleaning but no help, use a different cable and it works

it's FM man!

[FlameArrow57]

;)

[The Giving One]

You probably already know, but I would still backup important data just in case. It is strange, how a power cable seems to have been the cause so thanks for the update on what it was perhaps, and keep an eye out on the drive.

I am certainly not saying you are wrong, but that it seems very unusual to have been a PSU/power problem.