Partially dead CPUs can absolutely still POST and boot. I work in a PC repair shop and see it all the time. Everything will work totally “fine” and you’ll get weird errors here and there similarly to failing RAM. You have to run a dedicated CPU test like the ones in OCCT (Windows-based, don’t lynch me) or similar to see if you’re getting WHEA or other errors.
The reason for this is that a lot of CPUs have built in redundancy to get around having imperfect silicon, and sometimes that is enough to make the system still work, but not be quite “right”.
The good news is, if you are producing such errors, you usually have a 3yr warranty on most CPUs and the OEM will RMA them for you.
That’s the name of the program. You can search it and it’ll pop right up. It is now owned by Cooler Master.
Once you download it, you can run either the CPU Srress test or the Linpack test (this is for Intel mostly as it is their proprietary test) and it’ll run while looking for math or WHEA errors.
While you’re doing science, I would also recommend doing a RAM test with memtest86+. You download the .iso and make a bootable drive, and boot into it. Both RAM and CPU can make similar weird failures so checking both is a decent idea.
Does UEFI initialize all the cores? I know the OS always starts with only one core available, but I’m not sure if UEFI just disables the cores after it’s done its thing, or if it doesn’t touch them. Because if it stays on core 0 and never even brings the other ones up, then this issue with core 2 could let it boot this far just fine.
you might be right, i left it for a couple minutes to write to amd about warranty and it booted up just fine into linux when i wanted to get the motherboard info. wtf. but now that i think about it, i do have weird cpu related blue screens and timeouts more often than what i’d like to think is normal
If the CPU died, the PC would not have booted up so far.
Partially dead CPUs can absolutely still POST and boot. I work in a PC repair shop and see it all the time. Everything will work totally “fine” and you’ll get weird errors here and there similarly to failing RAM. You have to run a dedicated CPU test like the ones in OCCT (Windows-based, don’t lynch me) or similar to see if you’re getting WHEA or other errors.
The reason for this is that a lot of CPUs have built in redundancy to get around having imperfect silicon, and sometimes that is enough to make the system still work, but not be quite “right”.
The good news is, if you are producing such errors, you usually have a 3yr warranty on most CPUs and the OEM will RMA them for you.
OCCT? Tell me more about it. Also I’ve only had my cpu since September so I can definitely RMA it if so
That’s the name of the program. You can search it and it’ll pop right up. It is now owned by Cooler Master.
Once you download it, you can run either the CPU Srress test or the Linpack test (this is for Intel mostly as it is their proprietary test) and it’ll run while looking for math or WHEA errors.
While you’re doing science, I would also recommend doing a RAM test with memtest86+. You download the .iso and make a bootable drive, and boot into it. Both RAM and CPU can make similar weird failures so checking both is a decent idea.
Does UEFI initialize all the cores? I know the OS always starts with only one core available, but I’m not sure if UEFI just disables the cores after it’s done its thing, or if it doesn’t touch them. Because if it stays on core 0 and never even brings the other ones up, then this issue with core 2 could let it boot this far just fine.
POST is supposed to check all CPU cores and all RAM. It’s check isn’t perfect, but it does check them all.
you might be right, i left it for a couple minutes to write to amd about warranty and it booted up just fine into linux when i wanted to get the motherboard info. wtf. but now that i think about it, i do have weird cpu related blue screens and timeouts more often than what i’d like to think is normal
Maybe do a memtest. Idk what the software was called exactly but you just flash it on a USB, boot from that USB and it will test if your RAM is okay.
ive already done one recently and it came out with no problems, maybe i’ll do another one
Try booting from a USB with a stock kernel (no Ubuntu derivatives) and then running a stress test.
I would make sure you set the logs to print to screen. If you have a dedicated graphics card try removing it. As you might have a bad gpu
Memtest86+ bloody great software.
RAM could be a cheaper culprit. Try re-seating it.