Crash: c0000005 - Report Log

R1CH

Forum Admin
Developer
x264 crashes indicate unstable hardware. Disable overclocks, update BIOS, test your RAM.
 

TheSaltyBaron

New Member
x264 crashes indicate unstable hardware. Disable overclocks, update BIOS, test your RAM.


Thanks for the response, my current OC has been stable over 8 hour stress tests in a couple benches, as well as mem testing, passes without issue, I'll still test out the OC idea though and lower them down/stock their amounts, cause this does seem a little strange.
 

TheSaltyBaron

New Member
x264 crashes indicate unstable hardware. Disable overclocks, update BIOS, test your RAM.
@R1CH

Hey there,

So after...a good deal of benchmarking, stability testing, talking full days. There doesn't seem to be instability. The testing methodology included:

20 passes in memtest86 (No OC activated except for RAM put to 3200 which is manufacturer recommendation)
8 Hours prime95
12 hours AIDA64 System Stability Test
6 hours Cinebench

I then repeated the same tests as above with ClockTuner Ryzen undervolting applied, which had similar performance, slightly higher than stock, but at significantly lower temperatures.

In both instances, OBS still crashes.

I've attached the latest crash report.


Do you have any benchmarks or recommendations that can help in terms of OBS testing besides what I did above?
 

Attachments

  • Crash 2021-01-29 12-23-27.txt
    150 KB · Views: 6

Xerocry

New Member
Same thing, no overclocks, last bios, good RAM.
Windows 10, Nvidia 2070 Super, B450 Tomahawk motherboard, ryzen 5 3600.

Getting crashes like every 5 minutes sometimes. Have to restart PC, after that crashes go away but only for an hour..

Here's my log also: https://pastebin.com/q3Ux70V7
 

Sukiyucky

Member
Xerocry, yours is not the same problem as the Ops. His has to do with x264.
Yours has to do with the Chromium plugin.

You are running 64 bit Windows. However, OBS is referencing the 32 bit libcef.dll. Did you install 64 bit OBS?

  1. Fault address: FDE4BB5 (c:\program files\obs-studio\obs-plugins\32bit\libcef.dll)
  2. libobs version: 26.1.1 (32-bit)
  3. Windows version: 10.0 build 19041 (release: 2004; revision: 746; 64-bit)
 

Xerocry

New Member
Xerocry, yours is not the same problem as the Ops. His has to do with x264.
Yours has to do with the Chromium plugin.

You are running 64 bit Windows. However, OBS is referencing the 32 bit libcef.dll. Did you install 64 bit OBS?

  1. Fault address: FDE4BB5 (c:\program files\obs-studio\obs-plugins\32bit\libcef.dll)
  2. libobs version: 26.1.1 (32-bit)
  3. Windows version: 10.0 build 19041 (release: 2004; revision: 746; 64-bit)

Oooh, thanks, I just saw that I've accidentally pinned x32 to start instead of x64. Probably that was the reason!
Still, where you find that it's chromium plugin error? I tried to understand the log, but can't see any reasons there..
 

Sukiyucky

Member
Its a chromium plugin error. The clue is in the log that says this:
Fault address: FDE4BB5 (c:\program files\obs-studio\obs-plugins\32bit\libcef.dll)

Its crashing in libcef.dll (Chromium). The pathname caught my attention as it says 32bit. Then I saw you were running under Windows 64 bit.
So I thought it maybe a 32 bit OBS installation trying to run on 64 bit Windows.
 
Top