F5F Stay Refreshed Power Users Overclocking Check if your overclocked i5 4670k can handle higher temperatures safely.

Check if your overclocked i5 4670k can handle higher temperatures safely.

Check if your overclocked i5 4670k can handle higher temperatures safely.

Pages (2): 1 2 Next
D
DrUnKeN_TiGeR
Junior Member
36
01-20-2016, 07:25 AM
#1
Hi, i recently overclocked my i5 4670k to 4.3ghz at 1.26volts with adaptive settings. it reached up to 1.28volts during a one-hour session of playing GTA V. the image you shared shows the temperatures. can these readings be safe for continuous use and gaming?
D
DrUnKeN_TiGeR
01-20-2016, 07:25 AM #1

Hi, i recently overclocked my i5 4670k to 4.3ghz at 1.26volts with adaptive settings. it reached up to 1.28volts during a one-hour session of playing GTA V. the image you shared shows the temperatures. can these readings be safe for continuous use and gaming?

A
alazykitten
Junior Member
22
01-20-2016, 01:21 PM
#2
The temperatures are acceptable, but you should halt when they reach the high seventies.
A
alazykitten
01-20-2016, 01:21 PM #2

The temperatures are acceptable, but you should halt when they reach the high seventies.

H
Hendog_the_1st
Junior Member
7
01-20-2016, 03:34 PM
#3
Ne0Wolf7 :
Those temps are fine, you really want to stop once you near the eighties.
Hey man i realised by downclocking my cache to 3.4ghz i can get 4.3ghz at 1.23v
http://imgur.com/a/4YtyK
Well this morning i got bsod so i bumped my vcore to 1.24v to see if its stable
H
Hendog_the_1st
01-20-2016, 03:34 PM #3

Ne0Wolf7 :
Those temps are fine, you really want to stop once you near the eighties.
Hey man i realised by downclocking my cache to 3.4ghz i can get 4.3ghz at 1.23v
http://imgur.com/a/4YtyK
Well this morning i got bsod so i bumped my vcore to 1.24v to see if its stable

L
lWiltedl
Junior Member
22
01-21-2016, 01:25 PM
#4
I noticed by lowering my cache speed to 3.4ghz I was able to reach 4.3ghz at 1.23v.
I also got BSOD this morning, so I increased my Vcore to see if it would stabilize.
Yes, that worked out and it was the right approach. You can do all the stability checks you like, but the main test is using your apps or games.
If you experience BSODs, raise your Vcore a bit as you did before. After that, keep monitoring temperatures to ensure they stay under 80C.
L
lWiltedl
01-21-2016, 01:25 PM #4

I noticed by lowering my cache speed to 3.4ghz I was able to reach 4.3ghz at 1.23v.
I also got BSOD this morning, so I increased my Vcore to see if it would stabilize.
Yes, that worked out and it was the right approach. You can do all the stability checks you like, but the main test is using your apps or games.
If you experience BSODs, raise your Vcore a bit as you did before. After that, keep monitoring temperatures to ensure they stay under 80C.

_
_juhuaxia12
Member
61
01-21-2016, 09:54 PM
#5
I noticed by lowering my cache speed to 3.4ghz I was able to reach 4.3ghz at 1.23v.
I also got BSOD this morning, so I increased my Vcore to see if it would be stable.
Yes, that was the correct approach. You should still perform stability tests, but the main test is running your apps and games.
If you experience BSODs, try raising the Vcore slightly as you did before.
When adjusting, keep an eye on temperatures to ensure they stay below 80C.
My gaming temps were around 72C max and about 63C average, with a few cores lower than that. I prefer 1.25-26vcore and adaptive settings, which give 1.28-29v for 4.4ghz.
However, I didn’t want to risk it and test stability, so I kept the original settings.
But before I knew it, I realized cache downclocking doesn’t hurt performance—I almost succeeded with this chip.
_
_juhuaxia12
01-21-2016, 09:54 PM #5

I noticed by lowering my cache speed to 3.4ghz I was able to reach 4.3ghz at 1.23v.
I also got BSOD this morning, so I increased my Vcore to see if it would be stable.
Yes, that was the correct approach. You should still perform stability tests, but the main test is running your apps and games.
If you experience BSODs, try raising the Vcore slightly as you did before.
When adjusting, keep an eye on temperatures to ensure they stay below 80C.
My gaming temps were around 72C max and about 63C average, with a few cores lower than that. I prefer 1.25-26vcore and adaptive settings, which give 1.28-29v for 4.4ghz.
However, I didn’t want to risk it and test stability, so I kept the original settings.
But before I knew it, I realized cache downclocking doesn’t hurt performance—I almost succeeded with this chip.

M
MissCGaming
Member
116
01-23-2016, 04:01 PM
#6
I noticed by lowering my cache speed to 3.4ghz I achieved a stable 4.3ghz at 1.23v.
This morning I experienced BSOD, so I increased my Vcore to see if it would stabilize.
Yes, that was the correct approach.
You can perform all stability checks, but the main test is running your apps or games.
If you encounter BSODs, raise your Vcore slightly as before.
After doing that, keep monitoring temperatures to ensure they stay under 80°C.
M
MissCGaming
01-23-2016, 04:01 PM #6

I noticed by lowering my cache speed to 3.4ghz I achieved a stable 4.3ghz at 1.23v.
This morning I experienced BSOD, so I increased my Vcore to see if it would stabilize.
Yes, that was the correct approach.
You can perform all stability checks, but the main test is running your apps or games.
If you encounter BSODs, raise your Vcore slightly as before.
After doing that, keep monitoring temperatures to ensure they stay under 80°C.

A
Ash_kachum
Junior Member
19
01-23-2016, 06:44 PM
#7
I got back at 1.24v but I think it wasn't a standard setting and my audio was acting odd too.
The computer restarted after a bugcheck. The details were: 0x00000124 with specific offsets and a dump saved at C:\WINDOWS\MEMORY.DMP. Report ID: 27083aad-332f-47dc-81d4-29d7f7bbe3fa.
It looks like your Vcore was too low—try 1.25V next time.
A
Ash_kachum
01-23-2016, 06:44 PM #7

I got back at 1.24v but I think it wasn't a standard setting and my audio was acting odd too.
The computer restarted after a bugcheck. The details were: 0x00000124 with specific offsets and a dump saved at C:\WINDOWS\MEMORY.DMP. Report ID: 27083aad-332f-47dc-81d4-29d7f7bbe3fa.
It looks like your Vcore was too low—try 1.25V next time.

M
MinecraftEuan
Member
87
01-24-2016, 02:38 PM
#8
burnhamjs :
Frsty98 :
I managed to boot at 1.24v, but I think it wasn't a standard one and my audio issues were pretty odd.
🙁
The system has restarted after a bugcheck. The details are: 0x00000124 (0x0000000000000000, 0xffffe48dee9eb028, 0x00000000bf800000, 0x0000000000000124). A dump was saved at: C:\WINDOWS\MEMORY.DMP. Looks like you went too low on your Vcore. Try 1.25V.
I increased the Vcore to 1.24v again, but it still boots. If it fails, I’ll try downclocking to 4.2ghz...
M
MinecraftEuan
01-24-2016, 02:38 PM #8

burnhamjs :
Frsty98 :
I managed to boot at 1.24v, but I think it wasn't a standard one and my audio issues were pretty odd.
🙁
The system has restarted after a bugcheck. The details are: 0x00000124 (0x0000000000000000, 0xffffe48dee9eb028, 0x00000000bf800000, 0x0000000000000124). A dump was saved at: C:\WINDOWS\MEMORY.DMP. Looks like you went too low on your Vcore. Try 1.25V.
I increased the Vcore to 1.24v again, but it still boots. If it fails, I’ll try downclocking to 4.2ghz...

T
TheBozoPlays
Senior Member
642
01-25-2016, 07:00 PM
#9
I got booted up at 1.24v but I think it wasn’t normal and my audio was acting odd too.
The system has rebooted after a bugcheck. The details were: 0x00000124 with specific offsets and a dump saved at C:\WINDOWS\MEMORY.DMP (Report Id: 27083aad-332f-47dc-81d4-29d7f7bbe3fa).
It looks like your Vcore was too low. Try 1.25v, then 1.245v, and if that still doesn’t work, consider downclocking to 4.2GHz.
These voltages are okay as long as temperatures stay under 80°C.
T
TheBozoPlays
01-25-2016, 07:00 PM #9

I got booted up at 1.24v but I think it wasn’t normal and my audio was acting odd too.
The system has rebooted after a bugcheck. The details were: 0x00000124 with specific offsets and a dump saved at C:\WINDOWS\MEMORY.DMP (Report Id: 27083aad-332f-47dc-81d4-29d7f7bbe3fa).
It looks like your Vcore was too low. Try 1.25v, then 1.245v, and if that still doesn’t work, consider downclocking to 4.2GHz.
These voltages are okay as long as temperatures stay under 80°C.

S
Star_Lars
Member
175
01-27-2016, 02:33 AM
#10
I got booted at 1.24v but I’m not sure if that was normal. My audio also acted odd.
The system has rebooted after a bugcheck. The details are: 0x00000124, with some specific offsets and a dump saved at C:\WINDOWS\MEMORY.DMP. Report ID is 27083aad-332f-47dc-81d4-29d7f7bbe3fa.
It looks like your Vcore was too low. Try 1.25V. I increased it to 1.24v again but still got boot issues. If that fails, I’ll try downclocking to 4.2GHz.
I didn’t really test at 4.4GHz for a while—I don’t want to risk damaging my chip. I passed Cinebench R15 with a score of 95 for 5 minutes and temperatures were around 80°C. I’m cautious because I’m using an air cooler Hyper 212 EVO, but I might need to buy a Corsair H100i.
S
Star_Lars
01-27-2016, 02:33 AM #10

I got booted at 1.24v but I’m not sure if that was normal. My audio also acted odd.
The system has rebooted after a bugcheck. The details are: 0x00000124, with some specific offsets and a dump saved at C:\WINDOWS\MEMORY.DMP. Report ID is 27083aad-332f-47dc-81d4-29d7f7bbe3fa.
It looks like your Vcore was too low. Try 1.25V. I increased it to 1.24v again but still got boot issues. If that fails, I’ll try downclocking to 4.2GHz.
I didn’t really test at 4.4GHz for a while—I don’t want to risk damaging my chip. I passed Cinebench R15 with a score of 95 for 5 minutes and temperatures were around 80°C. I’m cautious because I’m using an air cooler Hyper 212 EVO, but I might need to buy a Corsair H100i.

Pages (2): 1 2 Next