Question / Help Help with Problem with OBS crashing at open after update of AMD Raedon driver.

Vidgirl8

Vidgirl8

New Member
Is there any way to get OBS to work with AMD Radeon? I had an issue with OBS crashing on opening after I updated my AMD Radeon driver. Once I did that, OBS would not work at all. It crashed before it could open. I had to roll back my system to remove the update then OBS was able to work again. I would like to run Marbles On Stream and this problem is keeping me from being able to do that. I need to be able to run Marbles in a windowed resolution and because AMD is not present, there are no resolution choices to scale a window. Is there a way to make both OBS and AMD work at the same time?
 
Vidgirl8

Vidgirl8

New Member
This should be it here I think this is the correct day
 

Attachments

  • 2019-07-27 22-13-33.txt
    68.7 KB · Views: 42
Narcogen

Narcogen

Active Member
22:13:33.287: Windows Version: 10.0 Build 17134 (revision: 885; 64-bit)

This version of Windows is from April 2018 and has performance issues with OBS. There have been two major updates since then, you should apply them.

22:13:41.535: [AMF] [Capability Manager] Testing Direct3D 11 Adapter 'Radeon (TM) R7 M445 (VEN_1002/DEV_6900/SUB_7681028/REV_00c3)':
22:13:41.535: H264/AVC: Not Supported
22:13:41.535: H265/HEVC: Not Supported
22:13:41.535:
22:13:41.535: [AMF] [H264/AVC] Not supported by any GPU, disabling...
22:13:41.535: [AMF] [H265/HEVC] Not supported by any GPU, disabling...

If you're trying to use hardware encoding on this card, it won't work because your card does not support that feature.

22:13:50.993: adding 69 milliseconds of audio buffering, total audio buffering is now 116 milliseconds (source: Bugs)
22:13:51.767: adding 23 milliseconds of audio buffering, total audio buffering is now 139 milliseconds (source: Bugs)
22:13:51.906: adding 46 milliseconds of audio buffering, total audio buffering is now 185 milliseconds (source: Bugs)
10:13:53 PM.962: adding 46 milliseconds of audio buffering, total audio buffering is now 232 milliseconds (source: Media Source 53 background)
10:13:54 PM.089: adding 23 milliseconds of audio buffering, total audio buffering is now 255 milliseconds (source: Bugs)
10:13:54 PM.135: adding 23 milliseconds of audio buffering, total audio buffering is now 278 milliseconds (source: Media Source 53 background)

10:13:56 PM.181: adding 23 milliseconds of audio buffering, total audio buffering is now 301 milliseconds (source: Media Source 53 background)
10:13:56 PM.479: adding 139 milliseconds of audio buffering, total audio buffering is now 441 milliseconds (source: Media Source 53 background)
10:13:56 PM.922: adding 208 milliseconds of audio buffering, total audio buffering is now 650 milliseconds (source: Media Source 53 background)
10:13:57 PM.520: adding 255 milliseconds of audio buffering, total audio buffering is now 905 milliseconds (source: Media Source 53 background)
10:13:58 PM.186: Max audio buffering reached!
10:13:58 PM.186: adding 139 milliseconds of audio buffering, total audio buffering is now 1044 milliseconds (source: Media Source 53 background)

Something is overloading your CPU-- it looks like some particular media sources are causing a problem. (You have a LOT of them.)

You may want to create a new blank profile and scene collection without any 3rd party overlays and test it for performance and stability. If it still crashes, add those logs to the thread.
 
Vidgirl8

Vidgirl8

New Member
I have updated windows everytime they come through. "If you're trying to use hardware encoding on this card, it won't work because your card does not support that feature." I am not trying to use anything. I don't touch anything with graphics settings. The only reason I wanted to update the driver is because a window popped up and told me to. Media source 53 is my background wallpaper for my lobby. It is a motion background. The Bugs is a small rotating avatar of Bugs Bunny. More than likely it;s the wallpaper background that's causing the problem. So you're saying that if I eliminate that, both programs run simpatico?
 
Narcogen

Narcogen

Active Member
I can't say that removing those would fix your issue, but I can definitely tell that those sources are causing an issue for OBS. How much of your problem is caused by them I can't say.

That your Windows build is two major versions behind is definitely the case. If your auto-update is not working you should update manually. That particular build causes OBS to perform badly. This has been a known issue in the support boards widely discussed for the past several months since an update came out that fixed it.

I'm not sure what you mean by:

I need to be able to run Marbles in a windowed resolution and because AMD is not present, there are no resolution choices to scale a window. Is there a way to make both OBS and AMD work at the same time?
Click to expand...

By "AMD" I assume you mean your driver, and you need to have a driver installed, preferably the latest, to use the card's full capabilities. The log indicates you have a driver installed because OBS recognizes the card. Whether that driver is the latest or not I can't tell from the logfile.

If you're saying an old driver or accessory program you used to have allowed for features regarding resolution selection in your game that you currently don't have on the latest version, I don't know. I thought that possibly by "AMD not present" you meant the AMF encoder, so I was just pointing out that you can't use that on this card. This is also a common question where users attempt to use hardware encoding features of OBS on GPUs that don't support them.
 
Vidgirl8

Vidgirl8

New Member
I let windows update every time there is an update. OBS will not work when the current Raedon AMD driver is installed, that's why I had to roll back the system
windows.jpg
 
You must log in or register to reply here.
Top