Sound cuts out when opening games or apps in full screen: real causes and solutions

The sound cuts out right when opening a game or application in full screen. It's one of those problems that drives anyone crazy: the computer has more than enough power, the drivers seem to be up to date, everything sounds perfect on the desktop... but as soon as you put the game in full screen, the audio cuts out, goes silent for a few seconds or simply disappears until you close the game.

This mistake is not uncommon and is repeated in many different contextsNew PCs lovingly built for living room gaming, laptops connected via HDMI to a TV, users upgrading GPUs (for example, from an RTX 3070 to a 4090), people playing with soundbars, monitor speakers, AirPods via Bluetooth, or USB headphones. The pattern is the same: in windowed or background mode, the audio is fine, but when switching to full screen, the sound cuts out, crackles, goes silent, or only works through certain outputs. We bring you the solution right now. The sound cuts out when opening games or apps in full screen: the real cause.

What is the real cause when the sound cuts out in full screen?

Although from the outside it may seem like a "magical" or random failure, there are almost always several very specific technical causes. These factors combine when the game switches to full screen or changes resolution. Understanding them reveals why everything works in windowed mode and why certain "tricks," such as changing the refresh rate or audio format, temporarily restore sound.

The first thing to understand is that when you put a game in exclusive full-screen modeWindows no longer treats image and audio as on a normal desktop: the game takes more direct control of the GPU and sometimes forces changes in resolution, refresh rate, and even the audio path (especially when using HDMI or DisplayPort to a TV or monitor with built-in speakers).

These sudden changes in resolution or display mode This can cause Windows to "renegotiate" the HDMI audio device, as if the display were being plugged and unplugged, causing the system to:

• Change the default audio output without warning (for example, from HDMI to PC speakers).
• Re-detect the HDMI device with other compatible formats (different kHz or bits) and the game/Windows get "stuck" in a conflicting format.
• Lose the audio stream for 1-2 seconds Each time that renegotiation occurs, it's perceived as regular cuts every 10-20 seconds in some titles.

In cases where the audio cuts out on its own when using HDMI to connect to a television (with or without a soundbar, either via eARC or optical cable), and depending on the compatibility between televisionsThere's an added factor: the sound has to pass through several devices (PC → GPU → TV → soundbar), and each one imposes its own format compatibility (PCM stereo, Dolby, DTS, etc.). When the game changes resolution or activates HDR, some TVs perform a kind of "resynchronization" that can momentarily reset the audio.

There are also specific problems with audio and GPU drivers.: Nvidia, AMD or Realtek drivers that interfere with each other; added software such as Nahimic, "gaming" audio utilities or motherboard manufacturers that inject effects; and the browsers' own hardware acceleration, which can cause slowdowns and choppy audio when playing streaming video when the GPU is under heavy load with a game running.

Real-life cases that help to understand the problem

To see all the variations of the same failure, it is worth reviewing several real-world scenarios. that are repeated time and time again in Microsoft forums, PC communities, and technical support from various manufacturers.

A user buys a new game (like Star Wars Jedi: Survivor) on the EA appI've updated Windows, GPU drivers, and audio drivers, but the game sound still cuts out for about a second every 10-20 seconds. The most striking behavior: in windowed mode, the audio works perfectly, and if I minimize or send the game to the background (for example, from Task Manager), the sound playback is stable. The problem only occurs in full-screen mode.

This person manages to "fix" it one day by tinkering for hours with screen modesI leave it running, close the game, and the next day, without touching anything, the problem returns. The rest of the games work fine, and Jedi: Fallen Order ran perfectly on the same machine. I've already tried almost everything: verifying files, various audio formats (CD quality, 320 kbps, etc.), disabling enhancements, turning off Nahimic-type drivers, changing resolution and refresh rate, disabling HDR, etc.

When this happens, the pattern clearly points to how that particular title handles the exclusive full-screen mode.When changing resolution or display mode, the game causes micro-cuts in the HDMI signal or audio device, which only appear in full screen, while in windowed mode the game works "on top" of the Windows desktop, without affecting the audio/video chain in the same way.

In another case, a user with a new tower dedicated to the living room (Ryzen 7600, RTX 4070 Ti, B650M motherboard, 32 GB DDR5, NVMe SSD) suffers something more extreme: when playing in 4K, with everything maxed out, the HDMI audio completely disappearsThe Windows sound mixer clearly shows that there is a signal, but nothing comes out of the TV speakers or soundbar.

The sound only returns when the audio format is manually changed. in the Windows sound settings (for example, by changing from 16-bit 48kHz to another value). However, when returning to the game, the audio is lost again. Additionally, when playing YouTube or sports in the browser, the video sometimes slows down and the audio cuts out; this is much less frequent than in games, but clearly related.

The curious thing is that with USB headphones there is no dropout.This indicates that the problem lies with the GPU's HDMI device and the audio path to the TV/soundbar. Virtually every sensible troubleshooting step has been tried on this system: disabling AMD and Realtek audio drivers, leaving only Nvidia, replacing HDMI cables with new, high-quality ones, using a new TV (LG OLED G3) instead of an older model, swapping the GPU, switching between eARC and optical output, using the TV's speakers directly… and even swapping the PC with another one in the same room without the problem appearing on the other machine.

Even after reinstalling Windows 11, the user discovered that old drivers were still appearing. (such as a previous Nvidia driver) and AMD and Realtek audio drivers, suggesting that the "Reset this PC" process did not perform a completely clean installation. This whole situation points to a combination of:

• "Poisoned" or poorly migrated HDMI audio drivers, with remnants of previous versions;
• erratic format negotiation between GPU, TV, and soundbar when 4K HDR and high refresh rate modes are forced;
• full-screen graphics mode changes for games that force internal restarts of the HDMI device.

In a third scenario, the problem is limited to games in resolutions other than the native resolution of the monitor or television.There is no sound via HDMI when the game is in full screen at 1680 × 1050 (or any resolution lower than the native 1080p/4K), but there is sound using the analog outputs of the PC or the sound card, and it also works if the game is run in windowed mode, even at that same lower resolution.

This detail is key: when lowering the resolution and using full screen, the GPU usually changes the HDMI video mode.And some devices (especially TVs and AV receivers) treat this new signal as a "different input" or as a compatibility mode. During this transition, Windows may lose HDMI audio output, or the TV/receiver itself may stop accepting the audio stream because it doesn't properly recognize the format.

Another classic case: a laptop connected to a TV via HDMI running Windows 7, where everything sounds good (YouTube, Windows Media Player, and even certain emulators like MAME), but Games in full-screen mode leave the TV without audio.While in windowed mode there are no problems. Again, it's clear that the cause isn't "HDMI not working," but rather the screen mode change that the game only makes in full screen.

There are situations where the sound completely dies as soon as any game is openedEverything works fine on the desktop, but when launching games like World of Warcraft, Nioh 2, or the Yakuza series, all Windows audio disappears. Neither the system nor other apps produce sound. The only way to recover is by unplugging and replugging the audio device; if the game remains open, the problem reappears after a few seconds or minutes.

This type of extreme failure usually indicates a deep driver conflict.: a bug in the sound driver, a rare interaction between the GPU and audio drivers, or even poor management of virtual audio devices (e.g., surround sound drivers, 7.1 headphone software, etc.) that are activated when a full-screen program is detected.

Another striking example is the "high-pitched squeal" from the monitor speakers. When opening a demanding game like Baldur's Gate 3 or Path of Exile 2 in full screen, especially after upgrading from a GPU like the 3070 to a 4090, changing the HDMI cable doesn't help, and disabling the monitor's speakers in Windows doesn't seem to solve the problem either, because the monitor's own system still has the speaker active internally.

In such cases, that beep usually indicates interference or digital noise. This can be caused by the new graphics card, grounding issues, or even incompatibilities between the audio formats the GPU tries to send and those supported by the monitor. If other dedicated speakers are also connected, ground loops or level differences may occur, only becoming apparent under full GPU load.

Finally, there's the case of AirPods or other Bluetooth headphones. connected via a USB adapter: in the Windows sound panel there are two device modes, one of the “stereo” type with good quality, and another labeled as “hands-free” (HFP/HSP, often with the suffix “audio hands-free AG”).

Stereo mode sounds fine on the desktop, but when entering games like Valorant the audio cuts out completely.However, if you select hands-free mode (which is lower quality, noisier, and mono), the game does emit sound, albeit at a noticeably lower quality. This is because hands-free mode uses a Bluetooth profile designed for calls (with a microphone), while stereo mode uses a different profile (A2DP) that some games, drivers, or Windows configurations don't handle well when switching to full screen.

Why does the audio work in windowed mode but not in full screen?

The key to almost all of these problems lies in the difference between three display modes that games can use on Windows: exclusive full screen, borderless window, and normal window.

When a title uses exclusive full screenIt usually has more direct access to the GPU and can:

• Force non-native resolutions of the screen (for example, 1680 × 1050 on a 4K TV).
• Modify the refresh rate (from 60 Hz to 120/144 Hz, for example).
• Activate special modes such as HDR, VRR, G-Sync/Freesync which force you to renegotiate the signal with the television or monitor.

Every time a new combination of resolution, refresh rate, HDR, and so on is negotiatedThe HDMI output may "reset" for a moment; for the operating system and the TV, it's almost as if the cable were disconnected for a second. This, in turn, can:

• Reorder the list of audio devices (Suddenly, HDMI appears as a new device).
• Force Windows to change the default output to a different one.
• Restart the audio streamcausing the famous periodic power outages.

In borderless or normal window mode, the game runs "on top" of the Windows desktop.which is already locked into a specific resolution and mode. There aren't those aggressive mode changes, so the HDMI chain remains stable and the audio device doesn't restart every few seconds. That's why so many users report: "It works perfectly in windowed mode, but in full screen it's a nightmare."

This same principle applies to Bluetooth audio problems.Certain game engines or sound APIs perform a different initialization when they detect exclusive fullscreen, and that's where A2DP stereo profiles get stuck, forcing the system to switch to hands-free mode or, directly, to lose the audio device until the game closes.

Relationship between drivers, hardware, and audio formats

Beyond the change in graphics mode, many of the cases described are explained by poor driver compatibility. (Nvidia/AMD/Realtek, surround sound software, manufacturer equalizers) and by audio formats configured in a way that is not very compatible with the device chain.

On devices with HDMI audio output to TV and soundbarThe GPU exposes an audio device that often supports multiple formats: different levels of PCM, 5.1/7.1 compressed audio, Dolby Atmos, etc. If a format is selected in Windows that the TV or soundbar doesn't handle well, issues such as the following may occur:

• Absolute silence when changing to a certain resolution or full screen mode.
• Intermittent outages when the television “decides” to renegotiate or force another mode.
• Beeps, chirps, or digital noise when the signal is not interpreted correctly.

Generic drivers from Microsoft, Realtek, and GPU manufacturers (which include their own HDMI audio drivers) can overlap. Uninstalling some without cleaning up any leftover files, reinstalling Windows without a complete format, or leaving utilities like Nahimic, Sonic Studio, or other audio optimizers running often leads to strange conflicts, especially when launching a game that also tries to apply its own surround effects or settings.

In the case of browsers like Edge or ChromeHardware graphics acceleration can leverage the GPU to decode video; if at the same time a full-screen game aggressively uses the graphics, there have been cases where the browser enters a "slow motion" state, the video audio becomes desynchronized or disappears, and is only recovered by closing the browser or disabling that hardware acceleration.

Bluetooth audio adds to the confusion of profiles and codecsThe same device (for example, AirPods connected via Bluetooth dongle) appears as two or more different outputs in Windows, each with different capabilities. Some games only detect or use certain types of devices, and when they enter full screen, they force the system to switch to the hands-free profile, which prioritizes the microphone over audio quality, resulting in a significant drop in the sound experience.

Good practices and solutions that usually work

Although there is no single "silver bullet" that works for all possible combinations Regarding hardware, television, soundbar, Bluetooth, drivers, etc., there are a number of practices that, when combined, solve most sound problems when opening games or apps in full screen.

1. Try first in a borderless window
Whenever the game allows it, it's interesting to use borderless window mode instead of exclusive full screen. This mode looks virtually the same (it occupies the entire screen), but Windows treats it like a window: there are no such aggressive resolution changes or constant HDMI renegotiations.

2. Set native resolution and refresh rate in Windows and in the game
It is advisable that desktop and gaming use exactly the same resolution and frequency that the screen (for example, 3840 × 2160 at 60 Hz on a 4K TV, or 2560 × 1440 at 144 Hz on a gaming monitor). Avoid unusual or lower resolutions in full-screen mode that might cause the TV to treat them as an "old mode" without audio.

3. Simplify the HDMI audio path
If you use a PC → TV → soundbar setup, it's worth it. Try PC only → TV first and temporarily use the TV speakers. If the audio is stable in full screen, the problem is probably in the communication between the TV and the soundbar (eARC, ARC, optical). In that case:

• Force PCM stereo in Windows instead of strange surround formats;
• disable surround effects or advanced formats on the soundbar while it is being tested;
• Check if a newer firmware for the soundbar or TV improves compatibility.

4. Clean and unify audio drivers
When a driver conflict is suspected, a very effective solution is completely remove all third-party audio drivers (Realtek, AMD HDMI Audio, Nahimic-type software, etc.) and reinstall only what is essential:

• GPU driver (including its HDMI audio) from the official Nvidia/AMD/Intel website.
• Sound card or audio chipset driver for the motherboard, also from the manufacturer's website.

In extreme cases, it may be necessary to format and install Windows "from scratch". using a clean ISO, instead of the "Reset this PC" option which sometimes retains remnants of old drivers.

5. Choose conservative and compatible audio formats
In the playback device properties (Windows Sound panel), it's usually best Use 16-bit, 48 kHz, stereo PCM As a starting point, disable exotic formats and sound enhancements. Once the audio is stable in full screen, you can move on to more advanced settings.

6. For Bluetooth, select the "stereo" device and turn off hands-free if not needed
With AirPods-type headphones, the ideal is Always use the device labeled as stereo/A2DPThe hands-free profile (HFP/HSP) should be avoided, or even disabled if the Bluetooth adapter allows it. If the game insists on switching to the hands-free device, the following may help:

• Go into the game's voice settings and disable voice chat/microphone;
• In Windows, uncheck the hands-free device as the default input and output.

7. Temporarily disable hardware graphics acceleration in the browser
If videos play in the browser while gaming and experience buffering or slow motion, you can access the following in Edge or Chrome: Settings → System and performance and disable the option to use hardware graphics acceleration. After restarting the browser, many of these mixed (gaming + streaming) errors disappear.

8. Check that there are not multiple graphics adapters active at the same time
On laptops or computers with a more dedicated integrated graphics card, it's a good idea to go into the Device Manager (WIN + X → Device Manager) Check if there are two active graphics cards that might be interfering with how the HDMI output is handled. Disabling the integrated graphics card for testing purposes can help pinpoint the source of the problem.

9. Check the basics (even though it seems obvious)
Although sometimes overlooked, it is essential to check:

• Ensure the correct audio device is selected as the default (for example, the GPU's HDMI output and not the laptop's speakers).
• Make sure there are no other audio accessories connected and forgotten. (Bluetooth headphones, USB speakers) that are “stealing” the output.
• Make sure the volume is not muted on the mixer. for the executable of the specific game.

These measures include updating all graphics and sound drivers from the manufacturers' official websites.Most audio problems that occur when using games or apps in full screen eventually disappear.

There's no witchcraft behind a sound that cuts out when you put a game in full screen.Three very human things usually come together —long chains of devices (PC, TV, soundbar), drivers installed and reinstalled for years, and games that abruptly change resolution or graphics mode— and by disassembling these pieces one by one (simplifying the audio path, setting compatible formats, cleaning up leftover drivers and avoiding overly aggressive full-screen modes), the normal thing is to recover stable audio and forget about the problem for a long time.