Long Monitor Warmup results in Failed to call SetDisplayConfig. [HR: 31]

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

MiniJo

6 discussion posts

Hello,

I am on the latest beta (9.7.1 Beta 4), but the following issue has been occurring since March, ever since I got a new monitor (ASUS VG27AQ).

I have been running into Failed to call SetDisplayConfig. [HR: 31] whenever applying my monitor configuration and the primary monitor is asleep.

It seems this monitor takes a longer than expected time to wake up and once it does, DisplayFusion has already given up, reverted the config and shown this message.

I do have a workaround, where applying the config twice in a row, will work, BUT the message is already shown and clicking OK reverts the config (so I effectively have to apply it again after pressing OK).

Would you guys have a solution for me? Is there a way to increase this timeout?

Thanks,

Sep 1, 2020 (modified Sep 1, 2020) • #1

There is a way to increase the timeout, yep! You can set it in the Settings > Advanced Settings with this option: "Monitor Configuration: Confirmation Prompt Timeout (seconds)"

You can also disable the "Keep Changes" prompt permanently with this Advanced Setting: "Monitor Configuration: Don't Show Confirmation Prompt"

Related question: Does that HR:31 error show up only the first time you try to apply the config, or does a second copy of that error show up when you load it the second time as well?

Hope that helps!

Sep 2, 2020 • #2

MiniJo

6 discussion posts

Thank you for your reply Keith.

Apologies, it seems we were talking about a different timeout. I actually already had this "Keep Changes" prompt disabled, but I did went ahead and re-enabled it and increase its timeout to test.

The first try, the same error, without the "Keep Changes" appearing. On the second try, the "Keep Changes" window appeared when it succeeded at applying.

Quote:

Related question: Does that HR:31 error show up only the first time you try to apply the config, or does a second copy of that error show up when you load it the second time as well?

If I time it properly, then, no, only the first instance of the error is present.
However, If my second attempt is too quick (monitor still waking up) or too slow (monitor already went to sleep), it will fail again and there will be a second error window (or more depending on how many times I failed).

Let me know if you need anything from me,
Thanks

Sep 2, 2020 (modified Sep 2, 2020) • #3

Ok, thanks for the clarification! That makes sense.

Could you try enabling this option in the Advanced Settings and let me know if that makes any difference?

Monitor Configuration: Don't Show Error When Load Monitor Profile Fails

Sep 3, 2020 • #4

MiniJo

6 discussion posts

Quote:

Could you try enabling this option in the Advanced Settings and let me know if that makes any difference?

Monitor Configuration: Don't Show Error When Load Monitor Profile Fails

Thanks again Keith, turns out I already had this option enabled. But I did just try with and without it and there was no difference.

The clarify here are the Monitor Configuration options that I have enabled:

Don't show different numbers of monitor prompt
Don't show Confirmation Prompt
Don't show Error when Load Monitor Profile Fails

Sep 3, 2020 (modified Sep 3, 2020) • #5

Ok, interesting! Let me check in with our developers on this and I'll keep you posted on what I find out.

Sep 4, 2020 • #6

Would you be able to send us a debug log?

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Reproduce the error message and note the time so we'll know where to check in the log file
Click the "Export Info to File" button on the Settings > Troubleshooting tab
Reply with the file attached
Disable debug logging after sending the log

Thanks!

Sep 18, 2020 • #7

MiniJo

6 discussion posts

Quote:

Would you be able to send us a debug log?

Yes, of course. Sorry for the wait!

Attached is the log zip file, in this I am executing SetDisplayConfig twice as per my workaround.
So you should see (screenshotted):
1. At 15:20:28, this one fails
2. At 15:20:58, this one succeeds

It succeeds, but the error window is present, forcing me to do the workaround a third time as I dismiss it (because dismissing reverts back) I do not think this part is relevant, so I have omitted it from the log.

• Attachment [protected]: displayfusion-log-timestamps.png [68,948 bytes]

• Attachment [protected]: DisplayFusionDebugInfo.zip [79,620 bytes]

Sep 27, 2020 (modified Sep 27, 2020) • #8

Thanks! We'll check it out!

Sep 29, 2020 • #9

Just a quick update, we need to add some additional info to the logging. We'll do that for the next beta and then let you know when it's available

Thanks!

Sep 30, 2020 • #10

MiniJo

6 discussion posts

Great, thanks for looking into the issue!

Oct 1, 2020 • #11

MiniJo

6 discussion posts

Hi Keith,

A few betas has been released since our discussion. So I am providing you with a LogMinimal from the latest (beta 6).

You should see the error around 2020/11/14 22:16:29.2118

Thanks,
Jonathan

P.S. Really, at this point, I don't mind having to switch configuration multiple times. I would only wish that dismissing the Error Message would not revert it back.

• Attachment [protected]: DisplayFusionDebugInfo_2020-11-14.zip [296,822 bytes]

Nov 15, 2020 (modified Nov 15, 2020) • #12

Thanks! Apologies for not following up when the beta was released, somehow this dropped off of my to-do list

Our developers will check out the logs and we'll see what we can find out.

Nov 16, 2020 • #13