PC reboots. Hardware errors (NOW: GPU problems)

Ploppz · 2021-11-08 16:29:36

I have to post this fast before it happens again. Last time I only had 2 minutes between crashes.

Nov 08 17:25:35 nadir kernel: ACPI: \_PR_.C00B: Found 2 idle states
Nov 08 17:25:35 nadir kernel: ACPI: \_PR_.C00D: Found 2 idle states
Nov 08 17:25:35 nadir kernel: ACPI: \_PR_.C00F: Found 2 idle states
Nov 08 17:25:35 nadir kernel: ACPI: \_PR_.C011: Found 2 idle states
Nov 08 17:25:35 nadir kernel: ACPI: \_PR_.C013: Found 2 idle states
Nov 08 17:25:35 nadir kernel: ACPI: \_PR_.C015: Found 2 idle states
Nov 08 17:25:35 nadir kernel: ACPI: \_PR_.C017: Found 2 idle states
Nov 08 17:25:35 nadir kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov 08 17:25:35 nadir kernel: 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov 08 17:25:35 nadir kernel: Non-volatile memory driver v1.3
Nov 08 17:25:35 nadir kernel: AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
Nov 08 17:25:35 nadir kernel: ahci 0000:03:00.1: version 3.0
Nov 08 17:25:35 nadir kernel: ahci 0000:03:00.1: SSS flag set, parallel bus scan disabled
Nov 08 17:25:35 nadir kernel: ahci 0000:03:00.1: AHCI 0001.0301 32 slots 8 ports 6 Gbps 0x33 impl SATA mode
Nov 08 17:25:35 nadir kernel: ahci 0000:03:00.1: flags: 64bit ncq sntf stag pm led clo only pmp pio slum part sxs deso sadm sds apst 
Nov 08 17:25:35 nadir kernel: scsi host0: ahci
Nov 08 17:25:35 nadir kernel: scsi host1: ahci
Nov 08 17:25:35 nadir kernel: scsi host2: ahci
Nov 08 17:25:35 nadir kernel: scsi host3: ahci
Nov 08 17:25:35 nadir kernel: scsi host4: ahci
Nov 08 17:25:35 nadir kernel: scsi host5: ahci
Nov 08 17:25:35 nadir kernel: scsi host6: ahci
Nov 08 17:25:35 nadir kernel: scsi host7: ahci
Nov 08 17:25:35 nadir kernel: ata1: SATA max UDMA/133 abar m131072@0xfcc80000 port 0xfcc80100 irq 39
Nov 08 17:25:35 nadir kernel: ata2: SATA max UDMA/133 abar m131072@0xfcc80000 port 0xfcc80180 irq 39
Nov 08 17:25:35 nadir kernel: ata3: DUMMY
Nov 08 17:25:35 nadir kernel: ata4: DUMMY
Nov 08 17:25:35 nadir kernel: ata5: SATA max UDMA/133 abar m131072@0xfcc80000 port 0xfcc80300 irq 39
Nov 08 17:25:35 nadir kernel: ata6: SATA max UDMA/133 abar m131072@0xfcc80000 port 0xfcc80380 irq 39
Nov 08 17:25:35 nadir kernel: ata7: DUMMY
Nov 08 17:25:35 nadir kernel: ata8: DUMMY
Nov 08 17:25:35 nadir kernel: ahci 0000:30:00.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
Nov 08 17:25:35 nadir kernel: ahci 0000:30:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part 
Nov 08 17:25:35 nadir kernel: scsi host8: ahci
Nov 08 17:25:35 nadir kernel: ata9: SATA max UDMA/133 abar m2048@0xfce00000 port 0xfce00100 irq 41
Nov 08 17:25:35 nadir kernel: ahci 0000:31:00.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
Nov 08 17:25:35 nadir kernel: ahci 0000:31:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part 
Nov 08 17:25:35 nadir kernel: scsi host9: ahci
Nov 08 17:25:35 nadir kernel: ata10: SATA max UDMA/133 abar m2048@0xfcd00000 port 0xfcd00100 irq 43
Nov 08 17:25:35 nadir kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov 08 17:25:35 nadir kernel: ehci-pci: EHCI PCI platform driver
Nov 08 17:25:35 nadir kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov 08 17:25:35 nadir kernel: ohci-pci: OHCI PCI platform driver
Nov 08 17:25:35 nadir kernel: uhci_hcd: USB Universal Host Controller Interface driver
Nov 08 17:25:35 nadir kernel: usbcore: registered new interface driver usbserial_generic
Nov 08 17:25:35 nadir kernel: usbserial: USB Serial support registered for generic
Nov 08 17:25:35 nadir kernel: rtc_cmos 00:02: RTC can wake from S4
Nov 08 17:25:35 nadir kernel: rtc_cmos 00:02: registered as rtc0
Nov 08 17:25:35 nadir kernel: rtc_cmos 00:02: setting system clock to 2021-11-08T16:25:31 UTC (1636388731)
Nov 08 17:25:35 nadir kernel: rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov 08 17:25:35 nadir kernel: ledtrig-cpu: registered to indicate activity on CPUs
Nov 08 17:25:35 nadir kernel: hid: raw HID events driver (C) Jiri Kosina
Nov 08 17:25:35 nadir kernel: drop_monitor: Initializing network drop monitor service
Nov 08 17:25:35 nadir kernel: Initializing XFRM netlink socket
Nov 08 17:25:35 nadir kernel: NET: Registered PF_INET6 protocol family
Nov 08 17:25:35 nadir kernel: Freeing initrd memory: 8036K
Nov 08 17:25:35 nadir kernel: Segment Routing with IPv6
Nov 08 17:25:35 nadir kernel: RPL Segment Routing with IPv6
Nov 08 17:25:35 nadir kernel: NET: Registered PF_PACKET protocol family
Nov 08 17:25:35 nadir kernel: microcode: CPU0: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU1: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU2: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU3: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU4: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU5: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU6: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU7: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU8: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU9: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU10: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU11: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU12: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU13: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU14: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU15: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU16: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU17: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU18: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU19: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU20: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU21: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU22: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: CPU23: patch_level=0x08701021
Nov 08 17:25:35 nadir kernel: microcode: Microcode Update Driver: v2.2.
Nov 08 17:25:35 nadir kernel: mce: [Hardware Error]: Machine check events logged
Nov 08 17:25:35 nadir kernel: mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 5: bea0000000000108
Nov 08 17:25:35 nadir kernel: fbcon: Taking over console
Nov 08 17:25:35 nadir kernel: mce: [Hardware Error]: TSC 0 ADDR 7f365ed374e4 MISC d012000100000000 SYND 4d000000 IPID 500b000000000 
Nov 08 17:25:35 nadir kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1636388730 SOCKET 0 APIC 2 microcode 8701021
Nov 08 17:25:35 nadir kernel: Console: switching to colour frame buffer device 128x48
Nov 08 17:25:35 nadir kernel: resctrl: L3 allocation detected
Nov 08 17:25:35 nadir kernel: resctrl: L3DATA allocation detected
Nov 08 17:25:35 nadir kernel: resctrl: L3CODE allocation detected
Nov 08 17:25:35 nadir kernel: resctrl: MB allocation detected
Nov 08 17:25:35 nadir kernel: resctrl: L3 monitoring detected
Nov 08 17:25:35 nadir kernel: IPI shorthand broadcast: enabled
Nov 08 17:25:35 nadir kernel: sched_clock: Marking stable (284617577, -23329063)->(271536425, -10247911)
Nov 08 17:25:35 nadir kernel: registered taskstats version 1
Nov 08 17:25:35 nadir kernel: Loading compiled-in X.509 certificates
Nov 08 17:25:35 nadir kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 1d8db0e7a2fe4f8548eed7c91ad7c927176169f6'
Nov 08 17:25:35 nadir kernel: zswap: loaded using pool lz4/z3fold
Nov 08 17:25:35 nadir kernel: Key type ._fscrypt registered
Nov 08 17:25:35 nadir kernel: Key type .fscrypt registered
Nov 08 17:25:35 nadir kernel: Key type fscrypt-provisioning registered
Nov 08 17:25:35 nadir kernel: PM:   Magic number: 13:702:438
Nov 08 17:25:35 nadir kernel: iommu ivhd0: hash matches
Nov 08 17:25:35 nadir kernel: RAS: Correctable Errors collector initialized.
Nov 08 17:25:35 nadir kernel: ata10: SATA link down (SStatus 0 SControl 300)
Nov 08 17:25:35 nadir kernel: ata9: SATA link down (SStatus 0 SControl 300)
Nov 08 17:25:35 nadir kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 08 17:25:35 nadir kernel: ata1.00: supports DRM functions and may not be fully accessible
Nov 08 17:25:35 nadir kernel: ata1.00: disabling queued TRIM support
Nov 08 17:25:35 nadir kernel: ata1.00: ATA-11: Samsung SSD 860 EVO 1TB, RVT04B6Q, max UDMA/133
Nov 08 17:25:35 nadir kernel: ata1.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32), AA
Nov 08 17:25:35 nadir kernel: ata1.00: supports DRM functions and may not be fully accessible
Nov 08 17:25:35 nadir kernel: ata1.00: disabling queued TRIM support
Nov 08 17:25:35 nadir kernel: ata1.00: configured for UDMA/133
Nov 08 17:25:35 nadir kernel: scsi 0:0:0:0: Direct-Access     ATA      Samsung SSD 860  4B6Q PQ: 0 ANSI: 5
Nov 08 17:25:35 nadir kernel: ata1.00: Enabling discard_zeroes_data
Nov 08 17:25:35 nadir kernel: sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Nov 08 17:25:35 nadir kernel: sd 0:0:0:0: [sda] Write Protect is off
Nov 08 17:25:35 nadir kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Nov 08 17:25:35 nadir kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 08 17:25:35 nadir kernel: ata1.00: Enabling discard_zeroes_data
Nov 08 17:25:35 nadir kernel:  sda: sda1 sda2 sda3 sda4
Nov 08 17:25:35 nadir kernel: ata1.00: Enabling discard_zeroes_data
Nov 08 17:25:35 nadir kernel: sd 0:0:0:0: [sda] supports TCG Opal

So, maybe it's because I'm using a 21:9 ultrawide 1440p monitor now with an old Radeon HD 7850 card? That's at least what would have changed.
It was running fine for hours. Then it crashed. And then it subsequently crashed within 2 minutes.

Last edited by Ploppz (2021-12-28 22:51:02)

seth · 2021-11-08 16:48:59

Ryzen?
https://bugzilla.kernel.org/show_bug.cgi?id=206903

That's at least what would have changed.

The GPU or the monitor?

It was running fine for hours. Then it crashed. And then it subsequently crashed within 2 minutes.

Did the system cool down inbetween?

Ploppz · 2021-11-16 08:41:05

Sorry for the delay.

Yes I have a Ryzen 9 3900X.

I booted the PC in the morning in a cold room (17 C) and it immediately crashed again so it's not about any residual heat in the system.

>The GPU or the monitor?
The monitor.

And I was just about to say that the PC itself has been working fine before switching monitor.
However, there is ONE specific case where it would crash in a very similar way (with hardware errors in journalctl) before:
when playing League of Legends and only in ARAM mode.
But when not gaming, the PC has never crashed like this with a regular 16:9 1440p monitor.

Last edited by Ploppz (2021-11-16 08:42:04)

Ploppz · 2021-12-10 08:00:38

Update: It crashes immediately even with a normal 1440p monitor (it's newer though, maybe it's somehow different?). It starts making flickering weird graphics. Example picture: https://drive.google.com/file/d/1h6B5g1 … sp=sharing

Do I just have to get a new GPU? It's 10 years old. Or do you think it could actually be some other component like the CPU?

Last edited by Ploppz (2021-12-10 08:04:26)

seth · 2021-12-10 15:45:04

I don't see the system spontanously rebooting when the GPU drops out.
It's probably rather the board or the PSU - or it's the abrupt c-state raise, did you see https://bugzilla.kernel.org/show_bug.cgi?id=206903#c255 ?

Ploppz · 2021-12-13 08:53:47

Thanks for the link but I don't know how I can possibly issue a command on the PC as it immediately crashes when I plug in a screen.
Maybe relevant: It seems to run fine when I boot it _until_ I connect it to a screen - then I might see a couple of seconds of the login screen before it crashes.
And actually maybe forget that it reboots as the title says, because at least last time I tried, it didn't reboot but just made weird glitchy graphics.

seth · 2021-12-13 11:57:00

Does it also crash immediately if you only boot into the multi-user.target (2nd link below)
If not, you could issue the command there and then elevate into the graphical.target (to test the impact, if it works, we can focus on injecting that early)

Did you see https://wiki.archlinux.org/title/Ryzen#Random_reboots

Ploppz · 2021-12-15 20:11:08

Ok I tried that, I got as far as in the Emacs environment. I was in there for a while trying to make the correct changes. After some minutes, it starts glitching.
https://drive.google.com/file/d/1ikclJ- … sp=sharing
It alternates (per minute or so) between the above behaviour and then this: https://drive.google.com/file/d/1iojm4M … sp=sharing
In the latter case it still actually works to move cursor around and edit the text on the parts of the screen I can see. So it does seem like a purely graphical issue.

Edit: Now every time I boot it, it goes straight to glitch mode. That is, even before the grub bootloader. Like, as soon as the screen starts to get any signal from the PC.
It is almost like I have exhausted today's reservoir of graphics.

Last edited by Ploppz (2021-12-15 20:16:45)

seth · 2021-12-16 15:01:50

The first link is access restricted, the second is a signal error - you're transmitting too much data over the cable (that's also why the bigger output matters)
How's this wired specifically? HDMI?

Ploppz · 2021-12-16 15:14:05

Updated first link. https://drive.google.com/file/d/1ikclJ- … sp=sharing

HDMI yes. I tried DisplayPort and DVI both (alone), but in both cases nothing is sent to the screen at all (screen remains in stand-by).

seth · 2021-12-16 15:30:28

Try to boot "nomodeset" or enforce a lower resolution, https://raw.githubusercontent.com/torva … modedb.rst (VGA and XGA should™ be supported regardless of the actual monitor dimensions, because VESA)
It looks like the radeon card only supports HDMI 1.4, 3440x1440 should™ be possible at 24Hz and 30Hz but not at 60Hz - what does the monitor OSD say about the signal? (resolution/frequency)

Ploppz · 2021-12-16 19:20:57

Sorry for the confusion, I have actually in the last experiments been using a Quad HD screen (ASUS PA278QV) in an attempt to make it easier on the GPU so to speak. Screenshot of settings while my computer is connected with HDMI: https://drive.google.com/file/d/1jWMV_f … sp=sharing
It seems to be running only 1024x768 @ 60Hz.

I'm not sure what to make of the github page you linked. Also please note that I'm not able to do anything with the computer now since it won't even show me the bootloader.
The screen doesn't have a VGA input it seems.

seth · 2021-12-17 09:09:17

I have actually in the last experiments been using a Quad HD screen

OP wrote:

21:9 ultrawide 1440p

Quad HD *is* 3440 x 1440 …

I'm not sure what to make of the github page you linked.

it illustrates how to set framebuffer resolutions.

It seems to be running only 1024x768 @ 60Hz.

In doubt because there's no valid signal.

Also please note that I'm not able to do anything with the computer now since it won't even show me the bootloader.

Do you have other means to access the system (ssh, spare good old 1920x1080 monitor / maybe a Tv)?

Edit: at, that's a WQHD output and should™ be possible to drive at 60Hz on HDMI 1.3 and up.
Stupid question: do you have another HDMI cable?

Last edited by seth (2021-12-17 09:13:23)

Ploppz · 2021-12-18 19:27:30

I thought QHD is 2560 x 1440. That is what I meant.

In doubt because there's no valid signal.

I do believe that there was signal at that time, albeit all black.

I took some time to reply now because I went to friend with my desktop to borrow his 1920x1080 monitor.
With that monitor it was still all black (while actually getting a signal). Use HDMI. DisplayPort again gave absolutely no signal to the screen.
Then I transplanted his GPU into my desktop and then it worked just fine.
I take from this that my GPU is failing and I will buy a new one. Thanks for following me through this to make sure to rule out other possibilities.

Then it only remains to be seen whether the original "reboot" problem will come back or not once I get a new GPU.

Last edited by Ploppz (2021-12-18 19:28:28)

Ploppz · 2021-12-28 22:50:39

So I bought a GeForce GT 1030. PC now is functional and is getting a long anticipated -Syu!
However... and I'll just continue this thread with the following problem:
Keyboard input and also mouse pointer is lagging. Mouse pointer can move about fine on a clean workspace (i3), but if there is just one terminal window open it starts lagging. It's even worse with Firefox open.
The GPU is the cheapest I could find, it already cost me 200 euro, and yet it cannot even run properly with a terminal window open?!
I'm on the 2560x1440 monitor running at 60Hz with HDMI.

Last edited by Ploppz (2021-12-28 22:52:14)

seth · 2021-12-29 08:08:19

Hardly. More likely the driver setup.
Please post your xorg log and probably the output of "glxinfo -B"

Edit: please also open a new thread for this unrelated situation to keep this one cleaner for future readers, thanks.

Last edited by seth (2021-12-29 08:21:00)

Arch Linux

#1 2021-11-08 16:29:36

PC reboots. Hardware errors (NOW: GPU problems)

#2 2021-11-08 16:48:59

Re: PC reboots. Hardware errors (NOW: GPU problems)

#3 2021-11-16 08:41:05

Re: PC reboots. Hardware errors (NOW: GPU problems)

#4 2021-12-10 08:00:38

Re: PC reboots. Hardware errors (NOW: GPU problems)

#5 2021-12-10 15:45:04

Re: PC reboots. Hardware errors (NOW: GPU problems)

#6 2021-12-13 08:53:47

Re: PC reboots. Hardware errors (NOW: GPU problems)

#7 2021-12-13 11:57:00

Re: PC reboots. Hardware errors (NOW: GPU problems)

#8 2021-12-15 20:11:08

Re: PC reboots. Hardware errors (NOW: GPU problems)

#9 2021-12-16 15:01:50

Re: PC reboots. Hardware errors (NOW: GPU problems)

#10 2021-12-16 15:14:05

Re: PC reboots. Hardware errors (NOW: GPU problems)

#11 2021-12-16 15:30:28

Re: PC reboots. Hardware errors (NOW: GPU problems)

#12 2021-12-16 19:20:57

Re: PC reboots. Hardware errors (NOW: GPU problems)

#13 2021-12-17 09:09:17

Re: PC reboots. Hardware errors (NOW: GPU problems)

#14 2021-12-18 19:27:30

Re: PC reboots. Hardware errors (NOW: GPU problems)

#15 2021-12-28 22:50:39

Re: PC reboots. Hardware errors (NOW: GPU problems)

#16 2021-12-29 08:08:19

Re: PC reboots. Hardware errors (NOW: GPU problems)

Board footer