New CPU and mobo bootup issue I have?

[The_Nephilim]

Hey Guys,

 

I am on my last leg here to try and determine why I have this issue with my PC. What happens is when I do a coldboot the PC turns on then after a couple seconds it turns off again then turns on automatically then boots normally.. I only hit the power button once.

 

So I have tried contacting Gigabyte and they want me to RMA the board so they can check it out.. I do not have a 2nd CPU or RAM to test it with so I am pretty limited on what I can do to try and figure out what causes this.. Now I have googled the issue and of course checked most of the common things it could be..

 

The Thing is it only happens when I have OC the CPU and use the XMP PRofile. now before you say it is because of the OC to me that just does not make sense. I had another user say his does not exhibit this behavior, so either I have something wrong in the BIOS Settings or my board is defective..

 

Now I had a previous PC that did the same thing but it was a 11700K with an ASRock Z590 board.. so the possibility of this happening on 2 seperate PC is wierd. I had trued these things:

 

1. Try with 1 stick of RAM changed ram up tried in different slots. no matter how I did it I got the bootup issue..

 

2. Tried different version of BIOS F15, F16 and F16c.. all did the same thing..

 

3. tried unplugging all devices and extra cards and such did the same thing when booting up..

 

so I am sure there was a few other things I trued but not much more but zillions of combos in BIOS and settings nothing besides setting the BIOS to defaults will it properly boot up.. so what do you guys think it is?

 

 

[Blackrat_UK]

I had a similar thing many years ago it was the PSU,  see if you can swap it out and test?

[Lange_666]

6 hours ago, The_Nephilim said:

I am on my last leg here to try and determine why I have this issue with my PC. What happens is when I do a coldboot the PC turns on then after a couple seconds it turns off again then turns on automatically then boots normally.. I only hit the power button once.

Haven't checked the mobo specs myself but does it have a diagnostic display (mostly 2x8-digit) where you can follow the boot process.
If yes, you can follow the boot process and see what code is generated the moment the PC turns off again.
With that code you can then (mostly) determine what's the cause?

[The_Nephilim]

4 hours ago, Blackrat_UK said:

I had a similar thing many years ago it was the PSU,  see if you can swap it out and test?

I had changed the PSU on my other PC that exhibited this behavioir and it still did the same thing. the PSU I have now is the newest one.

2 hours ago, Lange_666 said:

Haven't checked the mobo specs myself but does it have a diagnostic display (mostly 2x8-digit) where you can follow the boot process.
If yes, you can follow the boot process and see what code is generated the moment the PC turns off again.
With that code you can then (mostly) determine what's the cause?

Yes it has the 2 digit readout and the 4 lights and it shuts down when the display is on the DRAM light and C5 is the last display, I checked C5 it was no code like reserved or similar..

 

[LucShep]

Last time I saw that "C5" code on a Gigabyte motherboard was with a Z170X UD5. But then, that was many generations ago (i7 6700K then) and lots has changed since.
I remember updating the bios, then resetting it afterwards, loading optimized defaults, reboot, and only then start to change and test things as necessary.
In this case, that C5 code, which is usually listed in the manual as "reserved" (thanks Gigabyte!!) was memory related. Though that code may pop as well with a badly seated CPU (or dirt) on the motherboard socket.
It might be a memory learning related thing, which could explain why it only makes it on cold boot, not on Windows restart(?).

I got no experience with the current "Arrow Lake" generation of Intel CPUs, or their motherboards, so I'll refrain from further speculation.
But, admittedly, I personally avoid Gigabyte motherboards like the plague (Asus or MSI beefy mid-range still my go to, everytime) because every single one I messed with has been finicky, very sensitive to different BIOS versions with varying behaviours (too much) when it comes to memory OC.

 In the meanwhile, I'd suggest having a look into similar subject in Reddit, and the official Gigabyte forums, as brainstorming occurs and might lead to something:

https://www.reddit.com/search/?q=gigabyte+z890+c5+error&cId=50b4f566-4b3d-405b-9c07-64dbf85fde16&iId=e306d4d6-b4db-431e-8c59-205ed1992d64

https://forum.giga-byte.co.uk/index.php

 

Edited March 29 by LucShep

[The_Nephilim]

Well the CPU is perfect and no bent pins or dirt or anything like that. it could be a memory incompatibility but some other user has the same issue with the same board and he thinks the OC and XMP PRofile are bugged or similar..

 

I too don't think anything is wrong with the parts or  anything. I had a similar issue and that board was an MSI so who knows. I just dont want to find out the day after my year is up for warranty I think and have something go south on me or cascade to a bigger failure..

 

LucShep I beleieve it does not have the boot issue on a restart usually on a coldboot only.. Gigabyte wants me to send the board in on an RMA so they can have a look at it but I have my reservations on they mess the Pins up and try and blame me then it is a he said she said issue I would prefer to avoid all together or even worse be without a PC until they find out what is going on with the board and then they determine nothing is wrong akkk!!..

 

I will just live with it as my other PC was fine for some years with the same issue.. Personnely I tiink it their BIOS causing the issues.. one last thing the PC does not exhibit this behavior when I set to optimised defaults.. it will boot just fine then so who knows..

[LucShep]

Wether or not you want to RMA the motherboard is up to you.
Personally, I too don't think it's a big problem you got there. If all is good apart that little detail, maybe see how it goes and reavaliate such need closer to end of warranty.

And, yes, I'd strongly suggest to always load optimized defaults (and on any motherboard), then reboot, and do your personal preference adjustments in BIOS afterwards (OC or not), save a BIOS profile of your new settings, and you're off to the races.

Which it seems you already did and, if it does no longer present such problem, then I'd just do some stress testing to monitor temperatures, voltages and wattage, to be sure something isn't "odd" (if it is, adjust accordingly).
Some manufacturers pump "funny" higher voltages for better benchmark scores with optimized defaults BIOS settings, so this is just to be sure all is good.
If all good, consider it solved for now.   
 

Edited March 30 by LucShep

[The_Nephilim]

LucShep, Yes I had optimised defaults loaded then I set the OC and such over a span of two weeks until I had it dialed in. but after I set the OC and XMP PRofile and such settings I then get the boot issue.

I do not get it when I load just the optimised defaults on a cold boot, it boots normally then.. I hope that makes sense or I explained it right..

[LucShep]

13 minutes ago, The_Nephilim said:

LucShep, Yes I had optimised defaults loaded then I set the OC and such over a span of two weeks until I had it dialed in. but after I set the OC and XMP PRofile and such settings I then get the boot issue.

I do not get it when I load just the optimised defaults on a cold boot, it boots normally then.. I hope that makes sense or I explained it right..

Well, then it seems the problem is not on the motherboard or its default (optimized) settings.
Then that calls for troubleshoot, if you have the patience.

It seems fault is within some OC setting. Wether its CPU related, or RAM, is your investigation mission now, again if you have the patience.
XMP is a different thing (could be mem fault then), you need to test one without the other and, once found which one is, to see which related setting is causing it.
  All that fun stuff! 
 

Edited March 30 by LucShep

[The_Nephilim]

Well yes I have the patience but not quite sure what steps to take? 

 

I did try running just setting the XMP Profile after setting everything to default and had the boot issue. I also tried running OC on the Memory a little slower then the XMP Rated Profile.. I also tried just OC without an XMP PRofile and If I remeber correctly I had the same bootup issue..

 

So with that being said what else should I try to do at this point?

[LucShep]

5 hours ago, The_Nephilim said:

I did try running just setting the XMP Profile after setting everything to default and had the boot issue. I also tried running OC on the Memory a little slower then the XMP Rated Profile.. I also tried just OC without an XMP PRofile and If I remeber correctly I had the same bootup issue..

So with that being said what else should I try to do at this point?

You can try to repeat same process again with one of the two sticks only, load BIOS optimized defaults and save/restart.
Then enter BIOS, and either load XMP or do your own RAM manual setting adjustments (from the default optimized ones, without XMP loaded), as you've done already.

Try repeating the process with one stick on different RAM slots of your motherboard (of the four available), to isolate possible issues happening in a specific slot - then it'd be the motherboard's fault.
Supposing that only one of the two mem sticks has that bootup issue, in whatever RAM slot of the motherboard, then you have found a possibly faulty mem stick.

It could be that it is an untested memory kit that isn't listed in the QVL (see here if listed) and/or possibly unstable on that board.
Also remember - XMP isn't always guaranteed to work with full stability on whatever motherboard. Sometimes it doesn't.
Check if it's in the correct gear mode for the mem speed in place.
If it already is, then you may have to relax the primary timings (try one step down) and/or slightly increase the DRAM voltage (say, 0.05v). But even that isn't guaranteed to work.

Again, I have no experience with Arrow Lake, it works completely different to previous Intel CPUs, so can only speculate.
Maybe look into SkatterBencher's Arrow Lake MemSS OC guide (here), it could lead to some helpful pointers.
 

Edited March 30 by LucShep
added links

[The_Nephilim]

I tried with the 2 sticks in the a1,n1 slots altho I got the memory in the wrong slot error message it seemed to have booted fine and I am pretty sure I had trhe xmp profile loaded up.. I will retest a few timmes and see if it cold boots but it looks like slot A2,B2 are not working properly..

 

Will need to test a bit more to be sure.. hang tight!!

 

 

EDIT: Well I cold booted it an 2nd time and it fired right up so maybe something amis with those other slots.. looks like I might have to rma the board..

Edited March 30 by The_Nephilim

[LucShep]

13 hours ago, The_Nephilim said:

I tried with the 2 sticks in the a1,n1 slots altho I got the memory in the wrong slot error message it seemed to have booted fine and I am pretty sure I had trhe xmp profile loaded up.. I will retest a few timmes and see if it cold boots but it looks like slot A2,B2 are not working properly..

Will need to test a bit more to be sure.. hang tight!!
 

EDIT: Well I cold booted it an 2nd time and it fired right up so maybe something amis with those other slots.. looks like I might have to rma the board..

It's unfortunate (and most common) that you don't have another CPU for that socket, so to test if CPU and/or socket pins are not to be blamed.

But yeah, might be getting somewhere, because A2 and B2 should be able to each run single-channel mode (1x stick only) just fine.
And are both the ones to use for 2x sticks of RAM (dual-channel mode).

If A1 and B1 do not present the problem (no boot issue and no normal working issues, other than the wrong slot message from DRAM LED) then you may have found a culprit.  
Or a partial (temporary) solution, if that pair of slots in use result in less of an annoyance and you don't want to RMA the board yet. 


From your motherboard's manual:  

Edited March 30 by LucShep

[The_Nephilim]

Ok am going to try with 1 ram in slot b2 and see what happens. if it boots ok maybe it was a2 that had an issue..

 

thnx man..

 

EDIT: Well I tried the B2 single slot it still had the boot issue. I am wondering if I had no issue in the 1st two slots but then it had issues in the 2nd slots could that mena a problem with the Ram, IMS or the slots?? I am thinking maybe something with the IMC as there are two of them on this chip, I think I read that in the Article LucShep linked above,

Edited March 30 by The_Nephilim

[LucShep]

1 hour ago, The_Nephilim said:

Ok am going to try with 1 ram in slot b2 and see what happens. if it boots ok maybe it was a2 that had an issue..

thnx man..

EDIT: Well I tried the B2 single slot it still had the boot issue. I am wondering if I had no issue in the 1st two slots but then it had issues in the 2nd slots could that mena a problem with the Ram, IMS or the slots?? I am thinking maybe something with the IMC as there are two of them on this chip, I think I read that in the Article LucShep linked above,

I presume from previous replies that you already checked socket is ok (no bent pins or dirt) and reseated the CPU again, so at this point... yeah, could be any of those things.

The problem with this kind of issue is not having other components to test (other compatible CPU, other memory kit), there'll always be a hint of doubt (is it? could be?).

But, considering such limitations are what is normal for any regular user, and since you have a valid warranty, you're entitled to RMA that board if unhappy with its functioning.
 

Edited March 30 by LucShep

[The_Nephilim]

yes I pulled the CPU a few days ago and everything there looked perfectly normal and I put it back in a looked and worked good besides the reboot issue..

Thing with not having other parts is it could be either the memory or the mobo. I really want to avoid RMA'ng the board if possible.. I was going to get a new monitor  but now I am unsure if I would like to try other memory or get a different mobo and RMA this one..

 

 

EDIT: On second thought since I put the memory in the other slot and it worked it has too be the ram slots.. if it was the memory it would have behaved the same way when I switched it.. so know I am wondering should I get a 43" or 49" curved monitor?

Edited April 1 by The_Nephilim

[Nightdare]

Still sounds like a PSU problem to me, as if the capacitors aren't holding enough charge to supply the initial high peak at cold start

[BitMaster]

To me it sounds like your IMC can't fiddle out the RAM settings once your CPU is in OC mode, hence the retry/reboot.

I haven't read above that you tried to up the volts a little when in XMP. try some 0.05-0.15v more and see if that helps to register the RAM on boot.

 

Likely, you got an unlucky combo of RAM-Board-Bios at this moment in time. Another Bios might well cure the symptoms, might, maybe not.

[The_Nephilim]

OK I thought I had it but the XMP Profile was not loaded but when it wasn't it booted normal even with an OC on the CPU. So now I need to find out which setting is for the Memory voltage then I can set the manual volts..

 

Getting closer.

[The_Nephilim]

\I had found out the memory voltage is called CPU System Agent Voltage, I set that too 1.40v and it still had the boot issue.. I am pretty sure something wrong soewhere but not exactly sure if it is the ram slots or the imc?

[LucShep]

38 minutes ago, The_Nephilim said:

\I had found out the memory voltage is called CPU System Agent Voltage, I set that too 1.40v and it still had the boot issue.. I am pretty sure something wrong soewhere but not exactly sure if it is the ram slots or the imc?

You're crazy  that CPU is going to get fried soon with SA Voltage at 1.40v!

CPU System Agent Voltage is the power for the memory controller, and should be avoided to be messed with unless in specific OC'ing cases.
Yes, it usually helps with general OC'ing and also for RAM, but you need to know first what is the safe voltage limit for it on your specific CPU model. 
With the Intel 12th, 13th and 14th gen CPUs you'd risk degradation with that set at over 1.30v, and I don't think Arrow Lake accepts using that much (stock for it is what, 1.10v?).

The setting you need to look at in your BIOS is DRAM Voltage (which every manufacturer usually has in BIOS) - this is where you adjust the voltage for your RAM sticks.
 

Edited April 2 by LucShep

[The_Nephilim]

13 minutes ago, LucShep said:

You're crazy  that CPU is going to get fried soon with SA Voltage at 1.40v!

CPU System Agent Voltage is the power for the memory controller, and should be avoided to be messed with unless in specific OC'ing cases.
Yes, it usually helps with general OC'ing and also for RAM, but you need to know first what is the safe voltage limit for it on your specific CPU model. 
With the Intel 12th, 13th and 14th gen CPUs you'd risk degradation with that set at over 1.30v, and I don't think Arrow Lake accepts using that much (stock for it is what, 1.10v?).

The setting you need to look at in your BIOS is DRAM Voltage (which every manufacturer usually has in BIOS) - this is where you adjust the voltage for your RAM sticks.
 

well if it happens so be it but I guess I lucked out, so I am guessing I got some really bad intel.. will not mess anymore as I looked in the BIOS and it is not clear well at least to me what setting I should adjust..

[LucShep]

9 minutes ago, The_Nephilim said:

well if it happens so be it but I guess I lucked out, so I am guessing I got some really bad intel.. will not mess anymore as I looked in the BIOS and it is not clear well at least to me what setting I should adjust..

IIRC, Gigabyte motherboards usually have a section for DRAM VOLTAGE CONTROL with that setting (DRAM Voltage), it's located under the TWEAKER tab.

I haven't looked yet, but it helps looking at the BIOS manual of your motherboard: 
https://download.gigabyte.com/FileList/Manual/mb_manual_intel800-bios_e.pdf?v=3a1f079a1e6e76af6f34412100dfb61a

The example below is from a 13th/14th gen Z790 Aorus DDR4 motherboard:

Edited April 2 by LucShep

[The_Nephilim]

ok I will check and try to adjust it but not sure it will do anything but maybe it will thank you LucShep..

 

EDIT: Well I tried setting the DRAM Voltage and it still has the boot issue.. I think I am just going to have to RMA the board. as I do not have money to buy a new cpu and memory to test it..

 

thnx guys..

Edited April 2 by The_Nephilim

[The_Nephilim]

Well the tech help is wanting me to RMA the board so they can inspect it. I am really not wanting to do that at this point. I fear either they will do somethnig to break it or just say nothing is wrong with it. I am not even sure what else can be done.

 

I did find out when I disabled the XMP PRofile while the CPU was still OC I did not have the bootup issue.. So it is memory related but not sure if it is the slot, the memory or the IMC??

But I do not want to be without a pc for up to 2 weeks, I could reassemble my old PC but I don't have a windows for it.. and I really dont feel like assembling it and then dissassemble the reassemble the new pc haha!!