EndeavourOS crashing and rebooting after new CPU has been installed

I personally think my CPU is just not properly supported https://forums.debian.net/viewtopic.php?t=156151 - since my previous 3 2200G worked flawlessly and only crashing when overwhelmed (like expected), and the other day my PC crashed and rebooted 2 times within 20 minutes of each other, during a zoom call, then I switched to Windows, and again, no issues… The fact that Windows can run for 3 days straight with me gaming, video editing, just letting it idle, copy/move files, browsing internet and YouTube (pretty much doing everything that would generally crash Linux), whatever and have no crashes or hangs tells me that the 7 5700x just isn’t properly supported yet (either that or Windows has some sort of logic to restore a crashing system without letting the user even know the system is crashing), especially considering that I have checked the temps, stress test the CPU and RAM (on Linux, didn’t crash once during those tests either which was strange), reset my memory module, even tried running Linux Mint (no luck)… My friend had the same issue when he was on Linux Mint with his 5 5600X (and 0 issues on Windows too), until we switched him to Endeavour and the issue disappeared completely (suppose that somewhere the CPU got supported)

@joekamprad Got a 1080TI here, I’ll try your method, I really hope it helps, I have reached peak frustration at this point

@His_Turdness Will try this as well, hopefully it helps

This is totally untrue. The issue is more likely the motherboard and it’s implementation of UEFI Bios. Or the Cpu has been damaged installing it. Or it could be the power supply or ram.

Edit: Did you try these settings from the link.

SVM Mode - Enabled
Power Loading - Enabled
CEC2019Ready - Disabled
ERP - Enabled
Global C State - Auto
IOMMU - Disabled

Well, if it is not a support issue, then BIOS is the most likely culprit, since I am 90% sure the CPU is fine (have been stress tested multiple times with no issues during tests with heavy load - and Windows also not complaining about it during CPU intensive tasks). I highly doubt the PSU is an issue, it is still relatively new and 650w or so, with no power issues on Windows (where my CPU+GPU+RAM are often being almost fully utilised - way more pressure than I’d usually put on Linux day-to-day), and my RAM is fine, it was before upgrading my CPU, and was fine during RAM focused stress tests after CPU upgrade. The only reason I came to that conclusion was because I only seem to be experiencing issues on Linux, no matter the distro or versions, and because I’ve seen the same issue happening on my friends PC, which as previously stated was fixed when he upgraded to EOS with newer software.

SVM Mode - Enabled
Power Loading - don’t think I have this option
CEC2019Ready - don’t think I have this option
ERP - https://www.overclock.net/threads/how-to-enable-disable-eup-erp-in-asrock-bios.1348389/ don’t have the options they seem to be talking about
Global C State - Assuming auto? Same issue as above
IOMMU - https://us.informatiweb.net/tutorials/it/bios/enable-iommu-or-vt-d-in-your-bios.html#asus-uefi-bios-blue don’t know if i have these “bridges” most posts refer to

I also included screenshots of my BIOS for your reference, feel free to request more

And also thank you (all) for helping me so far






You haven’t tried updating the UEFI Firmware (Bios) to the latest. I know they have two beta versions which is ridiculous. Why they haven’t put out the a final is beyond me. The fact is the last two versions have updated AMD AGESA. This controls the power functions of the motherboard related to the Cpu. I know it say’s you can’t go back to previous Bios version which doesn’t make any sense to me. But you also can’t with the version you have now. Personally i am not afraid of using a beta Bios. But it’s your hardware so it’s up to you. I just think the updated AGESA is important. Will it correct your problem. I can’t say. :person_shrugging:

I will then trust your input, I’ll update to the latest version sometime after the 18th (got some important stuff that needs handling first, so cannot risk a broken system), but then I’ll get back to you on it - for now I’ll keep trying alternative methods

Data you requested: inxi -Gaz

Graphics:
  Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: ZOTAC driver: nouveau
    v: kernel non-free: 550.xx+ status: current (as of 2024-09; EOL~2026-12-xx)
    arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 1
    speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
    active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DVI-D-1 bus-ID: 08:00.0
    chip-ID: 10de:1b06 class-ID: 0300 temp: 35.0 C
  Device-2: Elgato Systems GmbH Game Capture Neo
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 3.0
    speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-1:2 chip-ID: 0fd9:008c
    class-ID: 0300 serial: <filter>
  Display: x11 server: X.Org v: 21.1.13 compositor: xfwm4 v: 4.18.0 driver:
    X: loaded: modesetting alternate: fbdev,nouveau,nv,vesa dri: nouveau
    gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26")
    s-diag: 583mm (22.95")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Elgato GC Neo built: 2023
    res: 1920x1080 dpi: 81 gamma: 1.2 size: 600x338mm (23.62x13.31")
    diag: 689mm (27.1") ratio: 16:9 modes: max: 3840x2160 min: 720x400
  API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
    device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
    drv: nouveau inactive: wayland
  API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 24.2.3-arch1.1 glx-v: 1.4
    direct-render: yes renderer: NV132 device-ID: 10de:1b06 memory: 10.73 GiB
    unified: no

It shows you are running on nouveau open source driver for Nvidia. Did you not install using the nividia menu option?

Edit: Nvidia drivers are not installed and they should work fine. Is working on GTX 1060 for me.

Sorry my bad, that is the one before the nvidia-inst install, here is the updated one

Graphics:
  Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: ZOTAC driver: nvidia
    v: 560.35.03 alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current
    (as of 2024-09; EOL~2026-12-xx) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s ports: active: none off: HDMI-A-1
    empty: DP-1, DP-2, DP-3, DVI-D-1 bus-ID: 08:00.0 chip-ID: 10de:1b06
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.13 compositor: xfwm4 v: 4.18.0 driver:
    X: loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa
    gpu: nvidia,nvidia-nvswitch display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26")
    s-diag: 583mm (22.95")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: Elgato GC Neo
    built: 2023 res: 1920x1080 dpi: 81 gamma: 1.2 size: 600x340mm (23.62x13.39")
    diag: 689mm (27.1") ratio: 16:9 modes: max: 3840x2160 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 560.35.03
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
    memory: 10.74 GiB

And no, I did not choose the NVIDIA option on install, since it says for the latest cards, and the 1080 is not that new anymore I think, but, if you believe reinstalling via that option would be better, I can, I don’t currently have any important files on my install, so won’t be a pain - and also same yeah, I very rarely had issues with my GPU in the past, especially after moving to EOS

Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: ZOTAC driver: nvidia
v: 560.35.03 alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current
(as of 2024-09; EOL~2026-12-xx) arch: Pascal code: GP10x

it shows the EOL: EOL~2026-12-xx
still 2 years support with latest nvidia drivers.

But no need to reinstall in case you are using nvidia-inst it will be all setup the same already.

I don’t want to get ahead of myself again, but I’ve been using it for about 6 hours straight now, doing what will usually makes it crash within 2-or less hours, no crashes of yet… Also no crashes last week either. It had one tiny hang which made me think it’s gonna crash, but it just continued working like a beast. Could it be that all of this time my GPU caused my CPU to have issues because of drivers - to the point of rebooting itself? Insane, would never have guessed that lol

I’ll keep y’all updated, if by Friday I still haven’t seen any issues, I will mark this as the solution

Thank you everyone for your help, issue seems to have been related to NVIDIA drivers, solution has been marked. Thank you once again!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.