Question / Help Obs Studio crash BF1 Beta

[Dorian_D]

Hi guys. I know BF1 is a beta and it will likely have some crashes, but I decided to try the NVENC encoder since my fps was not great when using X264. For 30mins the game and stream was fine until both of my monitors hard locked to black screens resulting me to shut down by holding the power button. I'm not familiar with the tech language in the crash file and stream log file so if someone can have a look at to see what caused the crash that would be greatly appreciated!

PC specs: core i7 3770, GTX 1070, 16gb ddr3 ram

Thanks,

Dorian

 

[CoDEmanX]

That crash message seems to have occurred for other people too (with other games / programs), see e.g.

• https://obsproject.com/forum/threads/obs-crashed-unhandled-exception-80000003.15448/
• https://obsproject.com/forum/threads/unhandled-exception-80000003.28694/
  
• http://forums.autodesk.com/t5/autoc...017/unhandled-exception-80000003/td-p/3857087
  
• https://www.reddit.com/r/gamemaker/...nal_exception_80000003_game_maker_crashes_on/

What were suggested in those posts is to not use NVENC, update the graphics card driver or uninstall a certain Windows update. I would guess it's a problem with Nvidia's GPU driver, perhaps in combination with the GTX 1070 or the Battlefield Beta.

Am I reading it correctly that you use 32bit OBS? Did you try 64bit as well?

 

[Beardedbob]

Hi @Dorian_D

I've also experienced this with BF1 though OBS wasn't running on my Gaming PC, what I found is that when the EA servers go down it hangs up the local client of BF1 with a black screen and only a hard restart will bring it back. Now the EA servers are online again after the hack attacks have you found this to be an issue still? if so have you tried it without OBS running?

Looking at your logs x264 will run your cpu hard as its only a i7-3770 on Nvenc the 1070 should be fine but could be a driver related issue as @CoDEmanX has said. Can you confirm if you on the latest drivers?

Cheers

Bob.

 

[Dorian_D]

Thank you guys for the replies @Beardedbob and @CoDEmanX !

The day before this issue I streamed BF1 and used x264 encoder and had nvidia driver 372.54. Stream was solid for the most part with a few fps drops.

Now the day of the problem. I streamed BF1 and installed the latest drivers geforce driver 372.70. For the first 2.5 hrs I was using the X264 encoder but the in-game frames were not so good (35-40 fps). So I decided to stop the stream and try NVENC encoder and boom massive in-game fps up to 80-100+ fps. For 30 mins it was solid then the game crashed with both of my screens going black. I could hear my friends in discord still, but my pc was completely locked so I had to do a hard reset.

I have not tested the game since, but I did uninstall my nvidia drivers with DDU (Display Driver Uninstaller) and performed a clean install the latest geforce driver 372.70 driver.

I have not tried the 64bit OBS Studio with BF1 but I will give it a go on the next cast. Only reason why I don't use OBS Studio 64bit is because Amarec live plugin is 32bit application.

Again, thank you guys for your feedback. I will check out those older threads with the similar crash exception error.

 

[Beardedbob]

@Dorian_D no problem see if it does it again and if it crashes let us know.

 

[Dorian_D]

@Beardedbob So I tried again and it crash pretty much the same way. I used OBS Studio 64bit. It lasted for about 1hr then the stream crashed. I attached the crash log and stream log. I figure that it is likely the NVENC encoder not working properly or it could be BF1 Beta. I will stick with X264 and adjust settings to improve in game fps.

 

[Jon Ferry]

Mine crashed on OBS Studio 32bit using x264 complete black screen

My BF1 was in DX12 so I had a hard time getting it to capture then i reverted to DX11 and it worked then I crashed

I am using Version 372.70 too

 

[Dorian_D]

@Jon Ferry My best guess it is either the BF1 Beta or it could be the Nvidia driver that is causing the issue. Other games have been solid and things were good on the past nvidia driver for me.

 

[Black Ops]

dx12 is the issue. DIsable it

 

[Dorian_D]

@Black Ops All my tests have been in DX 11.

 

[Black Ops]

Thats odd, i was getting crashes until i disabled dx12

 

[Dorian_D]

Well I decided to give BF1 one more shot with obs studio streaming. It crashed 2 hours into a stream. I figure with my computer it must be the latest nvidia 372.50 drivers not liking the game or BF1 beta just has crash problems. If anyone wants to check this crash log and stream log I have attached them.

Again thank you everyone for your help and input!

 

[CoDEmanX]

@dorian: Your CPU supports QuickSync, so you may give that a go. NVENC and QuickSync use hardware encoding, which means there will be only a very little additional workload for your computer to encode, but note that the video quality per bitrate is never as good as x264 (which will put noticeable load on your CPU).

On my desktop computer, I had to enable multi monitor support for the iGPU (the graphics unit integrated into the CPU) in the BIOS and connect my display once to the HDMI output of the mainboard in order to make QuickSync show up as an option in OBS.

For streaming, you are limited to CBR or VBR AFAIK, but quality should be acceptable around 3000kbps (note: using twitch, you should not go above 2000 if you have viewers outside the US). For offline recording, I can recommend LA-ICQ 30 and lookahead 100, which gives a pretty good quality while not creating overly large files as you would get with LA-ICQ 10 for instance. Here's a sample (you need to download it to see the actual quality): https://drive.google.com/open?id=0B4i9nvp7_qCsVUJGWHVSV0N6U1U (note that you see some blocking artifacts during the zoom-in on the map, but other than that, it looks pretty good at 1080p@60).

 

[Dorian_D]

@CoDEmanX Thank you for the suggestion. I may give Quicksync a shot before the beta ends, but for now I think I got my fill of BF1. Maybe if purchase the game for release and it has several obs bugs I will certainly try out all the encoders again. Thank you again for the help!