Is my MOBO broken? should i be worried?

fustrun

Distinguished
Feb 3, 2012
114
0
18,680
Well i recently started noticing bad performance from my computer, and discovered that one of my HD's was on his way out, S.M.A.R.T was showing that it was under "Caution" status, so i replaced it with an SSD and two 3T drives configured to run under Raid 1.
I installed the OS on the SSD and stated to run into more problems, crashes in skyrim, sound stutters in windows and some BSOD . . so i decided dig deeper and ran stress and memory tests on my PC and all the memory checked out ok so i moved on to the stress test and noticed that my PC was throwing CPU errors so i took the PC apart (Experienced not the first time) and applied a new layer of thermal paste thinking it was getting too hot and it's been ages since i've done it and attached all the memory sticks (note that i had them for over 4 years now and everything was working flawlessly before hand) and ran the tests again and failed OCCT but passed PRIME95 for 8 hours.

I was worried about the cpu but decided to try and taking out the memory and test it by adding a stick after stick and for my big surprise it passed the test, and with one paticular stick it didn't . . although all sticks passed the memtest . . then my computer stopped booting at all and long story short one of the mem slots just stopped working, i was very gentle and didn't break anything and even after trying everything cleaned it with a special computer board cleaning spray thing.

After all the fuss i decided to give up and just not use the slot because i had one stick that just wouldn't let me pass the OCCT test, so i thought i'd leave the stick out . . and 12gb is still more then enough.

About three days passe and yesterday i turned it on and it refused to boot (I have an Asus Sabertooth P67 Board) so i decided to use my boards, MEMok function and it booted my memory with 1000mhz speed and my default memorie's speed is 1600 . . i was very surprised but even more when windows tried to boot it gave me a bluescreen and refused to load, so after a lot of fuss i changed the Turbo mode feature (OC in other words) from Auto to X.M.P mode that has a profile set for some mem and cpu models and vendors (at least that's what i understood it does) and it booted up under 1600mhz just fine . . and windows right after it.

Now today i turned it on and it gave me the chasis intrude error, i am pretty sure it's a false possitive i haven't touched my hardware and have no loose wires inside the case then i tried to reboot and it came up again no problem . . without any changes.

This whole story has been stretched over for a few weeks and i'm just afraid to turn it off . . my PC passes all the tests and benchmarks including MEMtest, OCCT, Prime95 and 3Dmark and Heaven Benchmark, no errors and smooth performance but i'm just dreading turning him on, i have a friend who is a computer technician working in a store and came by and took a look on my PC and checked for damage and settings and said that everything is looking good and that a lifespan of a computer is about 4-5 years (my PC about 4.5) and that if everything's running fine just leave it as it is, but it ran ok just a week ago on the Auto OC settings and without touching it, it started doing problems untill i changed it to X.M.P and random chasis errors, am i just being too picky about all of this wanting my system to be "perfect" or does it sound to you like i have a serious problem ?

Sorry for the wall of text and any advice would be greatly appreciated !

Hardware :
Intel i7 2600 Sandybridge 3.40ghz
16gb Corsair Vengance RAM 1600mhz 9 9 9 24
Asus Sabertooth P67 MOBO
680 GTX 2gb Gigabyte Windforce
OCZ Vector SSD 128gb
1T Black Caviar
x2 3T Red Caviar (Raid1)
 
That is a 4GB Single Module DDR3 Memory Kit. XMP settings are for the use of a single DIMM, not 2,3, or 4 DIMMs. Compatibility is guaranteed within a single kit not multiple kits. By mixing memory kits together, there may be compatibility issues such as unable to boot or unable to operate at rated specifications.

You might try manually setting the memory clock to the next slower speed and using looser DRAM timings.