Hey yall,
I had a stable overclock running for about a year or so, but had to reset the CMOS because I pigheadedly disabled USB 2.0 for the UEFI. I recreated the settings as best I could, but after testing it with Final Fantasy 15, I got a BSOD with "k_mode_exception" or some such. That, I sort of expected, but what I hadn't expected was one of my monitors suddenly cycling through solid colors. Some smoke came out of the top vent and now the backlight won't stay on for more than a second, so I assume it was probably some capacitors. I'm quite certain the cause of the BSOD was a HT clock that was too high.
The question is this: did the system crash damage the monitor, or was it on its way out? (For reference, the monitor in question was a Vizio VMM26 from 2008 connected by DVI-D and the GPU ports are perfectly fine.)
I had a stable overclock running for about a year or so, but had to reset the CMOS because I pigheadedly disabled USB 2.0 for the UEFI. I recreated the settings as best I could, but after testing it with Final Fantasy 15, I got a BSOD with "k_mode_exception" or some such. That, I sort of expected, but what I hadn't expected was one of my monitors suddenly cycling through solid colors. Some smoke came out of the top vent and now the backlight won't stay on for more than a second, so I assume it was probably some capacitors. I'm quite certain the cause of the BSOD was a HT clock that was too high.
The question is this: did the system crash damage the monitor, or was it on its way out? (For reference, the monitor in question was a Vizio VMM26 from 2008 connected by DVI-D and the GPU ports are perfectly fine.)