Monitor Tests Forum

Full Version: AMD/ATI Pixel Clock Patcher
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
(02-28-2013 03:16 AM)Gil Wrote: [ -> ]Since I've started using CRU-p4 and the driver patcher, I see the frame rate on the top left corner in bright yellow colour.

How can one get rid of it?
Some program you're using is doing that such as Fraps or RadeonPro.

(02-28-2013 03:16 AM)Gil Wrote: [ -> ]Also, I've tried OC my refresh rate to no avail. I get a message on my LCD after I reboot to have the changes take affect, that the timings are not correct. But I used the my own LCD timings.

I use DELL U2412M and ATI HD6950 with latest drivers.
Some monitors simply can't handle higher refresh rates. 1920x1200 monitors are less likely to support higher refresh rates than 1080p monitors because of the higher pixel clocks and horizontal scan rates required.
I get a blue screen when booting Windows 7. I have a MSI Hd Radeon R7970 PE. Why is it doing that?
You need to enable test mode before rebooting. It can be enabled in safe mode.
I apply the patch, and then enable test mode. Reboot.

I found out that my monitor doesn't overclock well, so I decided to revert to normal mode. Reboot.

Then, my PC can't detect my GPU on windows. How to solve this?

Thank you.
Did you run the patcher again to restore the unpatched driver? The patched driver won't load if test mode is disabled.

Did you remove the overclock in CRU? You can also use reset-all.exe to reset all the monitors.
Hello ToastyX, I restored the unpatched driver and now my GPU is detected again.

Correct me if I'm wrong, the patched driver will only work on test mode, so we have to use test mode all the time to run the monitor past 330 MHz pixel clock limit. I'm on Windows 8 Professional x64.

Thank you.
(05-03-2013 11:09 AM)partogi Wrote: [ -> ]Correct me if I'm wrong, the patched driver will only work on test mode, so we have to use test mode all the time to run the monitor past 330 MHz pixel clock limit.
That's correct.
First of all, thank you for the patcher ToastyX!

2nd, I've found a conflict with another program. I'm not sure if you're familiar with MadVR, but in a nutshell, it's an ultra high quality video renderer. Whenever I use the pixel clock patcher, MadVR won't play videos (though audio still comes through). As soon as I restore the values, MadVR works again.

This happens on W8 64 bit/13.5 beta at 2560x1440 on a 6850 crossfire setup, and I vaguely remember having the same issue with older drivers. The refresh rate I set doesn't seem to matter.

MadVR's thread is here, and I'll probably mention the problem there once my 5 day registration period is up.
http://forum.doom9.org/showthread.php?t=146228
You need to disable hardware acceleration in the video decoder. If you're using LAV, set the hardware decoder to "None" in the video decoder settings.
Hello,

i need a pixel clock patch for Linux. I have installed Catalyst 13.4 on a Debian machine.
Can you help me?

Best regards

Thomas
Reference URL's