This isn't my area of expertise, but I don't think this is recoverable .. video frames never created/written to your drive
17:11:10.629: ==== Recording Start ===============================================
17:11:10.629: [ffmpeg muxer: 'simple_file_output'] Writing file 'C:/Users/User/Videos/2021-11-09 17-11-10.mkv'...
19:10:15.388: [ffmpeg muxer: 'simple_file_output'] Output of file 'C:/Users/User/Videos/2021-11-09 17-11-10.mkv' stopped
19:10:15.456: Output 'simple_file_output': Total frames output: 9242
19:10:15.456: Output 'simple_file_output': Total drawn frames: 152581 (214344 attempted)
19:10:15.456: Output 'simple_file_output': Number of lagged frames due to rendering lag/stalls: 61763 (28.8%)
19:10:15.500: ==== Recording Stop ================================================
19:10:15.687: Video stopped, number of skipped frames due to encoding lag: 9223/9261 (99.6%)
Basically the above means your computer was to busy to encode the video frames 99.6% of the time. Why?
That is a REAL old (9+ yrs), low-end CPU, optimized for battery life, not the computationally demanding task of real-time video encoding.
I recommend monitoring hardware resource (CPU, GPU, RAM, Disk I/O, etc) utilization [for ex. using Task manager’s Performance tab and/or Resource Monitor] to see if your system is being maxed out with your settings (and I'm sure your CPU is maxed out at 100% the entire time). And realistically, without a LOT of optimizations, I'd be surprised if such a system would do much.. ever. You can see these forums for recommended OBS settings on under-powered systems
'Koala' once indicated they thought a CPU benchmark (Passmark) of around 5000 was a minimum requirement. The Pentium 2020M gets about 1385 on Passmark. I tried last year to use a circa 2015 gaming laptop with an i5-6300HQ with an SSD and nVidea GPU for encode offload, which scores 4,682 on Passmark, and I could get OBS to run as long as I wasn't playing any pre-recorded videos (which was a requirement). And I'm fairly competent at optimization the Operating System (required as Microsoft default setting sap too much CPU with eye candy and other). So realistically, unless you have expert consulting available to you, and/or become fairly expert at optimizing Operating Systems and OBS, I wouldn't expect that old system to work. sorry.
Again, doubt it will help, but make Base Resolution and output resolution the same to minimize work (not having to re-scale video)
Very minor side note - It is recommend to NOT have audio input devices at different sampling rates, so fix (make consistent)
17:00:35.783: WASAPI: Device 'Altavoces (Conexant SmartAudio HD)' [44100 Hz] initialized
17:00:36.792: WASAPI: Device 'Internal Microphone (Conexant SmartAudio HD)' [48000 Hz] initialized
Also, if recording, why are you using Streaming setting with CBR (constant bitrate).. search forum for guidance on settings for Recording
https://obsproject.com/forum/threads/best-settings.140188/#post-514693 @FerretBomb comment #2
2) Record using CQP or CRF, not CBR. CBR is only used for streaming, where the back-end infrastructure requires it. CQP/CRF are quality-target based encodes, and will use as much or as little bitrate as is needed to maintain a constant image quality. No wasting bitrate on simple/slow scenes, no choking on fast-moving or complex scenes. 22 is a good starting point. 16 will result in much larger files, but near-perfect video. 12 should only be used if you plan to edit and re-encode later, and will be VERY large. Anything lower than 12 shouldn't be used unless you know exactly why you need it, and what problems it can cause.
just a fellow OBS user
