T
TechPrince
Guest
I previously had :
i5 760
Gigabyte P55-USB3
Sapphire Raedon HD 7770 with 14.12 catalyst drivers.
AOC 2236VW connected via DVI cable to GPU
Windows 7 x64
Recently i bought AMD FX 6300 processor with Gigabyte 76LMT-USB3 Rev 6 motherboard, formatted and installed Windows 7 SP1 and reinstalled all the drivers and softwares. I noticed a weird thing that my display stopped stretching when resolution was less than its native 1920x1080 and black bars are started to appear on top and bottom of the screen. This problem wasn't there before.
Monitor is set at 16:9 ratio which works perfectly fine before OS loads (POST, BIOS). Now in windows, screen fills perfectly at 1680x1050, 1440x900, 1280x960, 1280x720, 1024x768, 800x600 in desktop resolutions.
I do not have overscan / underscan options in CCC. All i have is GPU upscaling but that produces some FPS drops in my games. I already tried uninstalling then reinstalling the monitor drivers + catalyst drivers, re-seating the GPU, reconnecting the DVI cable however the problem remains the same.
i5 760
Gigabyte P55-USB3
Sapphire Raedon HD 7770 with 14.12 catalyst drivers.
AOC 2236VW connected via DVI cable to GPU
Windows 7 x64
Recently i bought AMD FX 6300 processor with Gigabyte 76LMT-USB3 Rev 6 motherboard, formatted and installed Windows 7 SP1 and reinstalled all the drivers and softwares. I noticed a weird thing that my display stopped stretching when resolution was less than its native 1920x1080 and black bars are started to appear on top and bottom of the screen. This problem wasn't there before.
Monitor is set at 16:9 ratio which works perfectly fine before OS loads (POST, BIOS). Now in windows, screen fills perfectly at 1680x1050, 1440x900, 1280x960, 1280x720, 1024x768, 800x600 in desktop resolutions.
I do not have overscan / underscan options in CCC. All i have is GPU upscaling but that produces some FPS drops in my games. I already tried uninstalling then reinstalling the monitor drivers + catalyst drivers, re-seating the GPU, reconnecting the DVI cable however the problem remains the same.
Last edited by a moderator: