Crash with slave OBS 30.0.2 (Advanced Scene Switcher 1.24.1 + WebSocket)

[justedit]

Hi all!
I work since 2 years in a big forum in Dubaï where I have 2 OBS stations (main + spare) feeding a 6400x1000px LED screen in a lobby (nvidia surround on RTX 4070)
My OBS main is using Advanced Scene Switcher with macros to time-switch between scenes and the "old" network tab to send websocket commands to slave my OBS spare.
My OBS spare use also the old "network" tab to receive OBS main websocket commands to switch in sync with the main.
It's been running from 4 days 24/24h like a charm. Since 2 days my OBS spare crashes (without any error, just closing OBS) After some investigations, it seems that it could be an WebSocket / GPU issue (see log attached) but I'm not a coder guy so I might be wrong.
Precision : only the OBS spare is crashing (the one who receive WebSocket). The main is runnnig 24/24h since 8 days.
Here are the last lines of the logs :
-------
13:49:16.337: [adv-ss] try to sleep for 300
13:49:16.638: [adv-ss] try to sleep for 300
13:49:16.938: [adv-ss] try to sleep for 300
13:49:17.239: [adv-ss] try to sleep for 300
13:49:17.540: [adv-ss] try to sleep for 300
13:49:17.841: [adv-ss] try to sleep for 300
13:49:18.141: [adv-ss] try to sleep for 300
13:50:21.193: Last log entry repeated for 209 more lines
13:50:21.193: User switched to scene 'HOLD_LOGO'
13:50:21.193: [adv-ss] switched scene
13:50:21.193: [adv-ss] client sent message:
13:50:21.193: message ok
13:50:21.223: Device Remove/Reset! Rebuilding all assets...
13:50:21.249: [adv-ss] try to sleep for 300
13:50:21.272: Failed to rebuild shared texture: 0x80070057
------
and the Crash file.txt :
Failed to recreate D3D11: Failed to create swap chain (8007000E)
------
Any idea ? Any workaround to try ?

Configuration :
13th Gen i7-13700
32GB ram
Windows 11 Pro 23H2
nVidia RTX 4070 12GB with 551.23 drivers (GeForce version)
OBS 30.0.2
Advanced Scene Switcher 1.24.1

 

[PaiSand]

This is the place for your issue:

Advanced Scene Switcher

Unfortunately, it is very difficult to say what the issue might be without further information. Can you share the two macros you have set up? You can do this by either by exporting the two macros or by exporting your settings to a file. It might also be of use if you can provide a log file...

obsproject.com

 

[justedit]

This is the place for your issue:

Advanced Scene Switcher

Unfortunately, it is very difficult to say what the issue might be without further information. Can you share the two macros you have set up? You can do this by either by exporting the two macros or by exporting your settings to a file. It might also be of use if you can provide a log file...

obsproject.com

Yes and no because I'm not really sure it's an Advanced Scen Switcher issue but more a Websocket / GPU issue (see the log)
Thanks

 

[justedit]

Here is a new log. OBS has not quit but it could play H.264 files anymore.

 

[koala]

13:50:21.223: Device Remove/Reset! Rebuilding all assets...
13:50:21.249: [...]
13:50:21.272: Failed to rebuild shared texture: 0x80070057
------
and the Crash file.txt :
Failed to recreate D3D11: Failed to create swap chain (8007000E)

This "device remove/reset" and subsequent texture and d3d11 errors indicate a graphics driver crash, then Windows restarts the graphic subsystem (if you observe this, you see the monitor going black for a few seconds), and some apps need a restart to initialize their graphics again. On laptops, it seems this behavior can also happen if you close the lid or the device goes to sleep, then wake up.

If it's not the sleep state that was entered, it's an indication of a defective graphics driver installation or malfunctioning hardware. Overclocking, overheating, insufficient power supply, faulty GPU hardware, or for new machines some incompatibility between GPU and mainboard.

 

[justedit]

This "device remove/reset" and subsequent texture and d3d11 errors indicate a graphics driver crash, then Windows restarts the graphic subsystem (if you observe this, you see the monitor going black for a few seconds), and some apps need a restart to initialize their graphics again. On laptops, it seems this behavior can also happen if you close the lid or the device goes to sleep, then wake up.

If it's not the sleep state that was entered, it's an indication of a defective graphics driver installation or malfunctioning hardware. Overclocking, overheating, insufficient power supply, faulty GPU hardware, or for new machines some incompatibility between GPU and mainboard.

Thanks for this answer. I'll try to downgrade the nvidia drivers and run some new tests!