libretro / libretro/RetroArch

Blue Screen (BSOD) when using Steam overlay for Steam Controller and GloSOC

Open
#12,174 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

Both the current stable and nightly run fine when started outside of steam. But when starting Retroarch in fullscreen with GLoSOC ( https://github.com/Thracky/GloSC/releases/tag/2.0.8 ) to be able to use the Steam Controller (SC) as an xinput device as well as the Steam overlay to rebind controls, Retroarch blue screens (BSOD's) my PC.

I have tried turning off all overlays, including the GloSOC overlay (just runs as a way to present SC as xinput device) as well as AMD overlay and the Retroarch overlay and notifications.

Expected behavior

Retroarch in full screen should allow the Steam overlay so I can rebind controls on my Steam Controller. Steam Controller with GloSOC has always worked with all my other games and applications without any bluescreen problems.

Actual behavior

Retroarch is conflicting with something in the Steam Controller overlay in fullscreen. It also may be the way GloSOC is implemented that is causing a conflict.

Steps to reproduce the bug
  1. Set Retroarch to start in full screen.
  2. Create a GloSOC shortcut for Retroarch.
  3. Start Retroarch using the GloSOC shortcut.
  4. Bluyscreen (BSOD).
Bisect Results

I don't know if this bug is a new one as I have not tried older versions.

Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.9.0

Will add nightly version number later.

Environment information
  • OS: Windows 10
For developers/log.

I don't have my PC in front of me but will add a verbose log ASAP.

The Steam Controller overlay can be used with almost any Playstation, Xbox or generic controller so you don't have to own an actual Steam Controller to test.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reproduction steps in the issue and collect RetroArch's Information/System Information details, including the nightly version, plus the promised verbose log. Reproduce the BSOD with fullscreen RetroArch, GloSC, and the Steam Controller overlay; completion requires identifying the conflicting component and a verified fix or actionable diagnosis.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.