Crazy memory issues

I have G.Skill DDR2-800 matching pair. Thouht I had an infection. (computer would quit responding after a couple days) Went through all of the steps with no infections. So I decided to check my memory. Used memtest86+. When I run both together it would restart after about 20 seconds. So I thought I had a bad stick. Tested them individually and both check out to be good. So here's the weird part. One of them is showing up as DDR3 in memtest!

Any thoughts or ideas on this would be greatly appreciated.....

 

One question from reading your MBRCheck log: in Device Manager, does your first hard drive show correctly, no strange letters?

Double-check the RAM readouts with CPU-Z, install and run it, switch to the SPD tab and compare the 2 sticks.

Is the RAM still under warranty?

 

As for the device manager, at first it was only showing 1 hdd. After playing with it for a minute the other one finally showed up. Not sure what I am looking for but nothing was out of the ordinary that I could see. One was named ST?????? which it always has. That is the default name from manufacturer. The other is named Daniel, which is me.

As for the memory I have posted an image from CPU-z. It looks as though the timings are different between the two sticks. I had my pc oc'd not long ago but went to fail safe when I started having issues. Not that it was oc'd very high. I think my cpu was pushing 3.26 or around that. (Q6600@ 2.40 now)

here is a link to memory I have
http://www.newegg.com/Product/Product.aspx?Item=N82E16820148163

 

STxxxxxx is hdd1, a Seagate drive, the hdd0 should also have a name that reflects the maker and model, is this not true for yours? Renaming the Explorer name for the drive (Daniel) should not affect the DevMan name which is read from the hardware.

If you didn't use some kind of 'tweak' to rename the hardware name of drive 0, I'd have to assume that there's something wrong with it and it would need backing up and replacing ASAP.

You're only looking at the stick in Slot 1 , In CPU-Z SPD > upper left, Slot #1 = dropdown and select Slot #2, then switch between the sticks to compare. Part number is the most important, unless the Slot #2 stick gives more details, in which case, #1 (stick or slot) has a problem.

 

Hdd0 is actually 2x 360GB in raid0. Im not sure if i renamed them or not when I went into the configuration utility and enabled the raid0.

As for the memory. They are both identical. Not sure why memtest is shutting down or why it is showing that one of the sticks is DDR3.

Backup was created a week ago.....

During post all hdd's show with manu. Names.

 

Ok, how about switching the RAM to the 3rd/4th slots if you have them?

I'm unsure of how DevMan should see the hdd0 if it's 2xdrives in RAID, shouldn't there be individual entries for each physical drive anyway, or does the RAID controller override that?

EDIT: just read your Edit, now makes more sense, I'd guess the drives are all fine from a hardware perspective,

 

I was just looking at that. It seems that there is a raid controller missing. Had to use the mobo disk to install driver but did not change the list for hdd's. During post it shows all three hdd's with proper st?????? Names. In bios it is different. It shows raid drives as " Intel Daniel". Went into raid config and it seems as though I named it. It does show all the hdd's with serial # as well. So obviously I renamed it. I would say that it is showing up properly imo. If you want to look deeper into this, I have a DFI x48 T2R mobo.

Now getting back to my original question, why would memtest show one of the sticks as ddr3? And when running memtest with both sticks it shuts down within 30 seconds?

Also switched slots on memory. Same problems.......

 

Right, we'll assume that the drives are all good then

For the RAM differences, I really can't say why MemTest flags them as different, did you see this when testing both or individually?

I'd have to put it down to a MemTest bug if CPU-Z finds them identical.

 

I have memtest86+ V. 3.5 Same one I used in the past. Guess I'll d/l newer version and see what happens.

 

Used v 4.2 memtest. Ran for 10 hrs with no errors.
But I am still having issues and have started a new thread.

Thanks for the help.....