Video summary

Running Windows on the Playstation 5's APU!

Main summary

Key takeaways

Technology

Summary (Windows on the PS5 APU / AMD BC250)

The video explores whether the hardware inside a PlayStation 5 (an AMD BC250 “PS5 APU” on a dedicated board) can run Windows 11 and what kind of gaming performance is possible. The creator ultimately shows that Windows can boot and some games can get partial graphical acceleration, but the results are largely poor and require major “hacks.”

System setup & boot process (how Windows was installed)

  • The BC250 is originally run on Linux; Linux is more reliable for basic driver support.
  • To attempt Windows:
    • The creator uses Windows 11 IoT Enterprise (a minimal Windows build: OS + web browser).
    • Direct installation attempts were problematic (bootloader/UEFI & USB install issues), leading to a janky approach:
      • Preload Windows onto an SSD/drive via another PC using UEFI/boot considerations (avoiding grub/UEFI conflicts).
  • Key hardware uncertainties for Windows:
    • How Windows handles GDDR6 on this APU/board.
    • Whether Windows can deal with required GPU/iGPU drivers.

Initial Windows results (iGPU / onboard graphics problem)

  • Windows successfully boots to desktop and detects general hardware like the BC250 and ~16GB RAM.
  • However, Windows initially lacks:
    • Graphics drivers (and related PCI/iGPU components).
    • Resolution is restricted to 800×600 @ 64Hz, indicating the system isn’t getting proper iGPU acceleration.
  • Attempted fix: install AMD Navi / mobile Navi drivers to enable the built-in graphics.
    • The creator repeatedly hits Code 43 (“graphics driver not available” / device not supported).
    • Briefly, one driver attempt gives “split-second” graphical acceleration, then fails again with Code 43.

Conclusion from phase 1: iGPU acceleration on Windows is effectively blocked because proper AMD drivers aren’t available/aren’t compatible.

Phase 2 workaround: hijack PCIe lanes from the M.2 slot to run an external GPU

Since iGPU enablement fails, the creator tries a different strategy:

  • They use an M.2-to-PCIe x16 adapter (including its own power) to attach a discrete GPU.
  • An RX 460 is installed as the external graphics card.
  • The goal is to use the external GPU for rendering while still outputting video through the APU’s onboard video connection.

Results:

  • Windows detects the RX 460 and shows signs of partial GPU use.
  • It still proves difficult to route display output properly:
    • Attempts to use the RX 460’s ports directly didn’t reliably produce usable display.
    • The onboard display output works but remains capped at 800×600 @ 64Hz.
  • A major “proof of concept” is achieved:
    • 3D utilization works and the RX 460 warms up.
    • Some games render, though performance is very limited.

Performance testing & benchmark findings (mostly 800×600 limitation)

Because the system can’t change resolution above 800×600, all benchmarks are constrained to that mode.

GTA V (Enhanced Edition)

  • ~14 FPS average (1% lows ~13 FPS).
  • Despite RX 460 utilization appearing high at times, frame rate impact is limited:
    • Overlay showed “100%” but real utilization seemed much lower (often ~25%, sometimes 15%).

GTA Online

  • Ran similarly to single-player; also not playable at practical speeds.

Counter-Strike 2 / Source 2

  • CS2 does not scale well to this setup:
    • Performance doesn’t improve meaningfully; not the same success story as older Source engines.

Black Mesa

  • Best “works surprisingly well” result:
    • ~79 FPS average, 1% lows ~65 FPS on ultra (still at 800×600).
  • Indicates the setup can accelerate properly when the title cooperates with how rendering is handled.

“Battlefield-like” / Banished benchmark (actually “Bannalord” in subtitles)

  • The benchmark reports GPU activity (~60–80 FPS), but CPU is reported as limiting.
  • Creator investigates CPU parking—CPU threads were actually busy, suggesting a measurement/engine integration oddity rather than true CPU limitation.

Tomb Raider

  • ~14 FPS locked, similar to GTA behavior (GPU warms up but frame rate doesn’t rise).

Fable: The Lost Chapters

  • Menu works but mouse control fails to enter the game, effectively unusable.

Fallout 4

  • One of the clear standouts:
    • ~45 FPS average, 1% lows ~32 FPS (800×600), ultra settings.
  • RX 460 hit ~100% utilization.
  • Video claims it’s responsive and works despite the system’s limitations.

Cyberpunk 2077

  • Does not work well on Windows with this GPU setup.
  • Built-in FSR/frame generation options don’t help.
  • External “Lossless Scaling” didn’t improve and caused ghosting.

“BNG” (likely “Breach/NG”?—subtitles say “BNNG”)

  • Another success case:
    • ~46 FPS average, 1% lows ~33 FPS at high (800×600).

Overall conclusion / recommendation

  • Windows can boot, and some graphical acceleration is possible, but:
    • iGPU acceleration is blocked by driver compatibility (Code 43 / unsupported device behavior).
    • Achieving usable graphics requires a discrete RX 460 over a hijacked PCIe lane from the M.2 port.
    • Resolution is locked to 800×600 @ 64Hz, with extra quirks (including capture difficulty).
  • Gaming performance is generally worse than on Linux, even when an external GPU is used.
  • Some games work well (examples: Black Mesa, Fallout 4, “BNNG”), others are disappointing or unusable (GTA V, CS2, Cyberpunk, Fable menu/input issue).

Technological “key concepts” highlighted

  • Driver compatibility issues
    • AMD mobile Navi iGPU drivers not usable in this configuration → Code 43
  • Storage/boot complexity
    • UEFI/grub/Windows install conflicts requiring an offline preload approach (Windows image applied via other system)
  • Hardware bridging
    • M.2-to-PCIe adapter to “force” an external GPU on a board not meant for normal Windows GPU use
  • Rendering constraints
    • No control beyond 800×600 @ 64Hz
    • Windows multi-GPU handling is unreliable without native driver support

Main speakers / sources

  • Main speaker: The video creator/host (speaks directly throughout; not named in subtitles).
  • Other referenced sources: Online/driver/adapter “reviews” and Google searches (no specific channel names cited).

Original video