CRC errors with large files...

Page 1 of 4 123 ... LastLast

  1. Posts : 7
    Windows 7 Ultimate N x64
       #1

    CRC errors with large files...


    Hello all. First time poster here, and I've got a doozy of a problem. I just hope this is in the right section. Pretty much all large files are corrupt if I save them to either of my hard drives. The limit seems to be somewhere around 30mb... under that I'm fine, over that I get CRC errors out the wazoo. I get occasional glitches in Windows, and I tried to run System File Checker, but it couldn't repair a LOT of stuff, complaining of hash mismatches. I've run Scandisk and it doesn't find any problems. I ran MemTest86+ for 48 hours, without a single memory error. I've used SeaTools for Windows and both drives pass all tests; SeaTools for DOS reports the drives are fine but the file system has errors it can't fix. I ran SpinRite through on both drives... Took it a couple of days but came back without any unusual errors. I can't for the life of me figure out what's going wrong... Can anyone point me in the right direction here?

    System specs can be accessed below on the "My System Specs" link.
      My Computer


  2. whs
    Posts : 26,210
    Vista, Windows7, Mint Mate, Zorin, Windows 8
       #2

    That sounds like a corrupted MFT. Have a look at this: (check the web - there are more tools)

    The MFT (Master File Table) is sometimes corrupted. If Microsoft's Checkdisk (chkdsk) failed to repair the MFT, run TestDisk. In the Advanced menu, select your NTFS partition, choose Boot, then Repair MFT. TestDisk will compare the MFT and MFT mirror (its backup). If the MFT is damaged, it will try to repair the MFT using the backup. If the MFT backup is damaged, it will use the main MFT.
    If both MFT and MFTMirr are damaged and thus cannot be repaired using TestDisk, you might want to try commercial software like Zero Assumption Recovery, GetDataBack for NTFS.

    Source: http://www.cgsecurity.org/wiki/Advanced_NTFS_Boot_and_MFT_Repair
      My Computer


  3. Posts : 7
    Windows 7 Ultimate N x64
    Thread Starter
       #3

    Okay, so I tried TestDisk and followed your instructions. It asked me if I wanted to fix the MFT mirror from the main MFT, I told it yes, and then it said "Failed to fix MFT mirror: Write error." Ooh boy. This doesn't look good.

    A friend of mine suggested that perhaps the issue is not with the drive, or data on the drive, but instead it's in the SATA controller on my motherboard... It was my understanding, though, that if a hard drive controller was going south, you'd see errors in HDD testing tools like SeaTools. Would this be correct, or is this line of thinking way off base?
      My Computer


  4. Posts : 1,170
    XP Pro SP3 X86 / Win7 Pro X86
       #4

    baralheia said:
    Hello all. First time poster here, and I've got a doozy of a problem. I just hope this is in the right section. Pretty much all large files are corrupt if I save them to either of my hard drives. The limit seems to be somewhere around 30mb... under that I'm fine, over that I get CRC errors out the wazoo.
    First step... check your cables and power connectors... It wouldn't be the first time a bad or dirty connection has sent techs flying off in a dozen directions....

    If your drives are passing all non-FS diagnostics (i.e. Read/Write/Erase stress testing) it's likely you don't have a serious hardware problem. More likely you have somehow managed to corrupt your file systems ... and when that happens, the first step is a virus scan... to play it safe.

    The next step is to ensure that you have proper drivers installed for your SATA controller... Check Device Manager and if there's a newer version, get it... If not, try an older version... It's entirely possible the current driver is a bit buggy...

    To attempt to fix the File System corruption use CHKDSK /F /R C: from a CMD window... Note: C is the letter indicating the drive to be tested... sub in your own drive letter as needed. This is going to take a while... with 500gb drives, about an hour to 90 minutes each. Please note that when you go to do your system drive it will want to schedule it for the next reboot and you should play along...

    There are third party tools but frankly I've never trusted them or found need of them.

    In the extreme... You end up doing a fresh install, using the windows installer's partitioning tool to destroy and recreate all partitions on your system.
      My Computer


  5. Posts : 1,170
    XP Pro SP3 X86 / Win7 Pro X86
       #5

    baralheia said:
    A friend of mine suggested that perhaps the issue is not with the drive, or data on the drive, but instead it's in the SATA controller on my motherboard... It was my understanding, though, that if a hard drive controller was going south, you'd see errors in HDD testing tools like SeaTools. Would this be correct, or is this line of thinking way off base?
    Yep... Diagnostics are written specifically to find problems with hardware. If the thing passes the diagnostics it's a pretty fair bet it's ok.
      My Computer


  6. whs
    Posts : 26,210
    Vista, Windows7, Mint Mate, Zorin, Windows 8
       #6

    To attempt to fix the File System corruption use CHKDSK /F /R C: from a CMD window... Note: C is the letter indicating the drive to be tested... sub in your own drive letter as needed.
    CHKDSK C: /F /R might work better
      My Computer


  7. Posts : 1,170
    XP Pro SP3 X86 / Win7 Pro X86
       #7

    whs said:
    To attempt to fix the File System corruption use CHKDSK /F /R C: from a CMD window... Note: C is the letter indicating the drive to be tested... sub in your own drive letter as needed.
    CHKDSK C: /F /R might work better
    Just a simple question...
    Did you try it my way and see what happens?
    Did you try it your way and see what happens?

    Really... It might be an idea to check these things before you go correcting people...
      My Computer


  8. whs
    Posts : 26,210
    Vista, Windows7, Mint Mate, Zorin, Windows 8
       #8

    CommonTater said:
    whs said:
    To attempt to fix the File System corruption use CHKDSK /F /R C: from a CMD window... Note: C is the letter indicating the drive to be tested... sub in your own drive letter as needed.
    CHKDSK C: /F /R might work better
    Just a simple question...
    Did you try it my way and see what happens?
    Did you try it your way and see what happens?

    Really... It might be an idea to check these things before you go correcting people...
    No, I did not check it your way. I just suggested the "official" cmd syntax. But maybe you can tell me what your way does in contrast to the cmd syntax. All I know is that cmd is very iffy when it comes to syntax errors.

    CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B]

    volume Specifies the drive letter (followed by a colon),
    mount point, or volume name.
    filename FAT/FAT32 only: Specifies the files to check for fragmentation
    /F Fixes errors on the disk.
    /V On FAT/FAT32: Displays the full path and name of every file
    on the disk.
    On NTFS: Displays cleanup messages if any.
    /R Locates bad sectors and recovers readable information

    PS: I just checked your way. It does work. I apologize - did not mean to be wise guy. That is the first time that cmd works when I deviate from the given syntax.
      My Computer


  9. Posts : 1,170
    XP Pro SP3 X86 / Win7 Pro X86
       #9

    whs said:
    PS: I just checked your way. It does work. I apologize - did not mean to be wise guy. That is the first time that cmd works when I deviate from the given syntax.
    Ok... apology accepted.

    FYI... I've been working professionaly in computers since before MS-DOS. I started out as a service tech working on IMSAI and ALTAIRE *kits* then moved over to the Intertec Superbrain, Victor 9000 and then PCs. I'm pretty sure that when I quote a simple dos command I'll get it right.
      My Computer


  10. whs
    Posts : 26,210
    Vista, Windows7, Mint Mate, Zorin, Windows 8
       #10

    CommonTater said:
    whs said:
    PS: I just checked your way. It does work. I apologize - did not mean to be wise guy. That is the first time that cmd works when I deviate from the given syntax.
    Ok... apology accepted.

    FYI... I've been working professionaly in computers since before MS-DOS. I started out as a service tech working on IMSAI and ALTAIRE *kits* then moved over to the Intertec Superbrain, Victor 9000 and then PCs. I'm pretty sure that when I quote a simple dos command I'll get it right.
    Thanks for your generosity. Unlike you, I spent my life on large systems (since 1961) and am still wrestling with the intricacies of the PC. But with some patience, I might get there - if I live long enough, LOL. The forums are a great asset in this regard.
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:29.
Find Us