After a final couple hours of troubleshooting I think I’ve settled on this issue being caused by faulty monitors. Here’s why:
Key: Group #) [phantom output/total system shutdowns] - who’s monitor, who’s cable, who’s PC
-
[0/20] - GF’s monitor, her cable, My PC
-
[1/2] - 1 of my monitors, my cable, her PC
-
[2/2] - both of my monitors, my cables, her PC
-
[1/2] My monitor, her cable, her PC
-
[0/10] Her Monitor, my cable, her PC
-
[0/10] 1 of my monitors and her monitor, 1 cable was mine 1 was hers, her PC RUNNING WINDOWS
The fact that I experienced no phantom output while dual booting into Windows on her PC is absolutely baffling to me. Based on seemingly no one else ever having experienced this issue before, or at least hasn’t posted about it, I think it’s safe to rule this as a faulty monitor and not an issue with the Linux kernel that doesn’t happen on windows.
Furthermore to the faulty monitor claim, when a normal monitor loses it’s input signal it will go into sleep mode and you can still press the monitor’s physical buttons to bring up an input selection menu. Instead, my monitors do not respond to the physical buttons including the power button. If this was an issue with PC hardware, unplugging the displayport cord would stop any constant signal being sent to the monitor. Instead, I believe it receives the signal to go to sleep, and then some type of short happens. It is VERY VERY strange that this same type of issue happened near the same time on both monitors.
Anyway, thanks to @ricklinux and @MikeDelta42 for spending the time to help me. I’ll be marking this as resolved soon!