Threaded Mode | Linear Mode

***ToastyX*** · 04-17-2016, 12:20 AM

(04-16-2016 11:48 PM)kilyan Wrote: Maybe 16.4.1 is not compatible with the patch?

It's definitely compatible. I just checked to make sure. I'm not seeing any reversion.

(04-16-2016 11:48 PM)kilyan Wrote: the weirdest thing is i did a clean install of 16.4.1 and when reverts back by applying the patch, it goes to 16.3, not 16.3.1-2 etc.., but the patch is there. If i don't apply the patch i cannot overclock, every frequence results in a blurry screen.

I don't see how that can happen. Maybe the software is not reporting the version correctly for some reason. Does it revert back to 16.4.1 if you run the patcher again and restore from backup?

kilyan · 04-17-2016, 12:59 AM

(04-17-2016 12:20 AM)ToastyX Wrote:
(04-16-2016 11:48 PM)kilyan Wrote: Maybe 16.4.1 is not compatible with the patch?
It's definitely compatible. I just checked to make sure. I'm not seeing any reversion.

(04-16-2016 11:48 PM)kilyan Wrote: the weirdest thing is i did a clean install of 16.4.1 and when reverts back by applying the patch, it goes to 16.3, not 16.3.1-2 etc.., but the patch is there. If i don't apply the patch i cannot overclock, every frequence results in a blurry screen.
I don't see how that can happen. Maybe the software is not reporting the version correctly for some reason. Does it revert back to 16.4.1 if you run the patcher again and restore from backup?

It stays 16.3

***ToastyX*** · 04-18-2016, 02:12 PM

(04-17-2016 12:59 AM)kilyan Wrote:
(04-17-2016 12:20 AM)ToastyX Wrote: I don't see how that can happen. Maybe the software is not reporting the version correctly for some reason. Does it revert back to 16.4.1 if you run the patcher again and restore from backup?
It stays 16.3

What is the file size in bytes of C:\Windows\System32\drivers\atikmdag.sys after patching and after restoring from backup?

kilyan · 04-18-2016, 05:19 PM

(04-18-2016 02:12 PM)ToastyX Wrote:
(04-17-2016 12:59 AM)kilyan Wrote:
(04-17-2016 12:20 AM)ToastyX Wrote: I don't see how that can happen. Maybe the software is not reporting the version correctly for some reason. Does it revert back to 16.4.1 if you run the patcher again and restore from backup?
It stays 16.3
What is the file size in bytes of C:\Windows\System32\drivers\atikmdag.sys after patching and after restoring from backup?

***ToastyX*** · 04-19-2016, 04:12 AM

I need the exact size in bytes as shown in the file properties.

kilyan · (Last edited: 04-19-2016, 05:39 AM by kilyan)

(04-19-2016 04:12 AM)ToastyX Wrote: I need the exact size in bytes as shown in the file properties.

not patched=26.345.472 byte dimension and dimension on disc are the same

patched=dimension:26.349.632 byte
dimension on disc:26.353.664 byte

Transmaniacon · 04-19-2016, 10:04 PM

Hi there, I recently purchased a HP 25XW monitor, which is 1080P and 60Hz stock. This monitor can be overclocked to 75Hz according to the NCX review. I have an AMD R9 390X with Crimson 16.4.1 connected to the monitor via HDMI.

I went in and applied the patcher, it found all of them except the 640X480. I then went into CRU and added a profile for 75Hz. When I went into my monitor properties I didn't see anything higher than 60Hz. In the Crimson utility, there is an option to set a custom resolution, but the highest it will let me go is 68Hz with a pixel clock of 168.3MHz. Am I doing something wrong here? Should every monitor of the same model overclock the same? I would like to get this up to 75Hz, but so far I am having no luck. Any ideas?

kilyan · (Last edited: 04-19-2016, 10:56 PM by kilyan)

(04-19-2016 10:04 PM)Transmaniacon Wrote: Hi there, I recently purchased a HP 25XW monitor, which is 1080P and 60Hz stock. This monitor can be overclocked to 75Hz according to the NCX review. I have an AMD R9 390X with Crimson 16.4.1 connected to the monitor via HDMI.

I went in and applied the patcher, it found all of them except the 640X480. I then went into CRU and added a profile for 75Hz. When I went into my monitor properties I didn't see anything higher than 60Hz. In the Crimson utility, there is an option to set a custom resolution, but the highest it will let me go is 68Hz with a pixel clock of 168.3MHz. Am I doing something wrong here? Should every monitor of the same model overclock the same? I would like to get this up to 75Hz, but so far I am having no luck. Any ideas?

use cru, not custom resolution than it will work.. i managed to reach 77hz on 1920x1080m but trying to figure out with the help of toasty, why my driver is reverting to 16.3 from 16.4.1 after using the patch. besides of that, it works. YOu need also to restart driver after setting the monitor frequence

Transmaniacon · 04-19-2016, 11:07 PM

(04-19-2016 10:55 PM)kilyan Wrote:
(04-19-2016 10:04 PM)Transmaniacon Wrote: Hi there, I recently purchased a HP 25XW monitor, which is 1080P and 60Hz stock. This monitor can be overclocked to 75Hz according to the NCX review. I have an AMD R9 390X with Crimson 16.4.1 connected to the monitor via HDMI.

I went in and applied the patcher, it found all of them except the 640X480. I then went into CRU and added a profile for 75Hz. When I went into my monitor properties I didn't see anything higher than 60Hz. In the Crimson utility, there is an option to set a custom resolution, but the highest it will let me go is 68Hz with a pixel clock of 168.3MHz. Am I doing something wrong here? Should every monitor of the same model overclock the same? I would like to get this up to 75Hz, but so far I am having no luck. Any ideas?

use cru, not custom resolution than it will work.. i managed to reach 77hz on 1920x1080m but trying to figure out with the help of toasty, why my driver is reverting to 16.3 from 16.4.1 after using the patch. besides of that, it works. YOu need also to restart driver after setting the monitor frequence

Are you using the same monitor? I just did it with CRU and if I entered a 75Hz refresh rate, it wouldn't show up in the drop down for my monitor. But if I put in 68Hz, then I can choose that when in display settings. Not sure why I can't get over the hump, could my cable be limiting the refresh rate?

kilyan · (Last edited: 04-19-2016, 11:14 PM by kilyan)

(04-19-2016 11:07 PM)Transmaniacon Wrote:
(04-19-2016 10:55 PM)kilyan Wrote:
(04-19-2016 10:04 PM)Transmaniacon Wrote: Hi there, I recently purchased a HP 25XW monitor, which is 1080P and 60Hz stock. This monitor can be overclocked to 75Hz according to the NCX review. I have an AMD R9 390X with Crimson 16.4.1 connected to the monitor via HDMI.

I went in and applied the patcher, it found all of them except the 640X480. I then went into CRU and added a profile for 75Hz. When I went into my monitor properties I didn't see anything higher than 60Hz. In the Crimson utility, there is an option to set a custom resolution, but the highest it will let me go is 68Hz with a pixel clock of 168.3MHz. Am I doing something wrong here? Should every monitor of the same model overclock the same? I would like to get this up to 75Hz, but so far I am having no luck. Any ideas?

use cru, not custom resolution than it will work.. i managed to reach 77hz on 1920x1080m but trying to figure out with the help of toasty, why my driver is reverting to 16.3 from 16.4.1 after using the patch. besides of that, it works. YOu need also to restart driver after setting the monitor frequence

Are you using the same monitor? I just did it with CRU and if I entered a 75Hz refresh rate, it wouldn't show up in the drop down for my monitor. But if I put in 68Hz, then I can choose that when in display settings. Not sure why I can't get over the hump, could my cable be limiting the refresh rate?

You put 68 with cru or crimson? try also to set no block option in the lower part of cru, and lcd standard or lcd reduced, if you have not tried yet