Multiple random crashes for the past week

[Chris]

For the past week or so, I have started to have random crashes. Somtimes it is just an app that crashes, sometimes the machine freezes up completely and sometimes it just reboots.

I ran a memory test for about 8 hours over the weekend and it found no issues. Looking through some of the crash dmesg files I see:

202009290318/dmesg.202009290318:1186:[ 5527.345666] BUG: unable to handle kernel paging request at ffffffffab1bd511
202009291228/dmesg.202009291228:1194:[12423.898689] BUG: unable to handle kernel paging request at ffffffffffffff8e
202009301804/dmesg.202009301804:1386:[31355.601321] BUG: unable to handle kernel paging request at ffffffffb2cbb6cf
202010011046/dmesg.202010011046:1200:[ 3081.774984] BUG: unable to handle kernel paging request at ffffa0bd8f625a50

Which still leads to think a memory issue. Going to run a longer memtest. I am usually pretty good and figuring out what is going on but this time I need some help to make sure I am on the right track or tell me I am completely wrong.

Thanks in advance.

ProblemType: KernelCrash
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-118-generic 4.15.0-118.119
ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
Uname: Linux 4.15.0-118-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chris 3921 F.... pulseaudio
 /dev/snd/controlC1: chris 3921 F.... pulseaudio
Date: Tue Sep 29 16:09:48 2020
InstallationDate: Installed on 2019-01-07 (632 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: MSI MS-7693
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=65a42e57-56c3-47ce-beb9-73c0f182e1d4 ro sbcore.autosuspend=-1 amd_iommu=on iommu=pt crashkernel=512M-:192M
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-118-generic N/A
 linux-backports-modules-4.15.0-118-generic N/A
 linux-firmware 1.173.19
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 970A-G46 (MS-7693)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd10/08/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7693
dmi.product.version: 2.0
dmi.sys.vendor: MSI

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1898091/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Mauricio Faria de Oliveira (mfo)]

Hi Chris,

Thanks for reporting this bug.

The faulting memory addresses alone are not sufficient to have an idea of what is going on.

Also, they might not necessarily indicate a memory problem, but incorrect code in whatever part of the kernel, targeting a memory address that is incorrectly calculated or no longer valid.

Could you please upload the crash dmesg files?
They should contain stack traces that provide more context about the faulty memory address.

[Gibby (gibby)]

Mauricio,

Thanks for the quick response. Attached is a zip of the files requested.

I have tried going back to older kernels that were already installed, and the issue still occurs.