Crash during hardware tests

I have a Win10 Haydes Canyon PC with the AMD processor and a fast i7 chipset.

the app crashes hard during hardware tests.

note that my PC does not have a camera and i intend to use my mobile phone for this.

i found this log file:

[1203/194702.913:ERROR:gles2_cmd_decoder.cc(16003)] Context lost because SwapBuffers failed.
[1203/194702.913:ERROR:angle_platform_impl.cc(54)] testDeviceLost(1899): The D3D11 device was removed, HRESULT: 0x887A0006
[1203/194702.913:ERROR:gles2_cmd_decoder.cc(16357)] Onscreen context lost via ARB/EXT_robustness. Reset status = GL_UNKNOWN_CONTEXT_RESET_KHR
[1203/194702.913:ERROR:gles2_cmd_decoder.cc(5699)] Error: 5 for Command kPostSubBufferCHROMIUM
[1203/194702.913:ERROR:gpu_channel_manager.cc(189)] Exiting GPU process because some drivers cannot recover from problems.
[1203/194702.913:ERROR:gpu_channel_manager.cc(189)] Exiting GPU process because some drivers cannot recover from problems.
[1203/194702.913:ERROR:gpu_channel_manager.cc(189)] Exiting GPU process because some drivers cannot recover from problems.
[1203/194702.914:ERROR:gpu_channel_manager.cc(189)] Exiting GPU process because some drivers cannot recover from problems.
[1203/194702.914:ERROR:gl_context_egl.cc(211)] eglDestroyContext failed with error EGL_CONTEXT_LOST
[1203/194702.914:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteFramebuffersEXT without current GL context
[1203/194702.914:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteVertexArraysOES without current GL context
[1203/194702.914:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteBuffersARB without current GL context
[1203/194702.914:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteBuffersARB without current GL context
[1203/194702.914:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteBuffersARB without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteBuffersARB without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteTextures without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteProgram without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteProgram without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteProgram without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteProgram without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteProgram without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteShader without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteShader without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteShader without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteShader without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteShader without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteShader without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteShader without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteShader without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteShader without current GL context
[1203/194702.915:ERROR:gl_bindings_autogen_gl.cc(12011)] Trying to call glDeleteShader without current GL context
[1203/194702.915:ERROR:gl_context_egl.cc(211)] eglDestroyContext failed with error EGL_CONTEXT_LOST
[1203/194702.922:ERROR:gl_context_egl.cc(211)] eglDestroyContext failed with error EGL_CONTEXT_LOST
[1203/194702.922:ERROR:gl_context_egl.cc(211)] eglDestroyContext failed with error EGL_CONTEXT_LOST
[1203/194707.549:ERROR:broker_win.cc(58)] Error reading broker pipe: The pipe has been ended. (0x6D)
[1203/194707.549:ERROR:cmd_buffer_helper.cc(139)] ContextResult::kFatalFailure: CommandBufferHelper::AllocateRingBuffer() failed

Hello there, may I ask which version of XSplit VCam are you currently using?

I’m a new customer so i have whatever is available for download right now. i only bought the app yesterday.

Installer is: XVC_Installer_2.0.2011.1701.exe

FYI. I’m also a software developer, so i may be able to help in ways that other are not. Let me know what you need. i have Visual Studio 2019 installed if you need me to run a debug.

Hi! We’ll have to check first if any drivers should be reinstalled or updated. Please send us your MSINFO32 file:

https://www.xsplit.com/support/useful-tools/generating-an-msinfo32-file

my-info.zip.json (231.8 KB)

Note: the attached files is a zip file. rename and remove the .json extension. the website does not allow uploads other than picture files.

Alright, we’ve received and are able to view the .nfo file. Check if you have any pending updates for your Intel and AMD graphics drivers, then restart the computer:

Already did updates. I tried to support myself by search the web and your forums.

This is an Intel NUC Haydes Canyon so it’s an atypical PC.

is there any way to bypass the hardware analysis?

May we ask if your DirectX 11 API is currently installed to your PC? Try using a USB connection to this link: https://www.xsplit.com/support/connect-webcam/troubleshooting/xsplit-connect-usb .

I also have a Hades Canyon and have similar problems with crash on calibration hardware tests. I think VCam has some trouble with the AMD GPU or its drivers, but does sort of work with the Intel on-board GPU. So it seems to work best if you use the Windows Graphics settings for VCam to set to use the power savings option (Intel graphics) when doing the test, and then switch to the High Performance (AMD RX Vega GPU) once the tests are done

holy cow! that worked!

took me awhile to figure out how to force an app to use the intel graphics…but i i found it (search for ‘graphics settings’ in Win10).

Thanks!