Data corruption ?

Discussion in 'PC hardware help' started by HeBeertje, Jan 21, 2010.

  1. HeBeertje

    HeBeertje Member

    Joined:
    Jul 21, 2009
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    11
    I'm at a loss. When unrarring files (using WinRAR 3.91) I sometimes get the error: 'file suchandsuch.r34 is corrupt'. When I try extracting that same batch of files again, it will sometimes say another file is corrupt; if I try often enough, it does extract completely and without error.

    This, however is not the only weird thing: When I use ABGX or SFV to check downloads, sometimes CRC will pass, other times it will fail and then it passes again when I'm checking the same file several times in a row. I have no clue where this data corruption occurs or how to test for it properly. I was thinking memory banks, but I rarely get any BSOD's or other unexplainable systemerrors - something that would be quite likely when dealing with corrupt memory. It also occurs on different harddrives.

    Can anyone please PLEASE shed some light on this issue ?

    TIA
     
  2. jony218

    jony218 Guest

    If you are using a download manager to download files, if you download too many files at the same time you encounter this problem.

    I use IDM (internet download manager), when I download more than 3 files at a time, I sometimes get file corruption. Since I've limited my downloads to 3 at a time I haven't had any more file corruption problems. It's been over a year since I've encounter a corrupt file.

    That's the only time I ever encountered corrupt rar files.
     
  3. KillerBug

    KillerBug Active member

    Joined:
    May 21, 2006
    Messages:
    3,802
    Likes Received:
    0
    Trophy Points:
    66
    I just use firefox...why use a download manager limited to 3 files when firefox has no problems downloading a dozen at once?
     
  4. HeBeertje

    HeBeertje Member

    Joined:
    Jul 21, 2009
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    11
    No, I don't use DLM's. However, I've found that running in safe mode for a day or so isn't generating the error. Must be some weird driver problem - perhaps through automatic update ?
     

Share This Page