OBS crashes 10 minutes into stream | Only change was third party driver after 1k hr uptime| Unhandled exception:c0000005, libobs, NVIDIA nvwgf2umx.dll

[thisTinker]

I stream 24/7 and use a variety of plugins/automation. We have a highly reliable setup, live since April- we change things cautiously. This is the first major OBS issue I cannot pinpoint a cause to (IE; a change that we can reverse which is related). Details below; I will be working on this essentially until a fix is found, but moving my setup to a backup machine first before i continue. Next steps are to test a few times live with a couple plugins removed, and in safe mode - but so far the crash has even happened while not-live just sitting dormant as OBS is open.

Nothing changed with my OBS setup, plugins, or machine - however, after installing a WACOM tablet driver and restarting this morning my OBS crashes 10 minutes after starting the stream (and some time after even being opened, possibly the same) every time. The crash shows a failure of Thread 8C6C: libobs: graphics thread (Crashed) , NVIDIA driver component nvwgf2umx.dll

it is worth noting that after the crashes OBS usually appears still in the bottom taskbar and shows as live; but it cannot be accesed/opened. If i go to task manager there are sometimes excess processes still active for OBS. The issue seems to only partially shut it down even after i get the 'whoops obs has crashed' dialog.

Uninstalling the WACOM driver changed nothing. Doing a clean reinstall and update of GPU drivers changed nothing. I stream 24/7 and have been for >3600 hours straight - the last 4 weeks have been without issues and changes until this. As it stands, Im primarily investigating the wacom driver as the cause but I have no clue what that messed with or how to fix it. It is vital my stream is up always, so I am very focused on solving this problem ASAP and may resort to a fresh install on a completely fresh machine - before doing so I want to see what is out there in the community, as I have seen other posts about the nvwgf2umx and libobs.

A week ago I did a BIOS update provided by CORSAIR to fix the intel microcode issue. We ran the stream fine and restarted fine every day afterward.

SFC scan found a corrupt img001.jpg file used by the windows login screen. found no evidence of drive degredation or other corruption, seems like a red herring.

Other troubleshooting steps included:

OBS repair
turning it off and back on while breathing heavily
Disabling my large set of browser pages and other sources
Reconnecting Twitch
Bitrate adjustments
disabling recording, buffer, other excess use of NVEC
basic scans using CORSAIR/windows tools (drivers, ssd, gpu, cpu, etc)

Steps to be taken today:
complete OBS reinstall
removing unnecessary plugins like the logitech one; but thats been installed for weeks without issue.
Praying to every god available
Running on safe mode (this seems simple, but alot of my stream depends on plugins like websocket so it is basically useless on safe mode but would help ID things - will update here when we learn more)
Scouring for relevant posts, more so than the hour spent this morning before work.


l am running Windows 11, Intel(R) Core(TM) i9-14900KF 3.20 GHz, NVIDIA 4090 Studio Driver 561.09 (after fresh GPU install, was functional on previous version as well)


Any suggestions, similar experiences, guidance, or emotional support appreciated.


Crash log:


Unhandled exception: c0000005
Date/Time: 2024-09-26, 13:43:11
Fault address: 7FFEC374C799 (c:\windows\system32\driverstore\filerepository\nvmdsi.inf_amd64_72e67a59bba77ee3\nvwgf2umx.dll)
libobs version: 30.2.3 (64-bit)
Windows version: 10.0 build 22631 (release: 23H2; revision: 4169; 64-bit)
CPU: Intel(R) Core(TM) i9-14900KF


Thread 8C6C: libobs: graphics thread (Crashed)
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
000000CD846FCCC0 00007FFEC374C799 0000000000605C76 000000000000EA60 00000000000017A3 000001EBBC1D5B80 nvwgf2umx.dll!0x7ffec374c799
000000CD846FCD30 00007FFEC24987D5 000001EB00000000 0000000000000010 000000CD00000000 0000000000000001 nvwgf2umx.dll!0x7ffec24987d5
000000CD846FCF80 00007FFEC2495EBD 000001EB50C7F2C0 000001EB0AA0E7F0 0000000000000000 000000CD846FD2E8 nvwgf2umx.dll!0x7ffec2495ebd
...
000000CD846FEDB0 00007FFED7752004 000001EB4CE37C30 000000CD00000002 0000000000000048 0000000000000000 d3d11.dll!0x7ffed7752004
000000CD846FEFB0 00007FFED7739B43 0000000000000000 0000000000000010 000001EB49B80000 00007FFE00000000 d3d11.dll!0x7ffed7739b43
000000CD846FF340 00007FFED77396BD 0000000000000001 000001EB1296C9A0 000000000000EA60 000001EB1296C880 d3d11.dll!0x7ffed77396bd
000000CD846FF3E0 00007FFE64639788 000001EB15A4E900 000001EB134FB2E0 000001EB0000EA60 0000000000000000 libobs-d3d11.dll!gs_texture_2d::InitTexture+0x418
000000CD846FF460 00007FFE64639FF0 000001EB1296C880 000001EB4CC960E0 000001EB4CBFC060 000001EB04D01F58 libobs-d3d11.dll!gs_texture_2d::gs_texture_2d+0x250
000000CD846FF4B0 00007FFE64633FDE 000001EB4CC960E0 0000000000000000 0000000000003A98 0000000000003A98 libobs-d3d11.dll!device_texture_create+0x8e
000000CD846FF540 00007FFE82517887 000001EB134F11B8 0000000000000071 000001EB04D00B20 000001EB134FB2E0 obs.dll!gs_texture_create+0xe7
000000CD846FF590 00007FFE8251CD62 000001EB04D00B20 00007FFE63E58648 0000000000000000 000001EB0A986940 obs.dll!gs_image_file_init_texture+0x62
000000CD846FF5D0 00007FFE63E517B4 0000000000000000 0000000000000000 0000000000000000 0000000000000000 image-source.dll!image_source_load_texture+0x44
000000CD846FF600 00007FFE63E51D9A 000001EB509530E0 000001EB04CFDEE0 000001EB04CFDEE0 0000000000000000 image-source.dll!image_source_tick+0x3a
000000CD846FF680 00007FFE824C17A2 000001EB509530E0 0000000000000071 000001EB04D00B20 0000000000000001 obs.dll!obs_source_video_tick+0x562
000000CD846FF6F0 00007FFE824D3CA6 000001EB4CBFC060 000000CD846FF820 0000000000000000 0000000000000000 obs.dll!tick_sources+0x266
000000CD846FF750 00007FFE824D7501 0000000000000000 0000037739578218 0000000000000000 0000000000000000 obs.dll!obs_graphics_thread_loop+0x171
000000CD846FF800 00007FFE824D7A4F FFFFFFFFFFFFFFFF 000000078F7B19CA 000000CD846FF919 0000000000000000 obs.dll!obs_graphics_thread+0x12f
000000CD846FF8B0 00007FFEBE0814A7 000001EB4FDADBC0 0000000000000000 0000000000000000 0000000000000000 w32-pthreads.dll!ptw32_threadStart+0x1b7
000000CD846FF980 00007FFEDE3F9333 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ucrtbase.dll!0x7ffede3f9333
000000CD846FF9B0 00007FFEDFCC257D 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffedfcc257d
000000CD846FF9E0 00007FFEE0AEAF28 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffee0aeaf28
...

Log info:
12:53:31.371: CPU Name: Intel(R) Core(TM) i9-14900KF
12:53:31.371: CPU Speed: 3187MHz
12:53:31.371: Physical Cores: 24, Logical Cores: 32
12:53:31.371: Physical Memory: 65381MB Total, 48026MB Free
12:53:31.371: Windows Version: 10.0 Build 22631 (release: 23H2; revision: 4169; 64-bit)
12:53:31.371: Running as administrator: true
12:53:31.371: Windows 10/11 Gaming Features:
12:53:31.371: Game DVR: On
12:53:31.371: Game Mode: Off
12:53:31.372: Sec. Software Status:
12:53:31.372: Microsoft Defender Antivirus: enabled (AV)
12:53:31.372: Windows Firewall: enabled (FW)
12:53:31.373: Current Date/Time: 2024-09-26, 12:53:31
12:53:31.373: Browser Hardware Acceleration: true
12:53:31.373: Hide OBS windows from screen capture: false
12:53:31.373: Qt Version: 6.6.3 (runtime), 6.6.3 (compiled)
12:53:31.373: Portable mode: false
12:53:31.570: OBS 30.2.3 (64-bit, windows)
12:53:31.570: ---------------------------------
12:53:31.570: ---------------------------------
12:53:31.570: audio settings reset:
12:53:31.570: samples per sec: 48000
12:53:31.570: speakers: 2
12:53:31.570: max buffering: 960 milliseconds
12:53:31.570: buffering type: dynamically increasing
12:53:31.571: ---------------------------------
12:53:31.571: Initializing D3D11...
12:53:31.571: Available Video Adapters:
12:53:31.572: Adapter 0: NVIDIA GeForce RTX 4090
12:53:31.572: Dedicated VRAM: 25314721792 (23.6 GiB)
12:53:31.572: Shared VRAM: 34278764544 (31.9 GiB)
12:53:31.573: PCI ID: 10de:2684
12:53:31.573: HAGS Status: Disabled (Default: No, Driver status: Supported)
12:53:31.573: Driver Version: 32.0.15.6109
12:53:31.573: output 0:
12:53:31.573: name=DELL S3220DGF
12:53:31.573: pos={0, 0}
12:53:31.573: size={2560, 1440}
12:53:31.573: attached=true
12:53:31.573: refresh=165
12:53:31.573: bits_per_color=8
12:53:31.573: space=RGB_FULL_G22_NONE_P709
12:53:31.573: primaries=[r=(0.675781, 0.314453), g=(0.272461, 0.657227), b=(0.151367, 0.068359), wp=(0.313477, 0.329102)]
12:53:31.573: relative_gamut_area=[709=1.245024, P3=0.917795, 2020=0.658457]



...

 

[thisTinker]

Wanted to add that we noticed after these crashes, after reopening it seems normal for the first 10 mins but during that time clicking 'exit' in OBS closes it normally but the icon still appears in the taskbar with the red record circle. stream has been on the phone for an hour, so after these crashes it seems to keep something running/think it's live until i restart the machine. Nothing can be found in task manager, however, with OBS related names. If i click that icon again as soon as it opens the crash occurs instantly (instead of being 10 minutes later). This cycle continues until the machine is completely restarted.


EDIT* we restarted the machine and tried to open OBS and it crashed upon opening the same way. So the issue does perpetuate through restarts somehow.

 

[thisTinker]

Removing excess plugins, doing the OBS check integrity : less than 5 minutes the crash happened. Notably, the video feeds stop but the audio channels seem to continue responding normally. The window is able to be moved without 'not responding' ; the bitrate shows zero. Viewers see a error on twitch's end. The video preview freezes but the rest of OBS ; all the UI and audio sources work fine. I can click sources on and off, etc, but there is no effect in the preview or output.


upon clicking yes in the whoops dialog OBS closes, then we get the issue of it still being open in the background. Even if i force stop all these tasks it still is in the background. Even if I restart the problem happens again immediately on opening, then again later 2-10 minutes in. Once i get a properly clean start it takes near 10 minutes minutes (usually nearly perfectly) for the crash to occur again. in the most recent test it occurred 8 minutes after starting OBS, not streaming or recording. the live logs showed nothing.

After resetting this cycle we started again, Running in safe mode: We are over 10 minutes in which is a good sign. if this runs ok for a bit longer I am going to try to do a clean reinstall of OBS. My procedure will be to export my profile and scene to import later. Use the built in windows uninstall for OBS. Then reinstall to the same directory.

If this persists the issue or someone suggests; I will delete all the OBS folders then do the reinstall then import my settings.

I am unsure how 'clean' the basic uninstall reinstall is.

 

[thisTinker]

A reinstall of OBS (without removing folders) was unsuccessful; notably, it only removed a single 3rd party plugin from my list (cloud captions) while auto scene switcher, captions (experimental), output timer, scripts, and websocket server settings were still available. I will reinstall cloud captions on a final working version as we use this to get speech to text output to our local python scripts through the caption sources that can be made (and transcripts).

Before trying to do a full 'clean' reinstall I am testing running >10 minutes off safe mode with the websocket NOT enabled, as this is the only one I have left running (with no connections). This test also failed with the same crash log.

Next in elimination, I deactivated all sources and moved to an empty scene. Crash still about 8-10 mins in. None of this while live, recording, or any of the rest of my GPU/CPU in use. Normally we run 50x this load 24/7.

I will now proceed with a full bare install. I will delete all the folders and then import my relevant scenes/profile.

 

[thisTinker]

On a fresh OBS install without my profiles/scenes imported I was able to keep it open for more than 10 minutes. I then added the cloud caption plugin (knowing that removing it didnt change the issue before) and had the same success. I now suspect maybe something in my sources was causing an issue, so we will need to do a process of elimination on those. I have lots of browser sources (10-20) and several video ingests (RTMP and SRT), so I will start with local devices and work outward.

My next thought was that because the crash output is related to the nvidia driver that I would try first changing the encoder before adding any sources or anything. I changed to NVIDIA NVENC H.264 on that same completely fresh OBS and waited 10 minutes again.

Next, i first imported and tested my profile the same way (following along from the encoder change). 10 minutes, no crash. The next step will be to import my scene and test all sources for a crash, from there if there is still a crash, eliminate them one by one entirely from OBS (not just from the active scene). 'check' indicates it did not result in a crash within 10 minutes.

Cloud Captions Plugin - check
Checking some obvious large data throughput sources:

Elgato Cam Link Cap Card source - check
Elgato Wave Link - check

Now, importing my scene. This was after waiting 10 minutes or more already.
Funny enough, the instant I imported the scene and selected it OBS crashed exactly the same way.

The final source to load before the crash was my camera that is attached to the cam link cap card source i mentioned above. So despite it working fine as a newly added source, it (or something above it in the load procedure but nearby) being imported caused the same response on an entirely new setup.

I deleted that source and reopened OBS back to the scene. The scene now has everything BUT that camera source (camlink) and I waited 10 minutes from there.

The log section for the source in question;
17:02:19.757: ---------------------------------
17:02:19.757: [DShow Device: 'CamLink1-Main'] settings updated:
17:02:19.757: video device: Cam Link 4K
17:02:19.757: video path: \\?\usb#vid_0fd9&pid_0066&mi_00#6&3b10acc&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global
17:02:19.757: resolution: 3840x2160
17:02:19.757: flip: 0
17:02:19.757: fps: 29.97 (interval: 333667)
17:02:19.757: format: NV12
17:02:19.757: buffering: disabled
17:02:19.757: hardware decode: disabled
17:02:19.813: using video device audio: no
17:02:19.813: separate audio filter
17:02:19.813: sample rate: 44100
17:02:19.813: channels: 2
17:02:19.813: audio type: Capture
17:02:19.964: DShow: HDevice::ConnectPins: failed to connect pins (0x8004022A):

my sample rates should be 4800 but I could not find a setting to change that, presumably it s on the camera itself. After waiting 10 minutes with this entirely removed, however, the problem still occurs

However, still, the problem persists- meaning it is another source of some kind - or one of the default plugins. Going back to SAFE mode stops the problem from happening, it also removes all BUT the auto confi wizard from the tools bar. Even a completely bare OBS still has these plugins by default:

auto scene switcher, captions (experimental), output timer, scripts, and websocket server settings

I need the websocket server, but I do not need the others. Scripts i may need later, the point is, I want to start to eliminate these from the equation.

1) How can i locate and delete auto scene switcher, captions (experimental), output timer, and scripts default plugins?
2) Does safe mode impact anything but plugins? Why might it prevent my sources from causing the crash?

Safe mode presumably only has an impact on those, but if it has an interaction with my sources that might be preventing them from crashing OBS this is worth knowing. I believe I have hit my limit of context needed to properly asses this problem, and ill wait for this to be reviewed/responded to unless i have any new major changes.

All of this started with a very simple driver install to get a very old wacom tablet connected. I didnt even NEED the tablet, just thought id get it done. God knows what sort of domino that tipped, but I hope to find out soon so I can get back to my normal life.

Despite my relative lack of knowledge of OBS backend Hopefully this extensive breakdown and walk through of the problem has been enough to sieve out individual sources of the problem OR could at least eliminate enough variables for someone experiencing or attempting to solve the same thing.

I will hold on updates until I hear from someone or come across a solution, but someone with more knowledge of what safe mode actually does will be more productive here than my troubleshooting playbyplay. My next steps, knowing safemode is working, will be to figure out what safemode is interacting with to prevent the crashes - whether this is a source or one of those default plugins.

 

[thisTinker]

On a fresh OBS install without my profiles/scenes imported I was able to keep it open for more than 10 minutes. I then added the cloud caption plugin (knowing that removing it didnt change the issue before) and had the same success. I now suspect maybe something in my sources was causing an issue, so we will need to do a process of elimination on those. I have lots of browser sources (10-20) and several video ingests (RTMP and SRT), so I will start with local devices and work outward.

My next thought was that because the crash output is related to the nvidia driver that I would try first changing the encoder before adding any sources or anything. I changed to NVIDIA NVENC H.264 on that same completely fresh OBS and waited 10 minutes again.

Next, i first imported and tested my profile the same way (following along from the encoder change). 10 minutes, no crash. The next step will be to import my scene and test all sources for a crash, from there if there is still a crash, eliminate them one by one entirely from OBS (not just from the active scene). 'check' indicates it did not result in a crash within 10 minutes.

Cloud Captions Plugin - check
Checking some obvious large data throughput sources:

Elgato Cam Link Cap Card source - check
Elgato Wave Link - check

Now, importing my scene. This was after waiting 10 minutes or more already.
Funny enough, the instant I imported the scene and selected it OBS crashed exactly the same way.

The final source to load before the crash was my camera that is attached to the cam link cap card source i mentioned above. So despite it working fine as a newly added source, it (or something above it in the load procedure but nearby) being imported caused the same response on an entirely new setup.

I deleted that source and reopened OBS back to the scene. The scene now has everything BUT that camera source (camlink) and I waited 10 minutes from there.

The log section for the source in question;
17:02:19.757: ---------------------------------
17:02:19.757: [DShow Device: 'CamLink1-Main'] settings updated:
17:02:19.757: video device: Cam Link 4K
17:02:19.757: video path: \\?\usb#vid_0fd9&pid_0066&mi_00#6&3b10acc&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global
17:02:19.757: resolution: 3840x2160
17:02:19.757: flip: 0
17:02:19.757: fps: 29.97 (interval: 333667)
17:02:19.757: format: NV12
17:02:19.757: buffering: disabled
17:02:19.757: hardware decode: disabled
17:02:19.813: using video device audio: no
17:02:19.813: separate audio filter
17:02:19.813: sample rate: 44100
17:02:19.813: channels: 2
17:02:19.813: audio type: Capture
17:02:19.964: DShow: HDevice::ConnectPins: failed to connect pins (0x8004022A):

my sample rates should be 4800 but I could not find a setting to change that, presumably it s on the camera itself. After waiting 10 minutes with this entirely removed, however, the problem still occurs

However, still, the problem persists- meaning it is another source of some kind - or one of the default plugins. Going back to SAFE mode stops the problem from happening, it also removes all BUT the auto confi wizard from the tools bar. Even a completely bare OBS still has these plugins by default:

auto scene switcher, captions (experimental), output timer, scripts, and websocket server settings

I need the websocket server, but I do not need the others. Scripts i may need later, the point is, I want to start to eliminate these from the equation.

1) How can i locate and delete auto scene switcher, captions (experimental), output timer, and scripts default plugins?
2) Does safe mode impact anything but plugins? Why might it prevent my sources from causing the crash?

Safe mode presumably only has an impact on those, but if it has an interaction with my sources that might be preventing them from crashing OBS this is worth knowing. I believe I have hit my limit of context needed to properly asses this problem, and ill wait for this to be reviewed/responded to unless i have any new major changes.

All of this started with a very simple driver install to get a very old wacom tablet connected. I didnt even NEED the tablet, just thought id get it done. God knows what sort of domino that tipped, but I hope to find out soon so I can get back to my normal life.

Despite my relative lack of knowledge of OBS backend Hopefully this extensive breakdown and walk through of the problem has been enough to sieve out individual sources of the problem OR could at least eliminate enough variables for someone experiencing or attempting to solve the same thing.

I will hold on updates until I hear from someone or come across a solution, but someone with more knowledge of what safe mode actually does will be more productive here than my troubleshooting playbyplay. My next steps, knowing safemode is working, will be to figure out what safemode is interacting with to prevent the crashes - whether this is a source or one of those default plugins.

As soon as I posted this and the time ran out to update my post the SAFE mode one crashed.

I found this in the analyzer/logs

'
Audio buffering hit the maximum value. This is an indicator of very high system load, will affect stream latency, and may even cause individual audio sources to stop working. Keep an eye on CPU usage especially, and close background programs if needed.

Occasionally, this can be caused by incorrect device timestamps. Restart OBS to reset buffering.

Source affected (potential cause): CamLink-Main
'

I am going to try figure out how to adjust the audio sampling on the camera attached to this, during this, I will test out of safe mode without this source yet again but waiting longer since the safe mode crashjust took a bit more time. I will also see if theres settings i need to change for timestamps, etc.

So it is most likely a source, or something core to my computer (but no other program is having issues as far as im aware).

The crash occurred even with the camlink source deactivated and in safe mode. I will now start the process of individually removing sources. Starting with the EOS webcam utility source that supplies the other USB connected camera.

 

[thisTinker]

I was able to get the problem to happen on demand by cycling an image slideshow that I use at a high rate (roughly 500ms for a bit of time, but even 1 second worked at one point). I am going to test running without the folder that contains that slideshow loaded at all. Previously, although the source was not visible I presume it may have either been running in the background or it was loading at least one picture regularly on restarts. I recently added quite a large new set of wallpaper images to that folder which I did not recall OBS was attached to till now.

My presumption is that OBS would struggle to load one of those images, already deleted, because of its sheer size. The largest image in the folder stack now is 18000kb. Image album contains TIF, JPG, PNG, and JFIF files. No one specific image seems to be the cause (but i may try to narrow that down later), but looking at the crash logs this is consistent across every change I have made.

00000028FDC6ED50 00007FFA20E49B43 0000000000000000 0000000000000010 000001696B150000 0000016900000000 d3d11.dll!0x7ffa20e49b43
00000028FDC6F0E0 00007FFA20E496BD 0000000000000001 00000169324D5430 000000000000EA60 00000169324D5310 d3d11.dll!0x7ffa20e496bd
00000028FDC6F180 00007FFA07129788 0000016915A4E900 00000169295771A0 000001690000EA60 0000000000000000 libobs-d3d11.dll!gs_texture_2d::InitTexture+0x418
00000028FDC6F200 00007FFA07129FF0 00000169324D5310 0000016971E10BB0 000001696E1BD1E0 0000016929594218 libobs-d3d11.dll!gs_texture_2d::gs_texture_2d+0x250
00000028FDC6F250 00007FFA07123FDE 0000016971E10BB0 0000000000000000 0000000000003A98 0000000000003A98 libobs-d3d11.dll!device_texture_create+0x8e
00000028FDC6F2E0 00007FF9E3E47887 000001692956D078 0000000000000072 000001692958F6A0 00000169295771A0 obs.dll!gs_texture_create+0xe7
00000028FDC6F330 00007FF9E3E4CD62 000001692958F6A0 00007FFA08AD8648 0000000000000000 0000016929578EE0 obs.dll!gs_image_file_init_texture+0x62
00000028FDC6F370 00007FFA08AD17B4 0000000000000000 0000000000000000 0000000000000000 0000000000000000 image-source.dll!image_source_load_texture+0x44
00000028FDC6F3A0 00007FFA08AD1D9A 0000016971EF33A0 0000016929594F20 0000016929594F20 0000000000000000 image-source.dll!image_source_tick+0x3a
00000028FDC6F420 00007FF9E3DF17A2 0000016971EF33A0 0000000000000072 000001692958F6A0 0000000000000000 obs.dll!obs_source_video_tick+0x562
00000028FDC6F490 00007FF9E3E03CA6 000001696E1BD1E0 00000028FDC6F5C0 0000000000000000 0000000000000000 obs.dll!tick_sources+0x266
00000028FDC6F4F0 00007FF9E3E07501 0000000000000000 0000071B487236C4 0000000000000000 0000000000000000 obs.dll!obs_graphics_thread_loop+0x171
00000028FDC6F5A0 00007FF9E3E07A4F FFFFFFFFFFFFFFFF 00000011ED3F0CC5 00000028FDC6F6B9 0000000000000000 obs.dll!obs_graphics_thread+0x12f
00000028FDC6F650 00007FFA1EA514A7 0000016970B82670 0000000000000000 0000000000000000 0000000000000000 w32-pthreads.dll!ptw32_threadStart+0x1b7
00000028FDC6F720 00007FFA278F9333 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ucrtbase.dll!0x7ffa278f9333
00000028FDC6F750 00007FFA28FD257D 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffa28fd257d
00000028FDC6F780 00007FFA2A1EAF28 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffa2a1eaf28


To hopefully get through my day I am going to remove all image loading/slide shows for now and give it a full test with all things reactivated, with hopefully overnight success that can confirm this was the problem source.

 

[thisTinker]

We successfully ran overnight; thus I am quite confident we found the source of the error.

Whether or not this image loading problem is concentrated to the large/odd file formats I had, I am not sure - when I have more time later I will probably test this by building increasingly long slideshow lists with increasingly file size until the error happens.

The 'randomness' with which the problem happened, and likely the reason it did not happen immediately when those images were introduced may have to do with the fact that the slides were still being randomly shuffled and thus didnt always land on a problematic image or cycle.

The other key here that I missed is that unlike other sources, even if the group a slideshow is in is not visible, the slideshow still may be running in the background. I can see this when i click on the source because it instantly shows each image with ease, shows no signs of loading or unloading like video feeds can.

Solved-ish : Removing image slideshow, but why image slideshows cause this problem? at what size/length are they problematic for OBS?