AMD/ATI Pixel Clock Patcher

[ToastyX]

(07-30-2013 07:49 PM)cypherix93 Wrote:  The problem is I can't get past the 165MHz limit, even after I have used the AMD driver patcher, test mode and all that. Not in the CRU, not in adlutil, nowhere.

I found a weird workaround though - In the EDID, if I set the byte that defines the display input to A5 (DisplayPort), I can get past that 165MHz limit in CRU (adlutil still won't work). I am running at 1080p@85Hz (which is around 203MHz) with custom settings and no problems whatsoever. BUT, AMD HD3D won't work under this configuration. Yes, it works without the EDID override.

I've noticed that if I keep everything else intact, and set the display input byte to A2 (HDMI 1.4a), AMD HD3D starts working, but I can't get past 165Hz (with my resolution and timings, it's maxed at 1080p@66.666Hz). So I am stuck... If I want 85Hz, I can't use HD3D. If I use HD3D, I am stuck at 67Hz.

I'm not able to reproduce the 165 MHz limit. Changing the display input byte makes no difference for me. Maybe there's something in the extension block that's causing the limit.

I need something that can read the extension block. Try this: http://devgurus.amd.com/servlet/JiveServ...ID-1.2.zip

Run OutputToFile.bat and paste the contents of the text file it produces.

I don't know what HD3D looks for. What happens if you disable the extension block?

(07-30-2013 07:49 PM)cypherix93 Wrote:  P.S. I don't know why HD3D works with my default config though (DVI to HDMI adapter). I have a dual link adapter, and it doesn't work with that. Is the single link adapter special? It came with the GPU btw... Did ASUS do something special to it?

The adapter shouldn't matter. HDMI is always single-link. Some adapters might have dummy pins, but that shouldn't affect anything.