same!! so thats 6 people
 

should we start a new thread with a more clear title to bring attention to this issue?

It's a problem for me too guys. It's getting frustrating. 

I tried it on another computer with a GTX960, that won't oc the memory either.
So it is with 3 cards, two GTX970s and one GTX960 on two different computers.
Using both Afterburner and EVGA PRE.X
One system is Win 8.1 Pro64 and the other is Win 7 Pro64
I tried it with the all settings stock and with the GOU overclocked.
 
Is there a setting we have to unlock or something?
 
EDIT: I just sent a PM to one of the EVGA techs pointing to this thread asking for some help.
So hopefully help will be on its way sometime in the near future.

bill1024
I tried it on another computer with a GTX960, that won't oc the memory either.
So it is with 3 cards, two GTX970s and one GTX960 on two different computers.
Using both Afterburner and EVGA PRE.X
One system is Win 8.1 Pro64 and the other is Win 7 Pro64
I tried it with the all settings stock and with the GOU overclocked.
 
Is there a setting we have to unlock or something?
 
EDIT: I just sent a PM to one of the EVGA techs pointing to this thread asking for some help.
So hopefully help will be on its way sometime in the near future.

Awesome, hopefully they come up with a solution. Ive gotten it to work some times and others it doesnt

Indeed, would sure be nice to get this issue resolved.

So I've been playing around with the memory clock offset and haven't been able to reproduce the same behavior that you guys are seeing.  Starting with no preset, I can make an offset, apply and see the change in the interface and under load with the hardware monitoring and the OSD.
 
Saving that as a preset then making another change to the memory offset again, I see this update as expected and click on the profile to have it update back to the saved value.  All of this can be seen change in the hardware monitor and OSD.  I can continue to do this with a second preset and go between both with updates as expected.  I threw in very mild changes to the GPU clock offset for both presets as well with no change in behavior.
 
I did all this on:
Windows 10 (Clean install)
Precision X ver 5.3.6 w/ 980's
 
No real changes done to the default Precision X settings except raising the power target before any of these changes where made.
 

bill1024
So it is with 3 cards, two GTX970s and one GTX960 on two different computers.
Using both Afterburner and EVGA PRE.X
One system is Win 8.1 Pro64 and the other is Win 7 Pro64
I tried it with the all settings stock and with the GOU overclocked.

Were you seeing this in Afterburner as well?
 
 
 
 

Yes with Afterburner as well. After I uninstalled EVGA PRE.X . on both systems. Win7 pro and win 8.1 pro.
3 different video cards, two GTX 970 and a GTX 960 all EVGA cards.
 
Thanks you for getting back to me/us here in this thread.
 

I'll have to direct this further up.  I tried another test bench, another GPU and still haven't been able to reproduce the error but from the information posted so far I can't determine whether the source is hardware or software.\
 
For now, if you haven't wiped the drivers from the system, do so.  Then use the clean install option under the Custom selection when installing drivers.  Looks like some users have had success with DDU.

Update on my end:
I think I have found a way to make it work, at least for me. When not running a 3d application, no matter what I do I can not get the memory clock adjustment to stick. Core clock does, memory clock always resets to 0 after clicking apply. This was with both Precision and with Afterburner.
 
Currently I am using Afterburner. So I went in to my 3d game, and whilst it was up and running, I then adjusted the memory clock - clicked apply - and it took the setting. I run two monitors, and have the AB software displayed on my second monitor, so it was easy for me to go in and make the memory clock adjustment whilst the game was running.
 
I have tested this a few times, and so far every time I make the memory adjustment whilst the game is running it sticks. Back at desktop, if I make a change to the memory clock  the memory resets to 0 after clicking apply. Don't know if by design this is the way it is supposed to be or not, but at least I can now get it to hold a memory overclock by doing it this way.