Bug Report OBS Crashs every 10 Minuts

Sat0re

New Member
Here my Crashlog...

OBS has encountered an unhandled exception and has terminated. If you are able to
reproduce this crash, please submit this crash report on the forums at
http://www.obsproject.com/ - include the contents of this crash log and the
minidump .dmp file (if available) as well as your regular OBS log files and
a description of what you were doing at the time of the crash.

This crash appears to have occured in the 'c:\program files (x86)\obs\libx264-136.dll' module.

**** UNHANDLED EXCEPTION: c0000005
Fault address: 6B281941 (c:\program files (x86)\obs\libx264-136.dll)
OBS version: Open Broadcaster Software v0.584b
Windows version: 6.1 (Build 7601) Service Pack 1
CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz

Crashing thread stack trace:
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
08D8A118 6B281941 0842B2A0 00000010 08D8A380 00000010 libx264-136.dll!0x6b281941
08D8A120 6B20BE99 00000010 08D8A380 00000010 0000000F libx264-136.dll!0x6b20be99
08D8A124 0842B2A0 08D8A380 00000010 0000000F 0000007E <unknown>!0x842b2a0

A minidump was saved to C:\Users\Sat0re\AppData\Roaming\OBS\crashDumps\OBSCrashDump2013-11-18_4.dmp.
Please include this file when posting a crash report.

List of loaded modules:
Base Address Module

15:59:13: Open Broadcaster Software v0.584b - 32bit (´・ω・`)
15:59:13: -------------------------------
15:59:13: CPU Name: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
15:59:13: CPU Speed: 3500MHz
15:59:13: Physical Memory: 4095MB Total, 3276MB Free
15:59:13: stepping id: 9, model 58, family 6, type 0, extmodel 1, extfamily 0, HTT 1, logical cores 8, total cores 4
15:59:13: monitor 1: pos={0, 0}, size={1920, 1080}
15:59:13: monitor 2: pos={1920, 0}, size={1920, 1080}
15:59:13: Windows Version: 6.1 Build 7601 S
15:59:13: Aero is Disabled
15:59:13: -------------------------------
15:59:13: OBS Modules:
15:59:13: Base Address Module
15:59:13: 00F60000 OBS.exe
15:59:13: 6BCC0000 OBSApi.dll
15:59:13: 6F4D0000 DShowPlugin.dll
15:59:13: 6F470000 GraphicsCapture.dll
15:59:13: 6F450000 NoiseGate.dll
15:59:13: 6F430000 PSVPlugin.dll
15:59:13: ------------------------------------------
15:59:13: Adapter 1
15:59:13: Video Adapter: AMD Radeon HD 7900 Series
15:59:13: Video Adapter Dedicated Video Memory: 3202392064
15:59:13: Video Adapter Shared System Memory: 1092509696
15:59:13: Video Adapter Output 1: pos={0, 0}, size={1920, 1080}, attached=true
15:59:13: Video Adapter Output 2: pos={1920, 0}, size={1920, 1080}, attached=true
15:59:13: ------------------------------------------
15:59:13: Adapter 2
15:59:13: Video Adapter: Intel(R) HD Graphics 4000
15:59:13: Video Adapter Dedicated Video Memory: 67108864
15:59:13: Video Adapter Shared System Memory: 1711276032
15:59:13: =====Stream Start: 2013-11-18, 15:59:13===============================================
15:59:13: Multithreaded optimizations: On
15:59:13: Base resolution: 1920x1080
15:59:13: Output resolution: 1280x720
15:59:13: ------------------------------------------
15:59:13: Loading up D3D10 on AMD Radeon HD 7900 Series...
15:59:13: ------------------------------------------
15:59:13: Audio Format: 48000hz
15:59:13: Playback device {0.0.0.00000000}.{d11d628d-fd72-4f3a-acf9-6e5aff26dace}
15:59:13: ------------------------------------------
15:59:13: Using desktop audio input: Lautsprecher (Logitech G930 Headset)
15:59:13: Using 7.1 surround speaker setup
15:59:13: ------------------------------------------
15:59:13: Using auxilary audio input: Mikrofon (Logitech G930 Headset)
15:59:13: ------------------------------------------
15:59:13: Audio Encoding: AAC
15:59:13: bitrate: 160
15:59:13: Using text output
15:59:13: Using bitmap image
15:59:13: Using graphics capture
15:59:13: Scene buffering time set to 700
15:59:13: Using custom x264 settings: "8x8dct=1 aq-mode=2 bframes=1 chroma-qp-offset=1 colormatrix=smpte170m deblock=0:0 direct=auto ipratio=1.41 keyint=120 level=3.1 me=hex merange=16 min-keyint=auto mixed-refs=1 no-mbtree=0 partitions=i4x4,p8x8,b8x8 profile=main psy-rd=0.5:0.0 qcomp=0.6 qpmax=51 qpmin=10 qpstep=4 ratetol=10 rc-lookahead=30 ref=1 scenecut=40 subme=5 threads=0 trellis=2 weightb=1 weightp=2"
15:59:13: The custom x264 command 'min-keyint=auto' failed
15:59:13: ------------------------------------------
15:59:13: Video Encoding: x264
15:59:13: fps: 30
15:59:13: width: 1280, height: 720
15:59:13: preset: faster
15:59:13: profile: main
15:59:13: keyint: 120
15:59:13: CBR: yes
15:59:13: CFR: no
15:59:13: max bitrate: 2400
15:59:13: buffer size: 2400
15:59:13: ------------------------------------------
15:59:13: MMDeviceAudioSource: Frequency for device 'Lautsprecher (Logitech G930 Headset)' is 1536000, samples per sec is 48000
15:59:13: MMDeviceAudioSource: Frequency for device 'Mikrofon (Logitech G930 Headset)' is 64000, samples per sec is 16000
15:59:14: SharedTexCapture hooked
15:59:16: Using RTMP service: Twitch / Justin.tv
15:59:16: Server selection: rtmp://live-ams.justin.tv/app
15:59:16: Interface: Realtek PCIe GBE Family Controller (ethernet, 100 mbps)
15:59:17: Completed handshake with rtmp://live-ams.justin.tv/app in 380 ms.
15:59:18: SO_SNDBUF was at 8192
15:59:18: SO_SNDBUF is now 65536
15:59:18: RTMPPublisher::SocketLoop: Increasing send buffer to ISB 131072 (buffer: 0 / 327680)
16:11:03: RTMPPublisher::SocketLoop: Received FD_CLOSE, 5054 ms since last send (buffer: 0 / 327680)
16:11:03: RTMPPublisher::SocketLoop: Aborting due to FD_CLOSE, error 0
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
First, try it without the custom x264 settings. There's really no need to have those settings at all. If that fails, then it's most likely a memory issue
 

Sat0re

New Member
Here the Screenshot :

LinX191120f1b4.png
 

Sat0re

New Member
Attachment and here the log file


OBS has encountered an unhandled exception and has terminated. If you are able to
reproduce this crash, please submit this crash report on the forums at
http://www.obsproject.com/ - include the contents of this crash log and the
minidump .dmp file (if available) as well as your regular OBS log files and
a description of what you were doing at the time of the crash.

This crash appears to have occured in the 'c:\program files (x86)\obs\libx264-136.dll' module.

**** UNHANDLED EXCEPTION: c0000005
Fault address: 6B281941 (c:\program files (x86)\obs\libx264-136.dll)
OBS version: Open Broadcaster Software v0.584b
Windows version: 6.1 (Build 7601) Service Pack 1
CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz

Crashing thread stack trace:
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
08D8A118 6B281941 0842B2A0 00000010 08D8A380 00000010 libx264-136.dll!0x6b281941
08D8A120 6B20BE99 00000010 08D8A380 00000010 0000000F libx264-136.dll!0x6b20be99
08D8A124 0842B2A0 08D8A380 00000010 0000000F 0000007E <unknown>!0x842b2a0

A minidump was saved to C:\Users\Sat0re\AppData\Roaming\OBS\crashDumps\OBSCrashDump2013-11-18_4.dmp.
Please include this file when posting a crash report.

List of loaded modules:
Base Address Module
 

Attachments

  • OBSCrashDump2013-11-18_4.rar
    171.5 KB · Views: 32

R1CH

Forum Admin
Developer
Are you overclocking at all? This almost certainly looks like hardware failure:

Code:
EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 6b281941 (libx264_136!x264_pixel_sad_16x16_sse2+0x00000011)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 08e8ac58
Attempt to read from address 08e8ac58

FAULTING_IP: 
libx264_136!x264_pixel_sad_16x16_sse2+11
6b281941 f30f6f02        movdqu  xmm0,xmmword ptr [edx]

eax=00000000 ebx=1ca940d0 ecx=00000010 edx=08d8a380 esi=1ca94088 edi=1ca94098
eip=76fd0c42 esp=08d88310 ebp=08d88320 iopl=0         nv up ei pl zr na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246

This means OBS crashed while trying to read memory at edx. The exception occurred because the memory at 0x08e8ac58 was not readable. However, edx points to 0x08d8a380.

This basically means the impossible happened, the CPU tried to read memory from somewhere it was never asked to. The only explanation is faulty hardware, overheating or overclocking.
 

Sat0re

New Member
Now i have 1 Error only by Call of Duty Ghosts on the map "Stoneheaven" looks like Graphiccard or?
 

Attachments

  • Unbenannt.png
    9 KB · Views: 13
Top