A cry for help!!!

ruskle

ruskle

ruskle

Associate
Joined
17 Aug 2011
Posts
81
Location
London
This is my first build, I put it all together on the weekend and when the monitor came today tried to switch it on.... lights come on, fans start but no signal to the monitor and the debug LED code reads 58 (CPU self test failed or possible CPU cache error). I've googled it and the general theme of the threads would suggest that it has something to do with memory so I've tried every config of the mem sticks I can. On their own one of the sticks on it own gets a 34 (CPU post memory initialisation) in every slot, the other gets 58. I've also tried reseating the CPU, no effect.

I don't want to sound melodramatic but I'm really upset, I've just had to leave it and get some strong beer from the shop. Its exacly what I was afraid of when my mate was saying "just build one yourself, its easy!". I'd really appreciate some help, I suspect there may actually be something wrong with the memory and the motherboard but being a total noob I naturally assume I've done something wrong.
 
First of all thanks for getting back to me so quickly, its good to know I'm not alone!

I've removed the graphics card to eliminate possibilities. The hdmi was plugged straight into the mobo anyway so should be able to run using the i5 gpu correct?. There is a CMOS reset button on the back, I have pressed it after shutting down with the power still on. I don't know if thats right.

I've pressed down on the cable connections all seem ok.

Whats worrying is that normally you find a thread where some dude had the same problem and sez "yeah that sorted it". I can't find such a thread, I fear Rik1254 maybe right....
 
The second power plug to the mobo was an 8 pointer with a little cap over 4 points. I originally plugged a 4 point cable into it. I've just taken off the cap and plugged in an 8 point cable....no effect.

Will try the jumper now.
 
ok I've just used the jumper as per the manual again to no effect.

What do people think of the fact the debug code changed depending on the ram config. I'm currently trying everything with just one stick in.
 
yeah well I think its either the ram, mobo or cpu... lol not much else it could be. Reckon I'm gonna call tech support tomorrow and then send them back.
 
Right pics, its a bit of a mess now cos I've been ****** around with it and changing power cables n stuff but here they are anyway

[23:18:56] swifty:
P1010367.jpg


[23:18:21] swifty:
P1010365.jpg
 
@Komedy - I really appreciate you taking your time to help me with this.

I've gone through the 6 steps and no dice. I read about problems with overtightening coolers when going through the initial build so had been careful, although I've tried it with the stock now and still no dice.

I'm going to RMA the board. I think I should also do the RAM given that I get different debug codes with the different sticks. To be on the safe side I'm gonna send back the CPU as well.

More bad news as well I bought my components from two sources OCuk and a competitor to get them as cheap as possible. I checked my orders and all the components that could be fooked are from the competitor and they don't have any technical support. Doh!
 
Quick update: I've RMA'd the mobo, cpu and ram.

Turns out the supplier did have tec support and after running through the steps I had, taken agreed it could be any of these.

I tried just motherboard, cpu, ram, cooler, psu, monitor to no avail. Unfortunately don't know anyone nearby with an i5 build or any ddr3 ram.

Will let you know what happens.
 
You must log in or register to reply here.
Back
Top Bottom