GPU Monitor Gadget 2.0 Released

Erm/Nightstorm1,

I think I identified the problem. Both of you were using the Windows SideShow capability with the "Bars" display style. Running the gadget using the files you sent me, but disabling the SideShow option seems to prevent the leak.



This make sense that no users have mentioned the problem, as I'm sure very few people use SideShow. The SideShow code does not execute at all if it is disabled, so this problem does not exist using just the sidebar gadget itself. Removing the prefWindow_#.json file and letting the gadget recreated it causes you to get the default settings, in which case SideShow is disabled.

Would you mind enabling the SideShow option again and see if the leak reappears? Then disable it again to see if it goes away. If you can reproduce, please try all 3 display styles and let me know those results as well. Also, what SideShow devices are you using?

In the meantime, I'll examine the code to track the problem down, as well as try version 2.2 to see if the problem existed there as well. I do not recall changing the SideShow code in 2.3, but will double check.

Vomit, you've been running SideShow for a long time now. Ever see the memory usage issue mentioned above? Have you upgraded to 2.3 and are still running your SideShow device?

 

Hiya

yes I still use the sideshow on two devices just depends what one is handy at the time to which one I use, but one is in use all the time my pc is booted.

I have never seen memory usage as described in the previous posts, I think i would soon run out of memory when playing games if their was a problem with it for my machine. The PC has been booted up for over a week and abused with long game sessions and i would have to say its memory usage was normal during that time.

I hope this helps

I have been running 2.2 since you sent me the update, forgot to mention that hence the edit

 

I have been running 2.3 since my last post, just under a month.

Despite several heavy duty game sessions and general pc abuse still no signs of the memory leak reported.

I have also tried running both my sideshow devices at the same time, both worked fine and still no leak.

 

I was wondering, is it possible to change the order in which the info shows up, my fan speed dropped to the bottom of the list and i want it back in between the memory clock and cpu temp.

 

You can reorder them in RivaTuner's hardware monitoring setup list using drag and drop (see the gadget's instructions tab for a pic). Then just open the gadgets settings and click OK to force a complete redraw.

 

Hi I have heard a lot of great things about this gadget! but! i know i need 2.25
im a newb to rivatuner... i am currently using afterburner... for the osd, i was told you can't run afterburner and rivatuner at same time is that right?
and seeing as i cant run rivatuner i cant get the gadget to work!

do i have to wait till 2.25?

 

Try Nick's gadget for MSI Afterburner.

 

hi great plugin only one problem so far in the cpu temp i only have core0 and core1 but no core2 and core3 i have everest ultimate installed and the plugin enable in rivatuner 2.24 msi but i get no reading for those core some help would be appreciated

 

Hi.

Can you please check these?

1 - ensure Everest is reporting them (1.png)
2 - ensure it is enabled in the preferences under external applications(2.png)
3 - look at your Everest.cfg The Everest names for those two readings are TCC-1-3 and TCC-1-4. Also note: A common mistake may be to copy/paste an existing entry but not increment the SourceX Number or ID.

You should have something like this in there:

Code:

[Source0]
ID          = TCPU
Name        = CPU Temperature
Dim         = °C
MaxLimit    = 100
MinLimit    = 0
GridDim     = 10
Desc        = CPU Temperature reported by Everest
Group       = CPU

[Source1]
ID          = TCC-1-1
Name       = CPU Core 1 Temperature
Dim         = °C
MaxLimit   = 100
MinLimit    = 0
GridDim     = 10
Desc        = CPU Core 1 Temperature reported by Everest
Group       = CPU

[Source2]
 ID          = TCC-1-2
 Name        = CPU Core 2 Temperature
 Dim          = °C
 MaxLimit    = 100
 MinLimit    = 0
 GridDim     = 10
 Desc        = CPU Core 2 Temperature reported by Everest
 Group       = CPU

[Source3]
 ID          = TCC-1-3
 Name       = CPU Core 3 Temperature
 Dim         = °C
 MaxLimit   = 100
 MinLimit    = 0
 GridDim    = 10
 Desc        = CPU Core 3 Temperature reported by Everest
 Group       = CPU

[Source4]
 ID          = TCC-1-4
 Name        = CPU Core  Temperature
 Dim         = °C
 MaxLimit    = 100
 MinLimit    = 0
 GridDim     = 10
 Desc        = CPU Core 4 Temperature reported by Everest
 Group       = CPU

If you have verified all this and it is not working, please close RivaTuner, edit the "Export = 0" line in the Everest.cfg to "Export = 1". Then reopen RivaTuner. This will create a Everest.log file in the plug-ins directory. Disable this Export option by setting to 0 again. Then post the contents of both the Everest.cfg file and the Everest.log file.

- Nick

 

humm verfied everything and this morning when i booted back window they where there i tought i only had to restart rivatuner to get them but i guess a good old reeboot did the job
thx

 

Hi Nick,

Happy New Year.

Quick question. Can the GPUMonitor.log be redirect to another disk drive?

Paul

 

Hi. Happy new year too!

Sure, just create a symbolic link for it. Here is a down and dirty example.

Code:

Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>cd ..

C:\Windows>cd ..

C:\>cd temp

C:\temp>mkdir temp2

C:\temp>mklink /?
Creates a symbolic link.

MKLINK [[/D] | [/H] | [/J]] Link Target

        /D      Creates a directory symbolic link.  Default is a file
                symbolic link.
        /H      Creates a hard link instead of a symbolic link.
        /J      Creates a Directory Junction.
        Link    specifies the new symbolic link name.
        Target  specifies the path (relative or absolute) that the new link
                refers to.

C:\temp>mklink GPUMonitor.log temp2\GPUMonitor.log
symbolic link created for GPUMonitor.log <<===>> temp2\GPUMonitor.log

C:\temp>echo %temp% > GPUMonitor.log

C:\temp>notepad GPUMonitor.log

C:\temp>notepad temp2\GPUMonitor.log

C:\temp>

Here's what that just did.....

1. set the working directory as C:\temp
2. create a folder called temp2 (full path of C:\temp\temp2)
3. create a symbolic link in C:\temp called GPUMonitor.log. It links to C:\temp\temp2\GPUMonitor.log.
4. write some text to the file - I just wrote out my temp variable
5. open the C:\temp\GPUMonitor.log in notepad
6. open the C:\temp\temp2\GPUMonitor.log in notepad

In both cases they open the same file which has the same contents of: C:\Users\Nick\AppData\Local\Temp

Look in windows explorer and you'll see C:\temp\GPUMonitor.log is a link, not an actual file. It looks like a text file, but is 0 bytes. C:\temp\temp2\GPUMonitor.log is an actual 35 byte text file.

Is this what you were looking for?

 

I think so.
Since I recently acquired an SSD, I've been looking into minimizing writes to that disk.
I would like to put the log on one of my regular hard drives.

 

Right. So that should work fine. Here is an example moving it to the root of an E:\ drive

1. open a command prompt as an admin
2. change the working directory to your existing temp (cd C:\Users\<username>\AppData\Local\Temp)
3. close the gadget
4. move the file to the new folder (move GPUMonitor.log E:\)
5. create the symlink (mklink GPUMonitor.log E:\GPUMonitor.log)
6. open the gadget

I haven't explicitly tried it, but this it should be fine. Let me know how you make out.

 

Thanks Nick, that worked great.

Paul

 

just wanted to know is this yours or a copy
http://www.softpedia.com/get/Windows-Widgets/System-Utilities/GPU-Monitor.shtml

 

Thanks for letting me know.

No, that is not this gadget. It just has the same name and does something similar.

 

STANGOWNER: i have the same problem.
Gadget isn't loading "GPUMonitor.exe" anymore!
It was ok before!

If i run "GPUMonitor.exe" manualy, everything works ok.

I don't wan't to add a shortcut of "GPUMonitor.exe " on startup folder, as a workaround.
I'd prefer to troubleshoot this issue and figure out why the gadget can not launch "GPUMonitor.exe".

Could you help me?

I saw the "gadget.js" file on scripts folder and there is the code that runs the "GPUMonitor.exe".

Could be a Windows Javascript problem?

I'm using Win7 x86 with Firefox 5!

I don't use Internet Explorer and i have uninstalled it.

Thanks for help.

 

What changed on your system between when it was working fine and now?

 

I don't know!
I can't remember anything that has changed!

Is there a way to DEBUG or to do something like this on GPUMonitor at the moment of it is loaded?

I'm planning to do something like do a step by step check on the load process of GPUMonitor.

Any help?

Thanks.