Post Reply
AMD/ATI Pixel Clock Patcher
06-15-2017, 10:16 PM (Last edited: 06-15-2017, 10:19 PM by kilyan)
Post: #781
RE: AMD/ATI Pixel Clock Patcher
latest crimson 17.6.2 gives error "failed create driver link".
17.6.1 works
Find all posts by this user
Quote this message in a reply
06-16-2017, 05:48 AM
Post: #782
RE: AMD/ATI Pixel Clock Patcher
(06-15-2017 10:16 PM)kilyan Wrote:  latest crimson 17.6.2 gives error "failed create driver link".
17.6.1 works

Now it doesn't work even on 17.6.1 wtf...before it worked
Find all posts by this user
Quote this message in a reply
06-16-2017, 06:31 AM
Post: #783
RE: AMD/ATI Pixel Clock Patcher
(06-15-2017 10:16 PM)kilyan Wrote:  latest crimson 17.6.2 gives error "failed create driver link".
17.6.1 works
That can only happen if something messed with the links.

Show me a screen shot of C:\Windows\System32\drivers\atikmdag-patched

Then delete the folder and run the patcher.
Find all posts by this user
Quote this message in a reply
06-16-2017, 07:41 AM
Post: #784
RE: AMD/ATI Pixel Clock Patcher
(06-16-2017 06:31 AM)ToastyX Wrote:  
(06-15-2017 10:16 PM)kilyan Wrote:  latest crimson 17.6.2 gives error "failed create driver link".
17.6.1 works
That can only happen if something messed with the links.

Show me a screen shot of C:\Windows\System32\drivers\atikmdag-patched

Then delete the folder and run the patcher.

http://imgur.com/a/bh4jm

Deleting the folder worked on 17.6.2, so that error is not driver version related. But never happened before, always used the patcher
Find all posts by this user
Quote this message in a reply
06-16-2017, 08:32 AM
Post: #785
RE: AMD/ATI Pixel Clock Patcher
(06-16-2017 07:41 AM)kilyan Wrote:  http://imgur.com/a/bh4jm

Deleting the folder worked on 17.6.2, so that error is not driver version related. But never happened before, always used the patcher
Something weird is going on because the patcher definitely didn't do that. The patcher created the symlink and something replaced it with a file. I'd like to know what because that shouldn't be happening.
Find all posts by this user
Quote this message in a reply
06-16-2017, 09:57 AM (Last edited: 06-16-2017, 09:58 AM by kilyan)
Post: #786
RE: AMD/ATI Pixel Clock Patcher
I used DDU to clean the previous driver, installe 17.6.2 and installed msi afterburner, maybe msi afterburner messed something, i don't know. Well, i uninstalled it already, it doesn't work for me.
Find all posts by this user
Quote this message in a reply
06-16-2017, 01:01 PM (Last edited: 06-16-2017, 01:02 PM by Hash)
Post: #787
RE: AMD/ATI Pixel Clock Patcher
Seems that i can't run 6 GPU's on Windows 10 anymore using the RX500 series. Anyone got a solution for that? Used old driver but using them will cause lots of issues when it comes to oc and bios modding.
Find all posts by this user
Quote this message in a reply
06-27-2017, 04:57 PM
Post: #788
RE: AMD/ATI Pixel Clock Patcher
is it no longer nessascary to use "atikmdag-patcher-bios" if we are only trying to get are cards recognized by the drivers after a bios update? i dont see that in the instructions anymore. also, what is the most recent driver version this functions with? im currently using 17.6.2 but not sure if it works higher.
Find all posts by this user
Quote this message in a reply
06-29-2017, 12:55 AM
Post: #789
RE: AMD/ATI Pixel Clock Patcher
(06-27-2017 04:57 PM)madLyfe Wrote:  is it no longer nessascary to use "atikmdag-patcher-bios" if we are only trying to get are cards recognized by the drivers after a bios update? i dont see that in the instructions anymore. also, what is the most recent driver version this functions with? im currently using 17.6.2 but not sure if it works higher.
The instructions haven't changed. The -bios option still works. It's not documented here. 17.6.2 is currently the latest driver available.
Find all posts by this user
Quote this message in a reply
07-06-2017, 01:38 AM (Last edited: 07-06-2017, 01:51 AM by ottoman)
Post: #790
RE: AMD/ATI Pixel Clock Patcher
I've been facing issues with my GPU ever since installing 17.6.2 AND patching it with 1.4.5

My eventlog is filled with this at random intervals (there are always some within the hour though)
Code:
Activation context generation failed for "c:\program files\amd\cim\bin64\SetACL64.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis.

Using "WhoCrashed" I've got the results below.I've had my PC crashing when left idle overnight and that led me to do a clean installation (plus getting an AM4 system) with latest 10 iso available.
Another thing to note is that, I have not had issues idling with my PC until the update 17.6.2 and patching ontop of it.Earlier Crimson versions I had no issues at all.
Extra notes:
I have HD 7790 that still gets driver support to latest, not legacy model.
I've run memtest86 after those issues occured, no errors were found.
I have a DVI-D connected screen at 73.5 Hz 1080p and a second monitor VGA to DVI-I 83.50 Hz at 900p.
I don't know if it's the driver itself, or the patch.But looking at the driver's location from below screenshot it has potential to be related.
[Image: GFrQ5Un.png]

My patch folder if needed.
[Image: irreW08.png]
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


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