Question / Help Fresh install results in crash

RytoEX

Forum Admin
Forum Moderator
Developer
If it's a fresh install and you have never used OBS Studio on this computer before, or if you don't mind losing your scenes and settings, you could try deleting all of the OBS Studio settings to force it to go back to default. If you want to do that, uninstall OBS Studio, delete "%AppData%\obs-studio", restart your computer, then reinstall OBS Studio.

If you don't want to lose all of your settings, you can try to delete just the profile settings file ("%AppData%\obs-studio\basic\<profilename>.ini" and see if OBS Studio will regenerate the file on restart. You will still lose some settings data this way.

If you really want to minimize your data loss, and you're comfortable manually editing OBS settings files, then you can try to manually edit your profile settings file ("%AppData%\obs-studio\basic\<profilename>.ini"). In it, you should see two sections labeled "[Output]" and "[SimpleOutput]". Try deleting those sections, and OBS should select default values the next time it loads the profile. If that doesn't work, try pasting this in place of those sections:
Code:
[Output]
Mode=Simple

[SimpleOutput]
FilePath=C:\\Temp\\videos
RecFormat=flv
UseAdvanced=false
RecQuality=Stream
VBitrate=2500
EnforceBitrate=true
Preset=veryfast
RecEncoder=x264
You'll still lose whatever settings those had previously been.


Let us know what you decide to do and how it works out. Let us know if you still have issues after that.
 

TheClimbing

New Member
So it seems there is a problem between my GPU drivers and OBS Studio.I went trough uninstalling all of my graphic drivers.Then after the clean uninstall of my Intel HD Graphics and AMD drivers.I installed the Intel drivers and tried to run OBS it was success.Then when I installed the latest AMD drivers for my GPU OBS started crashing again.
 

Attachments

  • 2016-11-11 15-41-53.txt
    2.8 KB · Views: 24
  • Crash 2016-11-11 16-00-37.txt
    17 KB · Views: 19

RytoEX

Forum Admin
Forum Moderator
Developer
OBS Classic doesn't have the AMD AMF encoder. That plugin's author has noticed a few odd driver conflicts between Intel and AMD. If you're not going to use the AMD AMF encoder plugin, you could probably just remove it from your installation. If you do want to use it, then you should probably work through the plugin's troubleshooting guide.
 

JanH

New Member
Same crashes. No AMD here but nVidia 970 and with OBS studio not in AppData/obs-studio but AppData\local\obs-studio.
The only ini file I can find sits in obs-studio\basic\profiles\profilename\basic.ini

redownloaded the installer, restarted, switched off any virus software, keep crashing on doubleclick startup.

Any suggestions?
 

Attachments

  • Crash 2016-11-11 21-38-22.txt
    50 KB · Views: 17

RytoEX

Forum Admin
Forum Moderator
Developer
@JanH
That is a completely different crash. Your crash is probably an image source that is too "big", likely a really large/long GIF. If you have a 64-bit OS, try running the 64-bit version of OBS Studio to get it to at least startup. Then, find and remove/replace the offending image.
 

RytoEX

Forum Admin
Forum Moderator
Developer
Sorry for the double post, wasn't sure if users get notified for being tagged in an edit.

@TheClimbing
Can you work through the troubleshooting guide for the AMD AMF encoder plugin? I've talked with @Xaymar about this, but we're not sure what's going on with your crash, so we need more information. What we're most interested in at the moment is what AMD card you have and what drivers you have installed.
 

TheClimbing

New Member
Ok so first my AMD GPU is R5 M330,And its as they say "headless" GPU because Intel is actually the CPU and GPU.The drivers i have installed are the latest from the official AMD support site.I just double checked and everything is up to date.If you want me to tell you the exact version of all my graphic drivers I'll check tomorrow.It's too late here.I'll come back with more information tomorrow
 

JanH

New Member
Hi RytoEX,

Thanks for the help. The 64bit version started fine. Thought I had the shortcut directed at the 64bit.
With a large image file you mean a Dxtory source or an image slideshow?

And I did not get a notification on the tag. Corrected in my profile. Responses will now be send via mail.
 

Suslik V

Active Member
@TheClimbing , Have you any option to switch your R5 M330 on and use it instead of Intel's graphics (in BIOS maybe)?

Edit: @RytoEX , Are you notified about tagging? This was in edit. Next time I will check quote in edit.

Edit2:
@Suslik V
I'm notified in this thread when any replies are posted, regardless of tagging. I guess my other concern was the time between my post and the edit, and whether or not the post had been seen already.
How about quoting, any changes? @RytoEX , so, no way... OK.
 
Last edited:

RytoEX

Forum Admin
Forum Moderator
Developer
@Suslik V
I'm notified in this thread when any replies are posted, regardless of tagging. I guess my other concern was the time between my post and the edit, and whether or not the post had been seen already.
 

TheClimbing

New Member
Sorry for being inactive for awhile.So from the BIOS i can select to use Switchable or UDF?(i dont remember exactly)so if I choose to not use the Switchable graphics it disables the dedicated or the AMD card.I've gone trough many sites and everyone is saying that every attempt to try making the PC use the AMD card instead of Intel graphics results in black screen or just disabling the AMD GPU.Which is afterwards fixed by reinstalling windows.When I said Windows...Now i'm running Windows 7 x64 bit but before the Win7 I was on Windows 8 x64 bit and there i think OBS Studio was able to start and all.So there is some issue between Win7 my graphics configuration and OBS Studio
 

Suslik V

Active Member
Log says that OBS Studio didn't have any evidence of AMD video card existence on your system, so it completely disabled. Why you need driver installed for this device (OBS Studio trying to get properties form the device and fails, because driver crashed)? Enable the AMD card or uninstall the device driver completely.
 
Top