New Build £1k Budget

FinalSquall said:
Can i confirm that it definately cant be the 3000MHz memory? Otherwise i wld try buying slme 2133MHz If i boot with no memory and still get code 55 it has to be CPU right?
Click to expand...

RAM is RAM, it will default to stock before you enable XMP anyway.

Check the CPU for bent pins or make sure the cooler isn't too tight.
 
Ok cheers for the response. Well after work i will loosen the cooler then try. Failing that i will take out the cpu and check pins. Plus give u guys some pics of socket and cpu to see if u can spot a bend i have missed.
 
Well, I have reseated the CPU looked for bent pins ( I really cant see any) and redone the CPU power cable in a different slot in the PSU just incase. Tried with 1 stick of RAM 2 sticks and no sticks, all giving me Error code 55. Here are pictures of the MOBO and CPU
Image of MOBO, though you cant really tell much from it, but I just dont see any of them being bent tbh.

Image here; https://imageshack.com/i/pnjuBKutj

I am out of ideas, any one got any thing else to suggest, or time to think of RMA? In which case, how do I know what is faulty MOBO or CPU (I have no spare 1151 gear to test with)
 
If you were local I would help and try some of your bits.

Socket picture, ideally needs to be face down as the pins are so small an angled shot wont give much away.

Youve tried clearcmos? you have made sure the RAM "clicks" into place and the retention clip goes inwards by itself.

And just to make sure you've not been daft (sorry) the cpu was inserted with the writing the right way up and the arrow on the corner of the cpu matching the little arrow marking on the cpu socket/pcb.
 
Hey stulid, yea its definately in the right place, I mean the Arrow in the bottom left of the CPU chip and the arrow in the bottom left of the MOBO socket its quite a no-brainer.

Hehe, near London area myself (Hertfordshire) so not local enough sadly =P

Here is a 'birds eye view' of the socket;

https://imageshack.com/i/pmJ3wrKBj

Tried clear cmos, only difference that made is that it made it keep resetting again.

Basically very first time it booted it did a reset loop, and continued to do so a few times after that, but eventually it stopped rebooting, and just stayed on with the 55 displayed on the Debug LED. Clear CMOS made it reset loop again (Note that is I did not let it keep rebooting itself, I was booting it off with power but eventually when I turned it on it stopped looping resets)

Plus on the RAM thing, I am pretty confident it is clicked in place, but I think that if the RAM was the issue I would get a different debug LED to 55 when booting with no RAM insttalled.
 
Last edited:
Just to cover the bases, this could not be a PSU issue right? I assume if it powers the MOBO properly it is providing power to the 12v properly? Issue can only really be MOBO/CPU related?
 
Hey, nah nothing else was plugged in, but its dismantled and sat in the box ready for return currently =(. Probably the mobo, but sending the CPU aswell just in case.

Two previous builds went perfectly smoothly, I suppose I was due one like this at some point =P. Maybe I should have stuck with an MSI board
 
Last edited:
Hey all, sorry to bump this thread again, but I have set things up after getting a new board on RMA and so far I am more successful, the PC get to post debug code AE and does not get past it

The code info says something about legacy OS, any ideas what this means, and what I could/should try to fix it?

I have seen some people say that the PC is booted at this point and should be showing hit del to change boot device. But I am getting no input to the monitor through the HDMI cable (note, no GPU plugged in)
 
Last edited:
Hmm, well putting a GPU in and using DVI for monitor seems to have solved that as I can now see the output, however I do wonder why the HDMI output wasnt working? Does HDMI not work until the PC is working at OS level?
 
Ok, I am now somewhat dissapointed, I noticed one stick of RAM wasnt working as I only saw 8GB, switched them round, and it seems to have caused this issue again? I.e. the issue mentioned early in the thread and now wont get past Code 55. Can a bad RAM stick literally take out a motherboard? Because that is waht seems to have happened. Doesnt matter what I do, chaneg them back round, take both out, or anything. It worked fine, it now wont get past code 55 again. /huge sigh

Must have got "lucky" this time and put the faulty stick of RAM in slot 2. But putting the faulty RAM in slot 1 = No post past 55. And no post past 55 ever again. Man, this sucks
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom