Windows 10: BSOD - PC is rebooted after a bugcheck

our times my PC has experienced a BSOD with the message "The computer has rebooted from a bugcheck" and I've performed the following actions which hasn't stopped the issue from happening again : - Verified the memory by running 'mdsched.exe' - Verified that Windows 10 v21H1 is up-to-date - Verified that the drivers are up-to-date by using IOBit Driver Booster V2 log collector 1.11.zip

:)

 

(BSOD) bugcheck was: 0x000000a0 INTERNAL_POWER_ERROR

Has any one got this BSOD when stress testing a overclock before? i can get the minidump if some one can read it for me i was trying for 4.5Ghz @ 1.31v and after around 20min of stressing i would get this BSOD and it would shut my system down not even sure i saw a BSOD just a shutdown?

 

PC reboots (no BSOD) on CPU stress

Hi fellow TPU members,

not too long ago, the box my gf's PC was transported in gave way on the stairs. Yes, you got it right, that sent a PC tumbling down a flight of steps alright.

Stuff broke. Also, stuff remained intact somehow.

I bought her a new case, new CPU cooler and we removed the floppy drive, so far so good. But the PC started crashing for no apparent reason, without a BSOD.

I tested:

• Memtest86+, left overnight, 0 errors
• Scanned the HDD for errors, nothing there
• Left FurMark burning up the GFX card and drawing some power, no problems there
• Ran Ubuntu from a Live CD doing nothing special, didn't crash
• Ran OCCT, Linpack, Prime95, all 3 caused reboots within minutes
• Oh, and I disabled "Restart on error" so I'm sure it's not a BSOD.

Now, I can still try and test something CPU intensive on Ubuntu, but my guess is the CPU didn't survive.
Before I do anything drastic like whippin' out the magic wallet and get her a new AMD quad, is there anything I didn't see?
I'm guessing the motherboard could be borkered as well, but can I check that other than replacing the CPU with a working one?
Any suggestions on which proggies I can use from an Ubuntu Live CD to stress the CPU?

 

This is causing 90% of my Win7 64bit BSOD's...

WTF is this?

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff9e0084e02c0, 0x0000000000000000, 0xfffff88003c7b293, 0x0000000000000005

any suggestions thnx a bunch!