F5F Stay Refreshed Power Users Overclocking overclocking broke monitor

overclocking broke monitor

overclocking broke monitor

Pages (2): Previous 1 2
V
Velizar06
Posting Freak
865
06-28-2016, 05:53 PM
#11
This would be an unusual situation. Do you have an optical drive in your PC or a USB drive accessible? I would consider downloading the ISO from the MS website to create a bootable drive for troubleshooting. It's still strange that this is happening despite the firestorm settings. Have you attempted turning off and then turning on your monitor?
V
Velizar06
06-28-2016, 05:53 PM #11

This would be an unusual situation. Do you have an optical drive in your PC or a USB drive accessible? I would consider downloading the ISO from the MS website to create a bootable drive for troubleshooting. It's still strange that this is happening despite the firestorm settings. Have you attempted turning off and then turning on your monitor?

F
73
07-01-2016, 07:22 AM
#12
I've attempted nearly all possibilities I could imagine.
F
Frowning_Clown
07-01-2016, 07:22 AM #12

I've attempted nearly all possibilities I could imagine.

O
oggypop
Member
240
07-01-2016, 01:21 PM
#13
Are there any built-in video connections on your motherboard? If so, attempt to remove all 960 ports and see if you can access Windows through them. This method might allow you to uninstall software like Firestorm. If that fails, consider using a different video output on 960 besides the one you're currently using. If none of these work, a CMOS reset could be an option, though it's unlikely to help. In such cases, creating an ISO or repair drive from another PC might be necessary.
O
oggypop
07-01-2016, 01:21 PM #13

Are there any built-in video connections on your motherboard? If so, attempt to remove all 960 ports and see if you can access Windows through them. This method might allow you to uninstall software like Firestorm. If that fails, consider using a different video output on 960 besides the one you're currently using. If none of these work, a CMOS reset could be an option, though it's unlikely to help. In such cases, creating an ISO or repair drive from another PC might be necessary.

M
Muezzze
Member
60
07-07-2016, 04:16 AM
#14
I managed to access Windows Repair using F11, reset my PC to 9/1/16, and that resolved the issue. Thanks for the assistance.
M
Muezzze
07-07-2016, 04:16 AM #14

I managed to access Windows Repair using F11, reset my PC to 9/1/16, and that resolved the issue. Thanks for the assistance.

Pages (2): Previous 1 2