Title

Message

Confirm

<< DiscussionsReply

Failed to call SetDisplayConfig. [HR: 31] -- but only occasionally

TimStevens
13 discussion posts
Hey there, have been getting this error intermittently when toggling displays:

An error has occurred while applying your new Monitor configuration.
Please check your settings and try again.
Error: Failed to call SetDisplayConfig. [HR: 31]
[System.Exception]

Weirdly, it only happens sometime, and I haven't been able to identify when. I read through a bunch of other people having this issue and none of them seemed the same, as this is only intermittent. I have four monitors, two profiles, one that disables 3 of them. The second profile re-enables those three and disables the first. It's always that profile that fails probably 30 percent of the time. But, once it fails I have to reboot the PC to get it to work.

I verified that all monitors are recognized by windows, tried turning them off and on again, all that works is a reboot.

Settings attached. Thanks for any guidance!
• Attachment [protected]: DisplayFusion Backup (2020-11-06 @ 15-08, 9.7.0.0, COMPUTERNAME, SettingsWindow).reg [472,656 bytes]
Nov 6, 2020  • #1
Owen Muhlethaler (BFS)'s profile on WallpaperFusion.com
Hi Tim,

Can you try updating to our latest beta and see if the issue persists? Here's the link: https://www.displayfusion.com/Download/Beta/

Let me know how that goes!
Nov 10, 2020  • #2
TimStevens
13 discussion posts
Thanks, just installed. Will keep an eye on it.
Nov 10, 2020  • #3
JM241
2 discussion posts
Been getting this a lot lately on 9.7.0. I just installed 9.7.1 beta 6 and it still failed with the same error when attempting to set profiles. Even a reboot wouldn't get it to work, always getting the [HR: 31] error.

I could manually change things like monitor enablement though, so I deleted and re-created both my 2 profiles. They worked reliably.

Then it occurred to me that both my profiles include a Dell monitor connected via USB-C. My laptop has two USB-C ports and I'm not rigorous about always plugging the cable into the same one, so I did an experiment and shifted the monitor back and forth between the USB-C ports.

If I connect the monitor to the same USB-C port as when I saved a given profile, the profile always works. If I connect the monitor to the other USB-C port then the Load Profile fails reliably, though it is of course the same physical monitor.

For now, it's easy for me to just pick a USB-C port and stick with it, but thought you should know.
Nov 10, 2020  • #4
Owen Muhlethaler (BFS)'s profile on WallpaperFusion.com
Hello,

Interesting observation, thanks for the feedback!
Nov 11, 2020  • #5
TimStevens
13 discussion posts
Circling back. I got the same error using the Beta 6 version. I attempted to open the log to see the details, but got this error:

The Debug Log file could not be found.
Make sure you have enabled Debug Logging first.


I don't see a place in the Troubleshooting window to enable logging, though. Where is that option? All the references I found in the forum indicated it should be on that section of the preferences but I don't see it.

I do have a copy of the full System Information if that's helpful.
Nov 13, 2020  • #6
Owen Muhlethaler (BFS)'s profile on WallpaperFusion.com
Hi Tim,

If you could send over a copy of your system information, that would be great. The steps to enable logging can be found below:

  • On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
  • Reproduce the issue 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

Also, if you happen to notice a trend of when this is happening, that would be great as well.

Thanks!
Nov 17, 2020  • #7
TimStevens
13 discussion posts
Here you go. This happened around 7:45pm ET. I have four monitors and two configurations. One config disables the right three and enables the left one. The second configuration reverses that. This only ever happens when moving to the second configuration, and maybe 50% of the time.
• Attachment [protected]: DisplayFusionDebugInfo.zip [29,699 bytes]
Nov 18, 2020  • #8
Owen Muhlethaler (BFS)'s profile on WallpaperFusion.com
Hi Tim,

Thanks for sending those over, we're going to look into this further. I've noted down your contact information, and we'll be in touch either to collect more information, or to let you know when we have a fix.

Thanks!
Nov 18, 2020  • #9
TimStevens
13 discussion posts
Thank you!
Nov 18, 2020  • #10
TimStevens
13 discussion posts
Any updates on this, perchance? Hadn't seen this in a little while but just this week it started happening again.
Jan 7, 2021  • #11
Owen Muhlethaler (BFS)'s profile on WallpaperFusion.com
Hi Tim,

Has it only started happening since updating to 9.7.1?

Thanks!
Jan 8, 2021  • #12
TimStevens
13 discussion posts
Yes, happened just yesterday. Was working fine for a number of weeks before, though.
Jan 8, 2021  • #13
Owen Muhlethaler (BFS)'s profile on WallpaperFusion.com
Hi Tim,

Can you try deleting and recreating your monitor profiles and see if the issue persists?

Thanks!
Jan 8, 2021  • #14
TimStevens
13 discussion posts
Hi there, same issue, sorry to report. Log file is attached, happened at approximately 3:20pm ET.
• Attachment [protected]: DisplayFusionDebugInfo 320 pm.zip [67,068 bytes]
Jan 11, 2021  • #15
Owen Muhlethaler (BFS)'s profile on WallpaperFusion.com
Hi Tim,

Interesting, thanks for sending that over. Was the issue originally happening with 9.7.0?

Thanks!
Jan 12, 2021  • #16
TimStevens
13 discussion posts
Not sure what version I was running back in November, sorry to say. I have it set to look for updates automatically so it should have been whatever was current.
Jan 12, 2021  • #17
Owen Muhlethaler (BFS)'s profile on WallpaperFusion.com
Hi Tim,

Not a problem. These error 31 issues are tough to pin down, as they are just a general hardware error, and don't really tell us anything about the issue itself.

I'm going to attach a link at the bottom of this thread for you to roll back to 9.7.0. Can you let me know if the issue persists?

Thanks!

https://www.binaryfortress.com/Data/Download/?OldVersion=1&DownloadID=34204533-0a63-442a-84af-63025d8cabdd
Jan 14, 2021  • #18
TimStevens
13 discussion posts
It certainly looks like downgrading has solved the issue. Thank you. I guess I'll stick on that version until you tell me it's safe to upgrade?
Feb 9, 2021  • #19
Owen Muhlethaler (BFS)'s profile on WallpaperFusion.com
Hi Tim,

Interesting, I've bumped this up for us to look into for v10. We'll take a look at the changes we made between v9.7.0 and v9.7.1 and see if we can find the root cause.

For now you can stay on 9.7.0 if it's working good for you.

Thanks!
Feb 12, 2021  • #20
TimStevens
13 discussion posts
Copy, thanks.
Feb 12, 2021  • #21
Was this helpful?  (1)  
<< DiscussionsReply