Currently setting up a new PC, the Mobo is a Gigabyte GA-F2A88XM-HD3 paired with an AMD Athlon X4 760K & HD7850 GPU.
Used the Gigabyte @BIOS tool to update the BIOS, it got part way through the process & then screen just went black, left it for 15 minutes & nothing changed. Turned it off & now all I get is a blank screen.
This mobo has Dual BIOS so should in theory fix itself but without getting a screen output I have no idea whats going on.
I've tried resetting the CMOS using the onboard pins, manual says only 5 secs needed (enough time?). I also took the battery out afterwards. Has made no difference.
What I'm wondering is if the clearing of CMOS or the dual BIOS recovery means the board is now trying to output through the onboard graphics rather than the GPU? Problem being that the 760K has no graphics chip so no way of using the onboard ports without getting an APU from somewhere.
Found some other pages that talk about shorting some pics on the BIOS chips to force the second BIOS to be used but dont want to do that if in fact the issue is just that I can't see what the recovery is trying to fix.
Anyone got any ideas?
Used the Gigabyte @BIOS tool to update the BIOS, it got part way through the process & then screen just went black, left it for 15 minutes & nothing changed. Turned it off & now all I get is a blank screen.
This mobo has Dual BIOS so should in theory fix itself but without getting a screen output I have no idea whats going on.
I've tried resetting the CMOS using the onboard pins, manual says only 5 secs needed (enough time?). I also took the battery out afterwards. Has made no difference.
What I'm wondering is if the clearing of CMOS or the dual BIOS recovery means the board is now trying to output through the onboard graphics rather than the GPU? Problem being that the 760K has no graphics chip so no way of using the onboard ports without getting an APU from somewhere.
Found some other pages that talk about shorting some pics on the BIOS chips to force the second BIOS to be used but dont want to do that if in fact the issue is just that I can't see what the recovery is trying to fix.
Anyone got any ideas?