F5F Stay Refreshed Power Users Overclocking Overclocking setup advice

Overclocking setup advice

Overclocking setup advice

J
JPP_Miam
Member
108
07-29-2024, 05:57 PM
#1
I understand this has been discussed before but I can't locate the exact details. I own an ASUS 970 Pro gaming aura, an FX 6300, Corsair Vengeance 8GB RAM, Sapphire R9 Fury Nitro, Coolermaster Evo 212, and a Thermaltake 650 with a smart PSU. I set the FX 6300 to 4.3 at 1.35v and everything worked fine after four hours on Prime95. No issues found. This morning I restarted my PC but couldn't boot; MB reported a memory error, though I didn’t adjust the settings during overclocking. I reset BIOS and restarted at default. I tried again at 4.2 with 1.32v since stock voltage is 1.21 and CPU is at 3.5. Any suggestions or guidance would be very helpful. This is my first overclocking attempt.
J
JPP_Miam
07-29-2024, 05:57 PM #1

I understand this has been discussed before but I can't locate the exact details. I own an ASUS 970 Pro gaming aura, an FX 6300, Corsair Vengeance 8GB RAM, Sapphire R9 Fury Nitro, Coolermaster Evo 212, and a Thermaltake 650 with a smart PSU. I set the FX 6300 to 4.3 at 1.35v and everything worked fine after four hours on Prime95. No issues found. This morning I restarted my PC but couldn't boot; MB reported a memory error, though I didn’t adjust the settings during overclocking. I reset BIOS and restarted at default. I tried again at 4.2 with 1.32v since stock voltage is 1.21 and CPU is at 3.5. Any suggestions or guidance would be very helpful. This is my first overclocking attempt.

H
HellNether
Senior Member
731
07-29-2024, 05:57 PM
#2
Memory can have errors like this and slip up sometimes, without you even touching them. Nothing to worry about if it just happened once. If the problem persists, I would say you may want to contact the manufacturer of your memory and see if you can get a RMA.
H
HellNether
07-29-2024, 05:57 PM #2

Memory can have errors like this and slip up sometimes, without you even touching them. Nothing to worry about if it just happened once. If the problem persists, I would say you may want to contact the manufacturer of your memory and see if you can get a RMA.

D
DeathbyFrog
Junior Member
35
07-29-2024, 05:57 PM
#3
Memory can have errors like this and slip up sometimes, without you even touching them. Nothing to worry about if it just happened once. If the problem persists, I would say you may want to contact the manufacturer of your memory and see if you can get a RMA.
D
DeathbyFrog
07-29-2024, 05:57 PM #3

Memory can have errors like this and slip up sometimes, without you even touching them. Nothing to worry about if it just happened once. If the problem persists, I would say you may want to contact the manufacturer of your memory and see if you can get a RMA.

O
OOGDRAFUL
Junior Member
34
07-29-2024, 05:57 PM
#4
Thank you for your response. It seems temperatures weren't a factor, as package readings stayed below 52°C and CPU temps never exceeded 62°C in hwmonitor. I'm currently executing prime95 at 4.2 @ 1.32v. The large packet test has been running for 2 hours, and everything is proceeding smoothly. Temperatures are around 55°C for the CPU and 47°C for the package. CPU vcore varies between 1.329 and 1.404.
O
OOGDRAFUL
07-29-2024, 05:57 PM #4

Thank you for your response. It seems temperatures weren't a factor, as package readings stayed below 52°C and CPU temps never exceeded 62°C in hwmonitor. I'm currently executing prime95 at 4.2 @ 1.32v. The large packet test has been running for 2 hours, and everything is proceeding smoothly. Temperatures are around 55°C for the CPU and 47°C for the package. CPU vcore varies between 1.329 and 1.404.

_
_C01
Junior Member
17
07-29-2024, 05:57 PM
#5
Sounds good.
_
_C01
07-29-2024, 05:57 PM #5

Sounds good.

M
Mrender3
Senior Member
412
07-29-2024, 05:57 PM
#6
After 5 hours and 30 minutes of p95, the computer stopped working. It wasn't clear if the system had enough resources or if something went wrong. The temperatures stayed the same as before, only slightly lower. I restarted the machine and everything worked again, so it might have been instability or Windows just needed more time.
M
Mrender3
07-29-2024, 05:57 PM #6

After 5 hours and 30 minutes of p95, the computer stopped working. It wasn't clear if the system had enough resources or if something went wrong. The temperatures stayed the same as before, only slightly lower. I restarted the machine and everything worked again, so it might have been instability or Windows just needed more time.

R
Robotic_Slap
Member
134
07-29-2024, 05:57 PM
#7
You don't have to be 100% stable to be good. On an AMD system I once boosted, Prime95 wasn't stable at all on the original speed. Just aim for stability during tests like Aidia 64 or any other stress test.
R
Robotic_Slap
07-29-2024, 05:57 PM #7

You don't have to be 100% stable to be good. On an AMD system I once boosted, Prime95 wasn't stable at all on the original speed. Just aim for stability during tests like Aidia 64 or any other stress test.

M
MCjeepers1009
Member
212
07-29-2024, 05:57 PM
#8
Thanks for the response. It seems my memory stops working when I increase the CPU speed. It works normally at stock speeds. Could it be that the memory isn't receiving enough voltage to keep up? Should I try raising the voltage slightly? Your advice has been really helpful and I value your guidance!
M
MCjeepers1009
07-29-2024, 05:57 PM #8

Thanks for the response. It seems my memory stops working when I increase the CPU speed. It works normally at stock speeds. Could it be that the memory isn't receiving enough voltage to keep up? Should I try raising the voltage slightly? Your advice has been really helpful and I value your guidance!