Post Reply
Custom Resolution Utility (CRU)
04-06-2018, 08:04 PM (Last edited: 04-06-2018, 08:08 PM by Luke M)
Post: #3461
RE: Custom Resolution Utility (CRU)
(04-06-2018 05:22 PM)ToastyX Wrote:  
(04-06-2018 03:21 PM)Luke M Wrote:  System: AMD A8-7410 (integrated graphics) / Win10

I'm trying to get AMD to not use the maximum reported resolution, but rather a (standard) resolution I select. Using CRU, I deleted all resolutions except the one I want (1280x800). And rebooted. But it doesn't seem to work, the AMD is still using the wrong resolution.

Any ideas?
Is this a laptop or a desktop? Keep in mind laptop screens can't display non-native resolutions without GPU scaling. If this is for a monitor, make sure to define it as a detailed resolution, not standard, and make sure there are no resolutions in the extension block.

Desktop. 1280x800 is a detailed resolution and I deleted everything else.

After some hours of random fiddling with AMD and Windows settings I was finally able to get 1280x800 output. I don't know how. But it's very fragile. If I disconnect the display and reconnect, for example, it reverts back to the wrong resolution and I don't know how to fix it.

This is for a projector, by the way. 1280x800 is the native resolution.
Find all posts by this user
Quote this message in a reply
04-07-2018, 08:45 PM
Post: #3462
RE: Custom Resolution Utility (CRU)
I installed the latest AMD driver (18.2.1) and...it works! But is this because

1) they fixed a bug

or

2) reinstalling the driver caused it to pick up the CRU EDID settings?

Any guess?
Find all posts by this user
Quote this message in a reply
04-07-2018, 10:53 PM
Post: #3463
RE: Custom Resolution Utility (CRU)
(04-07-2018 08:45 PM)Luke M Wrote:  I installed the latest AMD driver (18.2.1) and...it works! But is this because

1) they fixed a bug

or

2) reinstalling the driver caused it to pick up the CRU EDID settings?

Any guess?
They might have fixed something. What version were you on before?
Find all posts by this user
Quote this message in a reply
04-07-2018, 11:41 PM (Last edited: 04-07-2018, 11:43 PM by Luke M)
Post: #3464
RE: Custom Resolution Utility (CRU)
(04-07-2018 10:53 PM)ToastyX Wrote:  
(04-07-2018 08:45 PM)Luke M Wrote:  I installed the latest AMD driver (18.2.1) and...it works! But is this because

1) they fixed a bug

or

2) reinstalling the driver caused it to pick up the CRU EDID settings?

Any guess?
They might have fixed something. What version were you on before?

17.1.1. Yeah, I think they fixed something.

But I did run into another bug. If I edit the EDIDs of two monitors (both connected), the AMD driver crashes (bugcheck) during boot. If I edit the EDID of only one monitor (either one), then it doesn't crash.

This is the crash stack:

Code:
nt!KeBugCheckEx
nt!MiSystemFault+0x142f1b
nt!MmAccessFault+0x23d
nt!KiPageFault+0x40e
atikmdag+0x8bfa0
atikmdag+0xf1d06d
atikmdag+0xf1cd10
atikmdag+0x857cb
atikmdag+0x9b443
atikmdag+0x9b274
atikmdag+0x9b8de
atikmdag+0x19a92
atikmdag+0x1efd4
atikmpag+0x10805
dxgkrnl!ADAPTER_DISPLAY::DdiCommitVidPn+0x120
dxgkrnl!VIDPN_MGR::CommitVidPn+0xee
dxgkrnl!VIDPN_MGR::CommitVidPnOnAdapter+0x6a4
dxgkrnl!VIDPN_MGR::SetTimingsFromVidPn+0x643
dxgkrnl!DmmSetTimingsOnAdapter+0xe0
dxgkrnl!CCD_TOPOLOGY::ApplyTopologyOnAdapter+0x309
dxgkrnl!CCD_TOPOLOGY::ApplyTopologyWorker+0x6c0
dxgkrnl!CCD_TOPOLOGY::ApplyTopology+0x81
dxgkrnl!DxgkApplyPathsModality+0x5d
win32kbase!DxLddmPrimaryLockCleanUpSinglePDev+0x11e
win32kbase!DrvSetDisplayConfig+0x760
win32kbase!xxxUserSetDisplayConfig+0x224
win32kbase!DrvProcessSetDisplayConfigParameters+0x7b
win32kbase!DrvProcessDxgkDisplayCallout+0x1d0
win32kbase!VideoPortCalloutThread+0x26b
win32kbase!CCompositionToken::`vector deleting destructor'+0xf5b6
win32kfull!NtUserCallNoParam+0x5e
nt!KiSystemServiceCopyEnd+0x13
0x00007ffa`72491124
Find all posts by this user
Quote this message in a reply
04-08-2018, 09:13 PM
Post: #3465
RE: Custom Resolution Utility (CRU)
(04-07-2018 11:41 PM)Luke M Wrote:  17.1.1. Yeah, I think they fixed something.
That's old. I'm not sure about 17.1.1, but 17.2.1-17.3.3 had an issue with EDID overrides not loading. That was fixed in 17.4.1.


(04-07-2018 11:41 PM)Luke M Wrote:  But I did run into another bug. If I edit the EDIDs of two monitors (both connected), the AMD driver crashes (bugcheck) during boot. If I edit the EDID of only one monitor (either one), then it doesn't crash.
That's strange. I haven't heard of that happening. Report it to AMD: http://www.amd.com/report
Find all posts by this user
Quote this message in a reply
04-09-2018, 07:29 PM
Post: #3466
RE: Custom Resolution Utility (CRU)
(04-08-2018 09:13 PM)ToastyX Wrote:  
(04-07-2018 11:41 PM)Luke M Wrote:  17.1.1. Yeah, I think they fixed something.
That's old. I'm not sure about 17.1.1, but 17.2.1-17.3.3 had an issue with EDID overrides not loading. That was fixed in 17.4.1.


(04-07-2018 11:41 PM)Luke M Wrote:  But I did run into another bug. If I edit the EDIDs of two monitors (both connected), the AMD driver crashes (bugcheck) during boot. If I edit the EDID of only one monitor (either one), then it doesn't crash.
That's strange. I haven't heard of that happening. Report it to AMD: http://www.amd.com/report

On further testing, the crash is completely random, not related to multiple overrides. The EDID override I'm using just has 1 detailed resolution and nothing else. I'm guessing that the AMD driver is assuming there's more stuff, and if there isn't, it ends up reading uninitialized memory or something.
Find all posts by this user
Quote this message in a reply
04-12-2018, 02:12 AM (Last edited: 04-12-2018, 02:15 AM by Caveman)
Post: #3467
RE: Custom Resolution Utility (CRU)
Thanks ToastyX for creating this wonderful CRU!
Find all posts by this user
Quote this message in a reply
04-12-2018, 07:01 PM
Post: #3468
RE: Custom Resolution Utility (CRU)
(04-09-2018 07:29 PM)Luke M Wrote:  
(04-08-2018 09:13 PM)ToastyX Wrote:  
(04-07-2018 11:41 PM)Luke M Wrote:  17.1.1. Yeah, I think they fixed something.
That's old. I'm not sure about 17.1.1, but 17.2.1-17.3.3 had an issue with EDID overrides not loading. That was fixed in 17.4.1.


(04-07-2018 11:41 PM)Luke M Wrote:  But I did run into another bug. If I edit the EDIDs of two monitors (both connected), the AMD driver crashes (bugcheck) during boot. If I edit the EDID of only one monitor (either one), then it doesn't crash.
That's strange. I haven't heard of that happening. Report it to AMD: http://www.amd.com/report

On further testing, the crash is completely random, not related to multiple overrides. The EDID override I'm using just has 1 detailed resolution and nothing else. I'm guessing that the AMD driver is assuming there's more stuff, and if there isn't, it ends up reading uninitialized memory or something.

I tried making the minimum possible modification, only deleting 1 detailed resolution and leaving everything else alone, and this seems to work (no AMD driver crash).

I did have to toggle the "GPU scaling" option for the EDID modification to take effect. But it survives reboot.

It was a long road but it finally seems to be working. Thanks!
Find all posts by this user
Quote this message in a reply
04-18-2018, 02:07 AM
Post: #3469
RE: Custom Resolution Utility (CRU)
ToastyX, I have a question.

Does this program support Supersampling?

I have a 1080p monitor and I want to use 4k resolution (3840x2160) with a custom refresh rate.

Thanks for the answer Smile
Find all posts by this user
Quote this message in a reply
04-18-2018, 11:45 AM
Post: #3470
RE: Custom Resolution Utility (CRU)
(04-18-2018 02:07 AM)Michaelx25699 Wrote:  Does this program support Supersampling?
No.
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


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