The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.

Ugh... bad RAM

FrostozunaFrostozuna Registered User regular
edited April 2008 in Help / Advice Forum
After having lots of "fake" corruption problems when dealing with large files (.iso images, large patches, installing large package files for games, etc.) it was suggested that perhaps I had some bad RAM. I downloaded a copy of memtest86+ and ran it on boot with only one of my two sticks in (I'm currently running 2GB in dual channel mode with two 1GB sticks). Maybe 10 seconds after the test started, the screen started to scroll like CRAZY with errors; it only took a very short time until the error count reached like 20000+ and I just rebooted.

Is it possible for the RAM to be that bad? Or is there perhaps some kind of setting which I need to correct (I havent changed any of the default mtest86+ scan settings)?

edit: OK I just ran the test with the other stick in the first slot and it did the same thing- apparently both sticks have thousands and thousands of errors?

Frostozuna on

Posts

  • RaereRaere Registered User regular
    edited April 2008
    The only other logical thing would seem to be a bad motherboard. It's unlikely that both RAM sticks went that bad. Any other symptoms besides that?

    Raere on
    Raere.png
  • FrostozunaFrostozuna Registered User regular
    edited April 2008
    Raere wrote: »
    The only other logical thing would seem to be a bad motherboard. It's unlikely that both RAM sticks went that bad. Any other symptoms besides that?

    No thats really the only thing I'm going on. For instance, what prompted me to finally check the RAM was I tried to reinstall WoW today. I got to disc 2 and it told me there was corruption when it was trying to extract one of the big package files (I think it was sound.mpq). I rebooted and tried to reinstall, and this time it got past sound.mpq, but one of the other files was apparently corrupted now.

    The other symptom which happens very often is when I download a large torrent. The file will complete fine, then there will be supposed corruption problems during extraction. I recheck the torrent and the percentage drops to like 99.7% with utorrent going "oh found some bad parts, well just redownload". It completes again, but the "corruption" is never really gone; it keeps showing up for as long as I recheck the torrent

    How would I go about checking to see if its the motherboard and not the RAM?

    Frostozuna on
  • RaereRaere Registered User regular
    edited April 2008
    Frostozuna wrote: »
    Raere wrote: »
    The only other logical thing would seem to be a bad motherboard. It's unlikely that both RAM sticks went that bad. Any other symptoms besides that?

    No thats really the only thing I'm going on. For instance, what prompted me to finally check the RAM was I tried to reinstall WoW today. I got to disc 2 and it told me there was corruption when it was trying to extract one of the big package files (I think it was sound.mpq). I rebooted and tried to reinstall, and this time it got past sound.mpq, but one of the other files was apparently corrupted now.

    The other symptom which happens very often is when I download a large torrent. The file will complete fine, then there will be supposed corruption problems during extraction. I recheck the torrent and the percentage drops to like 99.7% with utorrent going "oh found some bad parts, well just redownload". It completes again, but the "corruption" is never really gone; it keeps showing up for as long as I recheck the torrent

    How would I go about checking to see if its the motherboard and not the RAM?

    Do you have any other computers that you can pop the RAM into, and run memtest on that? If the RAM passes on another computer, then that eliminates the RAM.

    Also, run a full chkdsk (chkdsk C: /r from cmd) which runs a full sector scan on your hard drive (Windows can only do it before it loads, so it'll ask you if you want it to run on next reboot. It'll probably take a half hour). It's possible that there's some bad sectors on your hard drive that are causing files written to it to get corrupted somehow.

    Raere on
    Raere.png
Sign In or Register to comment.