TimStevens
16 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]
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!
TimStevens
16 discussion posts
Thanks, just installed. Will keep an eye on it.
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.
Hello,
Interesting observation, thanks for the feedback!
TimStevens
16 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]
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!
TimStevens
16 discussion posts
Any updates on this, perchance? Hadn't seen this in a little while but just this week it started happening again.
Hi Tim,
Has it only started happening since updating to 9.7.1?
Thanks!
TimStevens
16 discussion posts
Yes, happened just yesterday. Was working fine for a number of weeks before, though.
Hi Tim,
Can you try deleting and recreating your monitor profiles and see if the issue persists?
Thanks!
TimStevens
16 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]
Hi Tim,
Interesting, thanks for sending that over. Was the issue originally happening with 9.7.0?
Thanks!
TimStevens
16 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.
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
TimStevens
16 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?
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!
Hello,
We've made some changes to our monitor configuration code that should fix this up in our latest beta, as described here: https://www.displayfusion.com/Discussions/View/monitor-configuration-backend-completely-revamped-in-displayfusion-100-beta-18/?ID=b17dacd1-0611-48c1-a29c-3a3e5046812a
Please let me know if you run into any issues after updating.
Thanks!