Bug Report OBS Crash : kernel problem

Fahrenheit

New Member
Hi everyone,

I have a huge problem OBS crash all the time when I streaming or recording, it worked perfectly last month and now it crash after 10 min !

I think it's a driver or something ? Can you help me please to solve the problem :)

I use QSV since the beggining and I don't want to use x248 ...

Thanks in advance

Code:
This crash appears to have occured in the 'c:\windows\syswow64\kernelbase.dll' module.

**** UNHANDLED EXCEPTION: 80000003
Fault address: 74CB3219 (c:\windows\syswow64\kernelbase.dll)
OBS version: Open Broadcaster Software v0.624b
Windows version: 6.1 (Build 7600)
CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz

Crashing thread stack trace:
Stack    EIP      Arg0     Arg1     Arg2     Arg3     Address
0036F200 74CB3219 000010E0 00007530 00000000 00000000 kernelbase.dll!0x74cb3219
0036F210 01062C1C 00000000 00000000 01081760 0006029A obs.exe!OBS::Stop+0x12c
0036F25C 01083174 000802A6 00000401 00000000 00000000 obs.exe!OBS::OBSProc+0x1a14
0036F348 75566238 01081760 000802A6 00000401 00000000 user32.dll!0x75566238
0036F374 755668EA 00000000 01081760 000802A6 00000401 user32.dll!0x755668ea
0036F3EC 75567D31 01081760 00000000 0036F480 75582292 user32.dll!0x75567d31
0036F44C 75567DFA 0036F51C 00080657 75567E92 75567D79 user32.dll!0x75567dfa
0036F45C 75582292 000802A6 00000000 00000000 00000001 user32.dll!0x75582292
0036F488 01056000 01010000 00000000 00672FF5 00000001 obs.exe!WinMain+0x8d0
0036F954 0109E8AA FFFDE000 0036F9E4 773C9D42 FFFDE000 obs.exe!__tmainCRTStartup+0xfd
0036F9A0 75663677 FFFDE000 767A66F7 00000000 00000000 kernel32.dll!0x75663677
0036F9AC 773C9D42 0109E7A3 FFFDE000 00000000 00000000 ntdll.dll!0x773c9d42
0036F9EC 773C9D15 0109E7A3 FFFDE000 00000000 00000000 ntdll.dll!0x773c9d15

Video thread stack trace:
Stack    EIP      Arg0     Arg1     Arg2     Arg3     Address
1795F4A8 773AF861 00000190 FFFFFFFF 00000000 6C70C2A0 ntdll.dll!0x773af861
1795F51C 75661184 00000190 FFFFFFFF 00000000 1795F820 kernel32.dll!0x75661184
1795F534 75661138 00000190 FFFFFFFF 00000000 00000000 kernel32.dll!0x75661138
1795F548 01067D9C 75663677 00000000 1795F870 773C9D42 obs.exe!OBS::MainCaptureLoop+0x1d9c
1795F828 01064D85 00000000 1795F870 773C9D42 00000000 obs.exe!OBS::MainCaptureThread+0x5
1795F82C 75663677 00000000 61D96763 00000000 00000000 kernel32.dll!0x75663677
1795F838 773C9D42 01064D80 00000000 00000000 00000000 ntdll.dll!0x773c9d42
1795F878 773C9D15 01064D80 00000000 00000000 00000000 ntdll.dll!0x773c9d15

Encode thread stack trace:
Stack    EIP      Arg0     Arg1     Arg2     Arg3     Address
176BF5E0 773B00ED 176BF630 176BF6A4 00000000 FFFFFFFF ntdll.dll!0x773b00ed
176BF684 7566162D 00000003 FFFDE000 00000000 FFFFFFFF kernel32.dll!0x7566162d
176BF6CC 75661921 00000003 0025E040 00000000 FFFFFFFF kernel32.dll!0x75661921
176BF6E8 0104C947 176BF854 176BF85C 0000000A FFFFFFFF obs.exe!QSVEncoder::ProcessEncodedFrame+0x37
176BF7A0 0104D536 001C3E00 176BF854 176BF85C 00020E90 obs.exe!QSVEncoder::Encode+0x86
176BF7F8 010655F0 176BF900 00000000 00000000 00000000 obs.exe!OBS::ProcessFrame+0xb0
176BF87C 01065BAB 75663677 00000000 176BF9A4 773C9D42 obs.exe!OBS::EncodeLoop+0x42b
176BF95C 01064D75 00000000 176BF9A4 773C9D42 00000000 obs.exe!OBS::EncodeThread+0x5
176BF960 75663677 00000000 612766B7 00000000 00000000 kernel32.dll!0x75663677
176BF96C 773C9D42 01064D70 00000000 00000000 00000000 ntdll.dll!0x773c9d42
176BF9AC 773C9D15 01064D70 00000000 00000000 00000000 ntdll.dll!0x773c9d15

A minidump was saved to C:\Users\Léonard Kück\AppData\Roaming\OBS\crashDumps\OBSCrashDump2014-09-05_1.dmp.
Please include this file when posting a crash report.

List of loaded modules:
Base Address      Module
 

Attachments

  • OBSCrashDump2014-09-05_1.rar
    325 KB · Views: 16

R1CH

Forum Admin
Developer
The crash is caused by QSV race conditions, so you'll need to use x264 to avoid it.
 

Fahrenheit

New Member
The crash is caused by QSV race conditions, so you'll need to use x264 to avoid it.

Hi R1CH !

QSV rare conditions ? I don't want to use x264 .. Any tips to find the problem ?

Audio ? Webcam ? Maybe Drivers ?
 
Last edited:

R1CH

Forum Admin
Developer
No, it's a known issue when using QSV. You could try the test build as a lot of QSV stuff was changed there.
 
Top