Quote from: painmaker on December 30, 2016, 03:06:03 PM

Quote from: thevictimofuktyranny on December 30, 2016, 02:50:29 PM

Quote from: painmaker on December 30, 2016, 02:19:38 PM

[SNIP]

[SNIP]
Nvidia Compute always drops memory to 2nd memory profile setting, which is legacy problem from the launch of 10 series cards.

You need to set up .sh overclocking profile that will add 404mhz (or whatever you GPU is short at) overclock to the memory to get the gaming memory performance of 8008mhz applied to the Compute tasks.

thanks a lot for your reply! i'm not sure i understand you correctly what you mean by 'set up .sh overclocking profile'.
i assume you mean i need to create a bash-script (.sh) which gets executed during startup (just as you posted in you guide)?
this is exactly what i have done and this leads to the described behaviour in my case (level 2 (without clock-offsets) of a total of 3 levels).

without the RegistryDwords-option, the card is stuck in level 2 (of 3) right from the beginning.

Yeah, bash-script.

Then, it is a problem with your driver installation.

Or, did you accidental say "Yes" to install Nividia drivers when installing Cuda 8 - that will wreck everything.

Or, you've got a corrupted Ubuntu OS installation.

Anyway, I would zero wipe your SSD and start again.