PC doesn't boot after CPU overheat message

[Soulreaver]

Hello,

my pc doesn't boot anymore. A friend and I tried several steps but nothing worked yet.

My System

RTX 4080/5070ti clarify in a bit
Asus Z690
i9 12900k 360mm AiO
32GbDDR5 6000Mhz
NVME Samsung 980
Sata SSD Sandisk (don't know the Model)
OS is Windows 10

What happened/we tried so far

I want to sell my 4080 and therefore removed my 5070ti and put in my 4080 for evidence of it working. At first everything was fine the 4080 was recognized in GPU-Z but the system acted choppy, so I restarted.
While booting there was an error message my CPU was overheating.
So I restarted again. Same message. I replugged the CPU header and everything was fine again regarding the cpu, but now my whole system doesn't boot anymore.
We removed the GPU and now run it over my 12900k as graphics output. Just to be sure.

Both of us are not very knowledgeable in Bios

We checked temps first. CPU temp was at 56°C so very elevated and in the process of going down. It's at a constant 32°C now.
Then there was no option to select any of the drives as bootdevices so after checking if the Mobo still recognized both my drives (it did) we went for a bios reset.
This didn't fix it.
We removed the Mobo Battery. Also no fix.
Then I tried a different slot for my boot drive, it still recognized it but not as bootable.
Then we tried changing some other settings.

Under Boot
OS Type -> From Other OS to Windows UEFI mode
Secure Boot Mode -> From Costum to Standard


Under Advanced
Trusted Computing -> Security device support -> From enabled to disabled
This doesn't go back to enabled when resetting the bios. But does when changed manualy.

Yeah this is pretty much where I'm at.

If that is of any help. My Bootdrive was set in the format that you can not use to upgrade to Win. 11. I don't remember how both of those formats are called. But maybe this gives further insight.

Update: I just tried an old Samsung 950. This one also isn't detected as bootable.

[Soulreaver]

Originally posted by Midnight Aurais:

try a air cooler instead as far as i know when a pump gets detected by the motherboard thermal shutdown temp no longer gets controlled by the motherboard instead the aio is responsible for it

unless something changed since it been ages since i had watercooling this should still be the same

Just sold my noctua. As everything regarding the CPU is fine temps, clocks, volts, SP rating. I assume reseating the CPU header did fix it.

The problem at this point also doesn't seem CPU related anymore. Atleast I wouldn't see why not detecting a bootdevice would be.

[ˢᵈˣ FatCat]

Check pin Socket

[Phénomènes Mystiques]

One thing that people forget to do when removing GPU and RAM is to either turn off the PSU in the back fully switched off and/or to unplug the machine from the outlet as not doing so can corrupt the system.

So tell me, did you properly de-power the system/hardware prior to uninstalling/reinstalling the hardware or did you do what many others do and attempt to uninstall/reinstall hardware while sitting on stand-by power?

[Soulreaver]

Originally posted by Midnight Aurais:

i think i misread it a bit thought the system refused to boot but it does boot as the bios posted it just does not boot into the os sorry about that

the only thing i can say about that is replug the m.2 or try a different m.2 slot the thing is 980's have premature deaths samsung issued a firmware fix for them you can find it online i got nothing to grasp onto other then maybe you had some terrible luck i doubt the pump header not being plugged in correctly could cause any issues but yeah

a harddrive or ssd crawling to its knees in the os is a sign of failure but the pump header issue you had to reseat might have obfuscated it and you said the temps were normal of the cpu so the cpu did not crawl just that the thermal protection kicked in of the aio because of the bad seating

so yeah if you can and want to see if you can get into a desktop environment linux is a good option because of live boot meaning you can boot off of a usb and try linux to see if everything is still functional

or get a different drive to install windows on

I already tried a different m.2 slot. It recognizes the drive there too. Just not as bootable.
I also have another sata ssd inserted that I can't use. So its not only regarding my current OS drive.

The CPU very likely was overheating. When I entered Bios the first time it was at 56°C. That's not normal behaviour for my CPU. As it must have already cooled down a bit. Its idle temp is around 40-45°C and I didn't have any load on it the whole time.

Yeah my buddy has a linux stick we wanted to try but he had to go. Will try that later if I can't solve it till then.

Update: I just tried an old Samsung 950. This one also isn't detected as bootable.

[Soulreaver]

Originally posted by WinterSorrow:

One thing that people forget to do when removing GPU and RAM is to either turn off the PSU in the back fully switched off and/or to unplug the machine from the outlet as not doing so can corrupt the system. :badluck:

So tell me, did you properly de-power the system/hardware prior to uninstalling/reinstalling the hardware or did you do what many others do and attempt to uninstall/reinstall hardware while sitting on stand-by power? :csd2smile:

No, PSU was unplugged and the switch was off. I even switched out the power connectors of the GPUs-

[Soulreaver]

Originally posted by Midnight Aurais:

it recognizes the drives welp XD

in bios you can check boot order by going to advanced then boot and looking if the os drive is on 1. or 2. it is not problem if 1. usb and 2. os drive because that means as long as no bootable usb is inserted it goes to 2. if you cannot find the boot menu look online different motherboard vendors have different uefi bios layouts

if this is fine and your os drive is set correctly in the boot order then yeah the linux usb would have helped because your boot partition of the os drive might be nuked

I just plugged in my Win10 Boot stick again. It's still only showing my stick as only boot option.
But my stick when booted obviously doesn't find a bootable device.

I think you talk about something else. It doesn't find any of my drives bootable. Even those that weren't connected during the original problem. I have drives I used previously that I had lying around. Those also don't get detected as bootable drives by my Windows Stick.

Edit: I could try an old HDD but as I already have a Sata SSD connected I don't think this will help.
I also forgot to mention I removed the GPU and use my CPU as Graphical output.

[Soulreaver]

Originally posted by Midnight Aurais:

you mentioned the boot format let me guess its mbr not gpt the windows 10 boot usb likely boots the setup in uefi install mbr is not supported in there as boot drives

easy way to figure that out is read the title of the windows install it wil tell you uefi

from the way you put it you installed it as a gpt then used cmd to make it mbr

if you did do this then you have to use a live distro and use the terminal to switch it again and it should work or you follow this microsoft post

https://answers.microsoft.com/en-us/windows/forum/all/my-new-windows-10-installation-is-on-a-non-uefi/967c696d-ce4f-4ad4-981c-8400c333356f

I assume you're onto something. Sadly I did understand barely any of your instructions.

Right now I'm letting the integrated Passmark check my Memory Sticks. It'll take a while. Would you be able to make the instructions a bit clearer?

Also my Win10 Stick doesn't boot in the usual Windows 10 graphical interface. It stays in command interface and tells me I have no bootdrive to choose from.

Don't know if thats important.

EDIT: Just saw your edit regarding Win11. I don't have anything against Win11 I just didn't reformat my drive yet because I didn't know how and it was no priority.

[Soulreaver]

Originally posted by Midnight Aurais:

so when you enter the bios your in the uefi bios which is a graphical interface this is the old legacy bios
https://us1.discourse-cdn.com/flex020/uploads/chuwi/original/2X/d/da6b81b93cdfc98ec888dfec35f98d4e91c1a283.jpeg
that is all you have to know on that part if it doesn't look like the old bios you are in uefi

mbr and gpt are boot tables both handle partitions differently again you do not need to exactly know you can wiki it it gets to complex to explain

all you gotta know about those is that mbr is for the legacy bios i posted a link to and gpt is the standard for uefi bios i mentioned above

partitions are like having a cake you want to split in pieces basically say you want 1 tb from your 2 tb ssd and want it separated you can by creating what is known as a partition it can be used for file management in this case

cmd is the terminal here you can execute commands like copy paste and all because it is what windows is just a fancy cmd with some graphical input that is why some just prefer to use cmd instead it is faster when you start understanding it it is why linux love the terminal so much XD

also could you make a picture of the windows setup interface that you are getting?

the linux boot usb would have resolved this already usually if i encounter this type of issue i have another device to plug it into as a second drive and fix it if you have a recovery versions of windows 10 it would be simple those often allow you to either enter cmd or a disk manager

We're creating a Linux and a fresh Win10 stick now.

[Soulreaver]

were in linux right now it sees all my drives and their files including windows files

[Soulreaver]

Okay my current assumption is

1. My windows iso was either broken or too old. Creating a new one solved the problem.
2. My GPU Driver ♥♥♥♥♥♥ the whole system up, when I switched from 50 series back to 40 series.

I don't know if a GPU driver can be this powerfull but I did a lot of troubleshooting today and everything points in that direction.

Everything on the Hardware side of things works fine.

CPU is idling at ~27°C with the fresh setup. I installed both GPU's they atleast work. Didn't test them yet in a stress environment. Try to go step by step and I'm still setting up everything.

However. Everything seems to be back to normal.

Midnight a big thank you for your help.

[GOD RAYS ON ULTRA™]

"Both of us are not very knowledgeable in Bios"

Did you try the setting called Compatibility Support Module? Maybe you had it enabled or disabled before. It would make a difference depending on how your drive is partitioned.

"If that is of any help. My Bootdrive was set in the format that you can not use to upgrade to Win. 11"

[Soulreaver]

Originally posted by Midnight Aurais:

Originally posted by Soulreaver:

Okay my current assumption is

1. My windows iso was either broken or too old. Creating a new one solved the problem.
2. My GPU Driver ♥♥♥♥♥♥ the whole system up, when I switched from 50 series back to 40 series.

I don't know if a GPU driver can be this powerfull but I did a lot of troubleshooting today and everything points in that direction.

Everything on the Hardware side of things works fine.

CPU is idling at ~27°C with the fresh setup. I installed both GPU's they atleast work. Didn't test them yet in a stress environment. Try to go step by step and I'm still setting up everything.

However. Everything seems to be back to normal.

Midnight a big thank you for your help.

no problem a gpu driver should not have caused such damage that the boot partition craps itself one thing i recommend doing still is going to start and running "windows memory diagnostic" when you got time just to be safe that you do not have errors in your memory sticks that could cause corruption in the future

another factor that could be is malware that nuked the boot partition but we wil not know now so that one does not mather

tip when switching videocards the rule is run ddu before hand in safe mode
https://www.wagnardsoft.com/display-driver-uninstaller-DDU-

you can do this by holding shift and clicking restart it should enter in troubleshooting mode there you go advanced then startup settings it might have restarted 2 times by now usually 1 time then in the startup settings pick safe mode or safe mode with networking does not mather

launch ddu unistaller do not change any settings without knowing the defaults are fine the way they are so click out of settings select in device type gpu and the box below nvidia then click the box "Clean and shutdown" then you can switch the cards do that again when you switch back

this case its a clean install so only when switching back to the 5070 ti you gotta do this

use this aswel when you start having weird issues with your card as multiple driver updates can leave lingering files that are not removed that are incompatible with eachother like my friend the lingering files were causing bluescreens ddu solved that

the clean install option in the driver install does not remove lingering files

Yesterday I already did 90 minutes of mem test. I'll run the windows memtest too now.

I don't think Malware is very likely. Here in Germany we have Chip a page that checks and uploads every major and a lot of minor programs. DDU, Audacity, Clipgrab, GPU-Z, HWInfo, VLC, Win Iso, Teamviewer. You name it you can download it there safely.

I run DDU once a year or so to get rid of some residual files but never did it for swapping GPUs. And I owned like 4 different GPUs in the last 6 years alone.
Well maybe with the new GPU generation one has to DDU.

[Soulreaver]

Originally posted by GOD RAYS ON ULTRA™:

"Both of us are not very knowledgeable in Bios"

Did you try the setting called Compatibility Support Module? Maybe you had it enabled or disabled before. It would make a difference depending on how your drive is partitioned.

"If that is of any help. My Bootdrive was set in the format that you can not use to upgrade to Win. 11"

The whole CSM section was greyed out.

[GOD RAYS ON ULTRA™]

See if you can disable secure boot. Then save it and reset into bios again and maybe if you can change the CSM option.

[emoticorpse]

I'd guess something that had to do with secure boot caused most of that.