Hello Guys, i'm having some trubles with my workstation:
i7 8700k
asrock z370 ext4
g skill 32gb ram
vega64

I was on win11, with lastest updates I started experiencing come trubles, which on forums adressed it on driver. I was really mad at windows so I decided to migrate to Ubuntu(already have it on my old laptop).
So I erased my sdd and i tried to install Ubuntu.
From now on i started get errors when run installations from live usb,both norma installation adn safe graphic, errors like:
-Black screen
- Kernel panic - Not syncing | Shutting down CPUs with NMI
- not present in page
- stack corrupted

Attatched an example of what I get:
https://i.postimg.cc/QNFMV0dz/IMG-20230307-192554.jpg
https://i.postimg.cc/SQVNZ3tj/IMG-20230307-194001.jpg

So what I tried is:
- reset bios, via cmos reset
- reset bios with rescatux (that only worked in filesafe mode)
- check all the components with Ultimate Boot Cd, and all the hw sames to works fine (mem, cpu, gpu, etc)
- tried to downgrade the bios
- tried to change bios setting like: power saving, wifi/bluetooth power, first gpu, audio etc

I don't really know what else to do! It happened all happened after win11 upgrade, i tought after erasing the sdd everithing will start to work, but nothing is working.
Do someone have some advices about it? Thanks a lot in advance guys!

I'd proceed with significant caution.

The "Thread overran stack or stack corruption" and accessing non existent memory pages are classic malware-type errors, as is a thread apparently resisting being killed. It's quite possible windows isn't really gone, because the kernel is giving knee-jerk reactions of the 'You touched my privates' variety.

If you were asking "Am I being hacked?" I'd say "Probably."

I'd boot from a live usb or dvd, dd zeroes onto that drive, and reinstall, unless others all think I'm being alarmist.

Hello, thanks a lot for aswering!
The prolem is that i get this errors, with a live usb.. I'm not able to access a live usb of some linux distro/windows (just some live usb tools with filsesafe mode), also with the sdd drive removed!
From what I know, the OS should be only on the drive isn't?

So what I'm thinking, is it possible that the malwere you were talking about, or windows itselfs, in some ways, corrupted the uefi?
I mean I can access uefi, I can change parameters, I make a downgrade; but is it possible that for example, the memory control part of the mobo firmware got corrupted?

I am unable to use those links, so can't see the messages - so I can't help. Maybe it's my VPN, maybe my script blockers; who knows.

Can you post the data here ?.

I canno paste here because I couldn't copy it.
Let's try with wetransfer https://we.tl/t-AKmGuTesrq
Can you see them?

Hmmm - that site dropped 17 cookies on me. Very rude. However I did get the photos. As per your explanation it is a (incomplete) listing of a kernel oops. I wonder if the Win11 update did a microcode update - I've seen such on my HP laptop.

Sorry, can't offer anything helpful.

Edit: I'm thinking this is not a disk issue.

Here's a sample of the error taken from one of the photos. There are a lot of repetitions of this sort of thing.

So, summarizing the posts so far: we are concerned, it's giving all the wrong signs, but there's no consesus, and you probably want to try stuff to eliminate this problem.

I would boot from a live usb (ideally an iso) with the hard disk unplugged. That could well confirm syg00's experienced instinct that this isn't a disk issue. It's important to unplug the disk (even an nvme) because some malware hides on the EFI partition. If the faults go away, you have your problem. Otherwise, read on.

Next, have a good read of these and any associated hyperlinks.
MoonBounce Malware
Lenovo Hacks
BlackLotus Malware
These are very low level hacks, and effectively your motherboard is infected, and anything that has been connected has to be treated with great caution. Curing these is seriously above my pay grade. The hardware solution is to remove & reprogram the BIOS EEPROM, but there could be less drastic means the Malware will allow.

EDIT: If there is some bios or uefi malware/corruption that a BIOS update won't fix, the simplest & easiest thing might be a new motherboard.

Hello Guys I make some tries.
First of all yep, I tried everithig also with unplugged nvme and data hdd.

After a few search I decided to flash the bios eeprom. I bought a ch314a flasher(7 euros on amazon), and with flashrom 1.2 I erased the memory and I flash the bios version in which the mobo came out (p1.30).

I'm really angry, I'm getting same problem daaamn!!

So memory could not be, becouse with a live tool I runned memtest86+ for like 12 hours and no errors came out.

I tested the Cpu, with another tool, and it looked ok.

Could it be the integrated gpu? But on bios the primary gpu is setted on pcie, so it should be the Vega 64.

I know I should buy everything new, but, I'm quite on the budget now and then i'd like to know what to buy, what is defective.

These could conceivably be symptoms of some very complicated low level hardware error. If you just try to do normal stuff, does it work?

Beyond admitting this is not my speciality at all, we can say this: Unless someone comes along with a better explanation than me and says: "Ignore business_kid," you seem to have some seriously nasty malware. Give it a day or two to let someone chime in. Quarantine anything that has been on or in that box as if they had Covid, until you know better.

Ask a moderator to transfer this thread to the Security forum. Reporting yourself is a good way . And start a trawl of security sites. It's infectious at some level because you got it. But it needed root access to insert itself into the BIOS, Microcode, or wherever it went. That may narrow it down if you think back. Have you windoze on that Box? That might even do it. If your motherboard is worth big money, professionals may help. If not, buying another might be an option.

When you run this down, as I expect you to, please post and let us know how it was sorted.

EDIT: These days a lot of peripherals have industrial cpus or microcontrollers simply as the laziest way of handling protocols. The Realtek 8111/8168/8411 1GB network card is an example, found in an awful lot of pcs. An easy thing to try would be disabling as many as possible(network, sound, video) with sshd running. Then log in remotely and check the logs .

"all happened after win11 upgrade" now that sucks...

Asrock support used to be known to only support winblows but doesn't hurt to try asking them.
Never know, they could answer: https://www.asrock.com/support/faq.asp?k=linux

Meanwhile, try booting from a slackware live usb and make note of the "UEFI Secure Boot" section:
https://docs.slackware.com/slackware:liveslak

Hello guys, after thousands of try, I came up with a solution (half solution, becouse pc now works but as my old laptop)

So, while changing all the uefi settings for the 1938394849 time, I tried to se the active cores = 1.
And magically Ubuntu booted with no kernel panic error! damnit jesus!

I installed Ubuntu, everything works!! The problem is that in Resource manager i'm running on 2 cores (think 1 core 2 threads?)
What can cause this? Could a core be fu**ed?

Guys i Came up with a solution that seems to work:
I activated all the cores in UEFI.
I do boot with grub selecting maxcore=1.
Then I wrote a stupid script(enable_cores.txt) in order to reactivate all the working cores(becouse from boot log, it says like cpu2 takes log time, watchdog..something like this)
Ok now I can see the cpus from the systemmonitor and from vital extension for gnome.
I also tried a tool test and all seems to works fine!(), just I canno read cpu load of all cpu on system monitor, but in the tool and vitals it wokrs.

Now do you know a smarter way to do what i've done, or is it the best one? I'm so happy I can use again my pc

Last message, thanks to this guide https://askubuntu.com/questions/2900...g-boot-as-root I set the script run automatically at start up.

No, that's a dodge that lets it work, OK for now.

GET IT BACKED UP! And start saving for the next one, because a fault like that is definitely an ominous sign.