F5F Stay Refreshed Power Users Overclocking Black screen right away after setting a new core clock for the GPU?

Black screen right away after setting a new core clock for the GPU?

Black screen right away after setting a new core clock for the GPU?

K
Killemandrun
Member
162
06-01-2016, 01:56 PM
#1
My build details are as follows:
https://au.pcpartpicker.com/user/sadpwne...iew=nxMkcf
It's a 500watt PSU, not 550.
I'm using an MSI afterburner with a power limit of +20.
When I raise my core clock to 1030mhz, do I get a black screen?
I managed to increase it from 980 in steps of 10b4.
K
Killemandrun
06-01-2016, 01:56 PM #1

My build details are as follows:
https://au.pcpartpicker.com/user/sadpwne...iew=nxMkcf
It's a 500watt PSU, not 550.
I'm using an MSI afterburner with a power limit of +20.
When I raise my core clock to 1030mhz, do I get a black screen?
I managed to increase it from 980 in steps of 10b4.

L
lazypigman
Junior Member
8
06-02-2016, 09:06 PM
#2
Please download OCCT and run the GPU test with error checking. This program identifies issues that aren't visible, such as artifacts, driver crashes, and potential BSODs. The problem lies in pushing your clocks too high, causing the GPU to overheat. Increasing voltage might boost OC speeds but also generates excessive heat. OCCT will force the GPU much harder than Unigine Valley, leading to higher temperatures and possible throttling due to heat. It's recommended to upgrade one clock at a time and record the maximum stable clock before resetting.
L
lazypigman
06-02-2016, 09:06 PM #2

Please download OCCT and run the GPU test with error checking. This program identifies issues that aren't visible, such as artifacts, driver crashes, and potential BSODs. The problem lies in pushing your clocks too high, causing the GPU to overheat. Increasing voltage might boost OC speeds but also generates excessive heat. OCCT will force the GPU much harder than Unigine Valley, leading to higher temperatures and possible throttling due to heat. It's recommended to upgrade one clock at a time and record the maximum stable clock before resetting.

R
Rayack
Senior Member
539
06-09-2016, 10:56 AM
#3
If you encounter a black screen while speaking, it means you are exceeding the recommended settings. The power limit only controls how the Core clock reduces its speed because of heat. It does not increase voltage for the GPU. Download OCCT and perform the GPU test with error checking turned on. Configure shaders to 7 or above for AMD GPUs and 3 for Nvidia. If errors appear, your OC is unstable; you must lower the core clock or memory clock. Run this test for an hour before declaring it stable.

EDIT:
During testing, avoid using the PC as it may produce misleading error results or fail to assess correctly.
R
Rayack
06-09-2016, 10:56 AM #3

If you encounter a black screen while speaking, it means you are exceeding the recommended settings. The power limit only controls how the Core clock reduces its speed because of heat. It does not increase voltage for the GPU. Download OCCT and perform the GPU test with error checking turned on. Configure shaders to 7 or above for AMD GPUs and 3 for Nvidia. If errors appear, your OC is unstable; you must lower the core clock or memory clock. Run this test for an hour before declaring it stable.

EDIT:
During testing, avoid using the PC as it may produce misleading error results or fail to assess correctly.

0
0Slender0
Member
211
06-14-2016, 05:52 PM
#4
If you encounter a black screen, it means you're pushing the system too far. The power limit only controls how the Core clock reduces due to heat; it doesn't increase voltage for the GPU. Download OCCT and perform the GPU test with error checking turned on. Set shaders to 7 or above for AMD GPUs and 3 for Nvidia. If errors appear, your OC is unstable and you should lower the core clock or memory clock. Run this test for an hour before considering it stable.

EDIT:
While running the test, avoid using the PC as it may produce false positives or inaccurate results. I've been checking stability with the unigine valley benchmark while keeping an eye on temperatures. The issue arises when entering 1025mhz as the clock value and applying it in msi afterburner. It causes a black screen, preventing further testing. I can use 1024mhz instead.

My current settings are:
core: 1024
Mem: 1695
0
0Slender0
06-14-2016, 05:52 PM #4

If you encounter a black screen, it means you're pushing the system too far. The power limit only controls how the Core clock reduces due to heat; it doesn't increase voltage for the GPU. Download OCCT and perform the GPU test with error checking turned on. Set shaders to 7 or above for AMD GPUs and 3 for Nvidia. If errors appear, your OC is unstable and you should lower the core clock or memory clock. Run this test for an hour before considering it stable.

EDIT:
While running the test, avoid using the PC as it may produce false positives or inaccurate results. I've been checking stability with the unigine valley benchmark while keeping an eye on temperatures. The issue arises when entering 1025mhz as the clock value and applying it in msi afterburner. It causes a black screen, preventing further testing. I can use 1024mhz instead.

My current settings are:
core: 1024
Mem: 1695

S
SpencerHaber
Junior Member
16
06-19-2016, 06:03 AM
#5
Please download OCCT and run the GPU test with error checking. This tool will identify issues that aren't immediately visible, such as artifacts, driver crashes, and potential BSODs.

The problem lies in pushing your clocks too high, causing the GPU to struggle. Increasing voltage might boost higher OC values but also generates excessive heat. OCCT will force the GPU much harder than Unigine Valley, leading to noticeable temperature spikes and possible throttling due to heat.

It's advisable to overclock one clock at a time, recording the maximum stable clock and reset, then proceed sequentially. This approach helps the clocks reach their limits safely for testing.

If you encounter black screens despite the GPU handling high core clocks, it suggests instability—even if the GPU technically supports 1024MHz, the performance drops to 1025 causing a crash. In my experience, a stable clock is reached before such failures occur.
S
SpencerHaber
06-19-2016, 06:03 AM #5

Please download OCCT and run the GPU test with error checking. This tool will identify issues that aren't immediately visible, such as artifacts, driver crashes, and potential BSODs.

The problem lies in pushing your clocks too high, causing the GPU to struggle. Increasing voltage might boost higher OC values but also generates excessive heat. OCCT will force the GPU much harder than Unigine Valley, leading to noticeable temperature spikes and possible throttling due to heat.

It's advisable to overclock one clock at a time, recording the maximum stable clock and reset, then proceed sequentially. This approach helps the clocks reach their limits safely for testing.

If you encounter black screens despite the GPU handling high core clocks, it suggests instability—even if the GPU technically supports 1024MHz, the performance drops to 1025 causing a crash. In my experience, a stable clock is reached before such failures occur.