Questions about GIGABYTE products > Motherboards with Intel processors

Z390 with I7-9700K, issue

(1/2) > >>

veresdavid:
I was using my PC for about 6 months when I had an issue with my MB and CPU so I sent them back to my supplier, and from their service I got the MB back as "repaired" and got a new CPU but it stil not working with my new CPU which is an Intel Core-i7 9700k (I was using the same model before), the orignal MB is a Gigabyte Z390 Aorus Pro (Rev 1.0).

I tested the MB with another  CPU, an Intel Pentium Gold G5400, working fine.
I also tested my CPU on an ASUS TUF Z390-PRO MB, working fine.

The only combination which is not working is my old MB (Z390) and the 9700K CPU.
The BIOS version is F11.

The following is happening:
after the start-up the CPU debug led flashed once, then the DRAM led flashed once, the VGA led also flashed once, after that the CPU led had a shorter flash and the system powered down and powered up again, and the cycle repeated until I switched off the power supply.
Clearing CMOS did not help, I also tried to boot with dedicated graphics card but the outcome was the same.


I would appreciate any advice on what this can be or what can I try to fix it.

shadowsports:
Greetings,
I have 2 of these boards, both with different CPU's i9-9900K.  One running F10, one F11.  Both are stable.

What memory are you using?  Is it on the QVL for your board?

First 6 months..  Does this mean the board and CPU combo working together trouble free for the first 6 months?

What changed?   

Did you upgrade the BIOS to F11?  If yes, how was the upgrade performed (QFlash or @BIOS)?

More info is needed. 


 

veresdavid:
Hi

I am using Kingstone HyperX Predator HX432C16PV3AK2/16, I did not find it on the QLV

"Does this mean the board and CPU combo working together trouble free for the first 6 months?"

Yes, everything was working fine, one morning I was typing my password to enter to Windows and the PC shut down and it did not turn back again.

I had F11 BIOS, I dont remember what did I use to upgrade it when I first built the PC.

But yesterday evening, after 40+ failed boot, it started working... No idea why.
I upgraded the BIOS  with QFlash to F12K

In the BIOS the CPU was running at 4.6 GHz, but in the Windows it was fine except that I could heared some coil whining sometimes.

Today I put it back in the case, and now it has the same problem as before.

shadowsports:
Greetings,
Moving target.  Best to confirm behavior and stability before making multiple changes. 

So, board and CPU was working OK outside of case (bench testing) with F11?

and also outside of case with F12K?...  but when you put it back in the case, the restart behavior returns?

Is this correct?

Thanks

 

veresdavid:
Hi

"So, board and CPU was working OK outside of case (bench testing) with F11?"

So at first when I assembled the board and the CPU with one stick of RAM outside of the case, the problem (described in tmy first post) was present, after that I took out the RAM stick and powered on the PC, the MOBOs debug flashed were ping-pongind from CPU to DRAM I let it run like that until the flashing stopped and only the DRAM led was lit.
After that I shut  down the PSU.
Next I put the RAM back to the same slot as before and when I powered up the system I manadged to get into the  BIOS.
At that time intel factory cooler was installed on the CPU which was running like hell, I noticed that the CPU VCORE was a bit high and the  VRM temperature was rising constantly and there was terrible coil whining (which I can't remember from before). After that I switched the CPU to a pentium G5400 to flash the latest BIOS to the MOBO because that contains a few improvement to Vcore voltage and power management for the MOBO.

After that  I put back the 9700K in the MOBO and I manadged to boot into the BIOS, still terrible coil whining high Vcore, VRM temp, so I applied the factory defaults for the BIOS and after the restart VRM temp and Vcore was much better, coil whining was still present under load.

I put the 2nd RAM stick into the  MOBO and I manadged to boot again and that is where I left it for the day.

Today I installed it to the case and when I tried to boot the issue was present again.

Navigation

[0] Message Index

[#] Next page

Go to full version