Computer Hard Resets After Starting Steam Game

[Detroitbecomemonke]

Hi there! I'm new to Linux Mint.

I'm desperate. I switched over from Windows 10 in order to test and see if this problem was isolated to Windows or would happen across platforms. It followed me. At this point I'm assuming my issue is hardware related, but please let me explain.

When I use Steam to open either the games Valheim, Risk of Rain 2, or Rocket League, my computer gets a few seconds into the game's boot process and spontaneously hard boots, then restarts. When I was on Windows 10, I attempted to try and troubleshoot the problem, but it would not generate a crash dump. Now that I'm here on Linux Mint 20.2, and having the same issue, I am unfamiliar with the system to find where a crash report would be or how to access it. I found the system logs for the last few boots, but I am unable to decipher exactly what I'm looking at.

The long and short is: I need help finding a crash file, if it exists, and if it doesn't, would it be possible to find out what the issue would be from the system logs if they're able to be viewed up until the point of restart?

Any and all constructive help is appreciated, and I hope to learn from this experience!

[Moonstone Man]

The long and short is: I need help finding a crash file....

No, you need help deciding where to start, and that would be with memtest86 running for a long soak test. The longer the better.

If that doesn't reveal an issue, a check for a BIOS update is in order. Whatever the issue is, it has nothing to do with Linux Mint. You also don't say if you are using the same downloaded version of the game so corruption at the file system level cannot be ruled out either.

[Detroitbecomemonke]

No, you need help deciding where to start, and that would be with memtest86 running for a long soak test. The longer the better.

Wonderful, as soon as I get home from work I'll begin running this. Please bear with me, I probably won't have results for the next 12 hours or so, with work and other stuff in between.

You also don't say if you are using the same downloaded version of the game so corruption at the file system level cannot be ruled out either.

Good point. Fresh install of Linux Mint, running on a separate hard drive. The installation of Steam and Valheim (the only game I had time to install last night) are both on the same drive as Linux Mint. The old Steam files are on the Windows install on another hard drive, and were not used for this test.

[Detroitbecomemonke]

I've run the memory test, I'll check for a BIOS update when I get home today. Anything else you could recommend for me to do?

[Moonstone Man]

Anything else you could recommend for me to do?

Yes. Please post the output of inxi -Fxz from a terminal and enclose it in code tags [code]output.here[/code]. You'll see the code tags icon </> when you reply.

[Detroitbecomemonke]

Yes. Please post the output of inxi -Fxz from a terminal and enclose it in code tags [code]output.here[/code].

Code: Select all

System:
  Kernel: 5.4.0-80-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 5.0.5 Distro: Linux Mint 20.2 Uma 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: ASUS product: All Series v: N/A serial: <filter> 
  Mobo: ASUSTeK model: X99-DELUXE v: Rev 1.xx serial: <filter> 
  UEFI [Legacy]: American Megatrends v: 3505 date: 01/13/2017 
CPU:
  Topology: 6-Core model: Intel Core i7-5930K bits: 64 type: MT MCP 
  arch: Haswell rev: 2 L2 cache: 15.0 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 83957 
  Speed: 1199 MHz min/max: 1200/3700 MHz Core speeds (MHz): 1: 1199 2: 1200 
  3: 1203 4: 1203 5: 1200 6: 1199 7: 1199 8: 1199 9: 1200 10: 1200 11: 1200 
  12: 1204 
Graphics:
  Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: eVga.com. driver: nvidia 
  v: 470.57.02 bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.9 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: NVIDIA GeForce GTX 970/PCIe/SSE2 
  v: 4.6.0 NVIDIA 470.57.02 direct render: Yes 
Audio:
  Device-1: Intel C610/X99 series HD Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Device-2: NVIDIA GM204 High Definition Audio vendor: eVga.com. 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 
  Device-3: Logitech HD Webcam C615 type: USB driver: snd-usb-audio,uvcvideo 
  bus ID: 3-10.1:5 
  Sound Server: ALSA v: k5.4.0-80-generic 
Network:
  Device-1: Intel Ethernet I218-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k 
  port: f000 bus ID: 00:19.0 
  IF: eno1 state: down mac: <filter> 
  Device-2: Broadcom and subsidiaries BCM4352 802.11ac Wireless Network 
  Adapter 
  vendor: ASUSTeK driver: bcma-pci-bridge v: N/A port: e000 bus ID: 02:00.0 
  Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb 
  v: 5.6.0-k port: d000 bus ID: 08:00.0 
  IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-4: Broadcom and subsidiaries BCM4360 802.11ac Wireless Network 
  Adapter 
  vendor: ASUSTeK driver: bcma-pci-bridge v: N/A port: d000 bus ID: 09:00.0 
Drives:
  Local Storage: total: 3.87 TiB used: 774.21 GiB (19.5%) 
  ID-1: /dev/sda vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB 
  ID-2: /dev/sdb vendor: Western Digital model: WD5000AAKS-22V1A0 
  size: 465.76 GiB 
  ID-3: /dev/sdc vendor: Samsung model: SSD 840 PRO Series size: 238.47 GiB 
  ID-4: /dev/sdd type: USB vendor: Sabrent model: SABRENT size: 465.76 GiB 
  ID-5: /dev/sde type: USB vendor: Western Digital model: WD10JMVW-11S5XS1 
  size: 931.48 GiB 
Partition:
  ID-1: / size: 457.45 GiB used: 25.09 GiB (5.5%) fs: ext4 dev: /dev/sdb1 
Sensors:
  System Temperatures: cpu: 28.0 C mobo: N/A gpu: nvidia temp: 51 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Info:
  Processes: 314 Uptime: 3m Memory: 62.73 GiB used: 1.20 GiB (1.9%) 
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
  inxi: 3.0.38 

[Moonstone Man]

Code: Select all

System:
  Kernel: 5.4.0-80-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 

There isn't anything there at all that would cause even the remotest level of suspicion but there are still some things that can be done to try and suss it out.

1) Post the output of this command: dmesg --level=err.

2) If the machine did not crash in the previous boot or you are unsure if it crashed or not, deliberately attempt to crash the machine then, if and when it crashes, reboot and post the output of:

Code: Select all

journalctl -o short-precise -k -x -b -1 -p 3

While you're waiting for a response from here to the above:

3) Shut the machine down, remove the power and video cords, press the power on button (to discharged any power stored in the PSU's capacitors), remove the video card completely, put it back and make sure it's firmly seated.

4) While you've got the video card out, look for capacitor plague. You're looking for anything that looks like this:





Notice the three green caps. Two have distended tops and one has a flat top. Also note the first green cap from the left has a brown, waxy substance on top. The cap with a flat top is ok, but the other two are plagued. If you see anything like that then your motherboard is the suspect.

Reconnect the cables and try again.

5) If it crashes after doing 3) and 4), shut it down again and apply some pressure to the motherboard with two fingers in various places then try again. You've applied enough pressure when you feel the board give by the tiniest amount. This is done in case there is an open circuit somewhere on the board. Applying pressure to make the board give just a tiny bit may temporarily close an open circuit, or it may make it worse or it may do nothing at all. If it doesn't crash after this then either there was a loose or open connection somewhere and it's now either permanently rectified or temporarily rectified. If it's temporary then the machine will often crash when it gets warmer. You'll just have to keep your eye on this if applying pressure actually works.

6) This, along with 7, 8 and 10, is where it can get expensive. Try a different video card. If need be, beg, borrow or temporarily steal one.

7) The power supply might be faulty and require replacement. If this is the case then searching online for how to test the PSU won't help unless you have appropriate electronic test gear, so again, you may have to beg, borrow or steal one to test this.

8 ) Stress test the CPU.

Code: Select all

sudo apt-get install stress
sudo stress --cpu  12 --timeout 90

If the machine crashes here then you should carefully rip the CPU out, clean all of the thermal grease, also carefully, using methylated spirits and a small clean cloth, being very careful not to bend any pins, reseat the CPU, apply a matchstick head's worth of new thermal grease, put the cooler back after cleaning out dust and muck and try again.

I've adjusted the CPU stress command above to suit your CPU. If it doesn't crash after 90 seconds, you can assume that at least the CPU, cooler and thermal grease are in working order.

9) Soak test the machine. Just leave it running for a full 24 hours but turn off display power management and only engage the screen saver. For this test, when the screen saver kicks in, you can turn the display off manually. You want power management disabled (DPMS) because you don't want the video card to go to sleep. You should know enough by this stage if you've got deeper problems because the soak test fails.

10) Take it to a computer repair technician, and prepare for the worst.

I've given you absolutely everything I would do, short of writing an Epic of Gilgamesh. Anyway, post the outputs I've asked for and we'll look them to see if anything reveals more clues about where to look next.

[Detroitbecomemonke]

1) Post the output of this command: dmesg --level=err.

Code: Select all

[    9.274845] bcma: Unsupported SPROM revision: 11
[    9.274855] bcma-pci-bridge 0000:02:00.0: bus0: No SPROM available
[    9.310354] bcma-pci-bridge 0000:09:00.0: bus1: No SPROM available
[   11.812014] sd 6:0:0:0: [sdd] No Caching mode page found
[   11.813001] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[   23.948934] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   23.950449] EDAC sbridge: Couldn't find mci handler
[   23.951368] EDAC sbridge: Failed to register device with error -19.
[   23.990720] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   23.992203] EDAC sbridge: Couldn't find mci handler
[   23.993097] EDAC sbridge: Failed to register device with error -19.
[   24.026620] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   24.028113] EDAC sbridge: Couldn't find mci handler
[   24.029008] EDAC sbridge: Failed to register device with error -19.
[   24.094878] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   24.096362] EDAC sbridge: Couldn't find mci handler
[   24.097253] EDAC sbridge: Failed to register device with error -19.
[   24.142730] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   24.144226] EDAC sbridge: Couldn't find mci handler
[   24.145124] EDAC sbridge: Failed to register device with error -19.
[   24.182797] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   24.184283] EDAC sbridge: Couldn't find mci handler
[   24.185193] EDAC sbridge: Failed to register device with error -19.
[   24.246822] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   24.292052] EDAC sbridge: Couldn't find mci handler
[   24.312465] EDAC sbridge: Failed to register device with error -19.
[   24.331925] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), Revision 1)
[   24.368391] b43-phy1 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), Revision 1)
[   24.426972] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   24.458454] EDAC sbridge: Couldn't find mci handler
[   24.458458] EDAC sbridge: Failed to register device with error -19.
[   24.631856] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   24.662167] EDAC sbridge: Couldn't find mci handler
[   24.677289] EDAC sbridge: Failed to register device with error -19.
[   24.770710] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   24.803379] EDAC sbridge: Couldn't find mci handler
[   24.819056] EDAC sbridge: Failed to register device with error -19.
[   24.894540] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   24.925958] EDAC sbridge: Couldn't find mci handler
[   24.941157] EDAC sbridge: Failed to register device with error -19.
[   25.002806] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
[   25.034025] EDAC sbridge: Couldn't find mci handler
[   25.049176] EDAC sbridge: Failed to register device with error -19.

I'll write more as I get it all done

[Detroitbecomemonke]

HUGE UPDATE

I managed to get Valheim to run, but as I was monitoring my GPU temps, they rose from 51C to 89C in a matter of seconds. I turned off the program, and now I'm going to attempt to clean off and apply new thermal paste to the graphics card to see if I can bring this old beast back from the dead. After doing this I'll attempt to check the next steps.

[Detroitbecomemonke]

SOLVED

I'm not sure if this was the only issue, but Valheim now works without issue. The hard reset issue is gone after applying new thermal paste to the GPU.