Random Crash CPU decoding architectural errors

[jeremyy44]

Hi,

So recently I have been getting random crashes out of nowhere.
They happen at random without anything that I can notice being related.
Im using rasdaemon to log the error since im new to looking through log files for errors and im not sure which file to look at exactly.
The error that I get in rasdaemon logs is

Family 6 Model 9e CPU: only decoding architectural errors

And its alway the same one before any crashes. A crash is also always followed by a second crash for some reason.

Id be glad to include any log file. Im just not sure shich one to include

Im running Kubuntu 21.04
I have a intel cpu (i5-9600k)

 

[KGIII]

Hmm...

I'd suggest installing 'ksystemlog' and using that to go through your logs to spot errors. See this link:

How To: Graphically Check Your Logs For Errors With 'KSystemLog' • Linux Tips

Today's article is going to be about one of my favorite tools for checking the various system logs, KSystemLog. Easily check your error logs.

linux-tips.us

 

[jeremyy44]

Hmm...

I'd suggest installing 'ksystemlog' and using that to go through your logs to spot errors. See this link:

How To: Graphically Check Your Logs For Errors With 'KSystemLog' • Linux Tips

Today's article is going to be about one of my favorite tools for checking the various system logs, KSystemLog. Easily check your error logs.

linux-tips.us

Thanks!

Ill look into it and wait for another crash to then look at the logs through there.

 

[KGIII]

You can usually then search those errors and find fixes. Or, frequently can... "Usually" might be a little strong. You'll see, it won't hurt anything - if nothing else. It can helpfully color-code them in order of severity.

If you catch the errors, and can't find anything about it, feel free to ask away.

 

[jeremyy44]

You can usually then search those errors and find fixes. Or, frequently can... "Usually" might be a little strong. You'll see, it won't hurt anything - if nothing else. It can helpfully color-code them in order of severity.

If you catch the errors, and can't find anything about it, feel free to ask away.

Ill keep a eye open for anything that pops up int it, it does seem like a very user friendly way to look through my logs.

Thanks a lot btw i wont!

 

[Fanboi]

It could be your memory, too:

Try testing it by downloading memtest here: https://www.memtest86.com/
and burning it to a flshdrive.

Could also be thermals. The memtest will show you these stats so two birds with one stone there.

Other than that, CPU socket? That gen, the 9xxx series (and newer?) intel chips have ghastly contects. Not proper pins. I haven't built in ages and when I did an intel build ~3 years back, I was like, "WTF is this? Where are the pins? Why is there no baggy with thermal paste? What is that square on the chip, thermal paste replacement? WTF do I do? Ah, fckit, YOLO it." Worked fine, but just saying. I'm much happier since I got my Ryzen. Good 'ol days chip.
Anyhoo, try reseating the CPU if the memory test turns up nothing. Make sure there's nothing loose and make sure the contacts are clean.

Good luck.

 

[jeremyy44]

It could be your memory, too:

Try testing it by downloading memtest here: https://www.memtest86.com/
and burning it to a flshdrive.

Could also be thermals. The memtest will show you these stats so two birds with one stone there.

Other than that, CPU socket? That gen, the 9xxx series (and newer?) intel chips have ghastly contects. Not proper pins. I haven't built in ages and when I did an intel build ~3 years back, I was like, "WTF is this? Where are the pins? Why is there no baggy with thermal paste? What is that square on the chip, thermal paste replacement? WTF do I do? Ah, fckit, YOLO it." Worked fine, but just saying. I'm much happier since I got my Ryzen. Good 'ol days chip.
Anyhoo, try reseating the CPU if the memory test turns up nothing. Make sure there's nothing loose and make sure the contacts are clean.

Good luck.

I did try memtest86 before posting and it did a full pass without any error tho I could try letting it run longer also changed thermal paste and reseated my cpu since I cleaned my pc completely last week I used mx4.

So yeah I could try a longer memtest run like 3 or 4 full pass but its just long to wait for it to finish.
I did that because I had some weird thermal throttling issue last week where I was thermal throttling after 5sc of stress with s-tui under linux i was going over 95c but was completely fine under windows running cinabench r20 for 10min never going below 85c and im overclocked to 5GHz so idk if its related or not just but my pc has been acting weird these past few weeks.

Anyway yeah ill try a longer memtest run letting finish completely without interupting after 1 pass this time.

 

[Fanboi]

I did try memtest86 before posting and it did a full pass without any error tho I could try letting it run longer also changed thermal paste and reseated my cpu since I cleaned my pc completely last week I used mx4.

So yeah I could try a longer memtest run like 3 or 4 full pass but its just long to wait for it to finish.
I did that because I had some weird thermal throttling issue last week where I was thermal throttling after 5sc of stress with s-tui under linux i was going over 95c but was completely fine under windows running cinabench r20 for 10min never going below 85c and im overclocked to 5GHz so idk if its related or not just but my pc has been acting weird these past few weeks.

Anyway yeah ill try a longer memtest run letting finish completely without interupting after 1 pass this time.

Best way to run memtest is overnight in another room, lol. But, yeah, probably won't make a difference if there's no fail after 1 full pass. The only thing you may learn is if the memory controller on the chip is acting up or if the RAM overheats given enough beating.
Your temps worry me a little. 95C is pushing it and I would advise against letting it reach beyond the 80-somethings. So, maybe drop the clock or consider better cooling (whether it solve this problem or not, it'll prolong the CPU's life). It's not just the CPU cooler, it's case airflow, too. Air exhausted for a video card rises, as hot air does, and hits the CPU. I think this is where air coolers have a slight advantage. So configuring your case fans is important. You may want to direct a push flow between the video card and CPU. Using a water cooler on the GPU also helps since it reduces the hot air rising (though if you do this, consult somewhere like r/buildapc for safety). If you have some spare headers, you can always add fans, even if your case doesn't have space (drill holes, use brackets, etc). Of course airflow in general is less effective when ambient temps are against you.
Your Linux freezing may well be related to the fact that Cinebench is not running you beyond your 85C but Linux is shooting you to 95C. That said, it is important to note that CPU temps are not always reported correctly and there's a known disparity between reading on Linux and Windows (I think it's to do with using difference sources, e.g. the BIOS vs the CPU reporting). So you may be rurnning the same on both OSes under load. I'd also try running Linux live from a flashdrive, without mounting your HDD/SSD. Another long shot may be to think about your motherboard as you may be experiencing voltage irregularities. Of course, you may wanna check background processes, too.
Other than that, make sure iucode is up to date and try to reproduce the freeze compiling Chromium or Firefox and keep an eye on the sensors as much as possible.

 

[jeremyy44]

Best way to run memtest is overnight in another room, lol. But, yeah, probably won't make a difference if there's no fail after 1 full pass. The only thing you may learn is if the memory controller on the chip is acting up or if the RAM overheats given enough beating.
Your temps worry me a little. 95C is pushing it and I would advise against letting it reach beyond the 80-somethings. So, maybe drop the clock or consider better cooling (whether it solve this problem or not, it'll prolong the CPU's life). It's not just the CPU cooler, it's case airflow, too. Air exhausted for a video card rises, as hot air does, and hits the CPU. I think this is where air coolers have a slight advantage. So configuring your case fans is important. You may want to direct a push flow between the video card and CPU. Using a water cooler on the GPU also helps since it reduces the hot air rising (though if you do this, consult somewhere like r/buildapc for safety). If you have some spare headers, you can always add fans, even if your case doesn't have space (drill holes, use brackets, etc). Of course airflow in general is less effective when ambient temps are against you.
Your Linux freezing may well be related to the fact that Cinebench is not running you beyond your 85C but Linux is shooting you to 95C. That said, it is important to note that CPU temps are not always reported correctly and there's a known disparity between reading on Linux and Windows (I think it's to do with using difference sources, e.g. the BIOS vs the CPU reporting). So you may be rurnning the same on both OSes under load. I'd also try running Linux live from a flashdrive, without mounting your HDD/SSD. Another long shot may be to think about your motherboard as you may be experiencing voltage irregularities. Of course, you may wanna check background processes, too.
Other than that, make sure iucode is up to date and try to reproduce the freeze compiling Chromium or Firefox and keep an eye on the sensors as much as possible.

Yeah I tought maybe linux wasnt displaying my temp right but my freq does follow the same curve as my temp so as soon as my temp in s-tui hits 90-95+ my freq drops from 5GHz to 4.1Ghz so that why I think it might be okay and I do have a AIO which is why idk temp dosnt seem to be the problem to me because I do get crashes even when im literaly just watching youtube but I havnt had a crash again yet so im still looking foward to it (never tought id say that) to look at my logg. And at idle im at 30c so thats why its rly weird for a crash to happen randomly without any stress. And I sadly donmt have any spare fans that I want to use the only one I have is a nzxt one that came with my AIO but its so loud the bearing are making so much noise as soon as I start using it. I will try a live usb tho I hadnt really tought of that. So ill keep updated when I get another crash because I rly dont know whats been happening but eh im sure its gonna heppen again so well see.

 

[jeremyy44]

Best way to run memtest is overnight in another room, lol. But, yeah, probably won't make a difference if there's no fail after 1 full pass. The only thing you may learn is if the memory controller on the chip is acting up or if the RAM overheats given enough beating.
Your temps worry me a little. 95C is pushing it and I would advise against letting it reach beyond the 80-somethings. So, maybe drop the clock or consider better cooling (whether it solve this problem or not, it'll prolong the CPU's life). It's not just the CPU cooler, it's case airflow, too. Air exhausted for a video card rises, as hot air does, and hits the CPU. I think this is where air coolers have a slight advantage. So configuring your case fans is important. You may want to direct a push flow between the video card and CPU. Using a water cooler on the GPU also helps since it reduces the hot air rising (though if you do this, consult somewhere like r/buildapc for safety). If you have some spare headers, you can always add fans, even if your case doesn't have space (drill holes, use brackets, etc). Of course airflow in general is less effective when ambient temps are against you.
Your Linux freezing may well be related to the fact that Cinebench is not running you beyond your 85C but Linux is shooting you to 95C. That said, it is important to note that CPU temps are not always reported correctly and there's a known disparity between reading on Linux and Windows (I think it's to do with using difference sources, e.g. the BIOS vs the CPU reporting). So you may be rurnning the same on both OSes under load. I'd also try running Linux live from a flashdrive, without mounting your HDD/SSD. Another long shot may be to think about your motherboard as you may be experiencing voltage irregularities. Of course, you may wanna check background processes, too.
Other than that, make sure iucode is up to date and try to reproduce the freeze compiling Chromium or Firefox and keep an eye on the sensors as much as possible.

Actually one thing I just realized since I have a kraken X as a AIO and NZXT dosnt have a official linux software for it im using liquidctl and GKraken to control it but I forgot that my temp curve dosnt actually work but I just tested with my fans at 100% but s-tui still says that im going to 90-95 in like 5sc then drops my freq directly so idk anymore what to think lol

 

[KGIII]

I do get crashes even when im literaly just watching youtube

Hmm... Which browser are you using when that happens?

 

[jeremyy44]

Hmm... Which browser are you using when that happens?

Chrome but as much as it can happen when watching videos it can happen when editing text or even gaming its pretty much when doing anything

 

[KGIII]

Oh...

LOL Try this:

Go to settings > advanced > somewhere in there > disable "Hardware Acceleration". It's a long story, but it may solve your freezing/crashing errors. Don't forget to restart Chrome after changing the setting.

 

[jeremyy44]

Oh...

LOL Try this:

Go to settings > advanced > somewhere in there > disable "Hardware Acceleration". It's a long story, but it may solve your freezing/crashing errors. Don't forget to restart Chrome after changing the setting.

Alright thx just did ill see if anything new comes up still havnt had another crash ocure juste yet

 

[KGIII]

Alright thx just did ill see if anything new comes up still havnt had another crash ocure juste yet

Odds are pretty good that your problem is now resolved.

See, Hardware Acceleration doesn't work in Linux and Google has no plans to make it work. However, it's there and enabled by default. Most of the time, it doesn't do any harm - but sometimes, on just the right system, it causes crashes when the browser is open and doing various tasks.

The crashes all seem random and unsolvable, until we find out Chrome is involved. Once Chrome is involved, that's usually the solution.

This is also true for Chromium, Brave, Opera, or any other browser built on Chromium. Just disable HA to avoid any potential risks.

 

[jeremyy44]

Odds are pretty good that your problem is now resolved.

See, Hardware Acceleration doesn't work in Linux and Google has no plans to make it work. However, it's there and enabled by default. Most of the time, it doesn't do any harm - but sometimes, on just the right system, it causes crashes when the browser is open and doing various tasks.

The crashes all seem random and unsolvable, until we find out Chrome is involved. Once Chrome is involved, that's usually the solution.

This is also true for Chromium, Brave, Opera, or any other browser built on Chromium. Just disable HA to avoid any potential risks.

Nice good to know.

And yeah I hope it is but as its going rn it all seems fine but then again I dont want to eat my words since I still have the thermal throthling issue to figure out.

But hey thanks a lot for all the help btw!

 

[KGIII]

Yeah, wait a couple of days and then celebrate.

 

[jeremyy44]

Well f**k cant celebrate just yet I had another crash happen again. I was just watching a video.
In journal ctl I get the same cpu decoding architectural error and in KSystemlog I see this. (crash.txt)
But idk if these are the logs before or after the crash.
Also attached my syslog tho idk if it could contain anything again I tried looking through it but it didnt make much sens to me

 

[KGIII]

Well, there goes that optimism. Still, leave HA turned off.

I'm flipping through your error logs as I type this... I'm seeing a lot of systemd errors, a bunch of theme errors, some bluetooth errors, and more.

Let's see what happens if we get some more eyes on your error logs. Be patient and someone may spot something I'm missing.

 

[jeremyy44]

Well, there goes that optimism. Still, leave HA turned off.

I'm flipping through your error logs as I type this... I'm seeing a lot of systemd errors, a bunch of theme errors, some bluetooth errors, and more.

Let's see what happens if we get some more eyes on your error logs. Be patient and someone may spot something I'm missing.

Alright thanks a lot again ill see on the next crash if I get some repeated error that gets logged