Multiple crashes in a row (libx264-164.dll)

[Valdevia]

Hey folks! I need some help figuring out some recent OBS crashes. They seem to happen at random so it's quite hard to find a cause.
Here are some recent crash logs, two of them identify libx264-164.dll as the cause of the crash (full files attached below, but here's the relevant part):

Crash 1 (last week)

Thread 60D8: (Crashed)
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
00000031D8F97D60 00007FF87F0A08C4 0000018F38C38A00 00000031D8F97E80 00000000000000B7 0000000000000003 libx264-164.dll!0x7ff87f0a08c4
00000031D8F97DB0 00007FF87F0BEDD7 0000018F38C38A00 0000000000005964 0000000000000022 0000018F000001E0 libx264-164.dll!0x7ff87f0bedd7
00000031D8F9DB90 00007FF87F0F3AE1 0000018F38C38A00 0000000000000000 0000000000001FDF 0000018F597C6580 libx264-164.dll!0x7ff87f0f3ae1
00000031D8F9FB70 00007FF87F0F497F 0000018F1E510840 0000000000000000 0000018F597C6580 0000000000000000 libx264-164.dll!0x7ff87f0f497f
00000031D8F9FBA0 00007FF87F0FCF24 0000000000000000 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ff87f0fcf24
00000031D8F9FBD0 00007FF87F0744C0 0000018F6AA88E60 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ff87f0744c0
00000031D8F9FC00 00007FF87F19C58A 0000000000000000 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ff87f19c58a
00000031D8F9FC30 00007FF8CE1A7374 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ff8ce1a7374
00000031D8F9FC60 00007FF8CF37CC91 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ff8cf37cc91

Crash 2 (today)

Thread 4BE4: (Crashed)
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
000000502DB57A40 0000000000004961 0000000000000000 000001E79A556040 00007FFEC50FEDD7 0000000000000000 <unknown>!0x4961
000000502DB57A48 0000000000001205 000001E79A556040 00007FFEC50FEDD7 0000000000000000 000000502DB57B40 <unknown>!0x1205

Crash 3 (today)

Thread 61EC: (Crashed)
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
00000094BF4C8050 00007FFB5F73EDD7 0000022BC175B040 0000000000000654 0000000000000035 0000022B000001E0 libx264-164.dll!0x7ffb5f73edd7
00000094BF4CDE30 00007FFB5F773AE1 0000022BC175B040 0000000000000000 0000000000001FDF 0000022BBAD65C40 libx264-164.dll!0x7ffb5f773ae1
00000094BF4CFE10 00007FFB5F77497F 0000022BAAFB49C0 0000000000000000 0000022BBAD65C40 0000000000000000 libx264-164.dll!0x7ffb5f77497f
00000094BF4CFE40 00007FFB5F77CF24 0000000000000000 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ffb5f77cf24
00000094BF4CFE70 00007FFB5F6F44C0 0000022BBAD32090 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ffb5f6f44c0
00000094BF4CFEA0 00007FFB5F81C58A 0000000000000000 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ffb5f81c58a
00000094BF4CFED0 00007FFBE1D17374 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffbe1d17374
00000094BF4CFF00 00007FFBE2AFCC91 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffbe2afcc91

(There was a third crash today but it didn't seem to generate a crash report)

Two of them appear to be related to "c:\program files\obs-studio\bin\64bit\libx264-164.dll", which appears to be part of the main obs-studio files and not related to any plugin/external source. I don't really know where to to from there. Some have related this to hardware issues which makes me worry. I'd love to hear your thoughts!

 

[Suslik V]

Unhandled exception: c0000005

Thread 61EC: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
00000094BF4C8050 00007FFB5F73EDD7 0000022BC175B040 0000000000000654 0000000000000035 0000022B000001E0 libx264-164.dll!0x7ffb5f73edd7
00000094BF4CDE30 00007FFB5F773AE1 0000022BC175B040 0000000000000000 0000000000001FDF 0000022BBAD65C40 libx264-164.dll!0x7ffb5f773ae1
00000094BF4CFE10 00007FFB5F77497F 0000022BAAFB49C0 0000000000000000 0000022BBAD65C40 0000000000000000 libx264-164.dll!0x7ffb5f77497f
00000094BF4CFE40 00007FFB5F77CF24 0000000000000000 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ffb5f77cf24
00000094BF4CFE70 00007FFB5F6F44C0 0000022BBAD32090 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ffb5f6f44c0
00000094BF4CFEA0 00007FFB5F81C58A 0000000000000000 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ffb5f81c58a
00000094BF4CFED0 00007FFBE1D17374 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffbe1d17374
00000094BF4CFF00 00007FFBE2AFCC91 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffbe2afcc91

Highly likely, your PC has hardware problems. It is no longer stable.

Details: https://obsproject.com/forum/threads/obs-crashing-every-few-minutes.168562/post-619305

 

[Suslik V]

If you familiar with FFmpeg, command line and ".bat" files, then you may try to run few test with x264 encoder (few runs needed in parallel to load all cores): https://obsproject.com/forum/threads/crash-during-stream-c0000005-libx264-164-dll.167133/post-614297

 

[Valdevia]

If you familiar with FFmpeg, command line and ".bat" files, then you may try to run few test with x264 encoder (few runs needed in parallel to load all cores): https://obsproject.com/forum/threads/crash-during-stream-c0000005-libx264-164-dll.167133/post-614297

Thank you! Trying this right now, I'm not seeing a problem so far. Also stress tested with LinX since I saw that recommended in this forum but it gave me a clean bill of health. Any idea how long I should be running this stress test? And am I just looking for crashes?

 

[Valdevia]

I should note I'm pretty wary of my CPU, it's one of the i9-14900K models that are famously unstable. This is my second one, after the first one gave out and was replaced by Intel. The latest BIOS updates after the instability became known are supposed to run it very conservatively to avoid instability, but suffice to say I do not trust it to last a very long time.
That said I haven't had any of the issues the last i9 gave me yet (mostly BSOD and slower performance) so this might be unrelated.

 

[Suslik V]

Any idea how long I should be running this stress test? And am I just looking for crashes?

Event Viewer of Windows should leave some traces during the test period if process will be terminated in unusual way. Usually, wrong settings, like overclock, under powered hardware, low timings for RAM etc, diagnosed (fails) faster than just the malfunction device. If in 4-5 hours it surely fails - you may try to isolate the CPU core, by setting affinity. You can remove the RAM modules one by one (sometimes, resitting the module also helps).

 

[R1CH]

Unfortunately libx264 crashes almost always point to hardware issues. I have found the y-cruncher BBP test limited to 1-2 threads is extremely effective at finding failing CPUs (14900k specifically).

 

[Valdevia]

Unfortunately libx264 crashes almost always point to hardware issues. I have found the y-cruncher BBP test limited to 1-2 threads is extremely effective at finding failing CPUs (14900k specifically).

Thanks a lot! I've been trying y-cruncher through the corecycler program (runs it on one core at a time) and after some time it triggered a BSOD. I assume that means bad news for the CPU...