Bug Report My OWN post regarding crashes after update to 552B version

[drhino]

Okay so someone said I should just start my own post so here it is. Basically, I was a new OBS user as of last week. Went through the how-tos and setup OBS per Twitch and OBS recommended settings. I have done various tests of rollbacks and still crashes, drops frame rates extremely low and ends up crashing the OBS when I try to stop streaming with "Not Responding". Trying to Stream Starcraft 2:HoTs via Monitor Capture and eventually probably Diablo III if I can get OBS to work and maybe more things.

Windows 7 64 Bit OS
Msi Z77-Mpower Motherboard
GeForce gtx650Ti Video Card
I7-3770K processor
N600 Dual Gigabit Router with Motorola Modem @ 108mbps consistent signal- hardlined via CAT6 Cables

CUSTOM BUILD Gaming PC


I have checked/tried all of the following:

*Have tested and/or adjusted settings to see if the changes affect drop loss or crash-NEGATIVE
*Have Scanned entire system for updates necessary to ALL Firmware, Software, Hardware, Utilities, BIOS, etc etc. including on the Router and modem- No Updates needed
* Have tested rollbacks and adjusted settings on all previous versions. stopped testing at 542B where the most significant difference was noted but eventually frames dropped out after a bit.
* Have tested different servers
*Have checked with "Network" and Negative no issues there
*Have checked system with HiJackThis: only thing necessary to remove was a toolbar that I never use
*All AV software is operated from a shadow drive -external drive where I keep all programs extracted regarding AV, Hijack, and other optimization softwares- NEGATIVE: NO interference as not operated at the same time as streaming or major lag-out and even worse.
*Have reset and reposted the Stream Key to settings/tried on default recommended settings as well as dropping max bitrate to test whether the setting needed adjusted and with or without downscales at various stats

After verifying that none of the other software on the computer is problematic I have uninstalled all versions of OBS and APPDATA infos to have a clean install of the most recent 0552B to do a clean test. NEGATIVE-Mass fail and crash log appears instantly. Since the update on 8/16/13 to V0552B this is consistent on all versions now:

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:\windows\syswow64\kernelbase.dll' module.

**** UNHANDLED EXCEPTION: 80000003
Fault address: 766C3219 (c:\windows\syswow64\kernelbase.dll)
OBS version: Open Broadcaster Software v0.552b
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
0056EDE4 766C3219 0000064C 0000EA60 02041320 00360400 kernelbase.dll!0x766c3219
0056EDF8 0024BD9E 00000000 0056F2B0 00246DF6 00000001 obs.exe!RTMPPublisher::~RTMPPublisher+0x7e
0056F270 0024BB1B 00000001 76B32DA4 76B4F1BA 004F0502 obs.exe!RTMPPublisher::`scalar deleting destructor'+0xb
0056F27C 00246DF6 00360400 00261D81 00000000 00261280 obs.exe!OBS::Stop+0x136
0056F2B8 0024572A 00000000 00261280 00000000 00120506 obs.exe!OBS::ToggleCapturing+0x1a
0056F2C0 00261D81 76B26D51 0056F3C4 76B262FA 004F0502 obs.exe!OBS::OBSProc+0xb01
0056F394 76B26D91 00261280 004F0502 00000111 00001389 user32.dll!0x76b26d91
0056F3CC 76B26D3A 00000000 00261280 004F0502 00000111 user32.dll!0x76b26d3a
0056F444 76B2965E 00ADE9B0 00000000 00261280 00001389 user32.dll!0x76b2965e
0056F488 76B296C5 004F0502 00000111 00001389 00120506 user32.dll!0x76b296c5
0056F4AC 708E4601 006B0170 00000000 00120506 006B0170 comctl32.dll!0x708e4601
0056F4CC 708E4663 54010000 00000001 00000000 7086B495 comctl32.dll!0x708e4663
0056F4E8 708E44ED 00120506 00000202 00000000 00030066 comctl32.dll!0x708e44ed
0056F548 76B262FA 7086B495 00120506 00000202 00000000 user32.dll!0x76b262fa
0056F574 76B26D3A 00000000 7086B495 00120506 00000202 user32.dll!0x76b26d3a
0056F5EC 76B277C4 7086B495 00000000 0056F680 76B4C81F user32.dll!0x76b277c4
0056F64C 76B2788A 0056F6FC 76B31246 76B278E2 03CD0693 user32.dll!0x76b2788a
0056F65C 76B4C81F 004F0502 00000000 00000000 00000000 user32.dll!0x76b4c81f
0056F688 0023CCC5 00220000 00000000 006536B4 0000000A obs.exe!WinMain+0x7d5
0056FB04 002A1E09 FFFDE000 0056FBD8 77319F72 FFFDE000 obs.exe!strstr+0x1c9
0056FB94 752933AA FFFDE000 777672E6 00000000 00000000 kernel32.dll!0x752933aa
0056FBA0 77319F72 002A1E5C FFFDE000 00000000 00000000 ntdll.dll!0x77319f72
0056FBE0 77319F45 002A1E5C FFFDE000 00000000 00000000 ntdll.dll!0x77319f45

A minidump was saved to C:\Users\GAMER\AppData\Roaming\OBS\crashDumps\OBSCrashDump2013-08-21_1.dmp.
Please include this file when posting a crash report.

List of loaded modules:
Base Address Module

 

[Mlynek18]

Re: My OWN post regarding crashes after update to 552B versi

I got the same problem.

 

[R1CH]

Re: My OWN post regarding crashes after update to 552B versi

Please include the .dmp file and your regular OBS log.

 

[drhino]

Re: My OWN post regarding crashes after update to 552B versi

I already posted my other files on my other posts. After several rollback installs Ive wiped it clean so what is posted is what I have now. I think I will just have to wait to see an update issued because everyone seems to be coming back with the same issue solutions that don't fix the problem. Not AV conflict and not "bad server connection, so switch servers". Would like to see OBS work fine on my system but it crashes the kernal file like no tomorrow and causes my game to crash too. Game Capture or Window Capture are just BAAAAAD for this software- too blurry. WHether I like it or not, I've determined that the problem was OBS crashing my system. something seriously wrong with it because the second I uninstalled, my computer wasnt crashing anymore. That's no bueno :/

 

[drhino]

Re: My OWN post regarding crashes after update to 552B versi

Checked with a repair geek and they looked into the error that was happening on my computer. They were able to duplicate on their gaming desktop. Said something about OBS is bouncing incomplete streaming bits and by doing so is working too hard to play "catch up" and overloading the Memory...hence the kernal.dll crash caused by OBS. But wierd thing here... a 16GB DDR3 should handle just fine with an I73770k processor so suggested I throw that information your way. Repository is not receiving all frames of the streams. Off to the new update patch when it gets here and lets all hope that works or I will be very sad.

 

[R1CH]

Re: My OWN post regarding crashes after update to 552B versi

If your entire computer is crashing it seems like the problem is unrelated to OBS. Maybe you have bad hardware or faulty drivers.

 

[drhino]

Re: My OWN post regarding crashes after update to 552B versi

This is excellent and just gets better and better every time. lol its a brand new computer bro and custom built by myself. nothing faulty at all. and as you can see in previous posts and not just in this thread, obs is causing the crashes not my computer. wow shocking u actually assumed that. ok so will wait for a new release to see fixes applied and if not then onto a different software. as an FYI, tried both xsplit and wirecast after obs crashes began and both work fine but I don't like the software so those were uninstalled from a-z because the free versions are fps restricted and more blur quality. Obs seemed much simpler and more to our liking but guess we shall see with new fixes if we can even use it. also as an fyi i have several friends that I have asked about their usage and 7 out of 10 are having the same issue and error with their Kernal files. so their hardware and drivers are faulty too?? I will make sure to tell them all that their brand new gaming computers are junk too if its crashing after 0552b downloaded to theirs. Very nice and dismissive bro.

As for my geek friend, they downloaded v.551b and worked fine for a bit. auto update prompt appeared after restart of computer and opening OBS. updated. within 5 minutes of update...dun dun dunnnn same error on THEIR computer. but I guess I have faulty hardware right? so with that said, your assumption was unnecessary had you read the post. How hard is it to just say you know what this sucks that we can't figure out what OBS is doing on your computer and our apologies but we are working on various fixes for the next release that we hope will resolve the various issues recently revealed after v.0552b was released? forget it I will wait for a new release. not appreciated. tyvm

 

[Krazy]

Re: My OWN post regarding crashes after update to 552B versi

kernelbase.dll is a core system file, and it's possible it got corrupted somehow. Have you ran a System File Check? (open elevated command prompt, type sfc /scannow)

 

[R1CH]

Re: My OWN post regarding crashes after update to 552B versi

OBS crashing my system

the second I uninstalled, my computer wasnt crashing anymore

This is why I thought your computer was crashing.

Anyway, it's probably a regional ISP issue or you have some 3rd party software conflict. I wouldn't trust your PC repair guy, statements like this are completely made up:

They were able to duplicate on their gaming desktop. Said something about OBS is bouncing incomplete streaming bits and by doing so is working too hard to play "catch up" and overloading the Memory...hence the kernal.dll crash caused by OBS.

There is no "kernel crash" as that would blue screen your entire PC. OBS is intentionally raising a breakpoint (which occurs inside Kernel32.dll) since the network thread is taking too long to close. The reason the network thread is timing out is because you have been disconnected and OBS was not informed, likely due to a network failure or a 3rd party firewall / router interfering with the connection.

 

[Lain]

Re: My OWN post regarding crashes after update to 552B versi

If you are referring to the kernelbase.dll crash, that's actually known and fixed on the git repository -- we added code that tries to finish the rest of the stream when you hit the disconnect button, but the send thread gets too far backlogged with packets, and we had it programmed to cause a breakpoint if it exceeded the thread timeout so we could see specifically where a thread was getting stuck. We determined which thread and which code and will release a hotfix for that particular issue soon. I'm just trying to fix some other bugs with saints row 3, batman arkam city, and doom 3, though I may have to delay one or more of those fixes just to release the patch for the kernelbase thing.

Now, if your entire computer is crashing as r1ch said, those sort of problems are actually not caused directly by OBS itself. Blue screens and similar things are hardware/driver issues that are not directly caused by OBS, only "triggered".

I already had PMed you about this before and told you we had solved the crash issue and posted it into various threads. I'm not entirely sure why you are here expressing your discontent. I will never state that the software is perfect or without flaws, but to argue about what causes what would be perilous ground.

If you were the programmer in this case you would not be saying the same things you are now. Also, R1CH implemented new network code because he wanted to fix the issue where the last [X] number of seconds of the stream would constantly get cut off when the user presses the disconnect button. He is one of the best coders I've ever met in my life, and I think you really need to just.. calm the heck down and switch to an older working version until we get that fixed, okay?

Just come on. We're only human beings here, you, I, all of us. Can you literally expect "perfection" from someone 100% of the time? Do you know how many times I've added some feature and broken something else? Do you know how many times I've sweated over problems I may have caused just because I've been trying to improve something? This job isn't easy. Cut us some slack.