Having problems, memory related?

Associate
Joined
19 Apr 2009
Posts
417
I brought this motherboard (along with processor). For the memory I brought this: http://www.overclockers.co.uk/showproduct.php?prodid=MY-041-KS&groupid=701&catid=8&subcat=813. Running at stock, this being detected as 667Mhz (not 800Mhz as advertised), and is also running at 1.8 Volts (instead of 2.0 volts)

After installing windows XP SP2 (which has been fine), I decided to install Soldier of Fortune (which installed fine): but when I do play it, the game keeps locking up. I asked one of my friends opinion (as he is a computer engineer), and suggested that I try uping the memory to the specs given (800Mhz and 2.0 volts). Whilst this has seemed to improve things slightly under the game, it still locked up after about 20 mins or so.

The next thing my mate suggested was to swap his DDR2 (one of the sticks is Team branded, I dont know what the other brand was) for the DDR2 I had brought: my system could then play soldier of fortune until the cows come home. This was being detected as 800Mhz (as it should be, according to the stickers on the memory)

However: after he put the kingston memory into his system (which was very reliable before putting in the kingston memory), he installed battlefield, and when he tried to play it, that too would also lock up. When I next saw my mate, he told me that he was experiencing memory dumps from the kingston memory whenever he pushed the system (unfortunately, I dont know how he "pushed" it, but he told me whenever he opened a program that relied on memory)

Today, I took out the sticks I had borrowed and reinserted the kingston memory. I ran memtest86+ (from a Linux Ubuntu CD) on both of the sticks individually and together but didnt come back with any errors, and soldier of fortune still locks up under the memory.

Needless to say I feel a bit "lost" as to what is wrong with the memory. When I uped the memory to 800Mhz and to 2.0Volts, I left the timings to auto as I figured that the "motherboard would sort itself out". Any suggestions as what I can do to try and overcome the problem (other than just replace the memory) or at least pin point a direct fault with the memory so I can RMA easily enough so I can get some different?
 
Back
Top Bottom