GA-Z97-D3H and MSI R9 270x Hawk won't boot

[knapper]

Hi all,

I'm trying to install a new GA-Z97-D3H (rev. 1.1) into my brothers PC, along with a new i5. With 270x installed it gets into a boot loop where powers on for 5 seconds or so, powers down, then restarts. During this process the monitor picks up no signal. With the card removed it powers on and happily uses the onboard graphics. I've upped the motherboard BIOS to the lastest version (f9), with no change in behaviour. The 270 was working with the old motherboard, I've tried fitting an old 9800gtx+ and that booted happily. I really not sure what else I can try.

Thanks for any input. 

[dmdilks]

Have you tried the other slot just to see if it will boot. If it does there could be something wrong with this slots.

[knapper]

Hi,

The 9800gtx+ works in the x16 slot so it appears the slots OK. I've tried resetting the CMOS which has slightly changed the behaviour, but not got things working as they should. I'm in contact with gigabyte and I've just updated them with these results;

"I've reset the CMOS by removing the power cable and battery. I have retested using a old 9800gtx+ and get the following behaviour;

1) With the 270X in the x16 slot it still goes into a endless reboot sequence as described (I stopped it after 8 restarts).

2) If I insert the 270X in the x4 slot after pressing the power button the computer briefly powers up, shuts itself down, restarts itself and successfully starts to boot.

3) If I install the old 9800gtx+ in the x16 slot it produces the same behaviour as outlined in scenario 2 (quickly shuts down once but begins to boot after it restarts itself)."

Before the latest CMOS clearing it wouldn't boot when it was in the x4 slot as far as I remember, but it still shows no signs of life when in the x16 slot.

 

[knapper]

On advice from gigabyte support I've tried changing the PCI settings manually and found that the Hawk will boot in the x16 slot when it's set to Gen2, but it'll go into the endless restart sequence when set to Gen3. It seems the basic problem is that for some reason the motherboard and 270X aren't happy to cooperate at Gen3 specs, the question now is why? is there a settings tweak that might work, or is it an insurmountable compatibility issue that means one has to go? 

[dmdilks]

The only other thing you could try is make sure everything is set legacy mode and seen what happens. 

VGA Support
Allows you to select which type of operating system to boot.
Auto Enables legacy option ROM only.
EFI Driver Enables EFI option ROM. (Default)

Boot Mode Selection
Allows you to select which type of operating system to boot.
UEFI and Legacy Allows booting from operating systems that support legacy option ROM or UEFI
option ROM. (Default)
Legacy Only Allows booting from operating systems that only support legacy Option ROM.
UEFI Only Allows booting from operating systems that only support UEFI Option ROM.

Initial Display Output
Specifies the first initiation of the monitor display from the installed PCI graphics card, PCI Express graphics
card or the onboard graphics.
IGFX Sets the onboard graphics as the first display.
PCIe 1 Slot Sets the graphics card on the PCIEX16 slot as the first display. (Default)
PCIe 2 Slot Sets the graphics card on the PCIEX4 slot as the first display.
PCI Sets the graphics card on the PCI slot as the first display

[dmdilks]

One other thing yes it will boot with the 9800gtx+ works in the x16 slot so it appears the slots OK. I have seen this in the past on some board this to happen. Why I can't tell that one. Like you said the board and the card just don't like each other. 

[knapper]

Thanks for the input, might try one or two little things but it appears that the only way things are going to work is to just keep it set to Gen2. Given the slight real world performance difference between 2 and 3 given todays hardware, this isn't really a big problem, however the main concern is does this reveal a weakness in the board design that might be more of an issue in the future? On the other hand the old motherboard was only a PCI 2.0 board so it be an issue with the card.

Basically, my choice is be happy things are working and ignore the lack of clear reasons where the compatibility problem lies, or try changing the board in the hope the eliminating the problem completely (even though performance wise it'll make little difference).