Endeavour OS Keeps Shutting Down My Computer Randomly

M

mondochon

New Member
Joined
Nov 13, 2021
Messages
9
Reaction score
9
Credits
68
As the title states. I'm sure it's not a hardware problem I checked the internals. I'm not sure what it could be, I keep the OS updated, I'm very diligent about it. Any help would be appreciated.

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 48 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 12
On-line CPU(s) list: 0-11
Vendor ID: AuthenticAMD
Model name: AMD Ryzen 5 5600X 6-Core Processor
CPU family: 25
Model: 33
Thread(s) per core: 2
Core(s) per socket: 6
Socket(s): 1
Stepping: 0
Frequency boost: enabled
CPU max MHz: 4650.2920
CPU min MHz: 2200.0000
BogoMIPS: 7403.11
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mt
rr pge mca cmov pat pse36 clflush mmx fxsr sse
sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rd
tscp lm constant_tsc rep_good nopl nonstop_tsc
cpuid extd_apicid aperfmperf rapl pni pclmulq
dq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe
popcnt aes xsave avx f16c rdrand lahf_lm cmp_l
egacy svm extapic cr8_legacy abm sse4a misalig
nsse 3dnowprefetch osvw ibs skinit wdt tce top
oext perfctr_core perfctr_nb bpext perfctr_llc
mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba i
brs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep
bmi2 erms invpcid cqm rdt_a rdseed adx smap c
lflushopt clwb sha_ni xsaveopt xsavec xgetbv1
xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm
_mbm_local clzero irperf xsaveerptr rdpru wbno
invd arat npt lbrv svm_lock nrip_save tsc_scal
e vmcb_clean flushbyasid decodeassists pausefi
lter pfthreshold avic v_vmsave_vmload vgif v_s
pec_ctrl umip pku ospke vaes vpclmulqdq rdpid
overflow_recov succor smca fsrm
Virtualization features:
Virtualization: AMD-V
Caches (sum of all):
L1d: 192 KiB (6 instances)
L1i: 192 KiB (6 instances)
L2: 3 MiB (6 instances)
L3: 32 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-11
Vulnerabilities:
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled
via prctl and seccomp
Spectre v1: Mitigation; usercopy/swapgs barriers and __use
r pointer sanitization
Spectre v2: Mitigation; Full AMD retpoline, IBPB condition
al, IBRS_FW, STIBP always-on, RSB filling
Srbds: Not affected
Tsx async abort: Not affected
Click to expand...
 


Generally two common things that cause random shut-downs 1) Graphics issues or 2) Weak power supply or not enough watts rating from the power supply - did you build your own machine?
 
Too many cooks spoil the broth, so I may leave you in the capable hands you are already in for the most part.

G'day @mondochon from DownUnder and welcome to linux.org :)

I would ask -
  1. Thanks for the output, better is, from within Endeavour session
    Code: 
    inxi -Fxz
    , with any and all drives plugged in - your use of the Codes tags is just what we like.
  2. Are you sole-booting Linux, or dual-booting with eg Windows 10/11, if the latter make sure you safeguard any data from the Dozer and have a recovery plan.
  3. How long (broad picture) can you maintain a session before being kicked out?
I'll watch with interest and kick in if I can help, and I have Endeavour and 8 or 9 other Arch in my stable of 70 or so Linux on this Dell, so can act as a sounding board.

Good luck

Chris Turner
wizardfromoz
 
Hey there!

I'm sole booting. The sessions last varying amounts of time. I find it shuts down most frequently while playing Magic the Gathering: Arena on a wine emulator. I actually lose money when this happens, isn't that crazy?

Anyway, here are the specs:
Code: 
System:
  Kernel: 5.15.2-arch1-1 x86_64 bits: 64 compiler: gcc v: 11.1.0
  Desktop: KDE Plasma 5.23.3 Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star
  model: MPG X570 GAMING PLUS (MS-7C37) v: 2.0 serial: <filter>
  UEFI: American Megatrends LLC. v: A.E0 date: 06/22/2021
CPU:
  Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP
  arch: Zen 3 rev: 0 cache: L2: 3 MiB
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  svm
  bogomips: 88837
  Speed: 2879 MHz min/max: 2200/3700 MHz boost: enabled
  Core speeds (MHz): 1: 2879 2: 3602 3: 2879 4: 3022 5: 2876
  6: 2952 7: 2879 8: 2874 9: 3212 10: 3654 11: 2876 12: 3688
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti]
  vendor: Micro-Star MSI driver: nvidia v: 495.44 bus-ID: 2d:00.0
  Display: x11 server: X.Org 1.21.1.1 driver: loaded: nvidia
  resolution: 1920x1080~60Hz
  OpenGL: renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
  v: 4.6.0 NVIDIA 495.44 direct render: Yes
Audio:
  Device-1: NVIDIA GP107GL High Definition Audio
  vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
  bus-ID: 2d:00.1
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
  driver: snd_hda_intel v: kernel bus-ID: 2f:00.4
  Sound Server-1: ALSA v: k5.15.2-arch1-1 running: yes
  Sound Server-2: JACK v: 1.9.19 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.40 running: no
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: Micro-Star MSI X570-A PRO driver: r8168 v: 8.049.02-NAPI
  port: d000 bus-ID: 27:00.0
  IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives:
  Local Storage: total: 465.76 GiB used: 157.3 GiB (33.8%)
  ID-1: /dev/nvme0n1 vendor: PNY model: CS3040 500GB SSD
  size: 465.76 GiB temp: 39.9 C
Partition:
  ID-1: / size: 456.88 GiB used: 157.3 GiB (34.4%) fs: ext4
  dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 296 KiB (0.1%) fs: vfat
  dev: /dev/nvme0n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Info:
  Processes: 299 Uptime: 10h 28m Memory: 7.74 GiB
  used: 4.77 GiB (61.7%) Init: systemd Compilers: gcc: 11.1.0
  Packages: 1489 Shell: Bash v: 5.1.8 inxi: 3.3.07
 
Thanks for that, love to see someone focused (on Linux, LOL)

Off for evening meal but back on my tomorrow.

Cheers

Chris
 
Installing the 470.86 Display driver from Nvidia may help. IF you want to try.

On this page click on the green numbers that say 470.86. From there you will be directed to another page where you can download the

Linux x64 (AMD64/EM64T) Display Driver​

IF you install the driver and it doesn't help you can always remove it:-

Unix Drivers | NVIDIA

Unix Drivers
www.nvidia.com

Can you boot to a Live USB OR> CD/DVD of any Linux distro?

How old is your mobo/machine?

Your PSU could be headed south:-
There are some signs to know if the power supply is on it's way out.
Random crashes, extra noise coming from the pc case, recurring failure of pc components/hardware and other poor performance issues.

You can test your PSU with a paper clip.
 
Alexzee said:
You can test your PSU with a paper clip.
Click to expand...
Sorry, @Alexzee, but this is a silly (and potentially dangerous) test, and I would discourage anyone from trying this. As the video says, it only simulates hitting your power switch, and you only determine whether the power supply will turn on or not. You know when you push your power button on the computer whether it will turn on or not. This test is more for a power supply that you found in the trash (or someone gave to you), and you want to know if it is dead or alive.

If a power supply is suspect, you can buy a cheap tester, such as this or this, to measure actual voltages. This is still not a perfect test either because the PSU could be failing under real-world load conditions, not just running idle with a tester connected. But knowing whether the PSU voltages are within their specified no-load ranges at least provides something tangible to consider in troubleshooting a problem. Those cheap testers may or may not be very accurate themselves. An even better idea is to use a quality multi-meter (like Fluke) and learning which pins to test, for those willing to put in that kind of effort.


mondochon said:
Graphics would make sense nvidia Gave me problems on Arch.
Click to expand...
And Endeavor OS is based on Arch. If a different driver doesn't help, maybe you should consider another distro.
 
mondochon said:
The whole build is less than 6 months. I’ll give the display driver a shot, thanks man! I’ll report back with findings.
Click to expand...
You're welcome.

The driver is a .run file so Google how to install a .run file in Linux.

If my memory serves me correctly you have to make it executable first and that run it.
askubuntu.com

How do I install .run files?

My PC has both Ubuntu and Windows 7 installed. I have installed all my drivers in Windows like Nvidia graphics, motherboard etc. Shall I install them in Ubuntu too? I looked on the web for my Nvidia
askubuntu.com askubuntu.com

Maybe give Linux Mint a try.
 
mondochon said:
The whole build is less than 6 months. I’ll give the display driver a shot, thanks man! I’ll report back with findings.
Click to expand...
How are things going for you?
 
If I were you I wouldn't manually download the run file because you will have to manually update that driver with every kernel update. Since you are using EndeavourOS use the nvidia-470xx packages from the AUR.

AUR (en) - nvidia-470xx-utils

aur.archlinux.org aur.archlinux.org

AUR (en) - nvidia-470xx-utils

aur.archlinux.org aur.archlinux.org

AUR (en) - nvidia-470xx-settings

aur.archlinux.org aur.archlinux.org
Using whatever AUR helper works for you, you will give yourself an easier time that way because you won't have to manually update the driver with every kernel update, also don't forgot to create a pacman hook for the Nvidia driver update.
 
f33dm3bits said:
If I were you I wouldn't manually download the run file because you will have to manually update that driver with every kernel update. Since you are using EndeavourOS use the nvidia-470xx packages from the AUR.

AUR (en) - nvidia-470xx-utils

aur.archlinux.org aur.archlinux.org

AUR (en) - nvidia-470xx-utils

aur.archlinux.org aur.archlinux.org

AUR (en) - nvidia-470xx-settings

aur.archlinux.org aur.archlinux.org
Using whatever AUR helper works for you, you will give yourself an easier time that way because you won't have to manually update the driver with every kernel update, also don't forgot to create a pacman hook for the Nvidia driver update.
Click to expand...
Has it always been that way that you have to update the driver with every kernel update?
 
Alexzee said:
Has it always been that way that you have to update the driver with every kernel update?
Click to expand...
Yes because when using the run file a kernel module gets compiled for the running kernel, when updated it needs to be rebuilt for the new kernel. Installing those Nvidia pacakges from the AUR should do that automatically when updating them from whatever AUR helper someone uses. That is why everyone always recommends installing the Nvidia drivers from the default repository of the distribution you are running, that is why I recommended the AUR Nvidia packages because I got the idea from the post that the OP was having problems with the newest drivers. The pacman hook is needed the upgrade the Nvidia driver for the intramfs.
 
f33dm3bits said:
Yes because when using the run file a kernel module gets compiled for the running kernel, when updated it needs to be rebuilt for the new kernel. Installing those Nvidia pacakges from the AUR should do that automatically when updating them from whatever AUR helper someone uses. That is why everyone always recommends installing the Nvidia drivers from the default repository of the distribution you are running, that is why I recommended the AUR Nvidia packages because I got the idea from the post that the OP was having problems with the newest drivers. The pacman hook is needed the upgrade the Nvidia driver for the intramfs.
Click to expand...
Got it, now I think I understand.
Thanks for the confirmation.
 
You must log in or register to reply here.

Members online

Total: 891 (members: 5, guests: 886)

Latest posts

Top