AMD/ATI Pixel Clock Patcher

[tedlasman]

(03-04-2015 03:47 PM)ToastyX Wrote:  

(03-02-2015 02:42 PM)tedlasman Wrote:  I'm pretty sure it's after i patch it. What should i do?

Does this only happen with custom resolutions? What driver version?

I haven't tried not having a custom resolution (using 96Hz atm)
Here is my display driver info: http://puu.sh/gmecI/c8e6e85c8c.png

[InstantAli3n]

Hey I found a bug with the latest ATI/AMD pixel patcher and Mantle in Crossfire.

If the patcher is used, BF4 trying to run mantle in crossfire will crash on startup with this error
DirectX Mantle
Mantle Function "grWsiWinTakeFullscreenOwnerhsip" failed with GR_ERROR_INVALID_VALUE. GPU: "AMD Radeon R9 200 Series" (26640), Driver: 188743680
http://cdn.overclock.net/9/9d/900x900px-...titled.png

I'm using the 15.x beta and 2 270X's. I'm 100% sure I've narrowed it down to this as I've been at it for close to 8 hours now... It's been a struggle.
I saw it reported on some page in the middle (don't know which one) but I didn't see a solution. Any insight?

[ToastyX]

(03-05-2015 09:29 AM)InstantAli3n Wrote:  Hey I found a bug with the latest ATI/AMD pixel patcher and Mantle in Crossfire.

If the patcher is used, BF4 trying to run mantle in crossfire will crash on startup with this error
DirectX Mantle
Mantle Function "grWsiWinTakeFullscreenOwnerhsip" failed with GR_ERROR_INVALID_VALUE. GPU: "AMD Radeon R9 200 Series" (26640), Driver: 188743680
http://cdn.overclock.net/9/9d/900x900px-...titled.png

I'm using the 15.x beta and 2 270X's. I'm 100% sure I've narrowed it down to this as I've been at it for close to 8 hours now... It's been a struggle.
I saw it reported on some page in the middle (don't know which one) but I didn't see a solution. Any insight?

That's not a patcher bug. CrossFire does not work properly at higher pixel clocks on older cards without two CrossFire bridges. This is listed in the requirements. This should happen even without the patch at 330 MHz pixel clock. R9 270X cards only have one CrossFire connector, so using two bridges is not possible.

(09-07-2012 09:07 PM)ToastyX Wrote:  

• CrossFire requirements:
  • R9 285/290/290X/295X2 cards can handle higher pixel clocks without CrossFire bridges.
  • Older cards require two CrossFire bridges if the pixel clock is greater than 300 MHz. This is only possible with cards that have two connectors. It will not work properly with more than two cards. Dual-GPU cards such as the 7990 will not work properly at higher pixel clocks.
    

[ToastyX]

(03-04-2015 05:32 PM)tedlasman Wrote:  

(03-04-2015 03:47 PM)ToastyX Wrote:  

(03-02-2015 02:42 PM)tedlasman Wrote:  I'm pretty sure it's after i patch it. What should i do?

Does this only happen with custom resolutions? What driver version?

I haven't tried not having a custom resolution (using 96Hz atm)
Here is my display driver info: http://puu.sh/gmecI/c8e6e85c8c.png

Isn't 96 Hz a custom resolution? What timing parameters are you using? Does it happen with the "LCD standard" timing parameters? Does it happen at 60 Hz without any custom resolutions?

Does the problem only happen after logging in? This seems like a driver issue, but usually sleep issues only happen when trying to wake up, not afterwards.

[InstantAli3n]

(03-05-2015 02:52 PM)ToastyX Wrote:  

(03-05-2015 09:29 AM)InstantAli3n Wrote:  Hey I found a bug with the latest ATI/AMD pixel patcher and Mantle in Crossfire.

If the patcher is used, BF4 trying to run mantle in crossfire will crash on startup with this error
DirectX Mantle
Mantle Function "grWsiWinTakeFullscreenOwnerhsip" failed with GR_ERROR_INVALID_VALUE. GPU: "AMD Radeon R9 200 Series" (26640), Driver: 188743680
http://cdn.overclock.net/9/9d/900x900px-...titled.png

I'm using the 15.x beta and 2 270X's. I'm 100% sure I've narrowed it down to this as I've been at it for close to 8 hours now... It's been a struggle.
I saw it reported on some page in the middle (don't know which one) but I didn't see a solution. Any insight?

That's not a patcher bug. CrossFire does not work properly at higher pixel clocks on older cards without two CrossFire bridges. This is listed in the requirements. This should happen even without the patch at 330 MHz pixel clock. R9 270X cards only have one CrossFire connector, so using two bridges is not possible.

(09-07-2012 09:07 PM)ToastyX Wrote:  

• CrossFire requirements:
  • R9 285/290/290X/295X2 cards can handle higher pixel clocks without CrossFire bridges.
  • Older cards require two CrossFire bridges if the pixel clock is greater than 300 MHz. This is only possible with cards that have two connectors. It will not work properly with more than two cards. Dual-GPU cards such as the 7990 will not work properly at higher pixel clocks.
    

THat doesn't make sense, I was able to run Crossfire at 120Hz using the patcher if I used DirectX instead of Mantle. (Though not as smooth as mantle).

[DeadlyDNA]

Thank you ToastyX for everything man. Your prompt updates with the new driver releases is just pure awesome. Soon as i can i am going to send another donation to your cause. You rock!

Between the new driver, and your Pixel clock patch things are working smoother than ever before.

[Balrogos]

Guys how to UNPATCH ? anyway gz with CRU i overclock my LCD from 60hz to 75hz

Okay guys i found:

Quote:To restore the unpatched driver, run the patcher again and click "Yes" to restore from backup.

[mojobear]

Thanks very much Toasty for these patches. Really amazing stuff. Donated

I have 3 Benq Xl2730z monitors and am running catalyst 15.3 (tried with 14.12 and had the same below issue). I have 4 R9 290s. Used pixel patcher 1.3.3 and CRU 1.2 in windows 7 pro 64.

Running eyefinity - DL DVI x 2 + DP

The DL DVI monitors each overclock to 120hz with pixel patcher + CRU (automatic - LCD standard). I can get eyefinity 120 hz 1440p working if I take out the 59.950 hz and replace it with custom resolutions.

Issue is when I then go into a game, my GPUs start to downclock at at any MHZ > 330....aka the normal limit for DL DVI. For me this is about 80 hz. If I try 85 hz....then the issue starts. Any thoughts of what I might be able to do? Could this be driver limitation?

Also - noticed that eyefinity will reset itself back to normal desktop at any custom resolution, whereas 60hz it maintains previous settings after reboot/shutdown.

[Balrogos]

Hey i have some questions the overlock can goes bad when someone using VGA cable with DVI adapters? or just for alone VGA(d-sub) or it must be DVI HDMI or DP?

[Black Octagon]

(04-01-2015 04:42 PM)Balrogos Wrote:  Hey i have some questions the overlock can goes bad when someone using VGA cable with DVI adapters? or just for alone VGA(d-sub) or it must be DVI HDMI or DP?

If you're trying to overclock a Catleap/Tempest/QNIX, use Dual Link DVI only (no adapters)