F5F Stay Refreshed Hardware Desktop You might be experiencing issues with your system, but I'm here to help you troubleshoot.

You might be experiencing issues with your system, but I'm here to help you troubleshoot.

You might be experiencing issues with your system, but I'm here to help you troubleshoot.

G
GeneralSami
Member
60
11-01-2019, 07:22 AM
#1
Last week I attempted to boost my Ryzen 5 3600’s performance via the BIOS on my Gigabyte gaming X motherboard. Since I’m studying IT, I rely on virtual machines for assignments, which limits my ability to use Ryzen Master for manual overclocking. I decided to go straight into the BIOS and adjust settings myself. I set the frequency to 4.2 GHz and voltage to 1.35 volts. For the core X I entered 42 and voltage 135 because I couldn’t include commas or periods. I’m unsure what I was doing, but after saving the changes and restarting, my PC failed to boot. There’s no display signal, yet the graphics card RAM appears to be functioning. All fans spin but don’t reach full speed. Finally, I tried clearing the CMOS again, but it didn’t help. Right now I’m occupied with work, so I haven’t taken my PC to a repair shop or tested another motherboard or CPU. I’m hoping for your advice. I’m open to buying any of those parts again if necessary, as my computer is essential for my job and my life depends on it. Please let me know your thoughts.
G
GeneralSami
11-01-2019, 07:22 AM #1

Last week I attempted to boost my Ryzen 5 3600’s performance via the BIOS on my Gigabyte gaming X motherboard. Since I’m studying IT, I rely on virtual machines for assignments, which limits my ability to use Ryzen Master for manual overclocking. I decided to go straight into the BIOS and adjust settings myself. I set the frequency to 4.2 GHz and voltage to 1.35 volts. For the core X I entered 42 and voltage 135 because I couldn’t include commas or periods. I’m unsure what I was doing, but after saving the changes and restarting, my PC failed to boot. There’s no display signal, yet the graphics card RAM appears to be functioning. All fans spin but don’t reach full speed. Finally, I tried clearing the CMOS again, but it didn’t help. Right now I’m occupied with work, so I haven’t taken my PC to a repair shop or tested another motherboard or CPU. I’m hoping for your advice. I’m open to buying any of those parts again if necessary, as my computer is essential for my job and my life depends on it. Please let me know your thoughts.

E
eryk123621
Member
66
11-04-2019, 10:33 PM
#2
No, I wasn't instructed to check that.
E
eryk123621
11-04-2019, 10:33 PM #2

No, I wasn't instructed to check that.

X
xDarkThund3r
Junior Member
4
11-05-2019, 12:49 AM
#3
Is the motherboard equipped with an error code display? Even when you apply the highest safe voltage—like MSI’s 1.44V limit—there can be minor fluctuations due to meter inaccuracies, resulting in readings around 1.45 to 1.47V. Many users report similar issues after overclocking; some have resolved them by clearing the CMOS, which involves removing the battery for an extended period before reinserting it. Others experienced different problems that might be linked to this situation.
X
xDarkThund3r
11-05-2019, 12:49 AM #3

Is the motherboard equipped with an error code display? Even when you apply the highest safe voltage—like MSI’s 1.44V limit—there can be minor fluctuations due to meter inaccuracies, resulting in readings around 1.45 to 1.47V. Many users report similar issues after overclocking; some have resolved them by clearing the CMOS, which involves removing the battery for an extended period before reinserting it. Others experienced different problems that might be linked to this situation.

Y
yJaaoxD
Member
203
11-05-2019, 01:10 AM
#4
Remove the CMOS chip briefly, then reinsert it. The same problem occurred with my 3900x after months of use; I just needed to reset the BIOS and it worked fine. With the Ryzen, adjusting settings can cause issues—especially when PBO is enabled, which led to the crash you mentioned.
Y
yJaaoxD
11-05-2019, 01:10 AM #4

Remove the CMOS chip briefly, then reinsert it. The same problem occurred with my 3900x after months of use; I just needed to reset the BIOS and it worked fine. With the Ryzen, adjusting settings can cause issues—especially when PBO is enabled, which led to the crash you mentioned.

M
MattHaan
Member
131
11-05-2019, 08:55 PM
#5
The process involved either disconnecting the pin or eliminating the cell. It was performed while the device was unplugged from the power source. Your information should be safe.
M
MattHaan
11-05-2019, 08:55 PM #5

The process involved either disconnecting the pin or eliminating the cell. It was performed while the device was unplugged from the power source. Your information should be safe.

I
iTestify
Member
95
11-07-2019, 02:16 AM
#6
Yes, that's correct.
I
iTestify
11-07-2019, 02:16 AM #6

Yes, that's correct.

A
Apel29
Member
192
11-07-2019, 03:24 AM
#7
It doesn’t show any error message, not even a small LED. I took out the battery for a day and unplugged everything, but there’s still no result.
A
Apel29
11-07-2019, 03:24 AM #7

It doesn’t show any error message, not even a small LED. I took out the battery for a day and unplugged everything, but there’s still no result.

A
Airty1
Junior Member
40
11-07-2019, 09:01 AM
#8
You mentioned everything you said, I gave it a try. It didn’t work. I think I should note this: there’s a burnt odor everywhere in the MB, like it was fried. I’m worried about my CPU too—maybe I messed up again.
A
Airty1
11-07-2019, 09:01 AM #8

You mentioned everything you said, I gave it a try. It didn’t work. I think I should note this: there’s a burnt odor everywhere in the MB, like it was fried. I’m worried about my CPU too—maybe I messed up again.

A
Aerogel
Member
79
11-08-2019, 09:02 AM
#9
It seems the 135V adjustment had a significant impact—I’m struggling to pinpoint exactly what failed, but it’s clear something went wrong. Sorry for the inconvenience.
A
Aerogel
11-08-2019, 09:02 AM #9

It seems the 135V adjustment had a significant impact—I’m struggling to pinpoint exactly what failed, but it’s clear something went wrong. Sorry for the inconvenience.