GA-X58A-UD3R & Enermax 1000w Galaxy won't start up

isaw

isaw

isaw

Associate
Joined
6 Aug 2004
Posts
60
Hey guys,

Thought I'd ask here as I've been scouring the webbernet for info.

I picked up a nice OC'd bundle from OCUK a couple days ago and go to stripping out my old stuff and putting this nice new Gigabyte GA-X58A-UD3R in its place.

I decided to "upgrade" my current Enermax 650w PSU (about 3+ years old) to a "newer" Enermax 1000w galaxy I had lying around. I actually bought that about 2+ years ago and simply never used it.

So anyway, system all fitted, 1000w galaxy fitted, etc, start up -- it starts for about 2 seconds, shuts down. Then starts up for a second or so, shuts down. This happens repeatedly until I manually turn off the PSU switch to wit it then beeps twice - the PSU that is.

I look it up in the manual and it suggests a possible short. Sigh.

Whip the board and bits out of the case, check all areas for any loose wires, screws touching anything, etc. So now I have the entire system outside of the case sitting on foam/boxes away from any metal bits, etc. Trying it again, same thing. Grr.

Ok, swap back to my old PSU - the Enermax 650w. Flippin hell, SAME THING! Now I'm thinking it's the mobo - but I've never had a prob with gigabyte boards and OCUK have overclocked this one for me themselves and I know they wouldnt send out a duff one.

So i google and google and eventually hit this link : http://forum.enermax.com/showthread.php?p=383

After checking and simulation with Gigabyte, we know what’s wrong.

Every PSU has an output timing control signal to tell MB if PSU is ready or fail. There is a PSU design guide to specify this signal. On the other hand, MB also has a corresponding control to recive the message from PSU. MB would also add a resistor on that control circuit IC, to protect the IC from interference (and some MB would not have that protection). Such resistor’s value would be vary by companies and models. This variation sometime confuses PSU, as certain resistor value would pull the PSU timing control signal out of range, making MB though that PSU is not ready, and making our Galaxy PowerGuard sending error message. As the result, system would not boot up.

Our Galaxy setting works fine with most MB models introduced before mid-2007, and a lot current new MB models. Yet we notice that some MB changes that setting from 2008, making such possible incompatibility issue happen when previous design ’ PSU meets latest MB.
Click to expand...

I suppose my question, after that huge diatribe, is has anyone every had a similar issue with an Enermax PSU? :confused:

I'm surprised that both of my Enermax's perform the same but then, they are old and this Gigabyte board is new.

Have a new Corsair HX1000w on the way to I hope that sorts this out.
 
Now that is strange.

Hope it all works out.

What you doing with the 1000w enermax? Where you live?
 
Well, at the moment, I might give it a try on my older mobo (Asus Stryker II) to see if it works on that one. If not, and that Asus is also "too new" - then sweet f.a. :/

I'm down south, Surrey way. :D
 
Will do - I'll know by tomorrow eve when my Corsair shows up and I rebuild my older system for my ladyfriend.
 
Hi, have you tried the memory in all the slots? Had this problem when I built an i5 setup a few weeks ago. I solved it by putting the memory in the slots furthest away from the CPU, I had assumed it went into the sockets closest to the CPU but after reading the manual it said to put it in the other slots (this is with a P55-UD5, two blue slots closest to the CPU and two white slots furthest away).

From what you've described it sounds exactly like the problem I had (restarting constantly every two seconds until I held the power button on the motherboard down). I took everything out of the case and rebuilt it on my desk and turned it on but the problem was still there, anyway to cut a long story short I read the manual and found out the memory was in the wrong slots. I felt so stupid. :o
 
Last edited:
Well, I've now tried it with a brand new Corsair HX1000W and same issue.

I can only guess something happened in transit.

I've RMA'd it and shipped it back. Only hope the same thing happens for them.

3 different PSUs can't *all* be bad.. 2 of them are now back in other machines running fine.

@Spokwiththeears - hmm, didn't try the memory in different slots - i did remove it and re-seat it but not diff slots. Mainly because as this was an OCuk OC'd bundle, they set & tested it before it left the shop so it should have been fine.

jeez - now I'm wondering more and more about the memory slots. I SHOULD have done what you said. But then, it should have been fine in the slots there were in as the OCUK boys set it all up for me. Man, this is gonna nag me until I find out what they say about the bundle..
 
What problems are UD3R users having? I was thinking of getting one.

and what is it with new PSUs and new motherboards these days? Just have a look at the cold boot issues on the Corsair forum, mostly with Asus boards I might add. I think the Corsair TX950 + Asus X58 boards didn't work well together.

I have an issue where my P6T SE will not cold boot if the thing is overclocked at all?!? but is fine at stock (HX850) Hitting restart it boots fine.

I would suggest you set BIOS back to default (OC is saved as a profile I guess) and try again.
 
I had this issue when I had tried to OC my i7 at first on my Gigabyte mobo, it's called boot looping. To fix it all I had to do was reset my CMOS and then re-do my OC afterwards.
 
Well, it's sorted now.

RMA'd it to OCUK and the boys tested it and had same issue, etc. They sent me a new one the next day and lo and behold, it's all good.

When I first hooked it all up with the Corsair HX1000W, it did an initial start but immediate shutdown and I cursed very loudly. But then within about 2 seconds it started up again and it was fine.

Don't know if that's some sort of safety feature of the Corsair PSU..?

Anyhow, works very well. And with the Corsair CPU HX50 water cooler, it's damned quiet. Very impressed with it right now. Just waiting on my nvidia 480 to complete the unit :)

fyi - I don't know what was actually wrong - the OCUK description on the RMA ticket said it was looping, mobo fault and issued a new mobo. <shrug>
 
Well, i wouldnt worry until you have something to worry about :)

My current one is running very nicely. The issue was, from the looks of it, a mobo issue as OCUK acknowledged it in the RMA description. Maybe something happened in transit.

If I were, I'd build it outside the case (safely of course!) so if you did have an issue, you don't have to strip it down/out. Real pain in the ass..

But again, mine's running fine, OC'd to about 4gh by the OCUK boys. :D
 
Yeah, I'm sure it'll be fine. When you read someone's problems though you can't help but have a niggle of concern. :p
 
You must log in or register to reply here.
Back
Top Bottom