OBS 31.1.1 recording failure

Bobw111

New Member
Just installed OBS 31.1.1 today, just before beginning my weekly session with a buddy in Arizona. Started recording, OBS showed recording during 2+ hour long session. Ended recording. OBS is set to automatically remux recording once recording is ended. Waited 5 minutes, but remux never began. Used Task Manager to end remux app, closed OBS, reopened OBS, and tried to remux recording. Remux ended almost instantly saying nothing to remux. I checked and the .mkv file that should have been recorded showed zero length. System is Windows 11 on a DELL Precision 3680 i7-14700 2.1GHz, 64GB ram, NVIDIA RTX 200 Ada w/16GB, drive recording stores to is 8TB with 3.84TB free space. I've previously had issues with OBS not stopping recording, or not remuxing, but can't figure out why. Only thing I have noticed is that Windows 11 might be putting hard drives into sleep mode since Windows explorer doesn't instantly open a drive like it used to on my old system with Windows 10. Any ideas would be greatly appreciate.
 

Attachments

The path has worked fine in the past with prior versions. I'll knock out the spaces between # and OBS to see if that helps though.
 
There is one more thing. Windows 11 updates keep setting my drives to power down after 1 minute. Drives me nuts because then it takes about a minute for the system to power back up and show me the drive content whenever I use Windows Explorer (which I use quite a lot.) I've reset windows to never power down the drive. Hope that works for today's session.
 
OK. Today I got a recording 80 minutes long, but when I hit "Stop recording" OBS just sat there saying "stopping recording." Usually it jumps right into remuxing. So, I had to kill OBS in the task manager. I then restarted OBS and recorded about another 61 minutes. This time when I stopped recording remux started up instantly. I then manually ran remux on the first file and the remux ran fine. So, I'm guessing the windows powering down the drive after 1 minute is what causes OBS to not record anything. However that still doesn't explain why "Stop recording" hangs and requires killing OBS in the task manager.
 
And once again today, I started recording, OBS showed recording, but nothing was recorded. Two hours of content completely lost. I guess you have to check the recording location on the drive every few minutes to make sure it actually is recording video.
 
Well... Not quite as bad as I thought. I had to kill OBS via the Task manager and Windows explorer showed the MKV file had zero bites at that point. I refreshed the task manager screen a couple of times and it kept showing zero length for the MKV file. So, I walked away in disgust. I came back 20 minutes later and the MKV file had magically grown to 12GB. I opened OBS and remuxed the file and it converted fine. SO, I got a recording, but it is a pain having to kill OBS and manually remux each time.
 
All the way at the end of your log. There's a conflict on the system. Is Adobe CC running?
14:53:43.943: Blocked loading of '\coresync_x64.dll' 3 times.

Some other things.
Scenes need attention. Only (1) Display, Window or Game capture per to avoid interference
Norton360 is a joke. More like malware.

 
Just an FYI. I noticed the installed driver is v571.59. Might want to think about updating to the latest available. Nvidia went through a stretch when the 5000 series was released where the drivers were causing all types of performance issues on multiple series of GPU's. I don't see that driver even listed anymore, probably pulled for a reason.

 
Just an FYI. I noticed the installed driver is v571.59. Might want to think about updating to the latest available. Nvidia went through a stretch when the 5000 series was released where the drivers were causing all types of performance issues on multiple series of GPU's. I don't see that driver even listed anymore, probably pulled for a reason.

Good catch on the driver. I downloaded a newer version on 6/7/25 and thought I had it installed. That's what "thought" did for me. Got it right now though.
 
All the way at the end of your log. There's a conflict on the system. Is Adobe CC running?
14:53:43.943: Blocked loading of '\coresync_x64.dll' 3 times.

Some other things.
Scenes need attention. Only (1) Display, Window or Game capture per to avoid interference
Norton360 is a joke. More like malware.

All the way at the end of your log. There's a conflict on the system. Is Adobe CC running?
14:53:43.943: Blocked loading of '\coresync_x64.dll' 3 times.

Some other things.
Scenes need attention. Only (1) Display, Window or Game capture per to avoid interference
Norton360 is a joke. More like malware.

Yes, I have adobe CC running since I use Premiere Pro, and a bunch of other CC products. Maybe I'm pushing OBS to far? I record online sessions with my USAF buddy of 50+ years. So, during each session we have MS Teams running. I'm recording me locally, then using OBS virtual camera to feed me to him through Teams, while recording him through through the Teams session in OBS. I also have another friend that I use basically the same setup on. I also share an MS Word document, or other content my system back to him through teams. We were using Skype for all of this, but MS killed Skype. We've tried 5 or 6 other software apps to replace Skype, but this Teams/OBS setup is the only one that lets us make long (2 hour plus) recordings without each of us having to spend a fortune of new software. Is coresyn_x64.dll critical to stopping recording and immediately starting remux? That seems like the final battle I'm fighting right now?
 
All the way at the end of your log. There's a conflict on the system. Is Adobe CC running?
14:53:43.943: Blocked loading of '\coresync_x64.dll' 3 times.

Some other things.
Scenes need attention. Only (1) Display, Window or Game capture per to avoid interference
Norton360 is a joke. More like malware.

I don't think I follow on the "Only (1) Display, Window or Game capture per to avoid interference." Are you saying I shouldn't try combining capture of multiple sources (Browser and MS Word window for instance) in the same scene at the same time? I don't remember that ever being a problem in the past. I thought that was kind of one of the benefits of OBS.
 
Check your new log, see if your graphics thread/frame output timing has improved with the new driver installed. According to the previous log, there's plenty of room for improvement considering the hardware that you have.
14:53:43.662: obs_graphics_thread(33.3333 ms): min=0.065 ms, median=2.581 ms, max=80.636 ms, 99th percentile=15.482 ms, 99.993% below 33.333 ms
14:53:43.662: ┣tick_sources: min=0.001 ms, median=0.021 ms, max=69.141 ms, 99th percentile=0.064 ms
14:53:43.662: ┣output_frame: min=0.058 ms, median=2.045 ms, max=80.481 ms, 99th percentile=15.099 ms

Kill Adobe before/while using OBS.

Not sure about the remux.
Something I have not encountered.

14:52:51.039: [ffmpeg muxer: 'adv_file_output'] Output of file 'H:/# OBS Recordings/2025-07-13 12-52-07.mkv' stopped
14:52:51.039: Output 'adv_file_output': stopping
14:52:51.039: Output 'adv_file_output': Total frames output: 1
14:52:51.039: Output 'adv_file_output': Total drawn frames: 217012 (217016 attempted)
14:52:51.039: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 4 (0.0%)
14:52:51.040: ==== Recording Stop ================================================
14:52:51.056: warning: Format matroska,webm detected only with low score of 1, misdetection possible!
14:52:51.056: error: EBML header parsing failed
14:52:51.056: media_remux: Could not open input file 'H:/# OBS Recordings/2025-07-13 12-52-07.mkv'
14:52:51.203: warning: 2 frames left in the queue on closing
14:53:14.583: warning: Format matroska,webm detected only with low score of 1, misdetection possible!
14:53:14.583: error: EBML header parsing failed
14:53:14.583: media_remux: Could not open input file 'H:\# OBS Recordings\2025-07-13 12-52-07.mkv'

If you want to avoid potential issues/interference, only use (1) per Scene. If quality doesn't matter, carry on as is.
 
Thanks for the advice. I'll start paying more attention to my log file and make sure I kill Adobe CC before I start a recording session.
 
Just had the same problem show up on my laptop after Windows 11 update. I did some testing and made sure that nothing for Adobe was running. Same issue, hit the "start recording" button, record for a bit, hit "stop recording" button and OBS just hangs. Have to kill OBS in task manager to close OBS. Discovered .MKV files show zero byte UNTIL you open OBS and tell it start normally. At that point the .MKV file for the previous session sets closed out and a data length shows. Just as a test I told OBS to start in "Safe Mode" after a test and recording started fine, recording stopped fine, and remux started automatically. The log file 2025-08-02 19-59-19.txt is from this "Safe Mode" run. The other two are test where I had to kill OBS in the task manager. I'm not an expert on these log files, so any help is greatly appreciated. FWIW I made sure that NO Adobe software was running when I ran these tests.
 

Attachments

The logs are truncated but this applies again.

the file path sticks out to me

Code:
H:/#          OBS Recordings/2025-07-13 12-52-07.mkv

This is older than dirt, needs update or removal:
19:49:45.267: [obs-backgroundremoval] plugin loaded successfully (version 0.4.0)

Usual suspects:
Norton360
HAGS

Other issues:
19:53:02.505: Skipping module '../../obs-plugins/64bit/onnxruntime.dll', not an OBS plugin
19:53:02.507: Skipping module '../../obs-plugins/64bit/StreamFX.dll' due to possible import conflicts
19:53:02.525: <StreamDeck> Plugin version 5.5.3.1

Sample rate mis-matches.
 
The truncated logs are obviously caused by having to kill the program. FIle path has worked fine for years, but I'll condense it although it made no difference on my desktop. I'll also clean out all the other items noted. Thanks for the input. I'll post the results after more testing.
 
I did a whole shitload of testing on my laptop, making sure all drivers were up to date, Windows 11 wasn't turning off the disk drives, disabling Norton 360, and anything else I could think of (including hiding any plugins or dlls OBS log showed a problem with), and the problem persisted "intermittently." It even occurred once after I did a safe mode restart.

So... I figured "what to hell" and raised the question to Grok as to whether others had this same sort of issue... And it turns out a lot of people are. After fine feeding grok details and a few back and forths, one recommendation popped out: "Unload Logitune" because there seems to be a know problem of it interfering with NVENC.

Because of the intermittent issue of the problem I can't say for certain this cured it. However, I uninstalled Logitune from both machines and was able to start and stop recordings without a problem. I tested on the laptop with a recording just over one minute. On my desktop I did a recording of slightly over 5 minutes and it stopped fine with remux starting automatically as it is set to do. I'll do more testing as time permits and update the results here.

The logs weren't much help as they can't pick up anything after you crash out OBS via the task manager. One interesting thing that did pop up occasionally was the reference to the number of memory leaks OBS was having. With 40+ years of programming and IT behind me (older languages, mainframe and mini computers) having a program tell me it has memory leaks is a bit disconcerting.
 
Yes sorry it never made it back to this thread but there was a Logitune update that caused these issues, either uninstalling or updating to the latest version of Logitune resolved this as they fixed on their end. As far as memory leaks, the log you posted shows 0 but chances are if you're seeing those they are from one of your third party plugins.
 
Yes sorry it never made it back to this thread but there was a Logitune update that caused these issues, either uninstalling or updating to the latest version of Logitune resolved this as they fixed on their end. As far as memory leaks, the log you posted shows 0 but chances are if you're seeing those they are from one of your third party plugins.
Thanks for the info. I'm pretty sure I was running the latest Logitune on both computers since it seems to update automatically, so it may still have problems. Logitune installed when I started using a Logitech 4K Brio camera. However, the camera seems to work just fine in OBS without it. I'll live without Logitune until an issue forces me to install it.
 
Back
Top