Logging function bug - Core1 speed doesn't update

[mikehd]

Hi everyone,

First, my thanks for a terrific little application. It's been very helpful in my recent mild overclocking adventures.

The bug I've found is in the csv table created with the logging function. For Core1, the speed never shows as increasing. Core0 tracks correctly. I'm using p95 64bit to create the core loads.

Code: Select all

Time	Core 0 Temp.	Core 1 Temp.	Low temp.	High temp.	Core load	Core speed	Low temp.	High temp.	Core load	Core speed
10:34:53	37°	40°	35°	53°	3%	2399.86 MHz	39°	54°	0%	2399.86 MHz
10:35:03	37°	40°	35°	53°	6%	2399.86 MHz	39°	54°	5%	2399.86 MHz
10:35:13	37°	40°	35°	53°	4%	2399.86 MHz	39°	54°	1%	2399.86 MHz
10:35:23	52°	53°	35°	53°	100%	3199.81 MHz	39°	54°	100%	2399.86 MHz
10:35:33	54°	54°	35°	54°	100%	3199.81 MHz	39°	54°	100%	2399.86 MHz
10:35:43	55°	55°	35°	55°	100%	3199.81 MHz	39°	55°	100%	2399.86 MHz
10:35:53	56°	56°	35°	56°	100%	3199.81 MHz	39°	56°	100%	2399.86 MHz

Sorry for the formatting, but you should be able to see that Core0 shows its core load going from 3-6% to 100% with the corresponding core speed going from 2.4GHz to 3.2Ghz. For Core1, core speed isn't shown as changing.

Not a killer bug by any means, but I noticed it and thought I would report it to you. Let me know if other info is needed.

Machine Info
Core Temp 0.99.6
e6750/P35-DS3R
Win7 64bit

[The Coolest]

I've tested this, and there is no problem with the logging.
Current version is a little bit problematic with frequency reporting, it could cause the second core to simply read 2400MHz incorrectly, and that is what got logged.
I'm working on a solution for this problem, and a public beta will be up shortly.

[mikehd]

Good to know, thanks for the quick reply. Looking forward to your next release.