Freezing/Crashing/Restarting when VR kicks in or Resolution changes

https://drive.google.com/drive/folders/1zUYdWIK0llocC5vU0szJ1ZLlhDq2DByc?usp=sharing < Please see this shared folder for my latest logs ("before" and after a full uninstall/reinstall) and a dxdiag.

Windows 10 x64 - 22H2 - 19045.2486

PC: Intel i5-8600k, 32 GB Ram, nVidia GTX 1080ti.

Displays: 1440x3440 (Primary), 720x1280 (Secondary), Samsung Odyssey+ HMD (VR)

I'm starting to think this all began with the 22H2 update. I've been a Fences user since Fences 2.x, also long time had 3.x, and had no issues until recently.  With recommendation from mods on Discord for continued support with latest Windows OS, I've recently done the upgrade purchase to Fences 4.x now, but still hasn't corrected my issue.

I frequently play older games and games that don't like my 21:9 display, these cause the desktop to resize. Also when you enable VR, it sees an extra display, which also causes desktop to refresh. Normally this isn't a huge issue for fences, it normally just takes 3-5 seconds after exiting the game and then Fences refreshes and resizes it all back to normal automatically.

But since this issue started happening, every time I start VR (Windows Mixed Reality app first) or I exit a game that has used a different resolution, Fences will now start to freeze (spinning wheel), or crash (fences and/or explorer will shut down and restart automatically, sometimes multiple times before it settles down, sometimes not until I reboot my PC). My only temporary workaround is if I go in to "configure fences" and remove the checkmark from "enable fences" in the home tab... and then when I'm done the game, right click desktop and choose "enable fences". Obviously this workaround shouldn't be required, and I'd appreciate any assistance possible.

Thank you.

8,189 views 3 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Please check if these steps help with your issue. https://forums.stardock.com/514583/get;3875625


Basj,
Stardock Community Assistant.

Reply #2 Top

Ah...

"one or more icons that were present prior are causing an issue. Almost always, it is an icon that links to a network location that is not available at boot time."

Network location... this must be it.  As it also did start occurring after I added a desktop link to a device that I don't have on all the time.  Deleted that shortcut and will test.  If this fixes it... will there be a different fix/workaround for this (or patch to address this from your side)?

Reply #3 Top

I believe there is a post in that same thread: https://forums.stardock.com/514583/get;3875669, mentioned that the issue is logged for Dev to look into. Hopefully, there will be a fix soon.

Thank you,

Basj,
Stardock Community Assistant

+2 Loading…