Hi all, I've had this computer for over a year now and mainly using it for gaming. However it's been plagued by what I thought were HDD problems since I got it (problems would start with a few corrupt files, serious error recovery messages, BSODs and then failure to boot up). I could usually "fix" these problems by formatting the HDD and reinstalling Windows and the computer would be problem free for a while. However, recently I installed a new HDD and on installing Windows, my computer crashed several times. I was told that it could be due to a problem with my RAM so I scanned it using Memtest86+ as well as Windows Memory Diagnostic Tool and sure enough Memtest found over 300,000 errors with it whilst my RAM failed all tests on the other program. I don't want to go out and buy new RAM however in case there is a more serious fault with my computer e.g with the motherboard or processor as 300,000 errors seems to high a number for the fault to be with my memory alone? Does anyone have any ideas how I can find out what is wrong with my computer and how to fix it? Thanks for any help System Specs -AMD Athlon 64 Processor 3500+, ~2.2Ghz -2048MB Ram -NVidia GeForce 7800GT Graphics card -AsRock AMD-SIS As20C motherboard
Welcome to hardwareforums CheeseBeard :beer: You could borrow RAM from another computer and put it in yours and then run memtest again
first clear cmos when you plug a new shit on your computer i simply dislike resetting it because i can't hold the jumper completely well hdd can be set up as 48bit mode from the bios (or is it 32 i don't remember clearly now i'm buying a couple of flight tickets at the same time ) i think that your mobo can't hold your new hdd if it is one of the old ones tahat have not seen sata 2 and ncq factory out (though amd doesn't support ncq) try your old hdd and run the mem test again if no errors are gained, try to find that setting from the bios if you can not flash the bios no problem with your ram exactly last chance is changing the mobo but don't worth it (sc939 supporting chipsets) again a foolish windows error
