PC turns on from sleep mode

Man, I was running this thing all day yesterday and it was smooth as silk, totally fine, right? So I shut it down in the evening, put everything away, and then this morning I go to fire it up... the initial boot starts, I see the macOS loading screen, and then—bam—just total silence. It’s supposed to show the cursor, but instead, I’m just staring at a pitch-black screen. Nothing. Zero. No response whatsoever. I end up having to force a hard shutdown by hitting the power button, then I try booting it up again, and suddenly it’s like nothing ever happened! It loads right up perfectly like it wasn't even glitching out on me. Just absolute nonsense.

If things stay smooth from here on out, looks like the computer just fixed itself. No need to sweat it...

Man, I’m having a massive headache with this thing—it acts up every single time I let it sit for a bit after shutting it down.
If I just hit reset or flip the power switch right back on immediately after turning it off, it behaves itself and boots up just fine on the first try.
But if I let it rest? Total disaster. It gets through the macOS loading screen, I'm waiting for that mouse cursor to pop up, and then—nothing. Just a black screen staring back at me, and the only way to fix it is to go full "hard turn off" by smashing the power button.

Man, I’m starting to think this is definitely some kind of hardware nightmare because I’ve literally tried everything. I went through all the connections, cleaned out the hard drive, the Wi-Fi card, the RAM—I even messed with every single cable just to reseat them. I was even shaking the thing while it was running, hoping I could force the glitch to happen again, but nothing! It’s like the universe is playing games with me. The only way I can actually trigger it is if I have everything perfectly organized, the laptop sitting totally flat, and then—get this—if I give the palm rest a little tap (not like a punch, obviously, just enough to rattle it) while simultaneously jiggling the screen, the display starts flickering like crazy—blacking out, coming back, blacking out again—until the whole damn system just freezes up and I'm forced to do a hard reboot.

Sometimes it doesn't even go full freeze mode; the screen just cuts out for a split second and pops back on, which clearly means something is seriously wrong, but I am completely lost on what the actual culprit is.

I tried messing with the hard drive while it was powered up, no luck. I jiggled the contacts and the wireless card, played with the RAM... absolutely nothing happens.

I even tried messing with the display cable, unplugging and plugging it back in while the machine was live, but that doesn't cause these specific symptoms. Sure, the picture goes dark when I pull it, but once I plug it back in, the image returns and the laptop keeps running fine without freezing.

I am genuinely stumped here. Does anyone have any clue what could be causing this kind of total system lockup?

To make matters worse, I have to restart it multiple times just to get it to behave because it almost always freezes on the very first boot attempt.

And when was the OS actually installed? If I were in your shoes, I’d probably just opt for a fresh OS installation from scratch.

I’m honestly telling you, you should just go ahead and wipe the drive and do a clean install of macOS. There's a very real chance the OS itself is what's causing all this headache.

What do you guys actually know about computers? I just installed macOS, and honestly, my IT help desk is dealing with the exact same weird issue you're having. Try googling "black screen after login." Some people find fixes that way, though they didn't work for me. Open the run command and try running scannow to see what errors pop up.

I still haven't fixed my own issue. I'll see if I can get it sorted by tomorrow, or maybe I'll just head over to the local repair shop. I'm going to test the voltage on the power supply first, then move to process of elimination—testing the GPU and RAM. I'm pretty convinced this is a hardware failure, not a software glitch.