Associate
- Joined
- 7 Apr 2006
- Posts
- 292
- Location
- USA
AMDmatt, I don't have a way to send you a PM and this was in reference to the forum thread on the AMD forums about Crimson causing black screens when using third party programs to overclock (usually when overclocking the video memory, when such overclock requires a voltage increase).
The forum thread was here:
https://community.amd.com/thread/197510
On the forums someone mentioned this registry variable and command:
REG DELETE HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000 /v PP_EscapeInput /f
The command is correct but the variable is from the old CCC drivers.
The correct one for Crimson is PP_CNEscapeInput
Deleting this manually before rebooting will cause Crimson to use pure original defaults on the next windows load. Of course any changes you make will be updated again so this has to be done via a script if you want it done whenever you reboot (which I don't know how to do). No idea how to make it apply if the overclock crashes as soon as you apply it though
As I mentioned in the AMD thread, what we need is a driver setting (EVEN if it's under power users, hidden, whatever) to make crimson either IGNORE this registry value (PP_CNEscapeInput), or just use pure defaults on every load (pretty much the same thing). Right now it's loading the last set GPU/Memory clocks (regardless if set through Afterburner, Trixx or Crimson) but NOT the voltages, which means memory clocks which require extra GPU voltage to work (e.g., like +25 VDDC at 1500 MHz GDDR5 on R9 290 series cards) will instantly black screen after windows boot as soon as any load forces the memory clocks from idle speed (150 MHz).
This should not be hard to implement. And this issue never happened in CCC--CCC always used pure driver defaults whenever you restarted the computer. (I think sometimes power limit was retained but not clocks).
The forum thread was here:
https://community.amd.com/thread/197510
On the forums someone mentioned this registry variable and command:
REG DELETE HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000 /v PP_EscapeInput /f
The command is correct but the variable is from the old CCC drivers.
The correct one for Crimson is PP_CNEscapeInput
Deleting this manually before rebooting will cause Crimson to use pure original defaults on the next windows load. Of course any changes you make will be updated again so this has to be done via a script if you want it done whenever you reboot (which I don't know how to do). No idea how to make it apply if the overclock crashes as soon as you apply it though
As I mentioned in the AMD thread, what we need is a driver setting (EVEN if it's under power users, hidden, whatever) to make crimson either IGNORE this registry value (PP_CNEscapeInput), or just use pure defaults on every load (pretty much the same thing). Right now it's loading the last set GPU/Memory clocks (regardless if set through Afterburner, Trixx or Crimson) but NOT the voltages, which means memory clocks which require extra GPU voltage to work (e.g., like +25 VDDC at 1500 MHz GDDR5 on R9 290 series cards) will instantly black screen after windows boot as soon as any load forces the memory clocks from idle speed (150 MHz).
This should not be hard to implement. And this issue never happened in CCC--CCC always used pure driver defaults whenever you restarted the computer. (I think sometimes power limit was retained but not clocks).