Just installed Windows 8 and downloaded the Catalyst version which ATI website recommended. However it says that it can't start! My main monitor is connected to my PC via a HDMI cable and the display is not full screen (there is a blank padding area around display). Usually I change overscan/underscan settings in CCC to reset it but since I have no access to it, I wanted to know if there is any way I can change it without CCC (through registry maybe?) Thanks.
I've had extensive discussion about the overscan/underscan dilemma with AMD developers who work on the Catalyst drivers.
The basic idea is that AMD would rather underscan some people whose HDMI displays don't overscan, and create too small of a picture (blank spaces around the picture), rather than not underscan and cause people whose displays always overscan (with no setting to change it and incorrect EDID information) to have the desktop display too large. The argument is that if the desktop is too large, then the user can't see where the Catalyst icon is or the start menu, and they therefore can't navigate the UI in order to make the appropriate change. So they are sticking to their guns on underscanning by default on HDMI to ensure that nobody gets stuck with a desktop that's too big for their screen (with UI elements hanging "off the screen").
I don't agree with the policy, but that's the way it is. It also seems to be a fairly unique decision among graphics driver developers, as I can't reproduce the weirdness on a number of other non-AMD devices: Android tablets, Nvidia cards, and Intel on-chip graphics.
There is a way to directly tweak the underscan/overscan on Linux by modifying values in the "PCSDB" (Persistent Configuration Store Database). I don't know what the equivalent is on Windows, or if you can even read/write the settings without using Catalyst.
I can't personally test this solution, but it appears that it worked for people on fairly recent drivers, so give it a shot: go to Tom's Hardware or I'll just re-post it here:
For Linux, the fix is to enter this in the Terminal:
(posting this here to just need a single bookmark for all platforms)
I had a similar problem, and wasn't able to install Catalyst Control Center...so also unable to adjust the underscan setting.
I was able to overcome it (more like mask the issue really) and adjust the Screen size setting on my Samsung TV that I have my PC connected to. By the sounds of it this exactly what AMD were trying to work around.
Now I can see the whole screen in 1080p, and luckily the TV is clever enough to have different screen size settings for each hdmi input.
Perhaps a similar approach might work for PC monitors?
This isn't directly for win8 but it worked in server 2012r2 so I assume it is at least parrotable in 8.1 or 8. Anyway I removed the default underscan? (image is smaller than display) by editing the BestViewOption_Hdmi binary key found at
where the GUID you are looking for is which ever one has lots of keys in
This is on Server 2012r2 using CCC 14.1beta
Anyway hope this helps someone.
I have a Hp pavilion dv6 with ati hd 4650 with windows 8.1 update.
In windows 8 it worked fine to change the values but in windows 8.1 update windows keep restoring the values so that black border is constant.
I solved it by specifically add user “system” to the 0000 regkey and anly allow system to read the values, and applied these security settings down on all keys,subkeys.
And now it works fine in Windows 8.1 to.
Hopes it helps someone.
I couldn't get it working with my Radeon HD 3600 on Windows 8.1 64bit with the proposed solutions from here. I tried everything including
Here's what finally worked for me - ending up with no CCC installed!
Now I have a sharp picture without CCC.
Installing CC in a different folder is all I needed to do to fix this. The default folder was corrupted no matter what.
Had the same problem and my solution is:
use regedit to set keys:
Reboot and see if it works
Changing only the first two values does not work for me.
You need to replace the *s with the approriate values found in your registry. I also quess that "0000" is the first screen, "0001" is the second and so on (the first one is my HDTV and the second one a common PC monitor - which had TVEnableOverscan set to 0 already)
I changed my registry settings (like said above) and changed my hdmi cable - nothing changed.
Then I shut down my PC, removed my second screen (DVI) and rebooted: everything fine now!
Maybe this saves someone some hours of testing and research...
For my oldish Samsung LCD I was able to fix the issue by changing P.SIZE from 16:9 to "Just Scan". Before now I had always installed the control center, lame!
I used steffen's answer to get this working on Windows 10 and tracked it down in a bit more detail.
I had previously tried disabling
Firstly, on Windows 10 the unpacked installer package (13.4 beta) refuses to run. Instead I went to Device Manager and uninstalled the display adapter, checking the box to delete the driver. I then chose Action->Scan for hardware changes and got a "Microsoft Basic Display Adapter". I right-clicked and chose update driver, then chose the option to specify the driver myself. I picked the folder
At this point I was able to adjust the overscan whilst running Process Monitor and watching which registry values were being set when I pressed Apply:
I believe the prefixes are the same paths resolved by the key
Finally, I again uninstalled the display adapter driver from Device Manager (including deleting the driver). Windows automatically went through another prolonged detection cycle and returned to the original, Microsoft-supplied driver. For some reason CCC appears to still work and now displays the more modern driver version. This allowed me to make the change in the GUI again and observe the effect. Confusingly, new entries are created under the
I did not test this without having first installed CCC but it was still working after removing it. I can only assume they are read by the driver: at worst at startup and probably on every major display event (like changing resolution).
Windows 10 TH2 (Threshold 2)
After install TH2 the overscan was back and worse. The binary blobs have changed size and the default is now 8 instead of 2. The driver version remains the same and the location of the binary data remains the same. DALR6 ones are still at byte 37 (offset 0x24), GDOADJR6 is still at byte 21 (offset 0x14). I initially mis-read the hex offsets in RegEdit, so installed the same Catalyst 13.4 beta VISION Control Center as before (without the driver). This time it worked first time and was immediately able to control the overscan from the GUI.
protected by Mokubai♦ Jan 4 '15 at 8:33
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site.
Would you like to answer one of these unanswered questions instead?