Question / Help Back for my yearly visit (Crash Diagnosis)

Funkays

New Member
Hey gang,

Usually get a crash once a year and it ends up being Motherboard BIOs being out of date.
Had a crash last month, lo and behold there was a BIOs update waiting for me on the MSI website (love how theres no notification for these).

Unfortunately even with this new update I found my OBS crashed this evening (about 2-3 streams since last crash) wondering if anyone can see the cause?
Furthermore is there anywhere on this site that teaches users how to read their own crash logs? I can't make heads nor tails of it.

Thanks again for your help!

Edit: tried to interpret the log, found
"Fault address: 7FFAB7048310 (g:\program files (x86)\obs-studio\bin\64bit\libx264-157.dll)"
Googled "libx264-157.dll"
Found 1 thread where a dude talks about needing to update his GPU drivers.
Turns out mine are out of date. Is this the cause? The thread i found the dude's were up to date. But i don't use Nvenc to encode so~


Log: https://obsproject.com/logs/IxDLpalsDLENy1gJ
 

Funkays

New Member
No crash tonight after 3 hour session. Was playing Classic WoW instead of Monster Hunter World. Unsure if the less hardware stressing game was a solution to no issues; or GPU driver update was the solution
 

Harold

Active Member
Libx264 crashes have very limited causes
1> ryzen microcode issues
2> unstable overclock
3> failing cpu/ram
 
Top