rdhoore108
New member
- Joined
- Apr 13, 2014
- Messages
- 1
I know this thread is abandoned, but in case other people like me, having the same trouble after overclocking, also see it as one of the first results in Google, I may add here what solved it for me.
So I had the same trouble: had changed overclocking settings (on a Gigabyte GA-F2A88XN-WIFI mobo with AMD A10-6800K APU) using Gigabyte's EasyTune6 tool, and after rebooting to take effect, the screen would simply remain black. No beeps, no hard drive light, no nothing. Resetting bios with the jumper on the motherboard (and power disconnected), did nothing. Tried removing one RAM stick, etc, most of the good troubleshooting stuff that everyone advised here, I had tried already.
Then, as I was reading this forum thread on my own pc, suddenly to my big surprise, I saw that Windows had tried to boot on the troubled pc. Well, it got stuck in the middle, but at least I knew my components were still alive. So, I pressed reset, and waited for what seemed eternity (like a minute or so), and indeed, suddenly my hard drive LED blinked once, and I was able to enter the BIOS with the DEL key. There I could load my previously saved safe defaults, and all was well. :thumb:
I decided to share this, as in my > 25 years of dealing with computers, I had never encountered this behavior of a very much delayed boot. And also no one else mentioned this here as a possible scenario, so perhaps I'm not the only one for whom this is new. One usually wants to switch off the pc in a failed overclock as soon as possible, to avoid something would fry, so waiting is not usually suggested anyway... I don't know why it took so very long to "quick boot" in this particular setup, and I'm not going to speculate about it, I just report it here so that hopefully one day someone else will benefit from it.
By the way, if you have the same hardware as mine and want to overclock, I strongly suggest doing it in the BIOS, don't use Gigabyte's ET6 tool... And save your BIOS original settings first ("Save Profile" in the "Save & Exit" tab), because loading defaults does not seem to reset the overclocking settings, at least not in BIOS version F4b.
So I had the same trouble: had changed overclocking settings (on a Gigabyte GA-F2A88XN-WIFI mobo with AMD A10-6800K APU) using Gigabyte's EasyTune6 tool, and after rebooting to take effect, the screen would simply remain black. No beeps, no hard drive light, no nothing. Resetting bios with the jumper on the motherboard (and power disconnected), did nothing. Tried removing one RAM stick, etc, most of the good troubleshooting stuff that everyone advised here, I had tried already.
Then, as I was reading this forum thread on my own pc, suddenly to my big surprise, I saw that Windows had tried to boot on the troubled pc. Well, it got stuck in the middle, but at least I knew my components were still alive. So, I pressed reset, and waited for what seemed eternity (like a minute or so), and indeed, suddenly my hard drive LED blinked once, and I was able to enter the BIOS with the DEL key. There I could load my previously saved safe defaults, and all was well. :thumb:
I decided to share this, as in my > 25 years of dealing with computers, I had never encountered this behavior of a very much delayed boot. And also no one else mentioned this here as a possible scenario, so perhaps I'm not the only one for whom this is new. One usually wants to switch off the pc in a failed overclock as soon as possible, to avoid something would fry, so waiting is not usually suggested anyway... I don't know why it took so very long to "quick boot" in this particular setup, and I'm not going to speculate about it, I just report it here so that hopefully one day someone else will benefit from it.
By the way, if you have the same hardware as mine and want to overclock, I strongly suggest doing it in the BIOS, don't use Gigabyte's ET6 tool... And save your BIOS original settings first ("Save Profile" in the "Save & Exit" tab), because loading defaults does not seem to reset the overclocking settings, at least not in BIOS version F4b.