Before everyone starts blasting me for not searching, all I'm trying to do is get the GPU usage to show in the hardware monitoring. In EVGA Precision it works just fine, so does GPU-Z. It shows GPU usage no problem, but I can't seem to connect the dots to enable it in Rivatuner 2.24c. I found it the power user registry entries but can't seem to figure out how to enable it after playing with those settings for a few hours today...I tried loading the NVPrefCount plugin to no avail (It never gave me more options to tick in the setup tab for monitoring. Can someone help me figure out how to enable this one setting? You'd be my hero for life! :cheers:
I think I found the answer in less than a minute. Here and Here RT has not been updated in a long time to include this feature.
I read both of those threads today, but they still leave me with two big question marks. 1)If EVGA precision is built mostly around Rivatuner, and Nvidia GPUs aren't suppost to be able to show that, then why is Precision able to show it? 2)Why would there be registry entries in the power user tab for GPU Usage under the Hardware monitoring folder? Also, these posts keep me wondering... Unwinder's reply
IF you want to use rivatuner to monitoring your gpu usage on nvidia cards, you can combine it with everest.
Hi... Looks sweet. Which Everest node did you have to check to get GPU usage. I've enabled CPU core voltage and have that working nicely in my LCD but I can't seem to find the usage one. All I see is vid memory stuff. TY
In AIDA64 its called "GPU Utilization", but I'm pretty sure that is what it was called in Everest too. EDIT: Sorry, you probably wanted: SGPU1UTI
Don't pretend to think I know what I'm doing. LOL I have enabled shared memory in AIDA64. I put These files in RT's monitoring folder. AIDA64 is active in RT's plugins after unpacking those files. I have Everest.dll unchecked in RT's plugins. I have CPU volts displaying fine via AIDA64.dll plugin because it is checked in AIDA64 under external applications and in RT. I have checked in external applications of AIDA64 the two items (GPU1 Util & GPU2 Util). Back in RT I do not see them to display and be shown in the monitor. oy Edit: Ah crap, rebooted and now the CPU volts stopped working. Screw it.
I'm still using this: http://forums.guru3d.com/showthread.php?t=332290#2. And I'm even still using aida64 1.2. Both have been working fine for months, and have not gotten around to updating them. I'll try to update tomorrow and let you know if mine goes to crap. BTW - this is my everest.cfg: Code: [Settings] Export = 0 [Source0] ID = SGPU1UTI Name = GPU Utilization Dim = % MaxLimit = 100 MinLimit = 0 GridDim = 10 Desc = GPU Utilization reported by Everest Group = GPU [Source1] ID = SUSEDVMEM Name = GPU Used VRAM Dim = MB MaxLimit = 1024 MinLimit = 0 GridDim = 10 Desc = GPU Used VRAM reported by Everest Group = GPU [Source2] ID = SMEMUTI Name = Physical Memory Used Dim = % MaxLimit = 100 MinLimit = 0 GridDim = 10 Desc = Used RAM reported by Everest Group = RAM [Source3] ID = TMOBO Name = Motherboard Temperature Dim = °C MaxLimit = 100 MinLimit = 0 GridDim = 10 Desc = Motherboard Temperature reported by Everest Group = MOBO [Source4] ID = TCPU Name = CPU Temperature Dim = °C MaxLimit = 100 MinLimit = 0 GridDim = 10 Desc = CPU Temperature reported by Everest Group = CPU [Source5] ID = TSPP Name = Northbridge Temperature Dim = °C MaxLimit = 100 MinLimit = 0 GridDim = 10 Desc = Northbridge Temperature reported by Everest Group = MOBO [Source6] ID = TMCP Name = Southbridge Temperature Dim = °C MaxLimit = 100 MinLimit = 0 GridDim = 10 Desc = Southbridge Temperature reported by Everest Group = MOBO [Source7] ID = TGPU1MEM Name = GPU VRAM Temperature Dim = °C MaxLimit = 100 MinLimit = 0 GridDim = 10 Desc = GPU VRAM Temperature reported by Everest Group = GPU [Source8] ID = THDD1 Name = HDD1 Temperature Dim = °C MaxLimit = 100 MinLimit = 0 GridDim = 10 Desc = Hard Drive 1 Temperature reported by Everest Group = HDD1 [Source9] ID = THDD2 Name = HDD2 Temperature Dim = °C MaxLimit = 100 MinLimit = 0 GridDim = 10 Desc = Hard Drive 2 Temperature reported by Everest Group = HDD2 [Source10] ID = FCPU Name = H2O Pump Speed Dim = RPM MaxLimit = 5000 MinLimit = 0 GridDim = 10 Desc = CPU Fan Speed reported by Everest Group = CPU [Source11] ID = FCHA1 Name = Chassis Fan 1 Speed Dim = RPM MaxLimit = 5000 MinLimit = 0 GridDim = 10 Desc = Chassis Fan 1 Speed reported by Everest Group = FAN [Source12] ID = FCHA2 Name = Chassis Fan 2 Speed Dim = RPM MaxLimit = 5000 MinLimit = 0 GridDim = 10 Desc = Chassis Fan 2 Speed reported by Everest Group = FAN [Source13] ID = FCHA3 Name = Chassis Fan 3 Speed Dim = RPM MaxLimit = 5000 MinLimit = 0 GridDim = 10 Desc = Chassis Fan 3 Speed reported by Everest Group = FAN [Source14] ID = FFAN1 Name = Fan 1 Speed Dim = RPM MaxLimit = 5000 MinLimit = 0 GridDim = 10 Desc = Fan 1 Speed reported by Everest Group = FAN [Source15] ID = FFAN2 Name = Fan 2 Speed Dim = RPM MaxLimit = 5000 MinLimit = 0 GridDim = 10 Desc = Fan 2 Speed reported by Everest Group = FAN [Source16] ID = FFAN3 Name = Fan 3 Speed Dim = RPM MaxLimit = 5000 MinLimit = 0 GridDim = 10 Desc = Fan 3 Speed reported by Everest Group = FAN [Source17] ID = VCPU Name = CPU Voltage Dim = V MaxLimit = 2 MinLimit = 0 GridDim = 10 Desc = CPU Voltage reported by Everest Group = CPU [Source18] ID = V33V Name = +3.3 Voltage Dim = V MaxLimit = 4 MinLimit = 0 GridDim = 10 Desc = +3.3 Voltage reported by Everest Group = MOBO [Source19] ID = VP5V Name = +5 Voltage Dim = V MaxLimit = 6 MinLimit = 0 GridDim = 10 Desc = +5 Voltage reported by Everest Group = MOBO [Source20] ID = VP12V Name = +12 Voltage Dim = V MaxLimit = 14 MinLimit = 0 GridDim = 10 Desc = +12 Voltage reported by Everest Group = MOBO [Source21] ID = VBAT Name = Battery Voltage Dim = V MaxLimit = 5 MinLimit = 0 GridDim = 10 Desc = Battery Voltage reported by Everest Group = MOBO [Source22] ID = V5VSB Name = +5 Standby Voltage Dim = V MaxLimit = 6 MinLimit = 0 GridDim = 10 Desc = +5 Standby Voltage reported by Everest Group = MOBO [Source23] ID = VDIMM Name = RAM Voltage Dim = V MaxLimit = 2 MinLimit = 0 GridDim = 10 Desc = RAM Voltage reported by Everest Group = MOBO [Source24] ID = VDIMMVTT Name = RAM DTT Voltage Dim = V MaxLimit = 1 MinLimit = 0 GridDim = 10 Desc = RAM DTT Voltage reported by Everest Group = MOBO [Source25] ID = VNBCORE Name = Northbridge Core Voltage Dim = V MaxLimit = 2 MinLimit = 0 GridDim = 10 Desc = Northbridge Core Voltage reported by Everest Group = MOBO [Source26] ID = VSBCORE Name = Southbridge Core Voltage Dim = V MaxLimit = 2 MinLimit = 0 GridDim = 10 Desc = Southbridge Core Voltage reported by Everest Group = MOBO [Source27] ID = VHT Name = HyperTransport Voltage Dim = V MaxLimit = 2 MinLimit = 0 GridDim = 10 Desc = HyperTransport Voltage reported by Everest Group = MOBO [Source28] ID = VCPUVTT Name = CPU VTT Voltage Dim = V MaxLimit = 2 MinLimit = 0 GridDim = 10 Desc = CPU VTT Voltage reported by Everest Group = CPU [Source29] ID = VCPUPLL Name = CPU PLL Voltage Dim = V MaxLimit = 2 MinLimit = 0 GridDim = 10 Desc = CPU PLL Voltage reported by Everest Group = CPU [Source30] ID = CCPU Name = CPU Current Dim = A MaxLimit = 30 MinLimit = 0 GridDim = 10 Desc = CPU Current reported by Everest Group = CPU [Source31] ID = PCPU Name = CPU Power Usage Dim = W MaxLimit = 30 MinLimit = 0 GridDim = 10 Desc = CPU Power Usage reported by Everest Group = CPU [Source32] ID = SCPUMUL Name = CPU Multiplier Dim = x MaxLimit = 12 MinLimit = 0 GridDim = 10 Desc = CPU Multiplier reported by Everest Group = CPU [Source33] ID = SCPUFSB Name = CPU Front Side Bus Dim = MHz MaxLimit = 500 MinLimit = 0 GridDim = 10 Desc = CPU Front Side Bus reported by Everest Group = CPU [Source34] ID = SMEMCLK Name = RAM Clock Speed Dim = MHz MaxLimit = 500 MinLimit = 0 GridDim = 10 Desc = RAM Clock Speed reported by Everest Group = RAM
Great. I updated to Aida64 1.5 today, and it still works fine. I didn't get a chance to try that other plug-in though.
Well I was knocking my brains trying to figure out why I would get intermittent freezing in games. I can not run AIDA64 (ver 1.50.1200) and monitor nodes from that program because it is the cause. No biggie, I've got a pretty good idea how my new build is reacting to being overclocked now anyways.
The Problem with GPU Load Memory Controller and Video Engine Load is that these are only available via NDA in Nvapi i think at least it was a while ago the case, though i see more and more software implementing it (even Sidebar Gadgets, directly no shared memory stuff) away from the big ones like Everest back then or GPU-Z so could be that Nvidia set it free from the NDA requirement by now. Though i think if that would be the case we would have a Rivatuner Plugin for it by now also, so seems NDA is still a requirement http://developer.nvidia.com/object/nvapi.html.
