8k5a2 - Boot problems, what's the propable cause?

[korpiotus]

Hello!

My 8k5a2 has started to act really strangely lately. It has apparently thought that I shouldn't oc my rig anymore, because it does the following:

1. If I raise voltages (vcore or vmem) even a notch, I get a c1 error and the motherboard fails to boot. Pressing reset doesn't help when this happens, only using the power switch.
After turning the computer back on it boots up a little further and stops at error code 26.
After a second flicking of the power switch the computer posts with default bios settings and works ok.

2. The same thing happens when I change the multiplier of the cpu or the fsb.

A strange thing is that every once in a while the board boots up with the voltages, multiplier or fsb I have selected and works ok the next couple of boots until it once again stops at the c1 error.

I have tried running the board without anything extra to try and find out what's causing the behaviour, but haven't managed to improve the situation even a bit.
I've also tried clearing the bios several times as well as re-flashing it.
It seems that the problem is caused either by my 8k5a2 (the propable cause), my psu (might be), my memory module (doubt it) or my display adapter (also doubt it).

I started to experience this behaviour after I installed my new shiny water block on the north bridge, but I don't think I broke anything major while installing it, because my computer works perfectly if I run it @ default bios settings (eg. no voltage adjusting or such)

I've seen this problem manifest itself with both of my T-Bred B cpu's (1700+ JIUCH0251 and my new 2100+ AIUHB0302), but I didn't encounter it with my 1800+ palomino (at least as I recall).

Any thoughts on what might be wrong with my otherwise excellent board?

[Crafter]

Hi, have you looked in your manual to see what the code from the leds report?I think the code are in the begining and some more detailed ones at the end of the booklet.As a rules of most OC guys, if you have anything funny going on with the voltages try a different power supply, often the PSU is the root of ALL evil :)I don't think it would have anything to do with the CPU's or N-bridge cooling.But try the PSU even though it may seem unrelated. cheers

[korpiotus]

Apparently everything was caused by the iru3055 voltage regulator malfunctioning.
It may have been overheating (as it often does on 8rda+) and thus causing the behaviour.
I solved the problem by saying "oh what the h*ll" and cutting the pin 16 from the iru3055 (=overvoltage protection).
This remedied everything..
Until a week or so later I head a funny sound from the motherboard and noticed that a condersator had blown up and another one had bulged. And one of the mosfets had gotten quite a tan.
A quick solution to this was to change the condensators and Behold! My motherboard was working once again.
For about five minutes.
Then the replacement capasitors blew up with a dandy smoke effect. And at the same time another mosfet gave up on me and broke down completely.

So now all I have is a broken 8k5a2 that needs 2 capasitors, a mosfet, heatsinks on all the mosfets and iru3055 chip to prevent overheating and I'll propably have to fix the pin 16 I cut by soldering..
Oh well
At least I got myself a 8rda+ as a replacement board [img]smile.gif[/img]

I think that the main reason for what happened is that I ran the motherboard at max voltages (vcore 2,15 / vmem 3,1v). This combined with epox's motherboards poor voltage regulation..*boom* [img]smile.gif[/img]