I'm trying to track down the cause of a recurring crash. I'm 99.9% sure it has to do with my GPU.
When my system locks up, a GIGANTIC chunk is added to my /var/log/systemlog file.
I have tracked when events happen (as best I can) with pen and paper, so I know the approximate time of the errors.
I'm not asking for my hand to be held (but I'm a babe in the woods, so maybe I am) so what command do I use to go to a specific time in the history of and EVENT or CRASH? I believe there exists GUI utilities for this, but I want to remain in command line a terminal world.
I recently built this PC from scratch specifically to get back into the world of LINUX so some of my hardware research may have been lacking prudence.

Thank you!

What GPU is this. What is kernel version, what distro are you using.

Thanks for the reply. I am new to the forum as well, so I hope this is the correct way to replay.
I really appreciate the help. Again, I don't want to be a pain. I need to hone my search skills so I
won't be so bothersome.

Cheers,
bluecrab

NAME="Linux Mint"
VERSION="20.1 (Ulyssa)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 20.1"
VERSION_ID="20.1"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=ulyssa
UBUNTU_CODENAME=focal

GPU is VisionTek Radeon HD 7750 EYE 4

Any time stamps? Go to the time it started the data dumps.

I've copied to Emacs very, very large sections of the systemlog file for comparison. I'll just have to ply through it.

To be honest, I only posted this question because, as a new to LinuxQuestions.org member, it was offered/suggested.
I feel like what I'm hunting is so basic that:

1) It probably annoys most folks in this forum
2) As I am trying to learn, hunting it out myself will probably enable me to learn better.

It's just been way too long since I've been able to enjoy Mr. Torvald's gift to the world that I'm finding myself quite rusty.

Hey, at least it's not 1996 and I need to get a printer to work. haha

Thanks for your patience, folks.

bluecrab

$ cat /etc/os-release
NAME="Linux Mint"
VERSION="20.1 (Ulyssa)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 20.1"
VERSION_ID="20.1"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=ulyssa
UBUNTU_CODENAME=focal

GPU:
$ lspci | grep VGA
2d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]

I'm thinking this is where the trouble began. I'll post the first couple pages. Then, there's many, many more that make no sense to my dinosaur brain that followed.

Feb 9 02:16:56 AtlanticVictor systemd[1]: packagekit.service: Succeeded.
Feb 9 02:17:01 AtlanticVictor CRON[3667]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 9 02:41:36 AtlanticVictor systemd-modules-load[429]: Inserted module 'lp'
Feb 9 02:41:36 AtlanticVictor systemd-modules-load[429]: Inserted module 'ppdev'
Feb 9 02:41:36 AtlanticVictor systemd-modules-load[429]: Inserted module 'parport_pc'
Feb 9 02:41:36 AtlanticVictor systemd-sysctl[455]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists).
Feb 9 02:41:36 AtlanticVictor systemd-sysctl[455]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists).
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Flush Journal to Persistent Storage...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Started udev Kernel Device Manager.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Finished udev Coldplug all Devices.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Helper to synchronize boot up for ifupdown...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Show Plymouth Boot Screen...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Finished Helper to synchronize boot up for ifupdown.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Activated swap /swapfile.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Reached target Swap.
Feb 9 02:41:36 AtlanticVictor systemd[1]: plymouth-start.service: Succeeded.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Started Show Plymouth Boot Screen.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Reached target Local Encrypted Volumes.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Finished Flush Journal to Persistent Storage.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Reached target Local File Systems (Pre).
Feb 9 02:41:36 AtlanticVictor systemd-udevd[470]: Using default interface naming scheme 'v245'.
Feb 9 02:41:36 AtlanticVictor systemd-udevd[470]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 9 02:41:36 AtlanticVictor mtp-probe: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.3/usb3/3-5"
Feb 9 02:41:36 AtlanticVictor mtp-probe: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-2"
Feb 9 02:41:36 AtlanticVictor mtp-probe: bus: 1, device: 2 was not an MTP device
Feb 9 02:41:36 AtlanticVictor mtp-probe: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.3/usb4/4-4"
Feb 9 02:41:36 AtlanticVictor mtp-probe: bus: 3, device: 2 was not an MTP device
Feb 9 02:41:36 AtlanticVictor mtp-probe: bus: 4, device: 2 was not an MTP device
Feb 9 02:41:36 AtlanticVictor systemd[1]: Found device Samsung SSD 970 EVO Plus 1TB EFI\x20System\x20Partition.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting File System Check on /dev/disk/by-uuid/89F1-2F2C...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Started File System Check Daemon to report status.
Feb 9 02:41:36 AtlanticVictor mtp-probe: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:08.1/0000:2f:00.3/usb5/5-1"
Feb 9 02:41:36 AtlanticVictor mtp-probe: bus: 5, device: 2 was not an MTP device
Feb 9 02:41:36 AtlanticVictor systemd-fsck[528]: fsck.fat 4.1 (2017-01-24)
Feb 9 02:41:36 AtlanticVictor systemd-fsck[528]: 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Feb 9 02:41:36 AtlanticVictor systemd-fsck[528]: Automatically removing dirty bit.
Feb 9 02:41:36 AtlanticVictor systemd-fsck[528]: Performing changes.
Feb 9 02:41:36 AtlanticVictor systemd-fsck[528]: /dev/nvme0n1p1: 11 files, 1997/130812 clusters
Feb 9 02:41:36 AtlanticVictor systemd[1]: Finished File System Check on /dev/disk/by-uuid/89F1-2F2C.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Mounting /boot/efi...
Feb 9 02:41:36 AtlanticVictor systemd-udevd[470]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Load/Save RF Kill Switch Status...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Mounted /boot/efi.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Reached target Local File Systems.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Load AppArmor profiles...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Set console font and keymap...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Clean up any mess left by 0dns-up...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Create final runtime dir for shutdown pivot root...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Create Volatile Files and Directories...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Finished Create final runtime dir for shutdown pivot root.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Finished Set console font and keymap.
Feb 9 02:41:36 AtlanticVictor apparmor.systemd[587]: Restarting AppArmor
Feb 9 02:41:36 AtlanticVictor apparmor.systemd[587]: Reloading AppArmor profiles
Feb 9 02:41:36 AtlanticVictor systemd[1]: dns-clean.service: Succeeded.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Finished Clean up any mess left by 0dns-up.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Started Nameserver information manager.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Reached target Network (Pre).
Feb 9 02:41:36 AtlanticVictor systemd[1]: plymouth-read-write.service: Succeeded.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Finished Tell Plymouth To Write Out Runtime Data.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Received SIGRTMIN+20 from PID 337 (plymouthd).
Feb 9 02:41:36 AtlanticVictor systemd[1]: Finished Create Volatile Files and Directories.
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Network Name Resolution...
Feb 9 02:41:36 AtlanticVictor systemd[1]: Starting Network Time Synchronization...
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] Linux version 5.4.0-65-generic (buildd@lcy01-amd64-018) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 (Ubuntu 5.4.0-65.73-generic 5.4.78)
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=35e0917f-fdb1-42bf-9246-8f430eb82c33 ro quiet splash
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] KERNEL supported cpus:
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] Intel GenuineIntel
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] AMD AuthenticAMD
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] Hygon HygonGenuine
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] Centaur CentaurHauls
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] zhaoxin Shanghai
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-provided physical RAM map:
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000009d81fff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x0000000009d82000-0x0000000009ffffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x000000000a200000-0x000000000a20ffff] ACPI NVS
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x000000000a210000-0x00000000dad4bfff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000dad4c000-0x00000000db0a8fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000db0a9000-0x00000000db10cfff] ACPI data
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000db10d000-0x00000000dcc0cfff] ACPI NVS
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000dcc0d000-0x00000000ddbfefff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000ddbff000-0x00000000deffffff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fd400000-0x00000000fd5fffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000081f37ffff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] BIOS-e820: [mem 0x000000081f380000-0x000000081fffffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] NX (Execute Disable) protection: active
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] e820: update [mem 0xd6007018-0xd6016057] usable ==> usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] e820: update [mem 0xd6007018-0xd6016057] usable ==> usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] e820: update [mem 0xd5fe8018-0xd6006657] usable ==> usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] e820: update [mem 0xd5fe8018-0xd6006657] usable ==> usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] extended physical RAM map:
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x0000000009d81fff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x0000000009d82000-0x0000000009ffffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x000000000a000000-0x000000000a1fffff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x000000000a200000-0x000000000a20ffff] ACPI NVS
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x000000000a210000-0x00000000d5fe8017] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000d5fe8018-0x00000000d6006657] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000d6006658-0x00000000d6007017] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000d6007018-0x00000000d6016057] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000d6016058-0x00000000dad4bfff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000dad4c000-0x00000000db0a8fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000db0a9000-0x00000000db10cfff] ACPI data
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000db10d000-0x00000000dcc0cfff] ACPI NVS
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000dcc0d000-0x00000000ddbfefff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000ddbff000-0x00000000deffffff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000df000000-0x00000000dfffffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000fd400000-0x00000000fd5fffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000081f37ffff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] reserve setup_data: [mem 0x000000081f380000-0x000000081fffffff] reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] efi: EFI v2.70 by American Megatrends
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] efi: ACPI=0xdcbf4000 ACPI 2.0=0xdcbf4014 SMBIOS=0xdda0d000 MEMATTR=0xd62dd698
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] secureboot: Secure boot disabled
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] SMBIOS 2.8 present.
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] DMI: Micro-Star International Co., Ltd. MS-7B93/MPG X570 GAMING PRO CARBON WIFI (MS-7B93), BIOS 1.90 09/07/2020
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] tsc: Fast TSC calibration using PIT
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000000] tsc: Detected 4199.976 MHz processor
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000850] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000851] e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000855] last_pfn = 0x81f380 max_arch_pfn = 0x400000000
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000858] MTRR default type: uncachable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000858] MTRR fixed ranges enabled:
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000859] 00000-9FFFF write-back
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000859] A0000-BFFFF write-through
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000860] C0000-FFFFF write-protect
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000860] MTRR variable ranges enabled:
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000861] 0 base 000000000000 mask FFFF80000000 write-back
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000862] 1 base 000080000000 mask FFFFC0000000 write-back
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000862] 2 base 0000C0000000 mask FFFFE0000000 write-back
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000863] 3 base 0000DD300000 mask FFFFFFFF0000 uncachable
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000863] 4 disabled
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000863] 5 disabled
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000863] 6 disabled
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000864] 7 disabled
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.000864] TOM2: 0000000820000000 aka 33280M
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.001440] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.001502] total RAM covered: 3583M
Feb 9 02:41:36 AtlanticVictor kernel: [ 0.001748] Found optimal setting for mtrr clean up

I'm going to tell you the practical side of this now. GPU locking up the computer like this is too often hardware issue, in a few cases driver/firmware issue. You could try and run from some liveCD and see if the problem persists, just to make sure it is not some corrupted file in your current installation causing this. Practically every distro has pastebin utility nowadays (pastebinit, wgetpaste, fpaste), you can use the one which comes with Mint and put the whole log into pastebin if you wish. But don't get your hopes high.

1 members found this post helpful.

Thank you Emerson!
I will give that a try, and no, not get my hopes up.
On another note, I feel like there's a better way to post multiple lines of code like I did above. Perhaps in a scrollable box?
I'm trying to not be rude here.

Thanks again.

bluecrab

I would think if you are getting tons of output, most of it will simply be repeats - might be helpful, might not. Start with the basics - this will list the last 30 lines of the messages from the previous boot.If you use [code]...[/code] for output (and code as I did), layout is maintained - and it's scrollable in need.

Edit: if that command doesn't work, may mean the distro doesn't use persistent systemd journal. That will make things more round-about but still do-able.

1 members found this post helpful.

Not at all; helping someone to help themselves is exactly why this forum is here. It's 1000% better than a lot of others who would just post their entire syslog and say "someone look at this and tell me what the error is".
Exactly
Printing has been the bane of my existence since the early 1980's, and continues to be a pain.

That said, I'll offer a suggestion, which would be to run:
(for example), to find the first occurrence of that date-string. That will give you the line number of the log file, and a point where you can start looking for the 'meat' of what's there. So if you know the system crashed at 2:42 on February 9th, that'll find things starting at 2:40. This:
....will take that starting chunk and shovel it out to a much smaller file, making it easier to look through.

1 members found this post helpful.

You can try
HTH

1 members found this post helpful.