Screen going back for a few seconds, randomly. (Fixed)

So I finished building my custom PC. Downloaded a few things then got onto playing some WoW.
From the get go, my screen would go black randomly, but at first I noticed it would go black in sync with my minifridge (when it turns off and on the screen would go black) which is connected to the same mains plug, but not the extension plug.
This mainly happened when I was playing WoW, I didn’t have a GPU in my system, I ran WoW off of my CPU on the lowest settings on a 1080p 240hz monitor. After a while I bought a 3090 and a new monitor, 4k 144hz. I unplugged my minifridge completely, but the screen would still go black for a few seconds, randomly. I plugged back my minifridge and it was still the same.
So here’s the fix I came up with, maybe it has something to do with it. I switched my monitor which goes black while playing WoW from a 1.4 DisplayPort to a 1.2 DisplayPort, in the monitor settings. Ever since then, the problem never happened again. Obviously this is not convenient as the screen looks a little off, since I cannot use HDR anymore on 1.2.
I am not very tech savvy and was wondering if anyone had a similar problem and went around it in a different way to fix it.

Any input would be appreciated. Thanks.

So heres why this is happening to me. I am trying to run the game on 144hz on 4K. However DisplayPort 1.4 does not work past 120hz at 4k, apparently.
So now, I am back on 1.4 DisplayPort, running at 4k 120hz. No blackscreen, nothing. I guess I shouldve known. Screen crashs mostly would be the Clock of the monitor. So until DisplayPort 1.4 can support 144hz at 4k, theres nothing I can do.

If anyone is playing WoW on 4K resolution at 144Hz+ please tell me your secret.
How can I run the game on the best settings, while giving my GPU 26% Juice and the GPU is running on 40% Power at the average temp of 40°c. How are there monitors out there running 4K+ on 240hz?
Is this really a DisplayPort cable problem?

DisplayPort cables have limits regarding the display refresh rates and resolution limits they can support. The related wikipedia article covers this quite nicely, but the short naswer to the question is: yes, this is very likely a result of the physical limitations of the technology used.