Custom Resolution Utility (CRU)

[SkOrPn]

Quick question please, and hello to all.

I built my own Yamakasi type monitor 2 years ago (2014) using a 2013 grade A panel direct from LG/Megatron (from HP wharehouse). It is a panel meant for the HP Z1 Workstation and is a LM270WQ1, just the same panel you find in overclocking Yamakasi's except Grade A worstation quality. I then purchased a Overclocking kit same as Overlords kit (I have all the pics). This was in 2014 and I was on Windows 7 using a AMD 5870. The monitor overclocked to 110Hz without fail, then I dropped it down to normal 60 hz so I could wait for a proper GPU someday, which will be Vega here soon. Since Vega is around the corner I would like to Overclock this again to 96 or 100hz today to see if the Overclocking still works like it did 2 years ago. BUT!

My Problem today is that I am now on Windows 10 (not changing that), and no matter how hard I try NOTHING seems to work like it did 2 years ago. I have CRU 1.3 and its launched as admin but it does not add any custom refresh to the Windows, or to Powerstrip or to the AMD drivers. If I try to raise the refresh using Powerstrip I instantly get all kinds of garbled mess on the screen and I have to hit the power button to restart the PC. If I try to install older inf files such as the "Catleap_Q270_OC_v2.inf" Windows refuses and says there was a problem. Is there something I am missing? Is Windows 10 Pro making this more difficult to accomplish? lol

System specs
Self-built Overclockable LG-LM270WQ1 with Overlord Kit (I expect 120Hz with Vega, but the 5870 was confirmed to do 110Hz on this setup, but I'm only trying 96 Hz today)
AMD 5870 (I know its old but it still works and Vega isn't released yet)
Drivers 15.7.1 = Last official WHQL drivers from 2015.
Really good Dual-Link DVI cable is installed that worked for 110Hz on Windows 7 back in 2014.

IS there a new way to Overclock this display on Windows 10 I haven't found yet, or does CRU still work and I am missing a step? Please point me in the right direction. Thanks


EDIT: Oh boy, let me guess... I forgot to patch the pixel clock using pixel clock patcher 1.4.4? LOL, I don't remember needing to do that 2 years ago, but maybe I did...
EDIT2: OK, I answered my own question. I failed to discover the Pixel Patcher part of the equation. Now its running fantastic and blur busters results couldn't be any better. Now I can't wait to see how this works for Vega, that is if there will be a DVI port on those GPU's..

@ToastyX Thanks for CRU and the patcher. Your awesome...