Random Shutdown

Bob Fletcher · 07-06-2020, 12:17 PM

Hardware:
CPU: AMD Ryzen 3 1300X Quad-Core Processor × 4
Memory: 16 GB
Mobo: Asrock B450M Pro4
GPU: NVIDIA Corporation GP108 [GeForce GT 1030]
HDD: Sabrent NVME 1TB
OS Manjaro

Hi, can you help I am getting random shutdowns? For some time I was running this in an ATX case with an MSI B450 Gaming Plus. I decided to change the case for something smaller and went for an mATX but this meant a change of motherboard so I went for the Asrock. Same chipset. The only other change was a Sabrent 1TB NVME drive.

The BIOS is at default. But I am getting random shutdowns with a flash of a "hardware error". It is too quick to read any more.

I installed "Sensors" and print output. I am concerned that AUXTIN2 is at 96C. I am a bit out of mt depth so I would appreciate some help. I am presuming this is a CPU core.

Code:

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +41.0°C  

nvme-pci-0100
Adapter: PCI adapter
Composite:    +27.9°C  (low  =  -0.1°C, high = +74.8°C)
                       (crit = +79.8°C)

nct6779-isa-0290
Adapter: ISA adapter
Vcore:                 336.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:                   328.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:                    3.42 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:                   3.42 V  (min =  +2.98 V, max =  +3.63 V)
in4:                     1.88 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                   848.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                   304.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:                    3.42 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:                    3.25 V  (min =  +2.70 V, max =  +3.63 V)
in9:                     0.00 V  (min =  +0.00 V, max =  +0.00 V)
in10:                  232.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                    1.06 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                    1.70 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                    1.05 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                    1.79 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                     0 RPM  (min =    0 RPM)
fan2:                  1232 RPM  (min =    0 RPM)
fan3:                   799 RPM  (min =    0 RPM)
fan4:                     0 RPM  (min =    0 RPM)
fan5:                   804 RPM  (min =    0 RPM)
SYSTIN:                 +31.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
CPUTIN:                 +29.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:                +88.0°C    sensor = thermistor
AUXTIN1:                +96.0°C    sensor = thermistor
AUXTIN2:                +22.0°C    sensor = thermistor
AUXTIN3:                -22.0°C    sensor = thermistor
SMBUSMASTER 0:          +29.5°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-00c3
Adapter: PCI adapter
Vcore:       1000.00 mV 
Vsoc:        838.00 mV 
Tdie:         +29.8°C  
Tctl:         +29.8°C  
Icore:         7.00 A  
Isoc:          5.75 A

beachboy2 · 07-06-2020, 01:45 PM

Bob Fletcher,

Those temperatures are normal.

Motherboard: SYSTIN: +31.0°C
CPU: CPUTIN: +29.5°C

CPU: Tdie: +29.8°C
CPU: Tctl: +29.8°C

AUXTIN can refer to the apparent/misreported PSU temperature, but it bears little resemblance to reality and can be ignored.
Is the back of your PSU very hot?
Probably not.

Your problem appears to be a hardware one and not related to overheating.

Bob Fletcher · 07-06-2020, 01:55 PM

Quote:

Originally Posted by beachboy2

Bob Fletcher,

Those temperatures are normal.

Motherboard: SYSTIN: +31.0°C
CPU: CPUTIN: +29.5°C

CPU: Tdie: +29.8°C
CPU: Tctl: +29.8°C

AUXTIN can refer to the apparent PSU temperature, but it bears little resemblance to reality and can be ignored.
Is the back of your PSU very hot?
Probably not.

Your problem appears to be a hardware one and not related to overheating.

Thank you very much for your comments. No, the PSU is not hot and I have plenty of ventilation. This only happened when I changed the mobo from MSI to Asrock both using the same B450 chipset. To me it is pointing at the mobo as that is the only component. I could try another mobo but that may be a waist of money.

pan64 · 07-06-2020, 02:08 PM

I don't really understand, but: https://linustechtips.com/main/topic...-is-it-so-hot/
Probably you need to configure your bios or linux to ignore it. Or check if it was a real alarm.

Bob Fletcher · 07-06-2020, 02:30 PM

Quote:

Originally Posted by pan64

I don't really understand, but: https://linustechtips.com/main/topic...-is-it-so-hot/
Probably you need to configure your bios or Linux to ignore it. Or check if it was a real alarm.

Thanks. It basically what beachboy2 had said. I am sorely tempted to get another mobo. The MSI ran with no problem at all.

pan64 · 07-06-2020, 02:52 PM

Quote:

Originally Posted by Bob Fletcher

Thanks. It basically what beachboy2 had said. I am sorely tempted to get another mobo. The MSI ran with no problem at all.

if it was a software issue you do not need to replace hardware. But it is your own decision.

mrmazda · 07-12-2020, 03:30 AM

Have you tried running memtest86 or memtest86+ multiple passes, at least two, preferably more?

Have you tried raising the RAM voltage one or two .05v steps?

Who made your power supply? What model is it?

Bob Fletcher · 07-12-2020, 04:02 AM

Quote:

Originally Posted by mrmazda

Have you tried running memtest86 or memtest86+ multiple passes, at least two, preferably more?

Have you tried raising the RAM voltage one or two .05v steps?

Who made your power supply? What model is it?

Hi thanks for getting back to me. I think I have fixed the issue. I was going to give it a few more days before I reported back. I did not consider the fact that I had updated the NVMe drive to a Sabrent 1TB. There are a number of people having overheating problems with NVMe drives and causing a shutdown and reboot. I have added a heatsink and so far there are no further issues but I wanted to give it a few more days before reporting back.

CascadeHealthcare · 07-16-2020, 05:07 AM

good to know

frankbell · 07-16-2020, 08:42 PM

Have you looked in the log files to see if they provide some hint?

Since you receive an error message right before the shutdown, there's a good chance something may have made it into the logs.

As an aside, I have a Zareason with an ASRock motherboard and it works quite nicely.

Bob Fletcher · 07-16-2020, 11:45 PM

Thank you everyove. I can report that since applying the heatsink to the NVMe drive all has worked well so I guess that has fixed that. I have ticked the thread as "Solved"