You could always try just the primary settings and leave everything else on Auto. From your earlier post, I would say your Trfc is too low.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

You could always try just the primary settings and leave everything else on Auto. From your earlier post, I would say your Trfc is too low.

I guess I just did something like that. I have found out that for MSI the LLC Mode1 is the most aggressive.
And it won't boot with Mode3 or 4 with a cpu voltage of 1.2375 volts but will boot with "auto" on.

But since I was having lockup issues it occurred to me to ask, what would happen if I set the CPU voltage to "auto" but left the LLC at Mode4? I have already tested Mode6 with voltage 1.2 and it would lockup once the app started. Etc.

I am currently speaking from the system as we sit here. And I need to go to work.

So here is my current stability test. :)

Tom

---

A proud member of the OFA (Old Farts Association).

What you are looking for is for the Vcpu readback voltage in your system monitor to be exactly what you set it to be in the BIOS. While under your typical crunching load. Try increasing levels of LLC until you observe no droop. But don't set it too high or you will spike the voltage when you remove the load.

I apparently missed class when we were introduced to "system monitor". Which app is that? The one I can't get to work?

Tom

I would suggest my favorite GKrellm. It takes up less real estate on the desktop compared to psensors. I just position it on the right hand side of the desktop and in nicely balances against the Dock on the left. By 'system monitor' I was referring to any app that displays your system physical parameters like temps and fan speeds. There is also the actual Gnome "System Monitor" which is a stock app for displaying the Processes/Resources/File Systems statistics of the host. That is not what I was referring to.

sudo apt install gkrellm

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

What you are looking for is for the Vcpu readback voltage in your system monitor to be exactly what you set it to be in the BIOS. While under your typical crunching load. Try increasing levels of LLC until you observe no droop. But don't set it too high or you will spike the voltage when you remove the load.

I apparently missed class when we were introduced to "system monitor". Which app is that? The one I can't get to work?

Tom

Just searched for and found the unknown SIO 0xd352. Found reference for installing nct6775 stuff, appear to have successfully compiled and installed it. Here are the results.

tom@EJS-GIFT:~/Downloads/nct6775$ sensors
iwlwifi-virtual-0
Adapter: Virtual device
temp1:        +26.0°C  

k10temp-pci-00d3
Adapter: PCI adapter
temp1:       +101.4°C  (high = +70.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +101.2°C  (high = +70.0°C)

nct6795-isa-0a20
Adapter: ISA adapter
in0:                    +1.25 V  (min =  +0.00 V, max =  +1.74 V)
in1:                    +0.99 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                    +3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                    +3.31 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                    +1.01 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                    +0.15 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                    +0.15 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                    +3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                    +3.26 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                    +1.80 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                   +0.69 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                   +0.69 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                   +1.15 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                   +0.69 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                   +1.53 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                  2830 RPM  (min =    0 RPM)
fan2:                  1370 RPM  (min =    0 RPM)
fan3:                   996 RPM  (min =    0 RPM)
fan4:                  1140 RPM  (min =    0 RPM)
fan5:                  1157 RPM  (min =    0 RPM)
SYSTIN:                 +36.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = CPU diode
CPUTIN:                 +56.0°C  (high = +110.0°C, hyst = +89.0°C)  sensor = thermistor
AUXTIN0:               +109.0°C  (high = +110.0°C, hyst = +89.0°C)  sensor = thermistor
AUXTIN1:                +43.0°C    sensor = thermistor
AUXTIN2:                +43.0°C    sensor = thermistor
AUXTIN3:                 -2.0°C    sensor = thermistor
SMBUSMASTER 0:         +101.0°C  
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
PCH_CPU_TEMP:            +0.0°C  
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled

k10temp-pci-00db
Adapter: PCI adapter
temp1:        +85.5°C  (high = +70.0°C)

k10temp-pci-00cb
Adapter: PCI adapter
temp1:        +93.0°C  (high = +70.0°C)

tom@EJS-GIFT:~/Downloads/nct6775$ 

I am interested in any comments you have. This was run well after the system was running under load. On the voltages front, do you have any recommendations?

I got no direction from the bios help on the LLC so I picked an entry (it had 8-9?) in the middle. Anything you see here should be reflecting that.

Tom

The in0 voltage is likely the one you set in your BIOS for Vcore. The k10temp temps are from the k10temp driver and not the nct6775 driver. I think that is the old version which shows the offset added temp and not the Tdie temp. CPUTIN could either be the die sensor or maybe the motherboard sensor. The other temps are likely duplicates of each other and either/or the PCH or VRM temps. The way to find out is to use a hair dryer and blow on parts while observing the temps to see which reacts. Fans can be determined by using your finger on the hub to stop rotation and observe which fan goes to zero. Gkrellm allows you to rename the sensor descriptor to something more understandable to you like fan position in the case or functional description like pump speed or radiator fans.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Why don't you ask Google the question? Or at least ask the question in your motherboard's forums.

Normally I start up the BoincMgr and then start up the browser. The last half dozen times I have had a locked up system before I could get in any useful research.

Right now I am not running the BoincMgr while I attempt some research.

I am aware that I may end up back at 3.9GHz which, I think, was stable. Or maybe not.

Tom

I already thought you were at 3.9Ghz from the last post you made about your first attempt at OC. I was not aware that you had pushed it further.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

You could always try just the primary settings and leave everything else on Auto. From your earlier post, I would say your Trfc is too low.

I guess I just did something like that. I have found out that for MSI the LLC Mode1 is the most aggressive.
And it won't boot with Mode3 or 4 with a cpu voltage of 1.2375 volts but will boot with "auto" on.

But since I was having lockup issues it occurred to me to ask, what would happen if I set the CPU voltage to "auto" but left the LLC at Mode4? I have already tested Mode6 with voltage 1.2 and it would lockup once the app started. Etc.

I am currently speaking from the system as we sit here. And I need to go to work.

So here is my current stability test. :)

Tom

You would have to ask in your MSI forums what LLC set on Auto equates to which level. The advantage of using Auto for Vcore is that the cpu automatically scales the voltage bins based on the attempted core frequency and the current loading. It is dynamic. The drawback is that the Auto mechanism may apply way more voltage than needed for the clock and loading which leads higher temps, which then scales back the clocks to get the TDP back under control. One way to prevent that is to use Auto with a negative offset. Best method is to determine the minimum voltage needed to run the speed and loading you will want to run.

You could try the Vcore on Auto and bump the LLC to LLC2 or LLC3 to prevent as much voltage droop. Stability testing takes time.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)