Hey everyone!
So I have an AMD FX-6300 overclocked to 4.2 GHz (The overclock itself is fine. It's running stable and temperatures are good). But there seems to be a strange bug regarding how it is counting framerates... When I boot up my PC normally, everything works just fine. But if I put it into sleep mode, it starts acting strange after I wake it up.
It starts counting framerates that are 20% higher than they actually are (20% is exactly the same as the ratio by which the CPU was overclocked from stock). For example, I know a particular game is running at exactly 60fps (synced with the display) but the framerate counter is displaying 72 fps. Conversely, if the PC tries to compensate for this, it will run the game at 50fps, while the framerate counter thinks it's at 60fps.
This results in games that don't run correctly, usually resulting in an unsightly 50fps cap (on my 60Hz display) with other games running in a sort of "slow-motion" 20% slower than they should be running.
I could simply avoid this by not using sleep mode at all, or not running my CPU overclocked. but I'd rather find a solution to this issue.
Thanks!
So I have an AMD FX-6300 overclocked to 4.2 GHz (The overclock itself is fine. It's running stable and temperatures are good). But there seems to be a strange bug regarding how it is counting framerates... When I boot up my PC normally, everything works just fine. But if I put it into sleep mode, it starts acting strange after I wake it up.
It starts counting framerates that are 20% higher than they actually are (20% is exactly the same as the ratio by which the CPU was overclocked from stock). For example, I know a particular game is running at exactly 60fps (synced with the display) but the framerate counter is displaying 72 fps. Conversely, if the PC tries to compensate for this, it will run the game at 50fps, while the framerate counter thinks it's at 60fps.
This results in games that don't run correctly, usually resulting in an unsightly 50fps cap (on my 60Hz display) with other games running in a sort of "slow-motion" 20% slower than they should be running.
I could simply avoid this by not using sleep mode at all, or not running my CPU overclocked. but I'd rather find a solution to this issue.
Thanks!
Facebook
Twitter
Instagram