Computer randomly restarting when idle.

[iameatingjam]

unless already done, remove any under/over on anything, add some little bit of Vs where it might be needed (like soc on amd), and see what happens.
the more stuff isnt "stock", the more possible points we have to verify

Yeah adding some voltage to SA was one of the first things I tried. But I am now almost certain ram doesn't have anything to do with it, with the amount of testing and different configurations I've tried.

Anyway, its only been a week BUT considering I found people with the same problem who also happened to find the same workaround as me, I think turning c-state 8 and 10 off ( actually I think its mostly 8 I'm not even sure 10 does anything ?) is the best way for now....Even though its raises idle voltage a bit ( which is of course the exact opposite reason I did this update.... but whatever.... can't have my computer restarting all the time so it will have to do for now.)

Since I have replaced my cpu and some another guy I met with the same problem also on a gigabyte board tried replacing his PSU and bought a ups trying to solve this problem without luck (poor guy).... I'm pretty sure its board/bios/ucode or some combination of the three causing the issue.

I've done my best trying to report the problem to gigabyte and also encourage others to do the same so hopefully word gets to some actual engineers.

 

[ShrimpBrime]

That seems to be fine for now even though its raised idle voltage a bit

There's the evidence of what I type here.

You have this installed>? Have tried previous versions? (this is software drivers, not firmware. These can be uninstalled and rolled back.)

Intel® Management Engine Drivers for Windows® 10 and Windows® 11

Intel® Management Engine Drivers for Windows 10* and Windows 11*

www.intel.com

 

[eidairaman1]

I have been... don't even get me started on that ugh, they are impossible to talk to. Every case only gets one answer, and if you ask a new question/ or rather I was just trying to make a bug report, and I included the previous case numbers for context, they don't read them. Because after I already explained it was brand new chip in my first query, on my third, they suggested contacting intel for an rma. In my last one I just begged them to shut up and please just give the information to the team that works the bioses.

They also say things like " you shouldn't have to make any changes to get it working at default settings"

Like no shit thats why I said I was making a BUG REPORT.

-----

I have been scouring forums for people with this problem and asking them to report their problems directly to gigabyte. Seems people really like to complain on reddit but not actually make it to formal report. But I've at least convinced two people to do it. So thats something I guess.

And that is just another reason I don't even consider them for builds, plus all the revs their mobos and gpus go through is ridiculous.

 

[iameatingjam]

There's the evidence of what I type here.

You have this installed>? Have tried previous versions? (this is software drivers, not firmware. These can be uninstalled and rolled back.)

Intel® Management Engine Drivers for Windows® 10 and Windows® 11

Intel® Management Engine Drivers for Windows 10* and Windows 11*

www.intel.com

You can roll those back? How?

 

[ShrimpBrime]

You can roll those back? How?

Well, there once was a link for older versions that's no longer there? Yeah, that's changed.

But you may find them from OEM distribution Here's 2410 for example.

Intel Management Engine Components Installer | Driver Details | Dell Ireland

 

[iameatingjam]

Well, there once was a link for older versions that's no longer there? Yeah, that's changed.

But you may find them from OEM distribution Here's 2410 for example.

Intel Management Engine Components Installer | Driver Details | Dell Ireland

tbh I've been avoiding anything that says intel me out of fear that it could complicate a bios downgrade if needed ( which it kind of is right now... just don't have the bios I need). But I suppose if its just drivers it can't be permanent. Since the actual firmware comes with the bios, right?

Well anyway I just created a restore point before installing it, installed it and now I'm playing around and seeing if anythings changed. vcore still flies off the rails at default settings, as expected. But perhaps it could at least solve the c-state problem so I tried re-enabling them. I see a random restart in my future but its worth a try I suppose.

I'm also going to try some of my old undervolting techniques to see if they magically start working again ( doubtful).

EDIT: Okay yeah nothing has changed undervolting wise. Its still either clock stretching, or not reaching max boost no matter what the numbers are if vcore <1.4. There's no perfect middle ground like there used to be. If I want under 1.4 and full boost I NEED to turn CEP off. Which is fine, it was already like that. I'll keep it in my back pocket if I ever need it and just run at a lower frequency for now.

But I'll leave the c-states on for a few days and see if those new drivers change anything for that.

@ShrimpBrime

EDIT: Okay so the reboot didn't even take an hour. I went back to my restore point and damn new drivers were able to survive it somehow. Well hopefully that doesn't cause problems if an opportunity for a bios downgrade comes up. Well I suppose if it does cause problems, I don't see how they could survive a windows reinstall. But I don't see that as likely scenario anyhow.

 

[ShrimpBrime]

tbh I've been avoiding anything that says intel me out of fear that it could complicate a bios downgrade if needed ( which it kind of is right now... just don't have the bios I need). But I suppose if its just drivers it can't be permanent. Since the actual firmware comes with the bios, right?

Well anyway I just created a restore point before installing it, installed it and now I'm playing around and seeing if anythings changed. vcore still flies off the rails at default settings, as expected. But perhaps it could at least solve the c-state problem so I tried re-enabling them. I see a random restart in my future but its worth a try I suppose.

I'm also going to try some of my old undervolting techniques to see if they magically start working again ( doubtful).

EDIT: Okay yeah nothing has changed undervolting wise. Its still either clock stretching, or not reaching max boost no matter what the numbers are if vcore <1.4. There's no perfect middle ground like there used to be. If I want under 1.4 and full boost I NEED to turn CEP off. Which is fine, it was already like that. I'll keep it in my back pocket if I ever need it and just run at a lower frequency for now.

But I'll leave the c-states on for a few days and see if those new drivers change anything for that.

@ShrimpBrime

EDIT: Okay so the reboot didn't even take an hour. I went back to my restore point and damn new drivers were able to survive it somehow. Well hopefully that doesn't cause problems if an opportunity for a bios downgrade comes up. Well I suppose if it does cause problems, I don't see how they could survive a windows reinstall. But thats a pretty unlikely scenario.

ME software can be un-installed reinstalled w/e. The firmware cannot. The bios can be rolled back, but not the firmware.

Any software on a fresh install will be new. It doesn't carry over unless you're doing an upgrade. So no worries there.

You could even go into device manager and disable firmware engine altogether. Plenty of stuff to try.

Sounds like it just doesn't like the under-volt all honesty. And that's not degradation, thats a cpu running out of spec.

Ok, so if you have adequate cooling, should be able to replicate from this thread. There are some settings, but nothing is crazy. 7zip bench-off. Where to find performance.

14700K 7zip battle | Warp9-systems

Hello! Frien

warp9-systems.proboards.com

 

[iameatingjam]

@ShrimpBrime

Ehhh its all good I already know how to get better performance if I need it. Just got to keep those c-states disabled, intel profile off, cep off, ac 40 really improves my scores at least in cpu mark, and enables me to game under 1.4 at max boost with no stretching which is all I ask for. I just - don't need it right now. I'm either gpu bound or actually more likely, not bound at all with 4k60, I can really only think of one game where I was cpu bound in a scenario like that. So unless I need it, I'd rather just, run with those protections in place and at a lower frequency most of the time. I'd just like to get those promised lower idle states while I'm there.

Its a shame I can't have both at once.... but tbh its hard to imagine being cpu limited much the way I game so, bigger mhz really come down nothing but ego in my situation. I should really let that go.

Though you make a good point I probably should have re-enabled those c-states AFTER testing the undervolts and putting everything back at defaults but w/e, I'm feeling pretty confident it wont matter, maybe delay it, but a reset will come, be in a day or 3 or 7. Already been here. Having a newer version of the drivers wont make a difference I don't think... it didn't change anything else. Though this whole thing has got me wondering again IF the board defaults ac 90 is the problem where that is concerned. If I'd have to go back up to 110.... do I even want lower idle voltages? 70 may not get me where it did before, but it still keeps higher end voltages down and doesn't trigger cep, so I've been keeping it like that after I found disabling c8 stops the restarts.

 

[iameatingjam]

No way!! Gigabyte finally coughed up the bios version I've been asking for!!! F10d. Thats the one with ucode 123 that also has an intel profile which was working quite well for me.

So... am I going to have issues installing this? The way gigabyte suggested that I downgrade to f9 make me thinks that I wont. But.... would be nice to have some re-assurance on that point.

I'm clearing out one of my drives so I have a place to reinstall windows if I need to, while also keeping my current one in place just incase its not needed.

----

Yeah it couldn't read the file. I thought maybe gigabyte sent the wrong revision or maybe the ddr4 version so I tried the f9 version they suggested previously and same thing. Considering qflash plus but idk, perhaps its stopping me for a good reason. Its not anything is overtly broken or not working right now, maybe I should just leave well enough alone.

Also I feel like I really can't trust anything gigabyte says.....

 

[iameatingjam]

---------

Okay, problem resolved! Gigabyte coughed up the beta bios....

I figured out why the bios wouldn't downgrade, the intel profile was preventing it. Just had to disable it.

So normal qflash worked!

So far, it seems like everything is like it was before. Including high end voltages. I can once again get max boost in gaming without exceeding 1.4 while keeping cep on ( still not going to do it normally though - only if needed)

AND idle voltages may go under .7, but not as far or as frequently as they did with f11. I can't confirm 100% it solves restart problems... but I'm 99% sure it will.

YAY!

Thanks for everybody's input.