Official GIGABYTE Forum

X58A-UD3R motherboard problem

grn

  • 10
  • 0
X58A-UD3R motherboard problem
« on: December 08, 2010, 02:59:30 pm »
I have just built myself a new PC and have a problem when I try booting it up.

The system is:

         1. Cooler Master HAF-X case
         2. X58A-UD3R motherboard
         3. 3x4GB Crucial memory modules
         4. Zalman Utlra Quiet CPU cooler
         5. Intel i7-950 CPU
         6. XFX P1-850B-NLG9 PSU

The graphics card I am using is temporary (I'm awaiting the card I want) - it is a Gigabyte GeForce 8400 GS.

When I power up the system, power comes on, then goes off and finally restarts after a couple os seconds. Is this normal?

The case has 4 case fans but there are only 3 fan headers on the mobo. There is an unused header for the northbridge fan and the power fan. Can I use either of these headers to power up the fourth fan? There is a fan header->molex connector and I have this connected to a Molex but the fan does not operate.

Thanks in advance
MB: GA-X58A-UD3R (Rev 2.0?)
CPU: I7-950 @ 3.07GHz
GPU: MSI GTX 670 PE OC
PSU: Coolermaster RS-850-SPHA-D3 850W Silent Pro Hybrid 80+ Gold
Mem: Crucial 3*4GB 1333

Dark Mantis

  • *
  • 18405
  • 414
  • 10typesofpeopleoneswhoknow binaryandoneswhodont
    • Dark Mantis
Re: X58A-UD3R motherboard problem
« Reply #1 on: December 08, 2010, 03:09:01 pm »
Hi and welcome to the Gigabyte UK Forum.

This is quite a common thing that happens and is not detrimental to the system components as far as I know. We were discussing this exact occurance  only a couple of weeks ago and we never did really come to a conclusion as to what causes it. I have had it on my own machines before and think it is caused by a coalition of certain parts coming together. Some people find it only happens on a cold boot and others that it happens all the time.

I would suggest that you check the molex adapter for the fan as it should work off that and is the most sensible way of powering it. Using the Northbridge header isn't really advised for case fans especially if they are large ones.
« Last Edit: December 08, 2010, 03:12:56 pm by Dark Mantis »
Gigabyte X58A-UD7
i7 920
Dominators 1600 x6 12GB
6970 2GB
HX850
256GB SSD, Sam 1TB, WDB320GB
Blu-Ray
HAF 932

Gigabyte Z68X-UD5-B3
i7 3770K
Vengeance 1600 16GB
6950 2GB
HCP1200W
Revo Drive x2, 1.5TB WDB RAID0
16x DLRW
StrikeX S7
Full water cooling
3 x 27" Iiy

grn

  • 10
  • 0
Re: X58A-UD3R motherboard problem
« Reply #2 on: December 08, 2010, 03:29:17 pm »
Thanks for the response. I'll see what happens after I get the OS installed.I did get an odd beep code as I put my memory modules in slots 2,4,6 instead of 1,3,5. It was a sequence of a long beep lasting a couple of seconds, followed by a pause then the sequence repeated. At least I think it was a long beep although it could have been a sequence of very short beeps - the long 'beep' was an oscillating tone not a continuous tone. It didn't seem to match up to any of the beep codes listed in the manual and I thought I had a graphics error until I realised my mistake with the memory slots.
MB: GA-X58A-UD3R (Rev 2.0?)
CPU: I7-950 @ 3.07GHz
GPU: MSI GTX 670 PE OC
PSU: Coolermaster RS-850-SPHA-D3 850W Silent Pro Hybrid 80+ Gold
Mem: Crucial 3*4GB 1333

Dark Mantis

  • *
  • 18405
  • 414
  • 10typesofpeopleoneswhoknow binaryandoneswhodont
    • Dark Mantis
Re: X58A-UD3R motherboard problem
« Reply #3 on: December 08, 2010, 03:37:24 pm »
You must install the modules in slots 1, 3 and 5 for Triple Channel mode. That is probably why you got the funny beep code.
Gigabyte X58A-UD7
i7 920
Dominators 1600 x6 12GB
6970 2GB
HX850
256GB SSD, Sam 1TB, WDB320GB
Blu-Ray
HAF 932

Gigabyte Z68X-UD5-B3
i7 3770K
Vengeance 1600 16GB
6950 2GB
HCP1200W
Revo Drive x2, 1.5TB WDB RAID0
16x DLRW
StrikeX S7
Full water cooling
3 x 27" Iiy

Sadah

  • 17
  • 1
Re: X58A-UD3R motherboard problem
« Reply #4 on: December 09, 2010, 10:10:02 am »
i actually had the same issue but that happened only after i o/c my cpu to 3.6 also xmp on. when running on default clocks this aint happening...
so i figured that it is maybe a psu issue, trying to set voltages right while booting on o/c mode...
btw that only happened on cold boots, never on restarts..