black screen immediately after entering new core clock for gpu?

Solution
Again, please download OCCT and use the GPU test with error checking on. This program will check for errors that you can not see. Unigine Valley is OK for a benchmark program but not as a stress test program. OCCT will detect errors that you can not see that can cause Artifacts, Driver crashes and possible BSOD.

The issue is you are pushing your clocks to far and the GPU is unable to operate at them. While adding voltage could help get higher OC's it adds a lot of heat also. OCCT will push your GPU a lot harder than valley so you will see the high temps and see if the GPU will throttle due to heat.

It is best to OC one clock at a time and write down the max stable clock and reset and OC the next. This will allow for the clocks to...
If you are getting a black screen as you say then you are pushing the clock to far.

Power limit only adjusts the point that the Core clock will throttle down due to heat. This does not add voltage to the GPU.

Download OCCT and run the GPU test with error checking enabled. Set the shaders to 7 or higher for testing AMD GPU's and 3 for Nvidia. If there are errors detected then your OC is unstable and the core clock or memory clock needs to be lowered. Run this test for 1 hour before calling it stable.

EDIT: while doing this test do not use the PC as it can give false positive errors or not test correctly.
 

sadpwner

Honorable
Aug 28, 2012
12
0
10,510


I've been testing the stability with unigine valley benchmark while monitoring the temps. The problem is the moment I enter 1025mhz as the clock value and click apply in msi afterburner. It gives me a black screen. It doesn't let me do any testing. I can apply 1024mhz fine.

My current clock is
core: 1024
Mem: 1695

I tested them and they are stable.
 
Again, please download OCCT and use the GPU test with error checking on. This program will check for errors that you can not see. Unigine Valley is OK for a benchmark program but not as a stress test program. OCCT will detect errors that you can not see that can cause Artifacts, Driver crashes and possible BSOD.

The issue is you are pushing your clocks to far and the GPU is unable to operate at them. While adding voltage could help get higher OC's it adds a lot of heat also. OCCT will push your GPU a lot harder than valley so you will see the high temps and see if the GPU will throttle due to heat.

It is best to OC one clock at a time and write down the max stable clock and reset and OC the next. This will allow for the clocks to reach there max and be added together at the end for testing.

If you are getting black screens like you say you are pushing your clocks to far. Even if the GPU can handle 1024MHz on the core clock I'm willing to say it is unstable because it is giving a black screen at 1025. In my experience with overclocking GPU's the stable clock comes long before the black screen.
 
Solution