Obs Studio 28.0.3 - Bugs, more bugs, 0Kbps and Bluescreen

Welington

New Member
Bluescreen does not occur in games, only in OBS Studio, I have FIFA 23, 22, 18 and other games and only in Obs Studio Bluescreen occurs.

Another error that occurs is that it crashes and streams at 0Kbps. It doesn't matter if the game streamed is FIFA 18 or FIFA 23.

I've lost many streams because of these problems.

There are no errors in the Log.
 

PaiSand

Active Member
Please post a crash report. When OBS crashes it produce a crash report. When no crash report is available most probably is due to another process crashing, like GPU drivers or something else. To identify which process crash you can see it on the windows events viewer.
 

Welington

New Member
event log - Error Name: Unknown

Crash folder is empty

Dxdiag:
Windows Error Reporting:
+++ WER0 +++:
Falha no bucket 1789347438366223050, tipo 5
Nome do Evento: AppHangB1
Resposta: Não disponível
ID do CAB: 0

Assinatura do problema:
P1: obs64.exe
P2: 28.0.3.0
P3: 63389406
P4: 4efb
P5: 67241984
P6:
P7:
P8:
P9:
P10:

Arquivos anexados:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER556E.tmp.WERInternalMetadata.xml

Esses arquivos talvez estejam disponíveis em:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_obs64.exe_446bc8e89a4fd03853794046ebf173a4485fcbd0_d8e4c579_b7c5c83c-b1dc-4e78-9a94-1a8c5bc10abb

Símbolo da análise:
Verificando novamente se há uma solução: 0
ID do Relatório: 592c4ac3-e41e-41e5-9c80-bdcf0dfe586d
Status do Relatório: 268435456
Bucket com hash: 279668631118ee57f8d50a03cb92eacaGuid do CAB: 0
+++ WER1 +++:
Falha no bucket , tipo 0
Nome do Evento: AppHangB1
Resposta: Não disponível
ID do CAB: 0

Assinatura do problema:
P1: obs64.exe
P2: 28.0.3.0
P3: 63389406
P4: 4efb
P5: 67241984
P6:
P7:
P8:
P9:
P10:

Arquivos anexados:

Esses arquivos talvez estejam disponíveis em:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_obs64.exe_446bc8e89a4fd03853794046ebf173a4485fcbd0_d8e4c579_b7c5c83c-b1dc-4e78-9a94-1a8c5bc10abb

Símbolo da análise:
Verificando novamente se há uma solução: 0
ID do Relatório: 592c4ac3-e41e-41e5-9c80-bdcf0dfe586d
Status do Relatório: 4
Bucket com hash: Guid do CAB: 0
 

Welington

New Member
What are the requirements needed to use these features that are not working here?
- Color Format: P010 and I010 not working
- Color Space: Rec. 2100 (PQ) and Rec. 2100 (HLG) not working
 

PaiSand

Active Member
From the 28 release notes;

28.0: 10-bit and HDR Video Encoding Support​


OBS now supports 10-bit and HDR, courtesy of rcdrone, YouTube, and Luxoft. New color format and color space settings have been added in the advanced settings to allow this.


Important notes about HDR and 10-bit:


  • HDR and 10-bit can only be encoded with AV1 and HEVC encoders.
  • The recommended settings for HDR are Color Format P010 and Color Space Rec. 2100 PQ.
  • If you wish to encode 10-bit SDR, you can use Color Format P010 with an SDR color space (e.g. Rec. 709, Rec. 601). However, AV1 or HEVC will still be required.
  • HDR streaming is currently only supported via YouTube's HLS service via an HEVC encoder.
  • When composing in SDR, games that operate in HDR can now be properly tonemapped to SDR.
  • Video capture devices can be used to capture and stream in HDR if the device supports it (e.g. EVGA XR1 Pro, Elgato 4K60 Pro Mk.2, AverMedia Live Gamer 4K).
  • Certain filters will not function if a source is rendering with HDR:
    • Apply LUT, Chroma Key, Color Key, Image Mask/Blend, Luma Key, Sharpness
  • Mac/Linux support is limited. HDR preview does not work, and several inputs/encoders still need to be updated.


Of course, you need a system to be capable of HDR, including the monitor.
You still need to provide a crash report and a log file.
If there's no crash report then most probably the crash is outside OBS.
As soon you open OBS a log file is generated. If you see no log files then something in your system is preventing OBS to function.

Streams at 0Kbps are usually due to netwrok issues. It could be in your home network or the ISP.
As you're not showing a log file it's imposible to try to figure out any of this.
 
Top