Thank you for contacting the Intel community.
It will be good idea to contact Zotac to find out compatibility problems or a BIOS update that can help you solve the problem.
Honestly, I have not seen similar issues like this especially because you are using Fedora and that will be out of our scope, have you tried posting your inquiry at the Fedora community, you can try here:
I’m sorry that I wasn’t a big help for you right now and if some user who had solved this issue before can share their experience with us and how to solve it that will be very much appreciated.
i already filed a incident at https://bugzilla.redhat.com/show_bug.cgi?id=1467040,
so the Fedora/Redhat engineers will check it. Anyway they have to fix a analysis
tool, in order to render a better bug description.
Anyway i identified a similar behaviour in the context of a IGT (xf86-video-intel) driver.
Maybe a bad memory map caused that error, so it is an Intel-issue. Your colleagues are
actually checking this issue, because the driver was developed by Intel ;-)
From you i was hoping to get some information of kind of CPU exception, that has been
caught. It is not a good idea to delegate the problem, when you might have an explanation
of the CPU state. I was not expecting a solution, just a hint (i.e. illegal access to a HW adress)
Thank you for the valuable information you have kindly provided, unfortunately with the log you provided I’m not able to check anything and please bear in mind that we don’t validate the Intel processors with Linux* so that is the reason why we don’t have much information about this issue, if you already post this issue at the website you provided I suggest you to wait for a solution there.
look at this, of course Intel is checking the state for their CPU's on Linux.
Your employer is one of the biggest Linux supporter ;-)
Thank you very much for this information Groovy, I really appreciate it, honestly this support is out of our scope, I hope this Microcode Data File you posted here can help other users who are looking for similar information.
This is really not helpful.
It is remarkable for the quality here, these guys here can not help,
regardless the fact, that they might have the answer, because they
had a very similar issue on their NUK systems.
But when these guys here read Linux it seems that they stop thinking
and say: go somewhere else.
A very frinedly staff from Intel (not thoses guys here!) remember, that
NUK had a similar issue and fixed it.
So iff you have a similar issue, go to your mainboard manufacterer and
tell him, what went wrong an that intel fixed their nuk to fix the issue.