Memory Faults

manisinghb · 8 Jan 2010 at 22:15

Hi guys, i have 6gb DDR3 Corsair memory (3x2gb sticks) but the system picks up 6.00GB RAM (4.00GB usable) and says i am running on a dual channel when it should be triple? i have tried switching the sticks around etc to see if any are faulty but all are running fine/ any suggestions??

manisinghb · 9 Jan 2010 at 01:19

windows 7 64 bit

manisinghb · 9 Jan 2010 at 14:47

MoBo - Gigabyte EX58-UD5, CPU - i7 920, Windows 7 Ultimate 64bit, GFX Card - ATi 5850

manisinghb · 9 Jan 2010 at 15:27

theron said:
i think corasiks suggestion of reseating the cpu (or at least the cooler) will help. ive heard of problems where the cpu cooler has been tightened too much and the pressure stops the imc from using all the installed ram.

i am using a watercooling system with a waterblock but maybe this might help, i will give it a go!

manisinghb · 9 Jan 2010 at 19:54

whats good memtest?

got a problem now guys, reseated the cpu and reconnected cpu waterblock but now the computer switches off as soon as i power the computer on. when i take the atx pci power connection for the CPU the computer remains powered on but obviously won't boot up. any ideas?

manisinghb · 9 Jan 2010 at 19:59

sandeep said:
Take the CPU out and check for any broken pins. First thing that came to mind.

done this mate dont seem to be any broke pins

manisinghb · 9 Jan 2010 at 20:10

sandeep said:
Ermm. What tim did you use. If it's as5 then check around to see if any has gone within the components.

Also check. You may have put too much pressure on the CPU.

whats a tim sorry? im using a UD5

manisinghb · 9 Jan 2010 at 20:23

oh im using mx3 which is non conductive i thinks

manisinghb · 9 Jan 2010 at 20:26

sandeep said:
Yes it isn't conductive. So you should be ok on that end. Check the pressure your block has on the CPU.

tried many pressures my friend, even tried with the block off, and at the moment the block is probably tightened 3 threads so not tight at all. even done it very tight lol. still no luck though...

manisinghb · 9 Jan 2010 at 20:31

sandeep said:
Try with only one stick of ram. If that doesn't work don't think you have another CPU to test in your current rig?

no i don't unfortunately, i have a VERY old CPU (from 2003) which i doubt will work

edit: the one stick ram dont help either

manisinghb · 10 Jan 2010 at 20:43

Phatzy said:
since no one said this.
Have you got memory remap enabled in bios?
Have you unticked memory in advance options in msconfig?

i can't do this mate as system won't even get 2 past the boot stage in order for me to enter setup, it shuts down almost immediately and keeps restarting itself in this way

manisinghb · 10 Jan 2010 at 21:00

sandeep said:
I take it there's no beeps to troubleshoot?
Also did you try using just one RAM Stick?

nope no beeps and yup tried that 1 ram thing

manisinghb · 11 Jan 2010 at 14:16

Phatzy said:
oh sorry i just read first few posts, i didnt realise you got another problem.

make sure the cpu contacts at the bottom of the cpu is clean of any thermal paste and the pins are not bent (i know you said they dont seem bent or missing, but double check).
check graphics card in another pc.
check psu in another pc.
and other stuff thats in the pci slots (if any).
have you cleared CMOS?
clear dust from ram slots and pci-e and pci slots.

what is the best way of cleaning the socket and contacts?
everything else ive checked and done, the thing is its a brand new system, was running fine except saturday when i reseated the CPU this happened...

manisinghb · 11 Jan 2010 at 14:42

does the thermal paste matter? because obviously i took the cooler and cpu off the motherboard do i need 2 reapply? should this affect the performance anyway?

manisinghb · 11 Jan 2010 at 14:53

ok guys update, when i take the 8pin power connection for the cpu socket out of the mobo, the system remains powered on...

manisinghb · 11 Jan 2010 at 15:35

QwaF said:
Yes

but would this be the cause of my system restarting itself and not booting up properly?

manisinghb · 11 Jan 2010 at 22:13

Phatzy said:
its stays on, what like, posts?, boots into windows?.
cpu's are very very rarely become faulty, try the cpu in another motherboard if you know a mate that has such a board.
maybe the motherobard got damaged while you was resetting cpu cooler.

no doesn't boot at all mate just stays on i.e. no booting 'beeps' no screen display nothing. i have to say though while reseating the cpu, the waterblock (cpu cooler for the water system) did hit a component on the motherboard. i don't know what it is or if it could have caused this and it wasn't a big hit either and i can't see no visual damage just worth the notice i think. looks like a heatsink, its a blue 'block' thing directly underneath the cpu socket on the Gigabyte UD5 mobo if anyone wants to check on google..

manisinghb · 12 Jan 2010 at 17:48

hey guys just an update 4 ya'all: couldn't get the MoBo to work normally even tried on another PSU etc. Have opened an RMA been asked to send it in and they will examine and replace (hopefully) for me. The technician I spoke to however did say that me dropping my waterblock on the NB heatsink shouldn't interfere or damage the MoBo's performance. Fingers crossed! will keep the status updated in this thread will post it off tomorow. Thanks for all your insight!
P.s. Sandeep - Kiddha veera

manisinghb · 13 Jan 2010 at 14:25

hey guys just a quick thing i was thinking of, on the mobo there is a 8pin pci power connection slot for the cpu socket. however, due to the shapes of the pins on the pci cable running from my psu, i was only able to connect 4pins out of 8. however, i then found an adapter in the psu box which lets me connect all 8pins to the 8pin slot on the mobo for the cpu socket. does anyone think there is a potential risk in doing this? overvoltage etc?

manisinghb · 13 Jan 2010 at 15:00

sandeep said:
The 8pin was there to be used. It provides extra power to the CPU. It won't burn anything out. I'm using it on my mobo with a 125w phenom ii so you should be ok.

But if you hadn't had that plugged in before your system messed up then that isn't the issue.

tbh i plugged this in to see if it works and it booted up normally. i then reseated the cpu (obviously after powering off) and thats when the problems started...