F5F Stay Refreshed Power Users Overclocking Case: Overclocking gone wrong, what could be the issue?

Case: Overclocking gone wrong, what could be the issue?

Case: Overclocking gone wrong, what could be the issue?

Pages (2): Previous 1 2
S
SavoiaB
Junior Member
37
07-19-2016, 01:47 AM
#11
Enough said? I understand I made a mistake and am aware it was a stupid move, but if you have any insight as to what went wrong I'd be interested to hear more than "enough said." That being said I'm gratefull you're willing to help.
S
SavoiaB
07-19-2016, 01:47 AM #11

Enough said? I understand I made a mistake and am aware it was a stupid move, but if you have any insight as to what went wrong I'd be interested to hear more than "enough said." That being said I'm gratefull you're willing to help.

A
ApexNinja02
Member
166
07-20-2016, 01:50 AM
#12
Sorry about that. Since the bios clear didn't resolve the issue, it seems a component has failed. You should begin replacing parts one by one to identify which part is defective.
A
ApexNinja02
07-20-2016, 01:50 AM #12

Sorry about that. Since the bios clear didn't resolve the issue, it seems a component has failed. You should begin replacing parts one by one to identify which part is defective.

B
Bazza130202
Senior Member
386
07-25-2016, 11:02 AM
#13
If you completed that guide and activated the llc, the voltage would have been greater than what you reported, indicating we’re uncertain about the actual value when it failed. Are you certain about the wattage each vCore consumes at each clock speed? Understanding the voltage increase per llc increment will help estimate the original power draw. The sabertooth with llc on one notch above standard (25% and 110%, which is one notch higher than regular) could add up to 0.05 volts, so a fourfold increase would result in around 1.5 volts maximum. Given that this only occurred after saving and restarting, it likely points to an excessively high voltage drawing more current than the PSU and motherboard could handle. It’s unclear if any safety protections exist to stop such unsafe configurations, even if they were present. This was a disappointing outcome.

Moving forward, my plan is to silence the fans using the standard method from Amazon, which should resolve the noise issue.
B
Bazza130202
07-25-2016, 11:02 AM #13

If you completed that guide and activated the llc, the voltage would have been greater than what you reported, indicating we’re uncertain about the actual value when it failed. Are you certain about the wattage each vCore consumes at each clock speed? Understanding the voltage increase per llc increment will help estimate the original power draw. The sabertooth with llc on one notch above standard (25% and 110%, which is one notch higher than regular) could add up to 0.05 volts, so a fourfold increase would result in around 1.5 volts maximum. Given that this only occurred after saving and restarting, it likely points to an excessively high voltage drawing more current than the PSU and motherboard could handle. It’s unclear if any safety protections exist to stop such unsafe configurations, even if they were present. This was a disappointing outcome.

Moving forward, my plan is to silence the fans using the standard method from Amazon, which should resolve the noise issue.

R
Redz
Member
118
07-25-2016, 04:08 PM
#14
Ensure the CMOS jumper is set, disconnect the CMOS battery, and remove power from your setup. Keep this for at least 15 minutes. Replace the jumper, restore the battery, reconnect power, and attempt to power on. If no response remains - goodbye.
R
Redz
07-25-2016, 04:08 PM #14

Ensure the CMOS jumper is set, disconnect the CMOS battery, and remove power from your setup. Keep this for at least 15 minutes. Replace the jumper, restore the battery, reconnect power, and attempt to power on. If no response remains - goodbye.

Pages (2): Previous 1 2