Question (SOLVED) Gigabyte Motherboard Not Booting - Boot Looping (GA-Z270X-Gaming K7 (1.0))

Status
Not open for further replies.
Sep 23, 2019
7
1
10
SOLVED: Motherboard was dead. Bought a new one.

Specs:

Product Name: GA-Z270X-Gaming K7 (1.0)
BIOS Ver: No way to know
Purchase Dealer: Newegg
Brand: GIGABYTE
CPU: Intel Core i7-7700k
Operating System: Win 10 64-bit
Memory Size: 8GB x 2
Memory Part No.: Ripjaws F4-2400C15D-16GVR
Power Supply: EVGA 500W W1, 80+ WHITE
Graphics Card: GIGABYTE GeForce GTX 1060 Windforce OC GV-N1060WF2OC-6GD Video Card

Problem:

I'm experiencing a boot loop with my Gigabyte motherboard. It cannot even boot to BIOS.

I have used this setup since Jan 2017 (nearly 3 years), and only suddenly has this problem started.

Symptoms:
1) Ever since installation, I periodically received a Windows blue screen of death for DRIVER_POWER_STATE_FAILURE (https://images.drivereasy.com/wp-content/uploads/2015/08/driver-power-state-failure-1.png). This would happen once every couple months. I am unsure if this is related.

2) About a week before today, my computer would suddenly without warning restart (but would get back into Windows 10 no problem).

3) I went into the BIOS settings and changed the settings to Secure Boot, as I was following a guide to try to resolve the restart issue.

4) Now the machine won't even boot to BIOS. It keeps restarting over and over, with the codes 22, then 65, then 97 immediately prior to the system shutting off, then trying again.

What I've tried:
1) Resetting the CMOS. (Removed the battery, shorted the CMOS reset pins, and even connected the +ve and -ve of the CMOS battery to ensure it was resetting. I'm fairly confident that the CMOS is successfully resetting, since the behaviour of startup changes (many different codes show first, prior to the boot loop restart failure occuring).

2) Replaced the CMOS battery.

3) Removed all hardware (graphics card, memory, SSDs, network... everything except the vitals)

4) Re-seated the memory cards.

5) Tried with a single RAM stick only (in all permutations).

6) Searched the entire motherboard for leaking or mushrooming capacitors. None found.
---------------------

I'm uncertain what to try next. I have a feeling that it's a short circuit somewhere, but I don't see how changing the BIOS settings would initiate the problem, despite my resetting of the CMOS several times over. (I assume my settings would be cleared?)

Thanks for your help,
 
Last edited:
From your specs list, I'm assuming you're only working with the iGPU(and not a discrete GPU)...? If so, see if you can source a higher wattage reliably built PSU to power the system, while breadboarded.

I'm using a NVIDIA GeForce 1060. (edited my post now). The problem persists with and without the discrete graphics card connected.

Good idea - I should try with a different PSU to see if that's the problem. I thought that 500W would be quite sufficient - do you think it's perhaps not enough?
 
After forcing a BIOS backup:

I connected pins 1 and 6 on the main Bios chip to force the BIOS backup.
No luck, but different codes now. It goes through a number of different codes before settling in 01 for 15 seconds, then the fans ramp up slightly, and it shuts off. I noticed that the shutdown always occurs immediately after the CPU light comes up.

I don't have access to a PSU but I'll try to locate one to rule out the PSU.

Other than that does anyone have any other ideas? Or is this just looking like a fried Mobo?
 
UPDATE:

Tried a new PSU. Problem persists.
Still waiting for Gigabyte to reply. Hoping they honor their warranty.

In the meantime, any other suggestions?
This sure is a quiet forum.
 
SOLUTION: Bought a new motherboard. RMA'd the old one. Good riddance.


Thanks for everyone's input. 👎
Hey buddy, just wanted to send my genuine thanks for creating this forum even though no one else replied, you replied the solution which helped me. Exact same freakin issue error 22, 66, 97 CpU light and CUT GONE. Reboot loop. I had it narrowed to CPU or Mobo, thank you so much man!!! You rock!
 
Status
Not open for further replies.