system files keep getting corrupted

lordSnake · 27 Dec 2013

I kept having issues with programs crashing (especially google chrome) and did an sfc/scan now and found a bunch of corrupt files which could not be fixed as the master copies were also corrupt.

I have reinstalled windows 3 times now, and the problem just keeps occurring, within days there are corrupt files which cannot be repaired.
Even if I restore system backups from when the system was fine, the corrupt files still exist afterwards.

I have used a Kaspersky rescue disk to scan my system and all drives, and not found any malware anywhere.
This feels like a corrupt disk, but I have test my disc (OCZ Agility 3 SSD) using various tools and found no errors.

anyone else got any ideas ?

matts6887 · 27 Dec 2013

Sounds like something possibly in the mbr(master boot record) for windows got corrupted which may be the reason even after re installing windows, you are getting those errors. You might have to totally wipe it clean by doing a complete format of the drive and THEN re install windows again; at that point hopefully everything should be good.

Kaktussoft · 27 Dec 2013

lordSnake said:

Even if I restore system backups from when the system was fine, the corrupt files still exist afterwards.

Are you really talking about an image backup? An image backup is a full backup of a disk volume. When you restore it ..... it is in same state as it was on the moment you made the backup.

Are you 100% sure that:

All was fine at time of backup
You have corrupt files just after restoring (and no windows update afterwards)

Kaktussoft · 27 Dec 2013

matts6887 said:

Sounds like something possibly in the mbr(master boot record) for windows got corrupted which may be the reason even after re installing windows, you are getting those errors. You might have to totally wipe it clean by doing a complete format of the drive and THEN re install windows again; at that point hopefully everything should be good.

@matts6887: MBR is the partition table, disk signature and Master Boot Code. Partition table is fine... machine can see partitions and they are working. disk sinature is for uniquely identifying system.... works as well. Master Boot Code is also in sector0 of physical disk. It has instructions to find an active partition and run the bootsector of that partition (that runs the bootmgr). You really think the Master Boot Code is faulty?

To rewrite MBR Bootcode of physical drive where volume C is:

Code:

bootsect/nt60  c:  /force  /mbr

To rewrite disk C bootsector.

Code:

bootsect/nt60  c:  /force

lordSnake · 27 Dec 2013

I have deleted all partitions and formatted and started completely from scratch.
I did a chkdsk and a sfc/scannow prior to doing a backup, and no errors were reported.
I have also used system restore to go back to previous state with no corruption, and that also fails.

If it is not the disk then the only other thing I can think of is that some windows updates are causing it.

matts6887 · 27 Dec 2013

Kaktussoft said:

matts6887 said:

Sounds like something possibly in the mbr(master boot record) for windows got corrupted which may be the reason even after re installing windows, you are getting those errors. You might have to totally wipe it clean by doing a complete format of the drive and THEN re install windows again; at that point hopefully everything should be good.

@matts6887: MBR is the partition table, disk signature and Master Boot Code. Partition table is fine... machine can see partitions and they are working. disk sinature is for uniquely identifying system.... works as well. Master Boot Code is also in sector0 of physical disk. It has instructions to find an active partition and run the bootsector of that partition (that runs the bootmgr). You really think the Master Boot Code is faulty?

To rewrite MBR Bootcode of physical drive where volume C is:

Code:

bootsect/nt60  c:  /force  /mbr

To rewrite disk C bootsector.

Code:

bootsect/nt60  c:  /force

Doh!....my bad; I just kinda thought that only because sometimes, depending on the situation; the mbr can become corrupt which can lead to the same or similar situation(s). So...I only thought it was just possible....also because he mentioned that every time he tried to re install windows; he was still getting corrupt files; and the mbr is what contains the "Code" ...to get windows to boot(along with all the other various files)

EDIT: I also thought that it could be mbr cause even if it shows that the mbr is ok; i believe it still can be bad. Dont forget all it takes is one small bad area to create a domino effect which can lead to errors, etc. So just because it shows its ok; there may still be errors elsewhere in mbr that may possibly not be picked up for whatever reason.