F5F Stay Refreshed Power Users Overclocking i5 6500 at 5.0ghz

i5 6500 at 5.0ghz

i5 6500 at 5.0ghz

Pages (2): 1 2 Next
J
Jelly1233
Member
190
11-08-2016, 01:10 AM
#1
Hello everyone, I'm just starting out with these threads and have a significant question. My i5 6500 OC'd at 5.0 GHz with an H100i is handling around 85% load. Is this a cause for concern?
J
Jelly1233
11-08-2016, 01:10 AM #1

Hello everyone, I'm just starting out with these threads and have a significant question. My i5 6500 OC'd at 5.0 GHz with an H100i is handling around 85% load. Is this a cause for concern?

L
Lancelot001
Junior Member
3
11-10-2016, 09:10 PM
#2
Benchmarks clearly demonstrate the situation. Though I admire your effort to surpass expectations and manage the 6500 to a somewhat unstable 5.0GHz, you missed the initial guideline for OC. Provide better cooling. It’s likely you’ve already triggered a chain reaction, reducing the lifespan of the CPUs by half. Any additional heat will only worsen the problem, and the impact won’t be proportional—it’s logarithmic. Anticipate more benchmarking to reduce the lifespan from years to months.
L
Lancelot001
11-10-2016, 09:10 PM #2

Benchmarks clearly demonstrate the situation. Though I admire your effort to surpass expectations and manage the 6500 to a somewhat unstable 5.0GHz, you missed the initial guideline for OC. Provide better cooling. It’s likely you’ve already triggered a chain reaction, reducing the lifespan of the CPUs by half. Any additional heat will only worsen the problem, and the impact won’t be proportional—it’s logarithmic. Anticipate more benchmarking to reduce the lifespan from years to months.

H
hydr087
Junior Member
1
11-11-2016, 12:22 AM
#3
5.0GHz on a locked 6500 with a 3.2GHz stock spec is quite a challenge. The temperatures are a bit elevated, but I'm pretty sure you won't be stable. Scale it down.
H
hydr087
11-11-2016, 12:22 AM #3

5.0GHz on a locked 6500 with a 3.2GHz stock spec is quite a challenge. The temperatures are a bit elevated, but I'm pretty sure you won't be stable. Scale it down.

B
bhend7
Junior Member
18
11-11-2016, 12:41 AM
#4
Barty1884 :
5.0GHz on a locked 6500 that is 3.2GHz stock? That's one heck of a BCLCK OC...
Temps are a little high, but I highly doubt you're stable anyway.
Scale that back.
+1 theres no way that is stable, also the Tcase on that CPU is 71, it is definitely throttling at 85 degrees.
Back that down A LOT before you do some damage. If you haven't already.
B
bhend7
11-11-2016, 12:41 AM #4

Barty1884 :
5.0GHz on a locked 6500 that is 3.2GHz stock? That's one heck of a BCLCK OC...
Temps are a little high, but I highly doubt you're stable anyway.
Scale that back.
+1 theres no way that is stable, also the Tcase on that CPU is 71, it is definitely throttling at 85 degrees.
Back that down A LOT before you do some damage. If you haven't already.

X
xoxo_blonde
Member
159
11-11-2016, 11:00 PM
#5
Rogue Leader:
Barty1884:
The 5.0GHz on a locked 6500 with a stock 3.2GHz is quite a challenge...
Temperatures are elevated, but I’m pretty sure you’re not stable either.
Reduce the frequency significantly.
There’s no chance it’ll hold up, plus the Tcase is already at 71 and it’s clearly throttling near 85°C.
Cut back a lot before you cause any damage—especially if you haven’t done so yet.
X
xoxo_blonde
11-11-2016, 11:00 PM #5

Rogue Leader:
Barty1884:
The 5.0GHz on a locked 6500 with a stock 3.2GHz is quite a challenge...
Temperatures are elevated, but I’m pretty sure you’re not stable either.
Reduce the frequency significantly.
There’s no chance it’ll hold up, plus the Tcase is already at 71 and it’s clearly throttling near 85°C.
Cut back a lot before you cause any damage—especially if you haven’t done so yet.

F
FureaMC
Senior Member
564
11-13-2016, 01:15 PM
#6
where are you getting your temps from? screenshot?
F
FureaMC
11-13-2016, 01:15 PM #6

where are you getting your temps from? screenshot?

J
jimmy1822
Junior Member
35
11-13-2016, 03:12 PM
#7
Benchmarks clearly indicate the situation. Though I admire your effort to surpass expectations and manage the 6500 to a somewhat unstable 5.0GHz, you missed the initial guideline for OC. Provide better cooling. It’s likely you’ve already triggered a chain reaction, reducing the lifespan of the CPUs by half. Any more heat buildup will only worsen it. The relationship isn’t straightforward—it’s logarithmic. Future tests should significantly reduce the lifespan to months rather than years.
J
jimmy1822
11-13-2016, 03:12 PM #7

Benchmarks clearly indicate the situation. Though I admire your effort to surpass expectations and manage the 6500 to a somewhat unstable 5.0GHz, you missed the initial guideline for OC. Provide better cooling. It’s likely you’ve already triggered a chain reaction, reducing the lifespan of the CPUs by half. Any more heat buildup will only worsen it. The relationship isn’t straightforward—it’s logarithmic. Future tests should significantly reduce the lifespan to months rather than years.

L
Leumas_R
Member
155
11-28-2016, 02:45 AM
#8
Benchmarks clearly indicate the situation. Your effort to push the 6500 to a stable 5.0GHz was commendable, though it required careful planning. However, you missed the first rule of OC—cooling is essential. It’s likely the CPU suffered some damage, possibly shortening its lifespan significantly. Any additional overheating will worsen the problem, and the impact won’t be linear but logarithmic. Expect more bench tests to reduce the lifespan from years to months. I only tested once at 4.7GHz and lowered it back to 4.5-4.6, wondering if that was the right approach.
L
Leumas_R
11-28-2016, 02:45 AM #8

Benchmarks clearly indicate the situation. Your effort to push the 6500 to a stable 5.0GHz was commendable, though it required careful planning. However, you missed the first rule of OC—cooling is essential. It’s likely the CPU suffered some damage, possibly shortening its lifespan significantly. Any additional overheating will worsen the problem, and the impact won’t be linear but logarithmic. Expect more bench tests to reduce the lifespan from years to months. I only tested once at 4.7GHz and lowered it back to 4.5-4.6, wondering if that was the right approach.

E
EdoubleO
Member
238
12-13-2016, 11:06 PM
#9
Where do you obtain your temperature readings from? I see a screenshot.
No, I'm relying on the CPUID command and recording it each time I run a benchmark or game.
E
EdoubleO
12-13-2016, 11:06 PM #9

Where do you obtain your temperature readings from? I see a screenshot.
No, I'm relying on the CPUID command and recording it each time I run a benchmark or game.

S
50
12-14-2016, 12:21 AM
#10
Rogue Leader:
Where do you get your temperatures from? Screenshot?
No, I'm using CPUID and I log almost every time I run a benchmark or game.
I meant could you share a screenshot?
And yes, 4.5 GHz is a much better idea.
S
spongebobtime2
12-14-2016, 12:21 AM #10

Rogue Leader:
Where do you get your temperatures from? Screenshot?
No, I'm using CPUID and I log almost every time I run a benchmark or game.
I meant could you share a screenshot?
And yes, 4.5 GHz is a much better idea.

Pages (2): 1 2 Next