This is why there is a burn-in period for new hardware...

New MB decided it didn't want to boot anymore. Rebooted after adding 
software: System would beep, The MB logo would show, screen would blank, 
system would beep, the MB logo would show, screen would blank ...

Pulled 1 memory module, same thing
Swapped memory module, same thing
Unplugged drives, same thing
Shorted CMOS reset jumper, same thing
Unplugged power cable, wait 30 sec, plug in, same thing

Called Gigabyte support, rep did all of the above plus

Unplug keyboard, same thing
Remove CMOS battery wait 30 sec, replace, same thing

Support rep concluded "Dead Board, here's our website for RMA"

crap.
-- 
~Mike

Post a reply to this message

> New MB decided it didn't want to boot anymore. Rebooted after adding 
> software: System would beep, The MB logo would show, screen would blank, 
> system would beep, the MB logo would show, screen would blank ...

Didn't you mention that the PSU you were using was a bit on the low side for 
your hardware?  Maybe the CPU and GPU combination all firing up to max at 
boot is enough to reset the PSU?

If you haven't already boxed it up, maybe you could try with an older 3D 
card that isn't as power hungry...

Just an idea.

Post a reply to this message

scott wrote:

> Didn't you mention that the PSU you were using was a bit on the low side 
> for your hardware?  Maybe the CPU and GPU combination all firing up to 
> max at boot is enough to reset the PSU?

It is, but within range for the requirements, just not a lot of 
headroom. Using the same graphics chipset with the older processor 
worked fine.

Watching the voltages in Speedfan when the system was running show no 
fluctuation, even when running processor and GPU heavy software. The 
system appeared stable otherwise.

I did at one point have everything unplugged from power except the GPU 
and fans, and motherboard; no drives or external devices.

I wouldn't think the GPU would cause high demand without being 
instructed to run 3D.

Maybe I'll walk the board down to the local shop and have them test it out.

I did some reading on the issue I'm seeing, and it seems as if it's 
likely a bad board, many people who have this board have encountered the 
same problem.

> If you haven't already boxed it up, maybe you could try with an older 3D 
> card that isn't as power hungry...

My older 3D card is AGP, this board uses PCIe... ;)



-- 
~Mike

Post a reply to this message

Mike Raiford <"m[raiford]!at"@gmail.com> wrote:
> This is why there is a burn-in period for new hardware...

Bought a new AMD machine as a secondary (to run time-consuming renders on) a few
months ago:

- Hooked it up to the VGA input of my 2-year-old 19" LCD; never used that input
before IIRC, just the DVI; had the computer run overnight, to wake up the next
morning to the smell of fried capacitor: LCD dead, after using the VGA input
for only a couple of hours.

- Only a few days later (using a spare 15" LCD meanwhile), computer fails to
boot up: Cannot find operating system; mainboard still detects that there is
*some* SATA device connected, but fails to make out any details; swapping SATA
ports with the CD/DVD drive (which was detected ok) doesn't change a thing:
Hard disk electronics dead, after only a few days.

Post a reply to this message

clipka wrote:

> - Only a few days later (using a spare 15" LCD meanwhile), computer fails to
> boot up: Cannot find operating system; mainboard still detects that there is
> *some* SATA device connected, but fails to make out any details; swapping SATA
> ports with the CD/DVD drive (which was detected ok) doesn't change a thing:
> Hard disk electronics dead, after only a few days.

Was it the monitor that took out the computer or the computer that took 
out the monitor?

-- 
~Mike

Post a reply to this message

scott wrote:
>> New MB decided it didn't want to boot anymore. Rebooted after adding 
>> software: System would beep, The MB logo would show, screen would 
>> blank, system would beep, the MB logo would show, screen would blank ...
> 
> Didn't you mention that the PSU you were using was a bit on the low side 
> for your hardware?  Maybe the CPU and GPU combination all firing up to 
> max at boot is enough to reset the PSU?
> 
> If you haven't already boxed it up, maybe you could try with an older 3D 
> card that isn't as power hungry...
> 
> Just an idea.
> 
> 


Well, at the advice of some people on the support forums, I decided to 
try the board outside of the case, with nothing but the monitor and 
keyboard connected.

Worked perfectly...

I'm wondering now if the USB hard drive that was plugged in was causing 
it to reboot itself. The cable has been a bit dodgy lately, and I 
noticed it flaked out a bit on the old MB, vista complained about it 
being an unknown device... so, maybe that was it... <shrug>

Vista stayed activated. Neat-o.

Post a reply to this message

Mike Raiford wrote:
> 
> I'm wondering now if the USB hard drive that was plugged in was causing
> it to reboot itself. The cable has been a bit dodgy lately, and I
> noticed it flaked out a bit on the old MB, vista complained about it
> being an unknown device... so, maybe that was it... <shrug>
> 

So.. You actually did plug out the internal hard drives etc, but not the
external one?

-Aero

Post a reply to this message

Mike Raiford <"m[raiford]!at"@gmail.com> wrote:
> clipka wrote:
>
> > - Only a few days later (using a spare 15" LCD meanwhile), computer fails to
> > boot up: Cannot find operating system; mainboard still detects that there is
> > *some* SATA device connected, but fails to make out any details; swapping SATA
> > ports with the CD/DVD drive (which was detected ok) doesn't change a thing:
> > Hard disk electronics dead, after only a few days.
>
> Was it the monitor that took out the computer or the computer that took
> out the monitor?

In all likelyhood it were independent acts of suicide.

I was a bit worried that the computer might have fried the display, but they
gave it some thorough checking at the shop and found no fault. As both display
and hard disk were replaced free of charge, I also had no reason to try find or
construct any connection between the two events.

Post a reply to this message

Eero Ahonen wrote:

> So.. You actually did plug out the internal hard drives etc, but not the
> external one?

<sheepish> ehmmm.. rrrright. Didn't stop to think the external USB 
device would have any effect on whether the system would boot or not.

-- 
~Mike

Post a reply to this message