Question CRC/checksum errors in all files

[frostbyte9x]

I built a new PC, but I’m facing CRC (Cyclic Redundancy Check) errors everywhere. For instance, Steam and Epic Games redownload files when I install a new game, and any RAR archive I create shows CRC errors when tested. However, during normal usage, such as gaming, I don’t encounter any issues.

I’ve already checked my RAM using MemTest86, and CrystalDiskInfo reports my SSD health at 100%. What else can I do to troubleshoot this problem?

System Spec:
Ryzen 5 5600x
RTX 3060 12 GB OC
MSI b550m pro-vdh wifi motherboard
500 GB Crucial Gen4 M.2 NVMe SSD
G.Skill 16GB DDR4 RAM (Single stick)
550Watt PSU Corsair CX550

 

[rgd1101]

how are you testing crc?

 

[frostbyte9x]

how are you testing crc?

Recurring Download Errors on Epic Games​

I frequently encounter issues with Epic Games, when I'm downloading games, while they are veryfing the files it starts to download again, this is happening repeatedly. While Steam games prompts to verify the game files, and an error message suggests that there might be a problem with the files.

CRC Errors in Archives​

When I create archives in WinRAR, they often contain CRC errors when I re-test them. Maybe I'm thinking, this suggests that the issue is not related to my network connection, but rather a problem with the way files are being written or read.

 

[johnbl]

my first guess would be the network driver but It could still be other things:
ie update router firmware, network driver, bios, cpu chipset driver, and ssd firmware can all cause a problem like this. I would also check the RAM secondary timings to make sure they match the bios RAM settings

the last time I had a problem like this it was the caused by a intel network driver on a dell machine. it was not correctly passing a certain network packets and certain files would never complete downloads. It would just go into a loop where the client would ask for the server to retransmit the packet, the server would resent it and the cycle would restart until the server reset the connection.

I have also seen bugs in cache controllers in drive do the same thing. update drive firmware to fix. (assuming it is not a bug in the cpu chipset driver, or another driver involved int the path)