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 Specs
Motherboard: MSI B550M Pro-VDH WiFi
CPU: Ryzen 5 5600X
GPU: RTX 3060 OC 12GB
SSD: 500GB Crucial Gen4 M.2 NVMe
RAM: G.Skill 16GB DDR4 (single stick)
PSU: Corsair CX550 550w

 

[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)

 

[frostbyte9x]

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)

i mean, finding the source of this issue is not easy as there could be mutiple places from where this issue could arise, how do i begin troubleshooting?

 

[johnbl]

i mean, finding the source of this issue is not easy as there could be mutiple places from where this issue could arise, how do i begin troubleshooting?

just update all of the drivers, delete the pagefile.sys and reboot.

very hard to explain. for example if the problem is in the cache of a drive then windows will not do a restart. it will just start to shutdown but will not complete and may just go to a black screen while it waits for the drive to indicate all the data has been flushed to disk. You can turn off drive lazy writes for bugs in the drive firmware.

for RAM timing issues the file corruption seems to move from file to file with each attempted copy.

for network driver caused corruptions, you may find the same file not being completed each time you try to copy the file. Sometimes it depends on the size of the file or the sequence of the incoming files.

I would think that if you can play games then the network driver is ok, but if the download has crc errors the problem would be in the disk, the disk firmware, or the drivers for the disk interface.
ie while the game data is just being streamed it is not going to disk and is not being corrupted.
if windows detects the corruption it should retry the operation,
That is why I would think of a problem in the disk firmware or cache. (or the chip drivers intel rapid storage drivers tend to have lots of problems and do not get updated by Microsoft windows update. You have to update directly from intel)
https://www.intel.com/content/www/us/en/support/detect.html

for system that do not use the Microsoft generic drivers and use the intel custom drivers.

Microsoft does not update the custom AMD drivers either. You have to go to the amd website

 

[frostbyte9x]

just update all of the drivers, delete the pagefile.sys and reboot.

very hard to explain. for example if the problem is in the cache of a drive then windows will not do a restart. it will just start to shutdown but will not complete and may just go to a black screen while it waits for the drive to indicate all the data has been flushed to disk. You can turn off drive lazy writes for bugs in the drive firmware.

for RAM timing issues the file corruption seems to move from file to file with each attempted copy.

for network driver caused corruptions, you may find the same file not being completed each time you try to copy the file. Sometimes it depends on the size of the file or the sequence of the incoming files.

I would think that if you can play games then the network driver is ok, but if the download has crc errors the problem would be in the disk, the disk firmware, or the drivers for the disk interface.
ie while the game data is just being streamed it is not going to disk and is not being corrupted.
if windows detects the corruption it should retry the operation,
That is why I would think of a problem in the disk firmware or cache. (or the chip drivers intel rapid storage drivers tend to have lots of problems and do not get updated by Microsoft windows update. You have to update directly from intel)
https://www.intel.com/content/www/us/en/support/detect.html

for system that do not use the Microsoft generic drivers and use the intel custom drivers.

Microsoft does not update the custom AMD drivers either. You have to go to the amd website

deleted pagefile.sys....
did a memory diagnostic test... it said hardware issue was detected......
However there were no issues found in 2 passes for memtest86 which i did two days ago....
My PC runs fine without any issues... should i be worried?

this is the output...

- <Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events"> <LaunchType>Manual</LaunchType> <CompletionType>Fail</CompletionType> <MemorySize>16309</MemorySize> <TestType>10</TestType> <TestDuration>1039</TestDuration> <TestCount>12</TestCount> <NumPagesTested>4150506</NumPagesTested> <NumPagesUnTested>2283</NumPagesUnTested> <NumBadPages>58</NumBadPages> <T1NumBadPages>0</T1NumBadPages> <T2NumBadPages>0</T2NumBadPages> <T3NumBadPages>30</T3NumBadPages> <T4NumBadPages>0</T4NumBadPages> <T5NumBadPages>0</T5NumBadPages> <T6NumBadPages>0</T6NumBadPages> <T7NumBadPages>0</T7NumBadPages> <T8NumBadPages>0</T8NumBadPages> <T9NumBadPages>28</T9NumBadPages> <T10NumBadPages>0</T10NumBadPages> <T11NumBadPages>0</T11NumBadPages> <T12NumBadPages>0</T12NumBadPages> <T13NumBadPages>0</T13NumBadPages> <T14NumBadPages>0</T14NumBadPages> <T15NumBadPages>0</T15NumBadPages> <T16NumBadPages>0</T16NumBadPages> </Results> </UserData>

 

[frostbyte9x]

deleted pagefile.sys....
did a memory diagnostic test... it said hardware issue was detected......
However there were no issues found in 2 passes for memtest86 which i did two days ago....
My PC runs fine without any issues... should i be worried?

this is the output...

- <Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events"> <LaunchType>Manual</LaunchType> <CompletionType>Fail</CompletionType> <MemorySize>16309</MemorySize> <TestType>10</TestType> <TestDuration>1039</TestDuration> <TestCount>12</TestCount> <NumPagesTested>4150506</NumPagesTested> <NumPagesUnTested>2283</NumPagesUnTested> <NumBadPages>58</NumBadPages> <T1NumBadPages>0</T1NumBadPages> <T2NumBadPages>0</T2NumBadPages> <T3NumBadPages>30</T3NumBadPages> <T4NumBadPages>0</T4NumBadPages> <T5NumBadPages>0</T5NumBadPages> <T6NumBadPages>0</T6NumBadPages> <T7NumBadPages>0</T7NumBadPages> <T8NumBadPages>0</T8NumBadPages> <T9NumBadPages>28</T9NumBadPages> <T10NumBadPages>0</T10NumBadPages> <T11NumBadPages>0</T11NumBadPages> <T12NumBadPages>0</T12NumBadPages> <T13NumBadPages>0</T13NumBadPages> <T14NumBadPages>0</T14NumBadPages> <T15NumBadPages>0</T15NumBadPages> <T16NumBadPages>0</T16NumBadPages> </Results> </UserData>

update: if i keep virtual memory as zero, then my games are crashing, i turned it back on.... now they are running fine again.