F5F Stay Refreshed Power Users Overclocking The system overclocked during a one-hour stress test and has since crashed. Is it still safe to use it?

The system overclocked during a one-hour stress test and has since crashed. Is it still safe to use it?

The system overclocked during a one-hour stress test and has since crashed. Is it still safe to use it?

L
levoyageur92
Posting Freak
807
09-19-2016, 11:14 PM
#1
i increased my cpu's clock speed but it kept running smoothly in aida 64 for more than an hour before failing. given that my system won't be heavily loaded, is this overclock a safe choice for everyday use? i'm mainly gaming, not doing anything intensive like rendering. if i play games and the cpu usage stays around 50%, what's the chance of a crash? i'd prefer a very low probability—0.0001% or less would be fine. also, i've reached 1.45v, which is amd's recommended max for the vcore. going higher could still keep temperatures under 75c, which is safe at this voltage. nb, the soc voltage is currently 1.1v, and i'm considering pushing it to 1.25v as some others did. downclocking to 100mhz seems like a better option, but i'd rather push my chip if possible. any advice would be appreciated.
L
levoyageur92
09-19-2016, 11:14 PM #1

i increased my cpu's clock speed but it kept running smoothly in aida 64 for more than an hour before failing. given that my system won't be heavily loaded, is this overclock a safe choice for everyday use? i'm mainly gaming, not doing anything intensive like rendering. if i play games and the cpu usage stays around 50%, what's the chance of a crash? i'd prefer a very low probability—0.0001% or less would be fine. also, i've reached 1.45v, which is amd's recommended max for the vcore. going higher could still keep temperatures under 75c, which is safe at this voltage. nb, the soc voltage is currently 1.1v, and i'm considering pushing it to 1.25v as some others did. downclocking to 100mhz seems like a better option, but i'd rather push my chip if possible. any advice would be appreciated.

K
KaiVLG
Junior Member
5
09-20-2016, 06:52 AM
#2
Both factors play a role. Frequency influences the likelihood of errors during each operation, with increased CPU usage leading to more tasks processed per second. Consequently, greater load results in a higher probability of error over time. Running at maximum frequency with half the load should generally produce fewer errors on average compared to full capacity. The specific type of load also matters, which explains why stability can vary between different stress tests.
K
KaiVLG
09-20-2016, 06:52 AM #2

Both factors play a role. Frequency influences the likelihood of errors during each operation, with increased CPU usage leading to more tasks processed per second. Consequently, greater load results in a higher probability of error over time. Running at maximum frequency with half the load should generally produce fewer errors on average compared to full capacity. The specific type of load also matters, which explains why stability can vary between different stress tests.

S
Schmallie
Member
53
09-28-2016, 04:19 AM
#3
You run the risk of random crashes, but they should be far less frequent than once an hour. I believe there's also a small possibility of occasional data corruption.
S
Schmallie
09-28-2016, 04:19 AM #3

You run the risk of random crashes, but they should be far less frequent than once an hour. I believe there's also a small possibility of occasional data corruption.

C
Chiefly
Member
66
09-28-2016, 06:20 AM
#4
TJ Hooker :
You run the risk of random crashed, but they should be far less frequent than once an hour. I believe there's also a small possibility of occasional data corruption.
is it about hitting the core frequency that triggers the crash or is it the cpu load (e.g. 100% load) that causes a crash. which one is more likely to cause a crash? in games i imagine the frequency will always be as high as possible whereas load is usually not ever 100%
C
Chiefly
09-28-2016, 06:20 AM #4

TJ Hooker :
You run the risk of random crashed, but they should be far less frequent than once an hour. I believe there's also a small possibility of occasional data corruption.
is it about hitting the core frequency that triggers the crash or is it the cpu load (e.g. 100% load) that causes a crash. which one is more likely to cause a crash? in games i imagine the frequency will always be as high as possible whereas load is usually not ever 100%

F
FoxGamer_66
Junior Member
8
10-06-2016, 02:47 AM
#5
Both factors play a role. Frequency influences the likelihood of errors during each operation, with increased CPU usage leading to more tasks processed per second. Consequently, greater load results in a higher probability of error over time. Running at maximum frequency with half the load should produce fewer errors on average compared to full capacity. The specific type of load also matters, which explains why stability can vary between different stress tests.
F
FoxGamer_66
10-06-2016, 02:47 AM #5

Both factors play a role. Frequency influences the likelihood of errors during each operation, with increased CPU usage leading to more tasks processed per second. Consequently, greater load results in a higher probability of error over time. Running at maximum frequency with half the load should produce fewer errors on average compared to full capacity. The specific type of load also matters, which explains why stability can vary between different stress tests.

R
Raze_FR
Member
200
10-13-2016, 05:10 PM
#6
Both would help reduce errors. The frequency influences error chances, with more operations happening when CPU load is higher. Greater load increases the likelihood of mistakes per second. Running at full capacity with half the load should lead to fewer errors overall. Load variations can also play a role, which explains why stability might differ between tests.
R
Raze_FR
10-13-2016, 05:10 PM #6

Both would help reduce errors. The frequency influences error chances, with more operations happening when CPU load is higher. Greater load increases the likelihood of mistakes per second. Running at full capacity with half the load should lead to fewer errors overall. Load variations can also play a role, which explains why stability might differ between tests.