Page 1 of 1

Problem with Win10 and older games

Posted: Fri Apr 01, 2016 12:31 am
by stormi
Sorry, it's me again.
I have another issue with Core Temp RC8 and Windows 10.

When Core Temp is running with some older games, after starting them (in fullscreen), Core Temp always forces back to the desktop (the game keeps running minimized/in the background). When switching back to the game it again instantly forces back to the desktop. Without Core Temp running there's no such problem.

I have another device running on Windows 8 without this problem. I don't know if that's caused by Windows 10 or just my configuration.

Booth are mobile devices running on Intel Core CPUs with integrated graphics and recent graphic drivers.

Re: Problem with Win10 and older games

Posted: Fri Apr 01, 2016 1:54 pm
by The Coolest
That's odd, first time I hear of this issue.
Make sure that you don't have Core Temp set to be 'Always on top'.
Minimize the program before you run the games.
What games are those? I can try this on my Win10 system, which also runs a mobile Intel core CPU.

Re: Problem with Win10 and older games

Posted: Fri Jul 29, 2016 8:07 pm
by xraale
Ok, I can confirm this bug. I've been having it ever since I upgraded to Windows 10 and it has been driving me mad until I finally found out that CoreTemp is causing it.

It's nothing to do with older games. To reproduce:

- Use Windows 10, CoreTemp running and minimised.
- Have a "Change the size of text and other items" at >100%. This is the DPI.
- Open a full screen game that has a *lower resolution* screenmode.

The screen will open, get kicked back to desktop, then refuse to switch back to the game again. Usually the only way is to use the task manager to kill the game. This doesn't happen on all games - DOOM 4 is fine, XCOM 2 and Rome: Total War are not.

If you set the DPI to 100%, then the bug does not occur. Same if you open the game and it has the same screenmode.

I'm pretty sure this has something to do with CoreTemp's taskbar icon and the DPI switch. When a full screen game opens in Windows 10, it changes the desktop resolution to the game's resets the DPI to 100%. For some reason, this screws up something in Win10's screen opening.

Re: Problem with Win10 and older games

Posted: Sat Aug 13, 2016 10:38 am
by Naki
xraale - what exact videocard brand & model do you use - AMD Radeon or Nvidia GeForce, what model?
What version of GeForce or AMD Radeon video drivers?
Might be driver issue.

Re: Problem with Win10 and older games

Posted: Fri Aug 19, 2016 8:27 pm
by xraale
Naki wrote:xraale - what exact videocard brand & model do you use - AMD Radeon or Nvidia GeForce, what model?
What version of GeForce or AMD Radeon video drivers?
Might be driver issue.
I have an AMD Radeon R9 390. I'm using 16.7.3 Crimson software.

I've had the issue as long as I've had Windows 10 - I thought it was a bug in Windows 10 until I got so annoyed one day I disabled everything and tried disabling everything and enabling it one at a time. That's how I found it it was CoreTemp that was doing it.

Re: Problem with Win10 and older games

Posted: Fri Sep 16, 2016 1:18 am
by The Coolest
I finally setup a Win10 (Anniversary Update) machine I can run tests on, although it only has an Intel iGPU.
I'll try to reproduce what you mentioned, and see if I can get a hold of those games you are talking about.
Could you please list all the games you encountered this problem with?

Now here's a question: Do you guys happen to have logging enabled in Core Temp?
Try turning it off and then see if this problem persists. It's possible that there is some sort of weird interaction between Core Temp and the way the game keeps focus, it's also possible that an AV software could be involved as well.

Re: Problem with Win10 and older games

Posted: Fri Sep 16, 2016 12:22 pm
by The Coolest
@xraale
I have a 1680x1050 monitor connected to a PC running i3 540 using its built in graphics.
I set DPI to 125%, game to 1280x800, Core Temp minimized and even with logging on.
Then I launched Rome: Total War and it fired right up and is working fine without being kicked out anywhere.
I'm not sure what the issue is. As I mentioned in my previous post it might be some sort of conflict between several pieces of software.