Post Reply
AMD/ATI Pixel Clock Patcher
09-15-2016, 09:51 PM
Post: #661
RE: AMD/ATI Pixel Clock Patcher
(09-15-2016 07:39 PM)Sampulla Wrote:  I am having a problem with newest version of patcher 1.4.1 and 16.9.1 WHQL driver. I am using Windows 10 anniversary with latest updates. When i try to patch it gives me error: Failed to create driver links. Using DDU and reinstalling drivers didnt help.
Is this happening with the 64-bit version of Windows? Are you using any antivirus software?
Find all posts by this user
Quote this message in a reply
09-15-2016, 10:20 PM (Last edited: 09-15-2016, 10:27 PM by the9quad)
Post: #662
RE: AMD/ATI Pixel Clock Patcher
(09-15-2016 01:24 AM)ToastyX Wrote:  This should work: https://www.monitortests.com/atikmdag-patcher-1.4.1.zip

If you used the old 1.3.6 patcher, you'll have to run it three times to patch it the new way. The first time, it will just fix the low-resolution limit and leave everything else alone. The second time, it will restore from backup. The third time, it will patch the new way. You only need to reboot after the third time.

Thanks toasty, didn't expect a fix to be honest. Just though I'd report the issue. That works by the way.

I am on 64 bit windows, I don't use anti-virus
Find all posts by this user
Quote this message in a reply
09-16-2016, 07:21 AM
Post: #663
RE: AMD/ATI Pixel Clock Patcher
(09-15-2016 09:51 PM)ToastyX Wrote:  Is this happening with the 64-bit version of Windows? Are you using any antivirus software?

I am using 64bit windows and Avira free antivirus. I tried disabling realtime protection on it, but that didn't help. Avira hasn't given me any problems before, but i will try uninstalling it for patching later today.
Find all posts by this user
Quote this message in a reply
09-22-2016, 07:33 PM
Post: #664
RE: AMD/ATI Pixel Clock Patcher
Hello. I'm new here. I've been using this utility and the CRU for a long time.
Now I think I might have found an issue that I wish to report.

I have a Radeon R9 380X and Windows 10 with the latest updates.
The drivers are the latest (16.9.2) and the patcher is 1.4.1.
When I wake from sleep, one of my two screens is not detected.
The one not detected is a DVI Samsung 226VL and the detected one is a VGA (DVI to VGA) LG Flatron L192WS.

Could someone check if he experiences the same bug and is it due to the drivers or the patcher? Thanks.
Find all posts by this user
Quote this message in a reply
09-23-2016, 02:29 AM
Post: #665
RE: AMD/ATI Pixel Clock Patcher
And now it, sometimes, doesn't even wake from sleep. Sad
Find all posts by this user
Quote this message in a reply
09-24-2016, 04:15 PM
Post: #666
RE: AMD/ATI Pixel Clock Patcher
(09-22-2016 07:33 PM)191x7 Wrote:  I have a Radeon R9 380X and Windows 10 with the latest updates.
The drivers are the latest (16.9.2) and the patcher is 1.4.1.
When I wake from sleep, one of my two screens is not detected.
The one not detected is a DVI Samsung 226VL and the detected one is a VGA (DVI to VGA) LG Flatron L192WS.

Could someone check if he experiences the same bug and is it due to the drivers or the patcher? Thanks.
This looks more like a driver bug or a hardware issue. Did you try it without the patcher? How about with the patcher and no changes with CRU?
Find all posts by this user
Quote this message in a reply
09-25-2016, 02:05 AM
Post: #667
RE: AMD/ATI Pixel Clock Patcher
(09-15-2016 07:39 PM)Sampulla Wrote:  I am having a problem with newest version of patcher 1.4.1 and 16.9.1 WHQL driver. I am using Windows 10 anniversary with latest updates. When i try to patch it gives me error: Failed to create driver links. Using DDU and reinstalling drivers didnt help.

Hello Toasty, I'm in the same boat as Sampulla. I was running Windows 10 64-bit using patcher 1.3.6 with no problems (Driver v. 16.9.1) and yesterday I updated to the Anniversary update. A few restarts after the update, my QNIX has reverted to 60hz.

I started from scratch, uninstalled my display driver and updated to 16.9.2 with your patcher v 1.4.1 and I am getting the error message "Failed to create driver links."
When I use patcher 1.3.6 I get instead the message: "Failed to locate driver file"

No patcher versions are working for me, I do not use antivirus, and I've tried everything besides reverting back to Win 10 build 10240.

Let me know if you have any ideas. I'm willing to experiment on your behalf.
Find all posts by this user
Quote this message in a reply
09-25-2016, 03:14 PM
Post: #668
RE: AMD/ATI Pixel Clock Patcher
(09-25-2016 02:05 AM)winterkid09 Wrote:  I started from scratch, uninstalled my display driver and updated to 16.9.2 with your patcher v 1.4.1 and I am getting the error message "Failed to create driver links."
When I use patcher 1.3.6 I get instead the message: "Failed to locate driver file"

No patcher versions are working for me, I do not use antivirus, and I've tried everything besides reverting back to Win 10 build 10240.

Let me know if you have any ideas. I'm willing to experiment on your behalf.
Run this and give me the debug.txt file: https://www.monitortests.com/atikmdag-patcher-debug.zip
Find all posts by this user
Quote this message in a reply
09-25-2016, 08:18 PM
Post: #669
RE: AMD/ATI Pixel Clock Patcher
(09-25-2016 03:14 PM)ToastyX Wrote:  Run this and give me the debug.txt file: https://www.monitortests.com/atikmdag-patcher-debug.zip

Alright, I have it attached.


.txt  debug.txt (Size: 3.64 KB / Downloads: 858)
Find all posts by this user
Quote this message in a reply
09-25-2016, 10:47 PM
Post: #670
RE: AMD/ATI Pixel Clock Patcher
(09-25-2016 08:18 PM)winterkid09 Wrote:  Alright, I have it attached.
The debug log is baffling. Everything looks fine until it abruptly quits with error 183, which means the link already exists, but how can the link already exist? It's creating them in a separate directory, and it removes existing links before creating them.

Does C:\Windows\System32\drivers\atikmdag-patched exist? If so, is there anything in it? If there is, try deleting the atikmdag-patched directory and run the patcher again. Then post the debug.txt here.

If it doesn't exist, then I have no idea what's going on. The debug log shows it's not trying to create the same link twice, and it's not a permissions issue because it has already written to the directory at that point, so I can't think of a reason for this to happen.
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


User(s) browsing this thread: 8 Guest(s)