Computer completely freezes once a month

[Pigeon]

About once a month my computer freezes completely - I can't move mouse, restart cinnamon, run console by Ctrl + Alt + F1, nothing works. I checked memory with memtest, and ssd S.M.A.R.T. It doesn't happen on Windows. When I checked syslog I only found weird "\00" sings as showed below. I have Linux Mint 18.3, but it also happened on 18.2. I have updated bios and kernel, reinstalled Linux Mint, and nothing helps.

My computer system:
AMD Ryzen 5 1600
Motherboard msi B350 PC MATE
SSD adata SX7000 M.2 256GB
Radeon R9 280X

syslog:

Code: Select all

Feb  9 13:01:06 Kompiuter cinnamon-screensaver-pam-helper: pam_ecryptfs: seteuid error
Feb  9 13:01:07 Kompiuter kernel: [ 1352.723549] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=1 ID=33922 DF PROTO=UDP SPT=53758 DPT=6771 LEN=145 
Feb  9 13:01:51 Kompiuter ntpd[2687]: 195.46.37.22 local addr 192.168.0.13 -> <null>
Feb  9 13:02:45 Kompiuter kernel: [ 1450.717419] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=1 ID=49941 DF PROTO=UDP SPT=53758 DPT=6771 LEN=145 
Feb  9 13:02:45 Kompiuter kernel: [ 1450.717445] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=255 ID=49942 DF PROTO=UDP SPT=6771 DPT=6771 LEN=145 
Feb  9 13:02:45 Kompiuter kernel: [ 1450.717470] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=255 ID=49943 DF PROTO=UDP SPT=6771 DPT=6771 LEN=145 
Feb  9 13:02:47 Kompiuter kernel: [ 1452.717534] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=1 ID=50208 DF PROTO=UDP SPT=53758 DPT=6771 LEN=145 
Feb  9 13:02:47 Kompiuter kernel: [ 1452.717560] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=255 ID=50209 DF PROTO=UDP SPT=6771 DPT=6771 LEN=145 
Feb  9 13:03:06 Kompiuter kernel: [ 1471.443798] [UFW BLOCK] IN=enp33s0 OUT= MAC=01:00:5e:00:00:01:90:5c:44:6f:b4:e6:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=19136 PROTO=2 
Feb  9 13:04:25 Kompiuter kernel: [ 1550.711710] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=1 ID=59720 DF PROTO=UDP SPT=53758 DPT=6771 LEN=145 
Feb  9 13:04:25 Kompiuter kernel: [ 1550.711736] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=255 ID=59721 DF PROTO=UDP SPT=6771 DPT=6771 LEN=145 
Feb  9 13:04:25 Kompiuter kernel: [ 1550.711758] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=255 ID=59722 DF PROTO=UDP SPT=6771 DPT=6771 LEN=145 
Feb  9 13:04:27 Kompiuter kernel: [ 1552.711804] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=1 ID=60080 DF PROTO=UDP SPT=53758 DPT=6771 LEN=145 
Feb  9 13:05:02 Kompiuter kernel: [ 1587.636861] [UFW BLOCK] IN=enp33s0 OUT= MAC=01:00:5e:00:00:01:90:5c:44:6f:b4:e6:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=19138 PROTO=2 
Feb  9 13:05:10 Kompiuter kernel: [ 1595.731680] [UFW BLOCK] IN=enp33s0 OUT= MAC=01:00:5e:00:00:fb:e0:b9:ba:a0:cb:54:08:00 SRC=192.168.0.171 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=49841 PROTO=2 
Feb  9 13:06:05 Kompiuter kernel: [ 1650.705854] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=1 ID=7914 DF PROTO=UDP SPT=53758 DPT=6771 LEN=145 
Feb  9 13:06:05 Kompiuter kernel: [ 1650.705882] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=255 ID=7915 DF PROTO=UDP SPT=6771 DPT=6771 LEN=145 
Feb  9 13:06:07 Kompiuter kernel: [ 1652.706010] [UFW BLOCK] IN=enp33s0 OUT= MAC= SRC=192.168.0.13 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=1 ID=7934 DF PROTO=UDP SPT=53758 DPT=6771 LEN=145 
\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00Feb  9 14:05:20 Kompiuter rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1393" x-info="http://www.rsyslog.com"] start
Feb  9 14:05:20 Kompiuter rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Feb  9 14:05:20 Kompiuter systemd-modules-load[584]: Inserted module 'ashmem_linux'
Feb  9 14:05:20 Kompiuter rsyslogd: rsyslogd's groupid changed to 108
Feb  9 14:05:20 Kompiuter rsyslogd: rsyslogd's userid changed to 104
Feb  9 14:05:20 Kompiuter systemd-modules-load[584]: Inserted module 'binder_linux'
Feb  9 14:05:20 Kompiuter systemd-modules-load[584]: Inserted module 'lp'
Feb  9 14:05:20 Kompiuter systemd-modules-load[584]: Inserted module 'ppdev'
Feb  9 14:05:20 Kompiuter loadkeys[576]: Wczytywanie /etc/console-setup/cached.kmap.gz
Feb  9 14:05:20 Kompiuter systemd[1]: Started Set console keymap.
Feb  9 14:05:20 Kompiuter systemd-udevd[608]: NAME="%k" is ignored, because it breaks kernel supplied names, please remove it from /lib/udev/rules.d/99-anbox.rules:1
Feb  9 14:05:20 Kompiuter systemd-udevd[608]: NAME="%k" is ignored, because it breaks kernel supplied names, please remove it from /lib/udev/rules.d/99-anbox.rules:2
Feb  9 14:05:20 Kompiuter systemd[1]: Started udev Kernel Device Manager.
Feb  9 14:05:20 Kompiuter systemd[1]: Starting Remount Root and Kernel File Systems...
Feb  9 14:05:20 Kompiuter systemd[1]: Started Remount Root and Kernel File Systems.
Feb  9 14:05:20 Kompiuter rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
Feb  9 14:05:20 Kompiuter systemd[1]: Starting Load/Save Random Seed...
Feb  9 14:05:20 Kompiuter systemd[1]: Starting Flush Journal to Persistent Storage...
Feb  9 14:05:20 Kompiuter systemd[1]: Starting udev Coldplug all Devices...

[tovian]

This will NOT fix the problem - but it may establish whether you are truly frozen or not.
It's also a good sequence to remember because it should work with ANY version of Linux when a computer appears to be dead.

enter this series of commands...
each command will consist of hitting three keys at the same time:
1) the [alt] key
2) the [printScreen] or [Sys Rq] key
3) a letter key (lower case)
(I find it easier to hold down the [alt] and [sys rq] keys with my right hand then hit each letter key with my left hand)
- after EACH command count 1001, 1002, 1003 before typing the next command *do not wait for a response... there will be none
- these commands can go in many different orders as long as the "B" goes last (it's the BOOT command)
- letters below are upper-case for ease of reading... they should be entered into the computer in lower-case
R
S
E
I (this is i as in India - not L as in Lima)
U
B

One acronym for this is Raising Skinny Elephants Is Utterly Boring and is often referred to simply as "Raising Skinny Elephants" - *You can Google that for more info
If the kernel is alive your machine will reboot, if nothing happens then you are truly frozen and you will have to cycle the power to restart.

Whatever you learn from this may help identify the problem.

[Pjotr]

Please generate an overview of your system like this:
- Launch a terminal window (this is how to launch a terminal window);
- make the terminal window full screen, to avoid chopped lines;
- Copy/paste this command into the terminal:

Code: Select all

inxi -Fxz

(if you type: the letter F is a capital letter)

Press Enter.

Copy/paste the output in your next message.

[JoeFootball]

Augmenting above: Use the Magic SysRq Key on Linux to Fix Frozen X Servers, Cleanly Reboot, and Run Other Low-Level Commands

[trytip]

Feb 9 14:05:20 Kompiuter systemd-udevd[608]: NAME="%k" is ignored, because it breaks kernel supplied names, please remove it from /lib/udev/rules.d/99-anbox.rules:1
Feb 9 14:05:20 Kompiuter systemd-udevd[608]: NAME="%k" is ignored, because it breaks kernel supplied names, please remove it from /lib/udev/rules.d/99-anbox.rules:2

did you remove what this says? do you still have anbox installed? if not delete these two files

[Pigeon]

This will NOT fix the problem - but it may establish whether you are truly frozen or not.
It's also a good sequence to remember because it should work with ANY version of Linux when a computer appears to be dead.

enter this series of commands...
each command will consist of hitting three keys at the same time:
1) the [alt] key
2) the [printScreen] or [Sys Rq] key
3) a letter key (lower case)
(I find it easier to hold down the [alt] and [sys rq] keys with my right hand then hit each letter key with my left hand)
- after EACH command count 1001, 1002, 1003 before typing the next command *do not wait for a response... there will be none
- these commands can go in many different orders as long as the "B" goes last (it's the BOOT command)
- letters below are upper-case for ease of reading... they should be entered into the computer in lower-case
R
S
E
I (this is i as in India - not L as in Lima)
U
B

One acronym for this is Raising Skinny Elephants Is Utterly Boring and is often referred to simply as "Raising Skinny Elephants" - *You can Google that for more info
If the kernel is alive your machine will reboot, if nothing happens then you are truly frozen and you will have to cycle the power to restart.

Whatever you learn from this may help identify the problem.

Thanks, nice trick, I am going to try it next time, my computer crashes.

Please generate an overview of your system like this:
- Launch a terminal window (this is how to launch a terminal window);
- make the terminal window full screen, to avoid chopped lines;
- Copy/paste this command into the terminal:

Code: Select all

inxi -Fxz

(if you type: the letter F is a capital letter)

Press Enter.

Copy/paste the output in your next message.

Here is specification:

Code: Select all

System:    Host: Kompiuter Kernel: 4.13.0-32-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.6.7 (Gtk 3.18.9) Distro: Linux Mint 18.3 Sylvia
Machine:   Mobo: Micro-Star model: B350 PC MATE (MS-7A34) v: 2.0
           Bios: American Megatrends v: A.70 date: 09/20/2017
CPU:       Hexa core AMD Ryzen 5 1600 Six-Core (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 38399
           clock speeds: max: 3200 MHz 1: 1550 MHz 2: 1550 MHz 3: 1550 MHz
           4: 1550 MHz 5: 1550 MHz 6: 1550 MHz 7: 1550 MHz 8: 1550 MHz
           9: 1550 MHz 10: 1550 MHz 11: 1550 MHz 12: 1550 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
           bus-ID: 23:00.0
           Display Server: X.Org 1.18.4 drivers: ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           GLX Renderer: AMD TAHITI (DRM 2.50.0 / 4.13.0-32-generic, LLVM 5.0.0)
           GLX Version: 3.0 Mesa 17.2.4 Direct Rendering: Yes
Audio:     Card-1 Advanced Micro Devices [AMD] Device 1457
           driver: snd_hda_intel bus-ID: 25:00.3
           Card-2 Advanced Micro Devices [AMD/ATI] Tahiti XT HDMI Audio [Radeon HD 7970 Series]
           driver: snd_hda_intel bus-ID: 23:00.1
           Sound: Advanced Linux Sound Architecture v: k4.13.0-32-generic
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: f000 bus-ID: 21:00.0
           IF: enp33s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 1160.2GB (23.0% used)
           ID-1: /dev/nvme0n1 model: N/A size: 256.1GB
           ID-2: /dev/sda model: SAMSUNG_HM160HI size: 160.0GB
           ID-3: /dev/sdb model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 226G used: 157G (73%) fs: ext4 dev: /dev/dm-1
           ID-2: /boot size: 473M used: 231M (52%) fs: ext2 dev: /dev/nvme0n1p2
           ID-3: swap-1 size: 8.54GB used: 0.00GB (0%) fs: swap dev: /dev/dm-2
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: No active sensors found. Have you configured your sensors yet? mobo: N/A gpu: 48.0
Info:      Processes: 311 Uptime: 4:47 Memory: 6920.3/7990.0MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35 

Feb 9 14:05:20 Kompiuter systemd-udevd[608]: NAME="%k" is ignored, because it breaks kernel supplied names, please remove it from /lib/udev/rules.d/99-anbox.rules:1
Feb 9 14:05:20 Kompiuter systemd-udevd[608]: NAME="%k" is ignored, because it breaks kernel supplied names, please remove it from /lib/udev/rules.d/99-anbox.rules:2

did you remove what this says? do you still have anbox installed? if not delete these two files

I have just deleted these files.

[Pjotr]

Very new hardware.... Try the 4.14 kernel, by means of the reliable Canonical Kernel Team PPA:
https://sites.google.com/site/easylinux ... ted-kernel
(item 8, right column)

[Pigeon]

Very new hardware.... Try the 4.14 kernel, by means of the reliable Canonical Kernel Team PPA:
https://sites.google.com/site/easylinux ... ted-kernel
(item 8, right column)

I can't really install kernel 4.14 from canonical-kernel-team ppa, as showed in this tutorial, because it provides only newer 4.13 kernel.

[trytip]

usually before a crash there will be a long array of errors in the .xsession-errors file open it and see if anything is helpful

[Pjotr]

Very new hardware.... Try the 4.14 kernel, by means of the reliable Canonical Kernel Team PPA:
https://sites.google.com/site/easylinux ... ted-kernel
(item 8, right column)

I can't really install kernel 4.14 from canonical-kernel-team ppa, as showed in this tutorial, because it provides only newer 4.13 kernel.

You're right: I saw 4.14 packages on the Launchpad web page of that PPA, but apparently they're not flagged for xenial (yet).....

In the meantime you might try the newer 4.13 kernel that's available by means of that PPA. And as soon as the 4.14 (or even the 4.15) becomes available, install it.

[Pigeon]

So far nothing have crashed. Installing the latest kernel helped. Thanks everyone!
Edit:
Ironically computer crashed the day after. This time there is nothing strange in syslog, also I've tested Alt + SysRq R E I S U B and kernel seemed completely dead. The last thing I did was updating systemd.

[Petermint]

Completely dead does happen. I have had completely dead Linux from a faulty USB device, an incompatible kernel, and "unknown" where a clean reinstall fixed it. You can also get completely dead from SSD, suspend, and network problems where you walk away for a couple of minutes and find the system wakes up. Kernel problems are sometimes fixed by a later kernel and at other times, you have to go back to an older version for a while until there is a new version with the fight fix.

Is there any common activity before the freeze? The fans winding up due to heat? You plug in a backup drive? Your neighbour starts arc welding? (That last problem did happen in an office next to a repair shop.)

[Pigeon]

Completely dead does happen. I have had completely dead Linux from a faulty USB device, an incompatible kernel, and "unknown" where a clean reinstall fixed it. You can also get completely dead from SSD, suspend, and network problems where you walk away for a couple of minutes and find the system wakes up. Kernel problems are sometimes fixed by a later kernel and at other times, you have to go back to an older version for a while until there is a new version with the fight fix.

Is there any common activity before the freeze? The fans winding up due to heat? You plug in a backup drive? Your neighbour starts arc welding? (That last problem did happen in an office next to a repair shop.)

I have SSD, but I never suspend my computer, because system is entirely encrypted. Fans had never winded before those crashes. And there is nothing common - the time is different, nothing strange had happened, before computer crashed, and it happens about once a month or two, so it is hard to notice.

[Petermint]

Ok. My Android stuff breaks every couple of weeks and requires a reboot. If it was major, I would schedule a reboot once per week. For Linux Mint, I switch off overnight so do not run into that type of problem.