Notebook Operating System and Recovery

Ive scoured every last nook and cranny of the internet and I seem to be th only person on the planet experiencing this issue.

PC runs perfectly fine UNTIL I restart or put the computer to sleep and wake from sleep immediately.

the screen then glitches with horizontal lines than move from the botton to the top before it flashes and crashes my sysytem.

It appears to be if the screen is shut off for any reason then turned back on too quickly.

No idea if this is a sortware, firmware, BIOS  or hardware error.

-if i restart the screen automtically shuts off for a second and back on, causing he glitch and causing me to never be able to restart (so cant install updates of any kind)

-if i put the pc to sleep via the power button and wake up immediately, it glitches out the same way

-if change the screen Hz from 40 to 60 or vice versa this requires the screen to reboot momentarily and causes the glitch as well.

Basically anything that causes the screen to shut off then turn back on instantly causes the screen issue and a system crash. HOWEVER, if i put it into sleep mode and wait more than 5 seconds to turn back on it works perfectly fine.

It seems to be an issue with sending power to the screen or video card or display driver. whatever it is seems to need a second to "catch up" or it glitches out and crashes 99.9% of the time.

Ive tried virtually everything with the exception of a clean install, which i cant seem to do anyway since this requires a "restart". Anything that turns my screen off for less than 5 seconds causes the pc to crash. So like i said, I cant update much since some require restarts. Im at a point where Windows is now forcing an update to 1703 but since I crash on a restart it cant install, So the next boot after a hard reset rolls back to 1609, which forces another update to 1703, etc etc etc.

Upon some roll backs the system gets corrupted. Ive had to spend hours trying to get a version of windows back up ad running only to run into this bizarre loop. (This is not the widespread restart loop reported earlier, this is specific to my restart issue)

Any thoughts?