HOW TO: Monitoring CPU and GPU Temperatures In-Game/In-Benchmark with On-Screen Display

Found out this doesn't work with games that use Mantle API. Hopefully that will be fixed eventually like they did with 64-bit.

 

If it gains enough market share to become truly relevant and eventually applies to NVIDIA and AMD they probably will at some point. If it stays proprietary the chances of it are probably less.

 

That's probably true however currently both Battlefield 4 and Thief support it so I think it will have a place in it. Thief apparently got a performance boost implementing Mantle into their game.

 

Hello

I've been using a different tool to check the general performance settings of my computer. It's called Pandora FMS and it helps to keep all the performance settings at monitored. It's a free tool, well it has some functions you need to pay for but the open version is very complete. For more information you can visit the following webpage: Pandora FMS - the flexible monitoring software

Regards
Ivo Yordanov

 

Please post some screen shots of Pandora FMS in action and let us know more about you use it. What are your system specs?

Does it output user-selected damage to the screen for active in-game monitoring? If so, are you using it with 64-bit games like BF4 and 64-bit benchmarks like 3DMark11?

 

Has anyone worked out a way to display FPS using Riva Tuna in 64bit ?

 

Yes. RTSS 6.0.0.6228. Works perfectly with 64-bit games and benchmarks.

 

As in not just the OSD but also the FPS ? ...

update: sorry I just looked at your video and you clearly had the FPS displayed..

Did you activate that somehow through Riva, HWinfo or with EVGA ?

I have FPS activated through EVGA but no dice bro
Can't find anything of any relevance with the other tools

 

Yup, that's right. "Show own statistics" should give you framerate on-screen even if HWiNFO4 is not running. Is this what you are asking about?

 

Lol whoooops. *INSERT GOOFY.gif HERE*

I goofed up and had never activated "Show own statistics".

Thanks champ!

 

I cannot get any of the monitoring software to run while Watch Dogs in up. The software is still running because I can open another game and it works fine but not in Watch Dogs. I had a similar issue on a game with steam and to fix I had to disable the Overscreen Display setting in Steam. So I did the same in Uplay and still it is not running in game. Any suggestions? I added the game to Riva Tuner OSD I turn detection all the way up.

 

Watch Dogs is probably 64-bit. You will need RivaTuner Statistics Server v6.0.0.6228 for that to work on 64-bit games. Here is a link where you can download it.

 

The download you linked me wont install properly for some reason


*EDIT


I made a mistake


And your suggestion fixed my problem. I am now able to monitor in Watch_Dogs

 

**Bumped**

 

Mr. Fox,
I am a noob to this and I just bought an Alienware 17 with Windows 8.1 64 bit and GEForce GTX 880M video card. I was wondering if my main objective is to be able the CPU, GPU performance with FPS for my laptop, which software would be more relevant without causing too much load to my system? Thanks in advance for the advice. Cheers.

 

Hey, without exception all of us began as noobs. This will put almost no measurable load on your system.

Download and install the latest RivaTuner Statistics Servers (v6.1.2) here: RTSS Rivatuner Statistics Server - Download

Download the latest HWiNFO64 beta portable version from here: HWiNFO, HWiNFO32/64 - Download

Choose a location to extract HWiNFO64... one where you want it to be placed permanently.

Set it up following the images in the screen shots album below, choosing which sensor values you want displayed, which row, column, etc.

<iframe class='imgur-album' width='100%' height="750" frameborder='0' src="http://imgur.com/a/UYC3s/embed"></iframe>

 

Fox, thanks for pointing me to the download links.
I could get the cpu/gpu monitoring using HWinfo and RTSS works like a charm but do I need another software to post FPS stats in my game?
Thanks!

 

No, open up RTSS and turn on "Show own statistics" and then you should see FPS stats in-game.

 

So I have been having black screens in Bioshock Infinite lately and today I started playing The Last Remnant and it did the same thing. I thought it was a video card issue but apparently its an OSD and Unreal Engine 3 issue?

I turned off RTSS and closed HWInfo64 and was able to play TLR without another black screen, which were occurring very frequently before that.

Any idea how I can fix this? Its going to really suck if I can't have my OSD.

I've got RTSS 6.1.2.7305 and HWInfo64 v4.42-2280. Options selected - GPU0 and GPU1 voltage, core, temp, CPU max core temp, show own statistics to get the framerate from RTSS.

Its nice to know it isn't my new cards but not so nice to hear it could be my OSD causing the issue.

 

Have you tried tinkering with the toggle switch for Custom Direc3D Support, or switching between Viewport and Framebuffer, Vector or Raster in the RTSS Control Panel? Having the D3D support option enabled sometimes causes really odd behavior. If changing those settings don't stop it, try dropping back to the previous 64bit version of RTSS. It is hard to find online sometimes, but you can get it here.

If you end up having to use the older version and find it works OK, go into the settings and change the check for updates option to "never" to keep it from looking for an update.

 

Make sure to disable your Steam or Origin overlay as it can interfere with RTSS. Especially Origin 'cause it's completely borked right now.

 

Good idea. The Steam and Origin overlay features, and the in-game community features are notorious from causing stupid behavior. I always disable those silly things. Using the RTSS Stealth Mode also sometimes corrects weirdness in certain games.

 

Thanks for the tips guys, I'll try em all. I have become OCD about having my OSD lol, both my laptop and my desktop have it.

Sent from my HTC One_M8 on Tapatalk

 

Yeah, I am OCD about that, too. I don't even like to game or bench without it any more, even with the GPUs running with no overclock. I'm so used to it that I have to know about everything that is going on or it just doesn't feel right and I end up not enjoying the game.

 

Okay, I figured out what it was.

Unreal Engine doesn't like low application detection level. Since these games aren't MMOs, I set application detection level to high and just played TLR without a black screen after trying to adjust all the other settings and getting a black screen within two or three minutes.

And wow does that game heat up my system! Boosted the whole time to 993MHz but temps were in the mid 80s which makes TLR the biggest furnace of a game that I have, putting both my CPU and my GPUs over 80 :O

 

Makes sense... The Last Remnant is an oldie from back in the day when game developers cared about product as much as profit... a time before console port mediocrity was standard fare and CPU performance was more important in gaming. The recommended system specs are Core 2 Duo, GeForce 8800, Vista and 2GB of RAM.

I think the last time I ran the TLR benchmark was like maybe 2010, LOL. I just now downloaded it and ran it. No adjustments or tweaks except 1080p full screen, just grab and run. My max CPU was 76°C and GPU was 69°C using stock Alienware fan profiles.

 

Its interesting that I kicked down my CPU's TDP to 47W and the temps on my cards dropped as well.

I just finished an hour and twenty minutes with no crashes, I think I found the culprit and I'm just going to have to set UE games to run without trying to hide RTSS' presence.

Gaming is much smoother on the new cards but the slave is running higher voltage so it has higher temps. Kind of odd that I have the same situation with two new cards (I confirmed they're different because their ASIC quality are different from my old ones) although at least they boost all the time now, even if the master is using 1.012v and the slave is using 1.018v to do it.

Spoiler

 

My secondary GPU almost always runs a bit warmer than the primary. It has always been that way for me with CrossFire and SLI. Using the stock vBIOS without the benefit of GPU Boost being disabled may explain the difference in voltage. The vBIOS may be telling it to pull more for some reason. The GPUs are going to be erratic and will not be in sync as they would with manual clock and voltage control and GPU Boost disabled.

 

Well I'm glad that I'm not nuts for thinking that it was normal to have the slave warmer, D2 had me convinced that I was wrong and the master should always be hotter.

I did do some more heavy duty gaming and tanked the second clear down to 888MHz with Sleeping Dogs. Apparently these cards don't like games that end in "Dogs" haha.

No more OSD weirdness, 3DMark doesn't even flicker anymore, I always thought that was a driver glitch but I changed the detection level back to low and it came back. I'm happy I took the time to ask about it, I had crashes with XCOM: Enemy Unknown too and I thought it was the drivers but come to find out that is also a UE3 game.

 

Yeah my slave GPU usually runs hotter as well. Temperature delta used to be up to 10C in GPU-intensive games. I've brought it down since then by dremeling the bottom cover to increase the intake hole for the slave card since it was really restricted before. Slave card also has a weaker fan and weak springs. I might mod it with some spacers to increase heatsink pressure. In CPU-intensive games, the two cards run about the same due to the primary and CPU sharing the same fan.

Sleeping Dogs is super demanding because of the SSAA on High and Extreme AA. If you run just Normal AA (FXAA) and cap FPS it'll bring your GPU usage down drastically at the expense of some additional aliasing. It's a shame we can't disable the in-game FXAA and force our own PPAA through the driver or an injector since the implementation in this game does a really poor job of removing jaggies.

Watch Dogs is super demanding because, well, it's an unoptimized Ubisoft title.

 

Yeah lol when I take the AA down from Extreme to High, my core drops down to 660 on both cards (I use adaptive vsync half-refresh to force 60FPS) and temps don't even hit 70.

I just wanted to see the beatdown. That game is officially the quickest way to bring my GPUs to the max 82C temp they can hit with the stock vbios before the core drops, it happens within about 15 minutes. I didn't notice that much of a visual impact for the performance hit to be honest and I prefer my cards running cooler (hell I don't even have to kick the fans up when I play it on High AA, they stay nice and quiet the whole time), I just figured "eh, why not"

I've noticed that the 880Ms throttle when in the presence of excessive AA, even if the temperature isn't the cause so its forcing the cards to hit some limit in the vbios.

 

Finally set this up

 

Edit I now have an issue.

When I play games My sound ches it will stop working them come on again.

When playing Metro LL the game keeps minimising to the task bar?

Okay I installed RTSS on my main drive, HWinfo64 on my other drive (where my games are) also had to install winzip to extract the RAR file.

Now the sound in my game glitches with the OSD?

 

It's not the OSD causing the glitch, it is monitoring utility software causing it because it is probing sensors that don't like to be probed. Disable Compal EC and Dell EC in HWiNFO64 because these devices being scanned will cause audio system glitches. On the 18 the glitches are really severe and obnoxious. On the M18xR2 it is merely an occasional faint, but still audible, "pop" sound that I can totally live with instead of disabling the Dell EC sensor.

 

Okay so I went into Sensors and disabld monitoring of the Dell EC, I can't find the compal EC though?

 

"EC Support" unchecked in the settings does that...

Disable Compal EC Sensors - uncheck box


Disable Dell EC Sensors - disable it, then hide it using right-click

 

Done Thanks Mr Fox

 

As you probably know, there have been problems with crazy numbers in HWINFO64. This is something I have written about the problem and told to Hwinfo forum. This is fixed now with the latest version of Hwinfo64 (ver 4.44) . This is the link for the thread: HWiNFO Maximum CPU Mhz Showing Crazy Numbers

 

Yep, I've gotten this before. It was pretty funny actually. :laugh:



Never bothered me because it's only happened once in my years of using HWiNFO64, but thanks for helping to get it finally resolved. :thumbsup:

 

RTSS Rivatuner Statistics Server Download v6.2.0 | Guru 3D

Here is a significant release of RTSS... Nice!

Version 6.2.0

• Improved compatibility with FRAPS in 64-bit mode
• Removed MSI Afterburner exclusivity lock for 64-bit On-Screen Display service*
• Drastically improved skin engine:
• Improved skin compiler gives more detailed error messages when skin compilation fail due to error in some source image file
• Source image file format is no longer limited to 24-bit BMP files only. Now skin compiler supports all possible bit depths for BMP format and fully supports PNG format with alpha channel
• Added built-in bitmap effect for extracting alpha-channel from PNG image files
• Skin format has been upgraded to v1.3. New format supports alpha channel based transparency for skinned window, allowing skin designers to define semi-transparent skin areas, apply antialiasing to the skin window edges and so on
• Added new skinned window composition modes support and “Skin composition mode” settings to “User interface tab”.

New settings allows you to use one of the following modes:

• Traditional mode – suits best for backward compatibility with existing skins and performance testing
• Layered mode with colorkey - provides much faster rendering of skins with non-rectangular window shape and additionally allows you to adjust transparency of skinned window
• Layered mode with alpha – provides per-pixel alpha channel support and advanced visual effects for compatible skins and also allows you to adjust transparency of skinned window
• Skin format reference guide has been updated to v1.7 to document these changes

*I never had any issue with this before and I think the lock never actually worked, but I am glad to see they lightened up their intentions.
The mere notion of RTSS becoming an MSI Afterburner "exclusive" feature was a real turn-off for me, and less than honorable in my opinion.

 

Yep, that and Afterburner 4 have been out for about a week. The exclusivity deal expired in September.

The lock was only when you tried to use 64-bit RTSS with Precision. Funny you should mention lack of honor. Unlike MSI, EVGA never contributed anything to the development of 64-bit RTSS or paid Unwinder a cent for RTSS since the very beginning, and when they didn't get it as a freebie again, they got mad and plagiarized Unwinder's work. Talk about entitled jerks.

 

Yeah, that's not excusable either. Stealing is never cool. I wasn't comparing which one is worse than the other in that respect... just the intent to make it not work with another product if you prefer the other product that I thought was crappy. I never appreciate having decisions about how I use a produce being pre-decided for me. I avoid products like that as much as I can, if for no reason other than principle... not going to let them tell me what I can and cannot do with a product.

 

Unfortunately, you have no choice in the matter as RTSS is one man's labor of love and the only OSD program of its kind in the world. Perhaps EVGA should've considered that in their negotiations with the developer. If anyone deserves the ire of you and other disgruntled Precision users, it's EVGA itself. The direct end result of corporate greed and shortsightedness is that the consumer suffers, always. Unwinder has had massive amounts of sh*t flung at him and been unfairly maligned for almost a year simply for sticking to his own principles, but everyone was pointing their finger at the wrong entity the whole time.

 

If it works the way I want it to, then I do have the choice and will do as I choose whether intended or not. If I cannot use a product as I deem fit, then I will just scrap it and find something else to use. I am thankful the lock never actually worked so I could have things the way I liked them and never had to choose an alternative that I viewed as being option #2. Unwinder being mistreated was terribly unfortunate, but that has nothing to do with personal preferences in my system configuration. The fact that it still worked in a way that wasn't intended makes using it "incorrectly" even more attractive.

Windows 8 isn't supposed to have a Programs menu or Aero transparency, but mine has both. Micro$haft didn't want it to have those features, but I don't really care what they think about it. Same goes for the unlocked BIOS that Alienware never intended for me to have on my M18xR1/R2 and the modded vBIOS that NVIDIA did not provide for my GPU... don't care what Dell or NVIDIA think about those things... none of their business. If they successfully lock me out to force the issue, I'll just buy something else next time instead of allowing them to have control over what I do.

 

Hi!
I come with some questions have you tried to use hwinfo osd rtss function with evga precision v16?
I can't get it working properly. I mean yes but I can't make it be hidden or disabled. I think I'm rolling back to previous version...

Thank you!!!

 

I'm using the previous version and have it set to check for updates "never" because I prefer the older version. But, you don't need EVGA Precision X or Afterburner. Using HWiNFO64 to output whatever sensors you want to RTSS/OSD works better than Precision X or Afterburner. Uninstall Precision and/or Afterburner. Download the latest version or RTSS here. If and/or when you reinstall Precision X or Afterburner, choose the custom installation and uncheck RTSS to prevent it from changing your current installation..

 

You as always are AWESOME thanks for the info I'm trying a lot of things since I'm in the hospital... Thinking about 980MSLI with CLU and slv7 vbios mod when available (I'm sure he will). Worst chapter of my life but fortunately I have this awesome machine to see the time goes by.

If you need any type of testing I'm more than willing to help this comunity as I have plenty of time. The only problem is that I don't have so much bandwidth here but at least I'm able to do some wifi audit...
Have a wonderful day

 

Thank you. Our thoughts and prayers are with you for a full and speedy recovery from whatever has you in the hospital.

 

Thank you

I was riding my bike and suddenly a son of a b**** jumped a red light and I could not avoid him. So... I'm glad to still be here.

 

Sometimes, I really don't have the patience for things on the computer... I'm trying to get my on-screen display settings back up after a few upgraded components a while ago, but I just can't seem to get things pieced together.

I took this picture via Afterburner's screenshot function (got stuck using F10 instead of NumPad 4 like I wanted).

1) I can't change "D3D9" to simply "FPS" for some reason. In Afterburner's settings (Monitoring > Framerate > Override group name), it's greyed out and says "APP".

2) I was able to successfully change the names of the supposed CPU usage meters in HWiNFO64 (CPU Usage 1 = "Max CPU/Thread Usage", CPU Usage 2 = "Total CPU Usage") as well as the temp (CPU Temp = "CPU 0"), but no units are actually showing.

3) Afterburner's on-screen display accepted the name changes above, but won't move the on-screen display to the top center of the screen like I want it.

Anyone run into these problems at all?