Entry № 041-3 / V-3932 · 0:00 synced

IMPOSSIBLE Doom Vulkan Glitch - Haunted Hardware Episode 1

Linus Tech Tips@LinusTechTips939.4K viewsSep 20, 201611:54
Source
YT
Views
939.4K
Subscribers
16.8M
Critic
?
Audience
?

0 up · 0 down · 0 ratings

Channels and socials

Have you ever had a hardware bug SO WEIRD that it feels as though your PC is... haunted??? Freshbooks link: For your unrestricted 30 day free trial, just go to freshbooks.com and enter “Linus Tech Tips” in the "how did you hear about us" section. TunnelBear message: TunnelBear is the easy-to-use VPN app for mobile and desktop. Visit tunnelbear.com to try it free and save 10% when you sign up for unlimited TunnelBear data. Buy Doom for PC on Amazon: geni.us Discuss on the forum: linustechtips.com Affiliates, referral programs, & sponsors: linustechtips.com Join our community forum: bit.ly twitter.com @LinusTech Intro Screen Music Credit: Title: Laszlo - Supernova Video Link: youtube.com iTunes Download Link: itunes.apple.com Artist Link: soundcloud.com Outro Screen Music Credit: Approaching Nirvana - Sugar High youtube.com Sound effects provided by freesfx.co.uk

Start
AI OverviewDefault language

Episode 1 of Haunted Hardware investigates a perplexing gaming hardware glitch that seems to blur the line between software and hardware quirks. The host begins by framing the problem as a haunting-like issue that defies straightforward explanation, then walks through a series of diagnostic steps using Doom with different graphics APIs to observe how performance counters and overlays behave. The video then shifts into a structured troubleshooting workflow, starting with sanity checks in-game, verifying API mode, and comparing OpenGL versus Vulkan behavior on a test bench. When the Vulkan path produces unexpected results, the host considers driver and application updates, and eventually opts for a clean slate approach including a full driver reinstall and even a fresh OS format to isolate the issue. Throughout, the host emphasizes practical testing habits, such as checking frames per second counters, validating software revisions, and isolating variables like onboard graphics to determine what is actually driving the anomaly. The episode closes with reflections on the limits of diagnostic testing, the unexpectedly robust performance of some tools (like Fraps) in environments where they should not function, and an invitation to the audience to follow along with more Haunted Hardware episodes for further exploration of hardware oddities and debugging workflows.

Topics · hardware · technology · gaming · troubleshooting · software-diagnostics · computer-science · hardware-hardware

Questions answered

What is the main issue explored in Haunted Hardware Episode 1?
The video investigates a mysterious Doom Vulkan glitch where a performance counter and overlay behaviors behave inconsistently, suggesting a hardware or driver quirk rather than a straightforward software bug.
What troubleshooting steps does the host perform first?
The host starts with sanity checks in the game settings, verifies API mode (OpenGL vs Vulkan), checks driver and game build versions, and tests whether Fraps overlays affect the observed behavior.
Why does the video consider a fresh OS format and clean driver install?
To rule out system-level corruption or lingering software factors that could be causing the Vulkan/OpenGL glitch, aiming to isolate the issue to GPU hardware or Doom/Vulkan integration.