Nearly all apps crashing and system freezes

okay it took like a 2 seconds

[gil@arch ~]$ nvidia-installer-dkms -t
2020-09-10 03:31:46 [INFO]: EndeavourOS Nvidia Installer v3.3.7
2020-09-10 03:31:46 [INFO]: All logs will be stored in /tmp/nvidia-installer.log
2020-09-10 03:31:46 [INFO]: Running the installer in testing mode...
2020-09-10 03:31:46 [INFO]: Updating Nvidia graphics cards database...
2020-09-10 03:31:46 [INFO]: nvidia-installer-update-db
2020-09-10 03:31:46 [INFO]: Installing nvidia-dkms driver...
2020-09-10 03:31:46 [INFO]: Removing conflicting packages...
2020-09-10 03:31:46 [INFO]: pacman -Rs --noconfirm --noprogressbar --nodeps nvidia
2020-09-10 03:31:46 [INFO]: Downloading and installing driver packages, please wait as this may take a few minutes...
2020-09-10 03:31:46 [INFO]: pacman -Sqy --noconfirm --noprogressbar nvidia-dkms libvdpau nvidia-settings lib32-nvidia-utils lib32-libvdpau
2020-09-10 03:31:46 [INFO]: Unpatching /usr/share/applications/nvidia-settings.desktop...
2020-09-10 03:31:46 [INFO]: /usr/bin/sed -i s|Exec=optirun -b none /usr/bin/nvidia-settings -c :8|Exec=/usr/bin/nvidia-settings| /usr/share/applications/nvidia-settings.desktop
2020-09-10 03:31:46 [INFO]: Creating /etc/X11/xorg.conf.d/20-nvidia.conf file...
2020-09-10 03:31:46 [INFO]: Installation finished. Nothing has been modified as testing mode was ON.

So now run

sudo nvidia-installer-dkms

okay a lot of errors: pastebin

In test mode there were no errors. I wonder if you were to switch to a TTY and log in as root and run it.

Edit: If you want to try
crtl alt f2
log in as root
nvidia-installer-dkms

IDK I can try it but last 20 min chromium crashed like 10 times:

[gil@arch ~]$ coredumpctl list
Thu 2020-09-10 03:19:38 +03    1958  1000  1000  11 present   /usr/lib/chromium/chromium
Thu 2020-09-10 03:19:53 +03    1723  1000  1000   5 present   /usr/lib/chromium/chromium
Thu 2020-09-10 03:21:19 +03    2700  1000  1000  11 present   /usr/lib/chromium/chromium
Thu 2020-09-10 03:23:20 +03    1921  1000  1000  11 present   /usr/lib/chromium/chromium
Thu 2020-09-10 03:23:29 +03    2050  1000  1000  11 present   /usr/lib/chromium/chromium
Thu 2020-09-10 03:25:13 +03    2169  1000  1000  11 present   /usr/lib/chromium/chromium
Thu 2020-09-10 03:33:32 +03    3164     0     0  11 error     /usr/bin/pacman
Thu 2020-09-10 03:37:20 +03    1700  1000  1000  11 present   /usr/lib/chromium/chromium
Thu 2020-09-10 03:38:01 +03    3796  1000  1000  11 present   /usr/lib/chromium/chromium
Thu 2020-09-10 03:38:04 +03    3837  1000  1000  11 present   /usr/lib/chromium/chromium
Thu 2020-09-10 03:38:11 +03    3821  1000  1000  11 present   /usr/lib/chromium/chromium
Thu 2020-09-10 03:38:28 +03    3701  1000  1000  11 present   /usr/lib/chromium/chromium


Okay after I did ctrl alt f2IMG_20200910_034200
Then when I tried to login:IMG_20200910_034222
But now my system is not even booting up: 15996990942664123858553969163122

Oh manā€¦i wasnā€™t expecting that to happen. There is something seriously wrong for most apps to be crashing and system freezing.

Edit : I do see a lot of errors and the chromium ones too.

Haha yeah from first image I think problem lies on nvidia. (Errors in libnvidia-glcore)
Maybe I should reinstall OS and install nvidia differently this time from the start? Any suggestions

I wonder if the computer will boot on Nouveau if you donā€™t install Nvidia. Then install the dkms version after. Iā€™m just not sure if it will boot on nouveau after itā€™s installed?

Edit: Some of these newer RTX series iā€™m not sure. Mine works but it is a GTX 1060

Iā€™m leaning towards it being video related. The dkms version is definately better anyway because it rebuilds the kernel modules every time there is an updated kernel.

Okay then, tomorrow I will try to reinstall.
BTW on nvidia forum there are lot of similar segmentation faults threads but no solution unfortunately.

Itā€™s probably related to the RTX 2060 card being the newer series as they do have some issues to work around sometimes. Segmentation faults arenā€™t good. It usually always causes a crash of some kind.

If you have some incompatible AUR packages installed, that could cause issues. Also, if some previous updates or installs were not properly finished, that can cause issues. Use only pacman to install or update packages, this narrows down potential reasons for issues.

And how to create the installer USB, and BIOS settings like secure boot should be checked that they are OK.

After the above is OK, reinstall most probably is the fastest way forward.

Iā€™m 90% sure itā€™s one of your SSD drives dining and if iā€™m right you wonā€™t be able to boot pretty soon.
Judging by amount of errors and randomā€¦

I leave only 10% because of that

Are you absolutely sure that you can use Win 10 right now without programs crashes, freezes etc?

This could also be a failing disk.

Try with the live environment and check that works correctly.

Yep, but if it is - then before using live usb itā€™s best to:

  1. Remove all drives and boot only from USB
  2. If it boots fine try to add one drive at a time, to check which one is failing
  3. Boot from USB again, if itā€™s fine try next drive etc.

Thatā€™s a good idea, but it wonā€™t help if the issue is caused by reading data from the drive. :wink:

1 Like

You mean live USB drive itself? :upside_down_face:

Well yeah, but thatā€™s more likely failure of SSD stillā€¦
Technically itā€™s possible that all drives and USB are failed, but not likely :sweat_smile:

I think itā€™s just one of SSDs, so best we can do is to try isolate which one :face_with_monocle:

If itā€™s a failed/failing disk, then itā€™s very likely the one which the OS is installed on.

Not really, i had seen multiple times personally that non-system secondary dead SSD caused such things, once you remove it - itā€™s perfectly fine again.

Of course still in that case - itā€™s very advisable to reinstall OS on system drive again, since who knows what kind of errors that failed secondary drive caused while such operationā€¦

I hate SSDs for that :laughing:
Every time when i see something that random and all over the system, first thing i do is excluding SSD :yum: