Quote:
Originally Posted by
IDavidRawr 
first of all he already has returning in mind.
second a asrock extreme 4 is like 50 bucks at mircocenter
he can get another cpu there too thatll save him 100 bucks why just settle for a free fix for a problem when you can upgrade and still save an extra 100 bucks last i checked
-100 is better than free
and
since he has a ib wouldnt it be common sense to just consider the upgrade especially since his board is probably 50-60 more than a z77, and isnt it ignorant to just not go for the obvious better solution
it saves him money fixes his problem, i dont see where im wrong here. as for your comment on no such thing as for sure fix, if what you say were true then this thread would be pointless. im not sure you realize
IT WILL WORK 100% if he just changes his things, dont be ignorant and just be open minded por favor
Oh hell here we go again, so you telling op to basically run out and purchase new stuff if his current setup runs into a little hiccup

last time i checked no matter how much you save while you are spending money its not better then fixing the problem for
FREE
If you would have payed some attention to the thread you would know he is running a 2700k and last time i checked that is a Sandy Bridge processor

I must not be the only person in this community to think you are being ludicrous and I am an open minded person but I am not a Naive person like you that would go out and start wasting money on product that may or may not fix a problem where the solution to the problem is to find the root of the cause and fix it. Are you 100% sure that a new motherboard will fix it? no because you never troubleshoot anything so please stop posting here unless you are willing to do some leg work and help op figure out the problem. Personally I don't think it has anything to do with ram not being compatible since its ddr3 on a ddr3 Dimm socket

and the 55 error code may or may not mean its a ram problem since i linked a thread earlier showing someone having the same exact problem and it needed a firmware upgrade. I am also aware that the 2700k was supported since firmware 1.10 but an update would not hurt if it would actually fix his problem.