- Jul 8, 2019
- 3
- 1
- 10
Hi,
I recently built my first own PC. On stock settings, everything worked fine. I tried to overclock it a little bit, but first the specs: Ryzen 7 1700, Gigabyte Vega 56, 16 GB G-Skill Aegis 3000MHz, MSI B450M-PRO VDH Plus, Thermaltake Smart RGB 600W. I achieved a stable 3.6 GHz on the CPU at 1.125 V. I tried going above that but the temperatures were unacceptable (stock cooler) or the system crashed. I set it back to 3.6 GHz (using Ryzen Master) and restarted the system. Just as normal, the fans start spinning. However, after a second the fans turn off (as well as the green CPU cooler light) and the system automatically restarts. I tried resetting the BIOS using the jumper method. Since the CPU cooler lights up white instead of green now, I assume it was reset just like it was supposed to. The problem is: the EZ-Debug CPU-LED lights up now (just the CPU light, not DRAM). After roughly 3s it shortly turns off and right back on again. All fans are spinning, but I don't get any video signal. The power LED on the case is on as well. I checked the EPS connector as well as all others. They are firmly locked in place. The BIOS is updated to the most recent version. After approximately 30 mins of this bootloop madness, the CPU-LED suddenly didn't turn back on. Still no video signal or any decrease in fan speed (the CPU fan seems to run at full speed judging by the loudness). If I press the reset switch the LED turns back on.
Any help is greatly appreciated.
Bastian
UPDATE: I did some testing with my multimeter and I found out that the 12V on the EPS connector are working just fine. When I unplug the connector and start the PC, I still don't get any beeps from the Mainboard speaker. The only difference is that the CPU light doesn't turn off every 2-3 seconds whereas when the connector is plugged in it turns off for ~.2 seconds every 2-3 seconds. The problem is still persistent.
UPDATE 2: Problem solved. Sorry guys, I accidentally jumped the JCI pins instead of JBAT. I have triggered a case intrusion alert that way... I don't know why it affected the PC in any way since I didn't even configure CI but I did a correct reset now and everything is up and running again.
I recently built my first own PC. On stock settings, everything worked fine. I tried to overclock it a little bit, but first the specs: Ryzen 7 1700, Gigabyte Vega 56, 16 GB G-Skill Aegis 3000MHz, MSI B450M-PRO VDH Plus, Thermaltake Smart RGB 600W. I achieved a stable 3.6 GHz on the CPU at 1.125 V. I tried going above that but the temperatures were unacceptable (stock cooler) or the system crashed. I set it back to 3.6 GHz (using Ryzen Master) and restarted the system. Just as normal, the fans start spinning. However, after a second the fans turn off (as well as the green CPU cooler light) and the system automatically restarts. I tried resetting the BIOS using the jumper method. Since the CPU cooler lights up white instead of green now, I assume it was reset just like it was supposed to. The problem is: the EZ-Debug CPU-LED lights up now (just the CPU light, not DRAM). After roughly 3s it shortly turns off and right back on again. All fans are spinning, but I don't get any video signal. The power LED on the case is on as well. I checked the EPS connector as well as all others. They are firmly locked in place. The BIOS is updated to the most recent version. After approximately 30 mins of this bootloop madness, the CPU-LED suddenly didn't turn back on. Still no video signal or any decrease in fan speed (the CPU fan seems to run at full speed judging by the loudness). If I press the reset switch the LED turns back on.
Any help is greatly appreciated.
Bastian
UPDATE: I did some testing with my multimeter and I found out that the 12V on the EPS connector are working just fine. When I unplug the connector and start the PC, I still don't get any beeps from the Mainboard speaker. The only difference is that the CPU light doesn't turn off every 2-3 seconds whereas when the connector is plugged in it turns off for ~.2 seconds every 2-3 seconds. The problem is still persistent.
UPDATE 2: Problem solved. Sorry guys, I accidentally jumped the JCI pins instead of JBAT. I have triggered a case intrusion alert that way... I don't know why it affected the PC in any way since I didn't even configure CI but I did a correct reset now and everything is up and running again.
Last edited:
Facebook
Twitter
Instagram