I’m getting the following messages every time I boot my Pc. It doesn’t seem to impact anything, but it worries me nonetheless. I just bought the cpu and motherboard, so I don’t think that it is actually damaged hardware. Does someone know how to fix this?
Please read this: [HowTo] Provide System Information
and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information… (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.
No, how do I do this? Simply boot into grub, go to the console and enter memtest?
Edit: Ok so I read through a view posts and it seems like I can’t really use it since I have an UEFI and can’t go into a bios mode
Sorry, the messages are shown at boot so I figured posting an image is my best option since I can’t copy-paste the messages. I would edit my question, but I can’t find a way to do so
I see there are BIOS updates too for this motherboard, It could be worth a try to update it (at your own risk of course). Switching kernel to 5.10 LTS could be a proper easier solution too.
I am getting the same error , I just got a new board , a intel z590 ( asrock entreme 590) that is when The error started . At 1st I thought to try different memory kits , reseat the GPU card , reseat the CPU .
Tried every bios setting under the sun . I also get with memtest " Internal error line 169 test C
nope not a memory issue the fact that we both have Asrock Z590 boards and both have the exact same problem , indicates to me some kind of bios, firmware issue
say what cpu are you using a rocket lake or comet lake ? Me I am using a 10600kf just wondering if it is because of not running a rocket lake and the kernal is seeing things being disabled
ok the problem is with the Asrock Z590 , I just swapped back to my MSI b460 Tomahawk and all those error messages went bye bye . I am sending My Asrock Z590 Extreme back to new egg , swapping it out for a MSI Z590 Torpedo https://www.newegg.com/p/N82E16813144390
I will update when I get the board to see if messages return
I’ve marked this answer as the solution to your question as it is by far the best answer you’ll get.
However, if you disagree with my choice, please feel free to take any other answer as the solution to your question or even remove the solution altogether: You are in control! (If you disagree with my choice, just send me a personal message and explain why I shouldn’t have done this or or if you agree)
P.S. In the future, please don’t forget to come back and click the 3 dots below the answer to mark a solution like this below the answer that helped you most:
so that the next person that has the exact same problem you just had will benefit from your post as well as your question will now be in the “solved” status.
I am not sure if I found THE solution , why do I say this ? Because I am moving to a different chipset , a b460 chipset and the problem went away . was it the chipset or the motherboard that caused the issue ?
Did Asrock produce a buggy board or is it something in the Intel Z590 chipset ?
is it that manjaro Just cant deal with a Z590 chipset ?
I will have a definite answer to that question soon as I have a new MSI Z590 en route to try out
I got the MSI Z590 installed with a fresh install of Manjaro , switched to the latest Kernel . 5.11 and the problem returns , not asrocks problem . I suspect it is a problem either with the Intel ME firmware or Manjaros’ kernel not seeing something … Not that I am complaining , it just too new cutting edge hardware . I am suprised that the B460 chipset worked so well
I had also a similar problem with different messages after updating my BIOS once and I had to disable IOMMU in BIOS to get rid of the message on boot. It took three consecutive BIOS updates for that to eventually being fixed. Maybe it is a not so serious issue that will get fixed in later BIOS check you manufacturer for new BIOS in the future.
ok problem is solved for me , MSI just released a cpu microcode update in a beta bios , I suspect Asrock needs to do the same .
Flashed to the latest bios and poof all gone