Messages

That's great Fred! Thank you so much for looking into this issue! 

Along with integrating GPU-Z for the temperature and load monitoring, does that also mean you'll be adding throttling ability for Intel GPUs to TThrottle as well?

Thanks again,

Mike

Looks like it fixed the temps being shown in Celsius instead of Fahrenheit when Fahrenheit is selected. And I can just barely see the CPU % line at the very bottom (riding along the 100 degree line) in Fahrenheit mode. It's kind of hard to tell what's going on with it at the very bottom.

Is there a way to add that 2nd vertical axis for the CPU/GPU % line instead of using the temp line as the basis for CPU Running percentage? This would allow the CPU/GPU% line to be in a consistent location on the screen no matter what unit of temp. measurement we are in. Plus in the Celsius mode the graph has a great symmetry about it. We could see our CPU/GPU% running at 100% percent at the top and as our temps started getting too warm (going up toward the top), the CPU/GPU% would drop down (from the top) showing the throttling happening. In Fahrenheit, the line a reversed and it make's it hard to see and more difficult to tell what's going on.

Even so, can TThrottle just use the data from the temp sensor located at the GPU portion of the integrated chip (or the sensor that reads hottest when GPU is under a full load/test) as the GPU temp data (it appears this is what other programs may be doing)? And is there anyway to then throttle the GPU portion separately on the integrated Intel chip? It appears that the CPU portion is being throttled independently of the GPU (since the GPU can run under full load/speed, while CPU is throttled low), so couldn't it be done the other way around as well?

Not that I can see. It shows GPU clock, GPU D3D Usage, GPU D3D Memory Dedicated, and GPU D3D Memory Dynamic, but no specific category that says GPU temp. as far as I can tell.

That's why I mentioned that GPU-z seems to be using the CPU package sensor (or CPU IA cores sensor) temp readings for their reading of GPU temp. HWiNFO also has another temp reading called CPU GT Cores temperature reading, which, from what I've read, could also potentially be the temp of sensor at the GPU portion of the integrate chip. I'm not sure which one of those 3 temp. sensors (CPU package, CPU IA cores, or CPU GT cores) is the correct sensor for reading for GPU temps., if any of them. But no,, nothing in HWiNFO that specifically states GPU temps as far as I can see.

[throttle]

Thanks for responding Fred. I've been monitoring the GPU temps, load/usage, power, and speed with GPU-Z. It looks like the sensor that GPU-z is using to read the GPU temp is what HWiNFO is calling the CPU package sensor (or CPU IA core sensor, they're almost always the same temp on mine).

So, either way I can keep track of the GPU temp, but neither program has the ability to throttle the GPU. That's where TThrottle comes in to save the day!! Is there anyway to throttle the GPU portion separately on an Intel chip? From what I'm seeing, it seems like the CPU portion is being throttled independently of the GPU, can it be done the other way around as well?

If any of the rest of you folks on the forum are interested in TThrottle adding Intel GPU detection and throttling, please reply or somehow second the motion. As Fred stated in the Work schedule thread "And as alway the more request for a certain feature the higher it will go on the list.
"

[temperature]

In the scalable graph, whenever someone has temperature set to Fahrenheit, it throws off the entire graph. The CPU temp, CPU %, and Max CPU are missing (possibly the temp., percent, and Max readings for GPU as well, but I'm unable to know for sure since TThrottle doesn't detect or throttle Intel GPU yet-another topic was submitted on that earlier). Right now, the Max CPU/(GPU?) is the only line that is visible (currently set at 158 (or 70 degrees C)-anyone know if that's too high for a mobile Intel i5?). Also, the CPU/(&GPU?) temps are showing up incorrectly in Celsius on the scalable graph, but shows up correctly (in Fahrenheit) on the graph tab of the main window.

It seems like, in Fahrenheit, the scaling (and the temps being shown in Celsius instead of Fahrenheit) could be the reason I'm not seeing CPU/(GPU?) temp, and CPU/(GPU?) Run Percentage%. Max CPU/(GPU?) temp is showing up correctly. Maybe the scaling is possibly pushing all the other measurements off the bottom of the viewable portion of the graph in relation to the higher Max CPU/(GPU) temp. line, which is at 158 degrees Fahrenheit? Are we also losing the CPU/GPU% off the bottom of the graph, since the program is plotting it against the vertical temperature axis at the 100 degree mark?

Could plotting CPU/GPU% against an added secondary vertical axis label (possibly on the right side) fix this problem? Therefor, no matter what unit the temperature is being measured in (Celsius or Fahrenheit), the measurements on the vertical axis for temp. can change as the unit is changed, and the CPU/GPU Percent% axis always stays in the same spot.

Also, can you please fix the CPU/GPU temps so they are actually plotting at the right temp. on the graph when Fahrenheit is selected?

It would be nice to be able to see the actual numbers for the Current CPU & GPU core temps, and Run % number in scalable graph window. I know we can see the Current CPU & GPU core temps from the temperature tab on the main TThrottle menu and the Run % number from the programs tab, but I was wondering if there is a way to get those numbers/fields also added into the scalable graph windows (maybe in the empty area just to the right of the time scrolling bars at the top), so we can see all the information in one place without having to bounce back and forth between screens. I realize the graph shows us all that information in an analog form if we do some figuring (i.e. we could determine it by following the lines across from right side to the left side to the corresponding numbers and figure it out), but it'd be  great if we could just look up above it for the actual current numbers. (Kinda similar to how most people prefer just getting the exact number by looking at a digital clock instead of trying to figuring up the minutes and hours on an analog clock). Maybe we could even have the ability to click within the graph at any certain previous time and see what the numbers were at that point, but that would be an added bonus if it's possible to do.

I saw that there was a previous message about this, but when I went to reply there, it recommended I start a new topic since the thread hadn't been posted in for a while.

I have an Intel i5 3210M Ivy Bridge processor that has the HD4000 graphics. After installing new drivers and the latest version of BOINC, BOINC now recognizes my GPU and utilizes it. However, TThrottle isn't detecting the GPU. Therefor, I can't throttle it. Another program I found (CPU-Z) does detect it and tells me temp and speed, but doesn't have anything that would allow me to throttle it. Now that many projects are added tasks that work on Intel GPU, can we get an update of TThrottle that will also recognize and throttle them.

Right now, when my computer starts to warm up TThrottle only throttles the CPU, not the GPU. However, most times, that actually causes the GPU to run up to it's max and much hotter. I've learned that this is because this opens up more CPU resources that many GPU based tasks also need to feed the GPU info, thus allowing the GPU the ability to run full out. Unfortunately, this just causes the system to heat up faster/higher which then leads to TThrottle clamping down further on the CPU causing a cascade effect until it reaches the point that all the computer is actually running are GPU tasks only. So right now, it seems I can have GPU can either run at max (without CPU tasks really being processed) or not at all.

Is there a way to get TThrottle to recognize these Intel GPUs and allow us to throttle them like it does for other GPUs? This would really help save many Intel computers from having these problems. Also, many projects are adding more and more tasks for Intel GPU processing, so it'd be great to have a TThrottle that could handle them. Please! add this.

I'm using and Intel i5 3210M Ivy Bridge processor that has the HD4000 graphics. It took a few different driver tests, but I finally got the Open CL2 Intel driver that works with BOINC. BOINC now recognizes my GPU and utilizes it. However, TThrottle isn't detecting the GPU. Therefor, I can't throttle it. Another program I found (CPU-Z) detects it and tells me all the speeds and temps, but doesn't have anything that would allow me to throttle it. Now that I have tasks using the iGPU, my computer is running much hotter. The only way I can remedy this is to really limit my CPU tasks with TThrottle. But, most times, that actually causes the GPU to run up to it's max and much hotter. I've learned that this is because I've opened up CPU resources that some GPU tasks also need to feed the GPU info, thus making the GPU able run full out. So right now, the GPU can either run at max or not at all, which requires me to stop GPU tasks. Is there a way to get TThrottle to recognize these Intel GPUs and allow us to throttle them like it does for other GPUs? Many projects are added more and more tasks for Intel GPU processing. So, it'd be great to have a TThrottle that could handle them.