My PC Randomly Resetting After Using Kombo Strike 3

[MasterKing-25]

Hello. I have MSI Mag X570S Torpedo Max motherboard when I tried to use Kombo Strike 3 for my Ryzen 5800X3D from BIOS, my PC resetting itself randomly. Is there anyone encountered this like situation at all?

 

[AusWolf]

It's best not to use aftermarket tuning software/options for more performance. If you want to tune, do it yourself manually. I'm sure you'll find lots of people who know their thing around here.

 

[Chomiq]

Isn't Kombo Strike just CO adjustment? As in level 3 is -30? If so, check Event Log for WHEA errors, see which core reportedly crashed and adjust CO value for that core.

It's best not to use aftermarket tuning software/options for more performance. If you want to tune, do it yourself manually. I'm sure you'll find lots of people who know their thing around here.

It's a bios setting.

 

[MasterKing-25]

Isn't Kombo Strike just CO adjustment? As in level 3 is -30? If so, check Event Log for WHEA errors, see which core reportedly crashed and adjust CO value for that core.


It's a bios setting.

Yes indeed it's a BIOS setting and as you said its doing same thing with PBO but with more simplier way also I tried to use PBO -30 setting in past still I had same resetting problem by the way when I use Kombo Strike 2 instead of 3 problem solving still curious why my PC can't handle Kombo Strike 3.

 

[AusWolf]

It's a bios setting.

I still wouldn't trust it as long as it's not developed by AMD/Intel.

 

[Taraquin]

Your cpu has one or more cores that cant handle -30 CO. Try using -20 and see if it works

 

[Chomiq]

I still wouldn't trust it as long as it's not developed by AMD/Intel.

It's just pre-set all core CO, lvl 3 is -30, lvl 2 is -20, lvl 1 is -10.

Yes indeed it's a BIOS setting and as you said its doing same thing with PBO but with more simplier way also I tried to use PBO -30 setting in past still I had same resetting problem by the way when I use Kombo Strike 2 instead of 3 problem solving still curious why my PC can't handle Kombo Strike 3.

One of the cores crashes when it doesn't get enough voltage. Usually happens when going in and out of low power state. Like I said, event viewer will show you the WHEA error and the thread that crashed which should tell you which core was unstable.

 

[AusWolf]

It's just pre-set all core CO, lvl 3 is -30, lvl 2 is -20, lvl 1 is -10.

Ah... useless bollocks, then.

Edit: I mean, if one wants to tune, then why wouldn't one just set CO manually to whatever works instead of using some automatic crap?

 

[Assimilator]

As @Chomiq says, Kombo Strike is just a brute-force tool that applies a (level * -10) undervolt to all cores (i.e. level 1 is -1, 2 = -20, 3 =-30). The fact that your CPU is crashing on level 3 means one or more of your cores is not capable of handling a -30 undervolt. Your only option is to use one of the lower levels, or rather AMD's own Ryzen Master software that has a per-core Curve Optimizer feature.

Ah... useless bollocks, then.

Edit: I mean, if one wants to tune, then why wouldn't one just set CO manually to whatever works instead of using some automatic crap?

Because users shouldn't have to endlessly dick around with tweaking and benchmarking to get their CPUs to consume sane amounts of power. Curve optimisation should be a default UEFI feature just like DDR5 memory training. This would also mean that motherboard vendors wouldn't need to provide their own crappy implementations like "Kombo Strike" that mostly harm more than help.

 

[AusWolf]

Because users shouldn't have to endlessly dick around with tweaking and benchmarking to get their CPUs to consume sane amounts of power. Curve optimisation should be a default UEFI feature just like DDR5 memory training. This would also mean that motherboard vendors wouldn't need to provide their own crappy implementations like "Kombo Strike" that mostly harm more than help.

I don't disagree with your point, but I also don't think that a regular user needs to tweak anything.

 

[MasterKing-25]

Isn't Kombo Strike just CO adjustment? As in level 3 is -30? If so, check Event Log for WHEA errors, see which core reportedly crashed and adjust CO value for that core.


It's a bios setting.

Hello again. Sorry for late response but my PC resetted itself again I checked WHEA errors but there was 2 this kind of error so may I ask how can I exactly check which core causing this problem? I mean when I check WHEA errors from Event Viewer it was a bit too complicated to me, I searched internet I saw people was saying Apid ID saying which core causing this problem so I'd like to learn which core exactly causing this problem and how can I learn it via Event Viewer.

 

[3x0]

Just set Kombo Strike to 2 and see if it stabilizes things. Chasing down each individual core for the perfect CO is very time consuming.

 

[Chomiq]

Hello again. Sorry for late response but my PC resetted itself again I checked WHEA errors but there was 2 this kind of error so may I ask how can I exactly check which core causing this problem? I mean when I check WHEA errors from Event Viewer it was a bit too complicated to me, I searched internet I saw people was saying Apid ID saying which core causing this problem so I'd like to learn which core exactly causing this problem and how can I learn it via Event Viewer.

You check the error and in details you should see something like:

A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 1
The details view of this entry contains further information.

This tells you which thread crashed, since threads are paired by core it goes like
APIC 0,1 = Core 0
2,3 = Core 1
and so on.

Check which APIC ID popped up in WHEA error, find the core it is linked to and decrease the negative offset value for that core.

 

[Deleted member 229121]

Kombo Strike is Core Offset, MSI uses this on some boards (including mine) and then offers "Core Offset" on others.

What you are posting about is an unstable undervolt:

Combo Strike 1 = -10 CO
Combo Strike 2 = -20 CO
Combo Strike 3 = -30 CO

If your chip isn't stable (it will crash at desktop / idle) then you need to back off and use a lower setting.
Try -20 CO (option 2) and see how it goes, if you still are experiencing crashes then you need to try option 1 etc.

This really just boils down to silicon lottery, my 5800X wasn't able to handle -30 CO, but fortunately my X3D was.

 

[freeagent]

out of my 3 Zen 3 parts, none can take -30 and be stable.

 

[MasterKing-25]

You check the error and in details you should see something like:


This tells you which thread crashed, since threads are paired by core it goes like
APIC 0,1 = Core 0
2,3 = Core 1
and so on.

Check which APIC ID popped up in WHEA error, find the core it is linked to and decrease the negative offset value for that core.

Thank you so much for detailed answer. Now I get it what I should do. I changed core 0 and core 5 after see Processor APIC ID: 0 and Processor APIC ID: 5 in Event Viewer. I hope this differences will fix my PC's resetting problem.

 

[3x0]

You check the error and in details you should see something like:


This tells you which thread crashed, since threads are paired by core it goes like
APIC 0,1 = Core 0
2,3 = Core 1
and so on.

Check which APIC ID popped up in WHEA error, find the core it is linked to and decrease the negative offset value for that core.

Just to add info, on CPUs which have disabled/fused off cores like the 5900X for ex., then it's best to use CPUz "Save Report as HTML" and verify which physical cores have been assigned which APIC by windows, as the rule mentioned above doesn't apply entirely.

I changed core 0 and core 5 after see Processor APIC ID: 0 and Processor APIC ID: 5 in Event Viewer.

No, APIC 0 is Core 0 as you mentioned, but APIC 5 is Core 2.

 

[eidairaman1]

Fill out your complete detailed system specs

 

[MasterKing-25]

Just to add info, on CPUs which have disabled/fused off cores like the 5900X for ex., then it's best to use CPUz "Save Report as HTML" and verify which physical cores have been assigned which APIC by windows, as the rule mentioned above doesn't apply entirely.


No, APIC 0 is Core 0 as you mentioned, but APIC 5 is Core 3.

Okay. Thanks for clarifaction on this. I will change what I did earlier for Core 5.

 

[3x0]

Okay. Thanks for clarifaction on this. I will change what I did earlier for Core 5.

Note that I edited the post, I made a mistake saying it's Core 3, it's Core 2.

What are you going to change the CO values for those two cores to?

 

[MasterKing-25]

Note that I edited the post, I made a mistake saying it's Core 3, it's Core 2.

What are you going to change the CO values for those two cores to?

I just saw your post edited recently and changed core 2 with 25 instead of 30. I did 25 because in past I was using 25 for all cores I had no problem like PC reset so reset problem only appeared when I changed values to 30 like you understand I just changed Core 0 and Core 2 (which is problematic ones) now problem should gone.

 

[RJARRRPCGP]

This really just boils down to silicon lottery, my 5800X wasn't able to handle -30 CO, but fortunately my X3D was.

My "regular" 5800X is suspected of having a dud IMC. I got a memory-related BSOD out-of-the-blue, but I never got a BSOD when gaming or running anything super demanding, SMH!
It also never crashed either when gaming or encoding!
It's possible that it's just flaky with warm ambient or a Windows 11 22H2 bug. It was in '23 and I was using 22H2.

I tested the same RAM (The G.Skill TridentZ Neo 3600 kit) on my X3D and was able to with no hardware error.

 

[INSTG8R]

Identical setup. Unfortunately I can’t really offer any advice because I’ve been using it all along without issue along with -30 in the Curve Optimizer

 

[Taraquin]

My "regular" 5800X is suspected of having a dud IMC. I got a memory-related BSOD out-of-the-blue, but I never got a BSOD when gaming or running anything super demanding, SMH!
It also never crashed either when gaming or encoding!
It's possible that it's just flaky with warm ambient or a Windows 11 22H2 bug. It was in '23 and I was using 22H2.

I tested the same RAM (The G.Skill TridentZ Neo 3600 kit) on my X3D and was able to with no hardware error.

Which bios? Updated amd chipsetdrivers?

 

[Deleted member 229121]

Identical setup. Unfortunately I can’t really offer any advice because I’ve been using it all along without issue along with -30 in the Curve Optimizer

It's the CPU itself (silicon lottery), if -30 isn't stable OP needs to try -20, -10 aka Kombo Strike 3,2,1 respectively.
The undervolt at -30 doesn't appear to be stable w/ crashes at idle and/or transient spikes (idle to load).