F5F Stay Refreshed Power Users Overclocking Your GPU Core and Memory MHz during Overclock for GTX1070

Your GPU Core and Memory MHz during Overclock for GTX1070

Your GPU Core and Memory MHz during Overclock for GTX1070

X
XIVphantom
Junior Member
4
07-14-2016, 09:46 PM
#1
Hello,
The GPU log you shared shows the sensor readings for your GTX 1070. To understand the real Core/MHz values, you may need to apply a multiplier based on the reported memory frequency. For the CPU, simply check the top numbers in the log. Let me know if you need further clarification.
Thank you
X
XIVphantom
07-14-2016, 09:46 PM #1

Hello,
The GPU log you shared shows the sensor readings for your GTX 1070. To understand the real Core/MHz values, you may need to apply a multiplier based on the reported memory frequency. For the CPU, simply check the top numbers in the log. Let me know if you need further clarification.
Thank you

L
LForLoser_
Member
79
07-20-2016, 10:53 AM
#2
Hello,
Here is the GPU log from running Fire Strike Ultra on GTX 1070.
You can find more details at the provided link.
Regarding your questions: you should multiply the memory speed by 4 to get the real value. Your core speed appears to reach around 2063, so adjusting the fan curve is recommended—especially since it changes significantly at high temperatures.
L
LForLoser_
07-20-2016, 10:53 AM #2

Hello,
Here is the GPU log from running Fire Strike Ultra on GTX 1070.
You can find more details at the provided link.
Regarding your questions: you should multiply the memory speed by 4 to get the real value. Your core speed appears to reach around 2063, so adjusting the fan curve is recommended—especially since it changes significantly at high temperatures.

X
71
07-20-2016, 03:53 PM
#3
Here is the updated version of your message:

Hey everyone, since this thread was already active, I didn’t think it needed a new one. If there’s a better place to ask, please let me know.
I’ve shared the details on how far I pushed my Gigabyte GTX 1070 G1. Interestingly, the clock rates were slightly higher before. I tested it with several hours of gameplay, ran through both Heaven and Valley benchmarks, and stress-tested it using MSi Kombustor for over five hours without any problems. However, when I ran the Firestrike benchmark, it crashed. I adjusted the clocks to match what’s shown in the link below, and it seems stable in Firestrike now. I’m curious if there are any known stability concerns with the Firestrike benchmark on Windows 10 64-bit.
Additionally, I was wondering how to assess the overall bandwidth of my memory after overclocking. The base speed listed is 8008 MHz, but GPU-Z shows the memory clock at 2265 MHz. Any guidance would be really appreciated.
Thanks in advance.
http://i.imgur.com/yCLjI3H.jpg
X
xXMin3rCraftXx
07-20-2016, 03:53 PM #3

Here is the updated version of your message:

Hey everyone, since this thread was already active, I didn’t think it needed a new one. If there’s a better place to ask, please let me know.
I’ve shared the details on how far I pushed my Gigabyte GTX 1070 G1. Interestingly, the clock rates were slightly higher before. I tested it with several hours of gameplay, ran through both Heaven and Valley benchmarks, and stress-tested it using MSi Kombustor for over five hours without any problems. However, when I ran the Firestrike benchmark, it crashed. I adjusted the clocks to match what’s shown in the link below, and it seems stable in Firestrike now. I’m curious if there are any known stability concerns with the Firestrike benchmark on Windows 10 64-bit.
Additionally, I was wondering how to assess the overall bandwidth of my memory after overclocking. The base speed listed is 8008 MHz, but GPU-Z shows the memory clock at 2265 MHz. Any guidance would be really appreciated.
Thanks in advance.
http://i.imgur.com/yCLjI3H.jpg

M
monkeyboo2004
Member
117
07-20-2016, 09:27 PM
#4
Hello,
Here is the GPU log for Fire Strike Ultra on GTX 1070.
You can find more details at the provided link.
Regarding your questions: the memory speed in the log was recorded at 2304, but you should multiply it by 4 to get the actual value. For the CPU, check the highest number at the bottom of the log.
Your core speed appears to be reaching around 2063, and it seems the fan curve needs adjustment—especially since it changes abruptly from 42% to 100% at 65°C.
M
monkeyboo2004
07-20-2016, 09:27 PM #4

Hello,
Here is the GPU log for Fire Strike Ultra on GTX 1070.
You can find more details at the provided link.
Regarding your questions: the memory speed in the log was recorded at 2304, but you should multiply it by 4 to get the actual value. For the CPU, check the highest number at the bottom of the log.
Your core speed appears to be reaching around 2063, and it seems the fan curve needs adjustment—especially since it changes abruptly from 42% to 100% at 65°C.

R
razorlazer82
Junior Member
21
07-22-2016, 06:55 PM
#5
Here is a revised version of your message:

Hello,

This is the GPU log from running Fire Strike Ultra on a GTX 1070. You can find it here: https://www.dropbox.com/s/7mnel1p1nep8h4...g.txt?dl=0

Could you clarify how to obtain the actual Core/Memory MHz value from this log? From what I see, the memory reached its maximum at 2304. Do you need to apply a multiplier to that number? For the CPU, simply scroll down and check the highest recorded value.

Thank you!
R
razorlazer82
07-22-2016, 06:55 PM #5

Here is a revised version of your message:

Hello,

This is the GPU log from running Fire Strike Ultra on a GTX 1070. You can find it here: https://www.dropbox.com/s/7mnel1p1nep8h4...g.txt?dl=0

Could you clarify how to obtain the actual Core/Memory MHz value from this log? From what I see, the memory reached its maximum at 2304. Do you need to apply a multiplier to that number? For the CPU, simply scroll down and check the highest recorded value.

Thank you!

T
TheMineSeven
Member
74
07-31-2016, 12:38 AM
#6
Adjust the memory speed by a factor of four. Your core speed appears to be reaching its peak around 2063. The fan curve needs fixing—it increases from 42% to 100% at 65°C. Thank you for the details.
I've already set the fan to full capacity before beginning Fire Strike Ultra, which might explain why GPU-Z detected it earlier.
I tested with a clock speed of +190 and memory frequency at +600Mhz; the log shows a top value of 2100.5 clock. It's unclear what clock setting is accurate because the GPU updates its readings automatically.
Based on this, I estimate the optimal range to be between 2063 and 2100.5 / 9216 memory.
T
TheMineSeven
07-31-2016, 12:38 AM #6

Adjust the memory speed by a factor of four. Your core speed appears to be reaching its peak around 2063. The fan curve needs fixing—it increases from 42% to 100% at 65°C. Thank you for the details.
I've already set the fan to full capacity before beginning Fire Strike Ultra, which might explain why GPU-Z detected it earlier.
I tested with a clock speed of +190 and memory frequency at +600Mhz; the log shows a top value of 2100.5 clock. It's unclear what clock setting is accurate because the GPU updates its readings automatically.
Based on this, I estimate the optimal range to be between 2063 and 2100.5 / 9216 memory.

G
GmC_Axel
Junior Member
4
08-04-2016, 06:42 AM
#7
Kagemaru shared his experience with the Gigabyte GTX 1070 G1, noting he had previously achieved higher clock rates before. He tested it with several hours of gameplay and ran benchmarks in Heaven and Valley, but encountered crashes during Firestrike benchmarking. He adjusted the clocks to match the stable setting in the provided link and is seeking information about stability issues on Windows 10 64-bit for Firestrike. He also asked about methods to assess overall memory bandwidth after overclocking, mentioning discrepancies between his GPU-Z reading (2265 MHz) and the GB Extreme Utility results (8008 MHz). He appreciated any guidance and provided the link.
G
GmC_Axel
08-04-2016, 06:42 AM #7

Kagemaru shared his experience with the Gigabyte GTX 1070 G1, noting he had previously achieved higher clock rates before. He tested it with several hours of gameplay and ran benchmarks in Heaven and Valley, but encountered crashes during Firestrike benchmarking. He adjusted the clocks to match the stable setting in the provided link and is seeking information about stability issues on Windows 10 64-bit for Firestrike. He also asked about methods to assess overall memory bandwidth after overclocking, mentioning discrepancies between his GPU-Z reading (2265 MHz) and the GB Extreme Utility results (8008 MHz). He appreciated any guidance and provided the link.