• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Idle clocks keep reseting

Meevinman

n00b
Joined
Oct 25, 2011
Messages
29
So i have created a preset for idle clocks within CCC and have set it at: GPU clock 450Mhz and memory clock at 900Mhz, however, every so often it will change itself back to it's default which is: GPU clock 850Mhz and memory clock 1200Mhz. While the latter clocks are running, my display will fail giving me the error of "Display driver amdkmdap stopped responding and has successfully recovered.". But if those clocks will stay at what i have set, these crashes will stop happening.

And please not, these Display crashes NEVER happen while playing games.

Anyone know what is causing the clocks to constantly change?

Current idle preset:

<Profile>
<Caste name="Graphics">
<Groups>
<Group name="Overdrive5">
<Feature name="TimeUnlocked" />
<Feature name="OverclockEnabled">
<Property name="OverclockEnabledProperty" value="True" />
</Feature>
<Feature name="AutoTuneSupport" />
<Feature name="CoreClockTarget_0">
<Property name="Want_0" value="40000" />
<Property name="Want_1" value="60000" />
<Property name="Want_2" value="85000" />
</Feature>
<Feature name="PowerControl_0">
<Property name="Want" value="0" />
</Feature>
<Feature name="MemoryClockTarget_0">
<Property name="Want_0" value="90000" />
<Property name="Want_1" value="90000" />
<Property name="Want_2" value="120000" />
</Feature>
<Feature name="CoreVoltageTarget_0">
<Property name="Want_0" value="900" />
<Property name="Want_1" value="1000" />
<Property name="Want_2" value="1175" />
</Feature>
<Feature name="MemoryVoltageTarget_0">
<Property name="Want_0" value="0" />
<Property name="Want_1" value="0" />
<Property name="Want_2" value="0" />
</Feature>
<Feature name="FanSpeedProtocol_0">
<Property name="FanSpeedProtocolProperty" value="Percent" />
</Feature>
<Feature name="FanSpeedAlgorithm_0">
<Property name="FanSpeedAlgorithm" value="Manual" />
</Feature>
<Feature name="FanSpeedRPMTarget_0">
<Property name="Want" value="1769" />
</Feature>
<Feature name="FanSpeedPercentTarget_0">
<Property name="Want" value="50" />
</Feature>
</Group>
</Groups>
<Adapter name="PCI_VEN_1002&amp;DEV_6718&amp;SUBSYS_22011458&amp;REV_00_4&amp;2F1C4782&amp;0&amp;0018A">
<Aspect name="Overdrive5" />
</Adapter>
</Caste>
<Caste name="Platform">
<Groups />
<Adapter name="PlatformAdapterUDID" />
</Caste>
</Profile>
 
Last edited:
The crashes aren't real per se, it is just that windows 7 is a zealot regarding timely responses, and if something takes longer than it thinks it should then it will restart the driver and tell you that it crashed.

The solution so far is to set the mem speed the same on all states, once that is done then you shouldn't experience any more atikmdag.dll crashes.
 
The crashes aren't real per se, it is just that windows 7 is a zealot regarding timely responses, and if something takes longer than it thinks it should then it will restart the driver and tell you that it crashed.

The solution so far is to set the mem speed the same on all states, once that is done then you shouldn't experience any more atikmdag.dll crashes.

Ok, have set them all the same, will see if it helps.

Edit: still the same, looks like i will just have to learn to live with it.
 
Last edited:
Wait, you are loading the profile and it still crashes?

That is a first for me honestly. Remember that after you create the profile you have to load it, and check in the overdrive section of the CCC to see that it was applied properly.
 
Wait, you are loading the profile and it still crashes?

That is a first for me honestly. Remember that after you create the profile you have to load it, and check in the overdrive section of the CCC to see that it was applied properly.

Yeah, under presets it has mine which i have called "Idle Clocks" I click on that and it should be staying at 400-900 but it keeps changing back to 850-1200 every so often.

Note that i have both "Want0s" as the clocks i would like it at, but then you have the other two clocks.
 
Back
Top