Freezing randomly

just encountered another freeze while watching youtube :confused:
one of my friend was having the same issue too with mate, i.e graphic drivers. he was having issues with the integrated intel graphics.I have integrated HD graphics too.
https://pastebin.com/zq9p1cA4
This is the log file just after turing on my pc after a hard shut down.

This is reminiscent of the C-state bug Intel caused in their i915 driver many years ago and never fixed, but I think your CPU shouldn't suffer from it. (Sorry, it's late and I'm too tired to go through ARK right now).
I'm guessing you don't know how to edit GRUB commands, and you definitely should not go down this road until you've explored all the other options, but if that time comes "intel_idle.max_cstate=1" is the magic setting.

1 Like

okay i did it cuz my pc froze again when i was in an important voice chat

Good evening,
I also face the same problem. I would be grateful if anyone could help.
Best
Yannis

Here are the results of the inxi-Fxxz

System:
Kernel: 5.0.0-27-generic x86_64 bits: 64 compiler: gcc v: 8.3.0
Desktop: MATE 1.20.4 info: mate-panel, plank, vala-panel wm: marco 1.20.3
dm: LightDM 1.28.0 Distro: Ubuntu 19.04 (Disco Dingo)
Machine:
Type: Laptop System: HP product: HP 240 G4 Notebook PC
v: Type1ProductConfigId serial: Chassis: type: 10
serial:
Mobo: HP model: 8131 v: KBC Version 30.0B serial: UEFI: Insyde
v: F.22 date: 11/11/2016
Battery:
ID-1: BAT0 charge: 41.2 Wh condition: 41.2/41.2 Wh (100%) volts: 16.6/14.6
model: Hewlett-Packard Primary type: Li-ion serial: status: Full
CPU:
Topology: Dual Core model: Intel Core i5-6200U bits: 64 type: MT MCP
arch: Skylake family: 6 model-id: 4E (78) stepping: 3 microcode: CC
L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19200
Speed: 500 MHz min/max: 400/2800 MHz Core speeds (MHz): 1: 500 2: 500
3: 500 4: 500
Vulnerabilities: Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Graphics:
Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Hewlett-Packard
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:1916
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
compositor: marco v: 1.20.3 resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
v: 4.5 Mesa 19.0.8 compat-v: 3.0 direct render: Yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:9d70
Sound Server: ALSA v: k5.0.0-27-generic
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 4000 bus ID: 01:00.0
chip ID: 10ec:8168
IF: enp1s0 state: down mac:
Device-2: Realtek RTL8723BE PCIe Wireless Network Adapter
vendor: Hewlett-Packard driver: rtl8723be v: kernel port: 3000
bus ID: 02:00.0 chip ID: 10ec:b723
IF: wlp2s0 state: up mac:
Drives:
Local Storage: total: 465.76 GiB used: 76.12 GiB (16.3%)
ID-1: /dev/sda vendor: Western Digital model: WD5000LPCX-60VHAT0
size: 465.76 GiB block size: physical: 4096 B logical: 512 B
speed: 6.0 Gb/s rotation: 5400 rpm serial: rev: 1A01 scheme: GPT
Partition:
ID-1: / raw size: 13.67 GiB size: 13.39 GiB (97.97%)
used: 9.19 GiB (68.6%) fs: ext4 dev: /dev/sda6
ID-2: /home raw size: 210.25 GiB size: 205.95 GiB (97.96%)
used: 66.87 GiB (32.5%) fs: ext4 dev: /dev/sda7
Sensors:
System Temperatures: cpu: 42.0 C mobo: 0.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 215 Uptime: 32m Memory: 3.77 GiB used: 2.59 GiB (68.6%)
Init: systemd v: 240 runlevel: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash
v: 5.0.3 running in: mate-terminal inxi: 3.0.33

arQon solution helped me! you should try it too.

Further to my entry above I have discovered a problem with the machine's RAM, so MATE is likely innocent.