Cpu cores overheeting

[Superteick245]

Hi, ive just started a game Leage and i cheke my temps (as i do every day) to see that everyting is workig but 2 cores of my i5-4670k was 127 degrees celsius and the other ones was 50 degrees. What does this men ?

[SpiralTTGL]

try a different monitoring software

[pxnguinPr3]

18 minutes ago, Superteick245 said:

Hi, ive just started a game Leage and i cheke my temps (as i do every day) to see that everyting is workig but 2 cores of my i5-4670k was 127 degrees celsius and the other ones was 50 degrees. What does this men ? 

There wouldnt be that much of a difference, either two of the thermometers are just broken, or your monitoring software is bad.

[Superteick245]

10 minutes ago, SpiralTTGL said:

try a different monitoring software

Wow, i didnt think about that. Guess corsair link is not working or my watercooler is to old to register temps well. Thank you so mutch.

Working fine.

[Superteick245]

9 minutes ago, pxnguinPr3 said:

There wouldnt be that much of a difference, either two of the thermometers are just broken, or your monitoring software is bad.

Yhe, realthemp worked better. But thank you for trying to help.

[mariushm]

Temperatures like 127 degrees or 255 or 256 degrees are pretty much always incorrect.

 

Numbers are stored in memory using one or several bytes, where each byte has 8 bits. Each bit has two states, 1 or 0, so a byte can hold a number between 0 and 255, or from -127 to 128 (127 + 128 + the 0 value = 256 values in total).

The 127 value is exactly 7 bits set to 1: 0111 1111

 

It's unlikely you'll get such a reading from the sensor and it's more likely the software is incorrectly reading some data from memory that isn't updated with the sensor information, so the software always receives this 127 value, bogus..

 

Most sensors will report a 10 bit (0..1023) or 12bit (0..4095) or 16 bit (0..32768) value and you divide these readings by some value to get decimals in your temperature readings for example your 10 bit : 0..1023 is treated as -512..511 and then you divide 0..511 by 4 (because the sensor has a 0.25c step) ... so for example if the software reads value 717, then software substracts 512 to change 0..1023 to -512 .. 511 and you get 205, which then is divided by 4 (because it's dealing with a 0.25c per bit) so 205 gets converted to 51.25 degrees Celsius and that's the value you see on screen.

When you see 127 on screen, you basically see some badly read value read from memory, incorrect, unlikely to be true.

 

[Superteick245]

34 minutes ago, mariushm said:

Temperatures like 127 degrees or 255 or 256 degrees are pretty much always incorrect.

 

Numbers are stored in memory using one or several bytes, where each byte has 8 bits. Each bit has two states, 1 or 0, so a byte can hold a number between 0 and 255, or from -127 to 128 (127 + 128 + the 0 value = 256 values in total).

The 127 value is exactly 7 bits set to 1: 0111 1111

 

It's unlikely you'll get such a reading from the sensor and it's more likely the software is incorrectly reading some data from memory that isn't updated with the sensor information, so the software always receives this 127 value, bogus..

 

Most sensors will report a 10 bit (0..1023) or 12bit (0..4095) or 16 bit (0..32768) value and you divide these readings by some value to get decimals in your temperature readings for example your 10 bit : 0..1023 is treated as -512..511 and then you divide 0..511 by 4 (because the sensor has a 0.25c step) ... so for example if the software reads value 717, then software substracts 512 to change 0..1023 to -512 .. 511 and you get 205, which then is divided by 4 (because it's dealing with a 0.25c per bit) so 205 gets converted to 51.25 degrees Celsius and that's the value you see on screen.

When you see 127 on screen, you basically see some badly read value read from memory, incorrect, unlikely to be true.

 

Thank you so mutch for trying to explain. I tryed to uderstad, litraly uderstad half but realy appreciate the effort