LDLC contacted me and suggested updating BIOS as there was some updates regarding the series of my CPU and to disable Windows fast startup, which I did.
We’ll see from here.
LDLC contacted me and suggested updating BIOS as there was some updates regarding the series of my CPU and to disable Windows fast startup, which I did.
We’ll see from here.
Use can use sensors to monitor fan and pump speeds.
$ sensors
asus_wmi_sensors-virtual-0
Adapter: Virtual device
CPU Core Voltage: 1.40 V
VPP MEM Voltage: 2.50 V
+12V Voltage: 9.97 V
+5V Voltage: 4.99 V
3VSB Voltage: 3.29 V
VBAT Voltage: 3.18 V
AVCC3 Voltage: 3.29 V
SB 1.05V Voltage: 1.03 V
CPU Core Voltage: 0.00 V
CPU SOC Voltage: 0.00 V
CPU Fan: 903 RPM
Chassis Fan 1: 813 RPM
Chassis Fan 2: 784 RPM
Chassis Fan 3: 0 RPM
AIO Pump: 0 RPM
Water Pump: 0 RPM
CPU OPT: 0 RPM
CPU Temperature: +36.0°C
CPU Socket Temperature: +25.0°C
Motherboard Temperature: +25.0°C
Chipset Temperature: +36.0°C
Tsensor 1 Temperature: +216.0°C
CPU VRM Temperature: +0.0°C
CPU VRM Output Current: 0.00 A
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +36.8°C
nvme-pci-0a00
Adapter: PCI adapter
Composite: +24.9°C (low = -273.1°C, high = +67.8°C)
(crit = +70.8°C)
Sensor 1: +24.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +30.9°C (low = -273.1°C, high = +65261.8°C)
nvme-pci-0900
Adapter: PCI adapter
Composite: +30.9°C (low = -273.1°C, high = +81.8°C)
(crit = +84.8°C)
Sensor 1: +30.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +30.9°C (low = -273.1°C, high = +65261.8°C)
$ sensors
gigabyte_wmi-virtual-0
Adapter: Virtual device
temp1: +30.0°C
temp2: +42.0°C
temp3: +50.0°C
temp4: +32.0°C
temp5: +42.0°C
temp6: +46.0°C
amdgpu-pci-1000
Adapter: PCI adapter
vddgfx: 1.34 V
vddnb: 1.02 V
edge: +43.0°C
PPT: 14.00 mW
acpitz-acpi-0
Adapter: ACPI interface
temp1: +16.8°C
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +50.8°C
nvme-pci-0200
Adapter: PCI adapter
Composite: +29.9°C (low = -20.1°C, high = +83.8°C)
(crit = +88.8°C)
Sensor 2: +39.9°C
Did you run ‘sudo sensors-detect’ first to setup?
$ sudo sensors-detect
# sensors-detect version 3.6.0
# System: LDLC PC11 ZEN-M5 TI PLUS PERFECT V2 [-CF]
# Board: Gigabyte Technology Co., Ltd. B650 EAGLE AX
# Kernel: 6.10.12-200.fc40.x86_64 x86_64
# Processor: AMD Ryzen 7 9700X 8-Core Processor (26/68/0)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 16h thermal sensors... No
AMD Family 17h thermal sensors... No
AMD Family 19h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Hygon Family 18h thermal sensors... No
Intel digital thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
Intel 5500/5520/X58 thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... Yes
Found unknown chip with ID 0x8689
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus
Module i2c-dev loaded successfully.
Next adapter: Synopsys DesignWare I2C adapter (i2c-0)
Do you want to scan it? (YES/no/selectively):
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: Synopsys DesignWare I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively):
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: AMDGPU DM i2c hw bus 0 (i2c-2)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 1 (i2c-3)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 2 (i2c-4)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 3 (i2c-5)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 1 (i2c-6)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 2 (i2c-7)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 3 (i2c-8)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-9)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 2 at 1:00.0 (i2c-10)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 3 at 1:00.0 (i2c-11)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 4 at 1:00.0 (i2c-12)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 5 at 1:00.0 (i2c-13)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 6 at 1:00.0 (i2c-14)
Do you want to scan it? (yes/NO/selectively):
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.
Accepted all default answers. sensors gives the same result.
If those screws were not initially tightened evenly the thermal paste on the processor would not be evenly distributed. It may not even be fully in contact across the processor and certainly would not be of even thickness.
Tightening the last screw would have evened out the contact and eliminated the uneven heat transfer.
Those screws must be evenly tightened and the cooler in full contact with the processor across the entire surface or there will be uneven heat transfer and hot spots.
Unfortunately I still had the problem today.
First picture is when I had the problem and the other is after reboot.
Here is the BIOS too
I got back my computer, they said the cause was a loose cable of the liquid cooler, I didn’t see anything personnally.
We’ll see if it works fine now.