Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsMost Steam Deck launch “crashes” in STAR WARS: Galactic Racer are recoverable states rather than a permanently frozen game. On the first boot, shader compilation can leave a gray or white window for several minutes. If the EOS overlay appears stuck, press B once and wait. For repeatable stutter, turn DLSS Resolution Scaling off (especially with DLAA enabled), then test a conservative 30 FPS, 1280×800, TSR profile with Frame Generation and Ray Reconstruction disabled. If performance collapses only after several races, restart the game—and Steam or the Deck if necessary—while recording when and where the slowdown starts.
Fastest recovery path
Work through these checks in order. Each step targets a documented failure mode and prevents you from changing several variables at once.
As an Amazon Associate I earn from qualifying purchases.
- Install pending updates. Update SteamOS, STAR WARS: Galactic Racer, and the Proton components offered by Steam. Driver changes have allowed at least one Linux user to get past the launch hang, but no single Proton build is guaranteed to fix every Deck.
- Give the first launch time. A gray or white fullscreen window can be shader compilation. Leave it open for several minutes instead of force-closing it. An unofficial 2026 Deck guide describes roughly two to three minutes on the first boot; that is a starting estimate, not a benchmark or guarantee.
- Dismiss the apparent EOS hang. When the Epic Online Services (EOS) overlay does not display, press B once, wait briefly, and return to the game.
- Disable the stutter trigger. Set Resolution Scaling to Off. If DLAA is enabled, turn it off while testing. Keep Frame Generation and Ray Reconstruction off until the base game is stable.
- Use a known conservative profile. Start at 1280×800, TSR, a 30 FPS target, Frame Generation Off, and Resolution Scaling Off. This is unofficial guidance, not a Valve-certified preset.
- Test both a race and a hub. Smooth racing with hitching while walking around a hub points to a location-specific frame-pacing problem rather than a Deck-wide performance failure.
- For a delayed FPS collapse, restart and log it. Close the game; if the slowdown remains, close Steam and restart the Deck. Record elapsed play time, the area where it happened, graphics settings, and whether DLSS was enabled.
What each symptom means
| Symptom | Most likely explanation supported by current reports | First action |
|---|---|---|
| Gray or white screen on first launch | Hidden splash window and shader compilation can trigger an “Application hung” message even while work continues. | Wait several minutes before closing the game. |
| Game appears stuck when an EOS prompt should be visible | The EOS overlay does not display on Steam Deck. | Press B once, then wait briefly. |
| Stutter starts as soon as graphics load | Developer support identified DLSS Resolution Scaling with DLAA as an immediate stutter trigger. | Turn Resolution Scaling Off and retest. |
| Races are smooth but hubs or on-foot movement hitch | Players describe a frame-pacing issue that is more visible outside races. | Compare one race with a hub walk and report the difference. |
| FPS tanks after three or four races, or after about 25 minutes | A community-reported long-session degradation; the cause has not been confirmed as a memory leak or anything else. | Restart, then capture timing and settings before contacting support. |
These categories can overlap. For example, a first-launch shader wait and an EOS overlay failure can look like the same frozen screen, while a hub-only hitch can occur even when racing performance is normal.
Update SteamOS, the game, and Proton first
Software versions matter in this case. A Valve Proton issue documents a Linux launch hang that changed behavior after a commenter moved to newer NVIDIA drivers. That observation does not establish a universal Steam Deck fix, but it is enough reason to remove pending updates before deeper testing.
#1 Best Overall
- 1TB NVMe SSD
- 1280 x 800 HDR OLED display with premium anti-glare etched glass, 7.4" Diagonal display size up to 90Hz refresh rate
- Wi-Fi 6E
- 50Whr battery; 3-12 hours of gameplay (content-dependent)
- Carrying case with removable liner
- Press the Steam button and open Settings → System.
- Install any available SteamOS update and allow the Deck to restart if requested.
- In your Library, open the game’s Properties → Updates page and let any game update finish.
- Check that Steam has finished downloading compatibility-tool updates before launching again. Do not assume that forcing one particular Proton version will solve every Deck; keep the version decision reproducible and note it in your troubleshooting log.
After updating, launch once without changing several graphics options. That clean run tells you whether the original problem was version-related or still present on the current software.
Fix a gray or white first-launch screen
Why it can look like a crash
Valve’s Proton issue tracker records a gray fullscreen window, a hidden splash window compiling shaders, and an eventual “Application hung” error. In that state, the visible window may not repaint even though shader work is still occurring. The unofficial Deck guide’s two-to-three-minute estimate is useful for setting expectations, but storage speed, installed shader cache, and the current software stack can change the wait.
What to do
- Start the game while the Deck is connected to power if practical, and avoid switching applications during the first boot.
- If the window is gray or white and there is other evidence that shaders are compiling, leave it open for several minutes.
- Do not repeatedly force-close it during this phase. A forced exit removes the opportunity to distinguish a slow first compile from a genuine crash.
- If the game eventually reaches its menu, quit normally and launch again. Later launches can behave differently once shader data is cached, so compare the first and second starts rather than judging the game from one boot.
If there is no progress after a reasonable wait, or the same hang occurs on every subsequent launch, continue with the EOS check and update steps instead of assuming it is still compiling.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallClear the Steam Deck EOS overlay hang
The developer’s October 6, 2026 known-issues notice gives a specific Deck instruction: “The EOS overlay will not display on Steam Deck, making the game appear to hang. Press ‘B’ to cancel and return to the game.”
- When the game appears to stop at the point where an EOS overlay should appear, press B once.
- Wait briefly for control to return to the game. Do not mash buttons or immediately terminate the process.
- If the game resumes, continue playing and note that the overlay—not the rendering engine—caused the apparent hang.
- If B has no effect after waiting, treat the event as an unresolved launch or freeze issue and record the exact screen, time, and preceding action for support.
This workaround is specific to the documented overlay behavior. It is separate from the shader-compilation wait: a gray first boot may need time, while an EOS prompt that cannot draw needs the B input.
Stop stutter caused by DLSS Resolution Scaling and DLAA
The confirmed setting interaction
Developer support states: “The stuttering begins immediately when DLSS Resolution Scaling with DLAA is enabled.” The same response says, “Disabling Resolution Scaling immediately removes the stuttering,” and asks players to keep Resolution Scaling Off as a temporary workaround.
That makes Resolution Scaling the first graphics variable to remove, even if your average FPS looks acceptable. A game can show a reasonable FPS number while producing uneven frame times; the uneven delivery is what your eyes perceive as hitching.
Isolation procedure
- Open the game’s graphics settings and set Resolution Scaling → Off.
- If the anti-aliasing option is set to DLAA, change it while testing so that DLSS and DLAA are not part of the active path.
- Turn Frame Generation and Ray Reconstruction off for this test. The support investigation found that changing those options did not alter the reported result, but leaving them off removes extra variables.
- Apply the settings, return to the same area where stutter was visible, and repeat the movement or race that exposed it.
- Only after the base configuration is stable should you test one optional feature at a time. If stutter returns immediately when Resolution Scaling is re-enabled, leave it off and report the result.
| Test state | Resolution Scaling | DLAA | Frame Generation | Ray Reconstruction | Use |
|---|---|---|---|---|---|
| Stability baseline | Off | Off while isolating | Off | Off | Determine whether the documented trigger is responsible. |
| Problem reproduction | On | On | Off | Off | Use only long enough to verify that stutter returns under the triggering combination. |
| Unresolved case | Record the value | Record the value | Record the value | Record the value | Give support an exact configuration rather than “default settings.” |
Use a conservative Steam Deck graphics profile
There is no authoritative Steam Deck average-FPS benchmark for this game. The practical target below comes from an unofficial 2026 Deck guide, so treat it as a starting point for consistent frame pacing rather than a promise that every scene will hold the number.
| Option | Starting value | Reason |
|---|---|---|
| Output resolution | 1280×800 | Matches the Deck’s native panel and avoids testing an external resolution at the same time. |
| Frame-rate target | 30 FPS | A conservative target intended to prioritize consistency over a higher but unstable ceiling. |
| Upscaling method | TSR | The unofficial guide’s baseline; use it to avoid the documented DLSS Resolution Scaling trigger. |
| Resolution Scaling | Off | Developer-recommended temporary workaround for immediate stutter. |
| DLAA | Off while diagnosing | Removes the DLAA side of the reported DLSS interaction. |
| Frame Generation | Off | Reduces variables while establishing base frame pacing. |
| Ray Reconstruction | Off | Keep disabled during isolation; support found no change in the reported stutter result when testing it. |
Once this profile behaves consistently, change one option at a time and repeat the same race and hub route. If image quality improves but hitching returns, stability and image quality are the trade-off; there is no single universal FPS setting supported by a canonical Deck benchmark.
Rank #4
- 【Upgraded】We sells product with professionally upgraded to 2TB SSD. Original Seal is opened for upgrade ONLY.
- 【Stunning 7.4" HDR OLED & 90Hz Motion】 Experience striking contrast and brilliant clarity with the all-new 7.4-inch HDR OLED display. Designed from the ground up for gaming, it features a 90Hz refresh rate for smooth motion and pure blacks. This handheld is capable of delivering an immersive visual experience, ensuring your Steam library looks better than ever with vibrant colors and amazing motion rendition.
- 【30-50% More Battery & Efficient Performance】 Play your favorites longer with up to 50% more battery life. By fitting a larger battery and a power-efficient OLED panel, this device provides extended gameplay sessions. It’s the perfect travel companion for long flights or commutes. The updated AMD APU ensures high-speed performance for AAA titles while maintaining incredible energy efficiency.
- 【3X Faster Downloads with Wi-Fi 6E】 Never wait for a game again. Equipped with Wi-Fi 6E, this Steam Deck OLED offers increased bandwidth and lower latency, delivering downloads up to 3 times faster than previous models. This ensures stable online play and rapid updates, making it the most reliable wireless gaming handheld for modern high-speed home networks.
- 【Responsive Touch & Enhanced Connectivity】 Enjoy a vastly improved touchscreen with higher fidelity and faster haptics. We’ve added a dedicated Bluetooth antenna to improve connections for multiple controllers. Whether using the built-in trackpads or the included external controller, this allows for precision play in everything from FPS to complex strategy games.
Diagnose race performance separately from hub performance
Several players describe smooth racing alongside stutter or hitching in hubs and on-foot sections. That pattern is important because it points to frame pacing tied to a game area, streaming workload, or scene transition—not automatically to a failing Deck.
A repeatable two-part test
- With the baseline profile applied, run one complete race. Note whether steering, camera movement, and the finish sequence remain smooth.
- Return to a hub and walk the same route for several minutes. Watch for short pauses, uneven camera motion, or delayed input even if the FPS counter does not fall dramatically.
- Repeat the pair after changing only one graphics option. Keep the route and approximate duration similar.
- Log the result as “race smooth/hub hitching,” “both hitch,” or “neither.” That wording is more useful to support than a single average FPS number.
If both races and hubs hitch immediately, start with the Resolution Scaling test and software updates. If only hubs hitch, preserve that distinction when submitting a report; it is a meaningful symptom rather than evidence that every part of the game runs poorly.
Free tools Windows power users keep installed
One-click scans. No signup required.
Recover from FPS collapse after several races
What is known
A Steam discussion describes FPS dropping sharply after three or four races. Another player says the game becomes unplayable after about 25 minutes. Closing the game—and, in some cases, Steam—or restarting temporarily restores performance. These are community observations, not a confirmed diagnosis. The available reports do not establish a memory leak, overheating fault, or a specific hardware cause.
Best Value
- Carrying case included
Recovery steps
- When the slowdown appears, finish collecting a quick note: elapsed play time, number of races, current location, output resolution, upscaling and DLSS values, and whether the problem is limited to a hub.
- Exit the game normally if controls still respond.
- Launch it again and repeat the same activity. A temporary recovery after relaunch supports the long-session symptom but does not identify its cause.
- If performance remains degraded, close Steam and restart the Deck. Do not present the restart as a permanent fix; it is a way to restore playability while gathering evidence.
- Compare a fresh session with a session that crosses the reported 25-minute or three-to-four-race point. Record the exact time at which frame pacing changes.
Avoid declaring a memory leak from one occurrence. Reproduction across sessions, with timestamps and unchanged settings, gives the developer something actionable.
A complete troubleshooting workflow
Use this order when you want one controlled pass rather than isolated fixes.
- Prepare: connect power if possible, close unrelated applications, and write down the current game and Proton versions.
- Update: install SteamOS, game, and compatibility-tool updates, then reboot if Steam requests it.
- Launch once: allow the first shader compilation to run for several minutes if the screen is gray or white.
- Handle EOS: press B once if the overlay appears to be the point of the hang.
- Set the baseline: 1280×800, TSR, 30 FPS target, Resolution Scaling Off, DLAA Off while testing, Frame Generation Off, and Ray Reconstruction Off.
- Run the location test: complete one race and walk through a hub, recording frame pacing separately.
- Run the duration test: continue for at least the point at which you previously saw degradation, noting elapsed time and race count.
- Change one variable: if stable, re-enable or alter only one option and repeat the same route. If unstable, return to the baseline before testing anything else.
What to include in a support report
The developer’s known-issues notice directs players to its Customer Support Centre and asks them to submit a bug report when their symptom is not listed. A concise report should let someone reproduce the exact state.
- Steam Deck model and SteamOS version.
- Game version and Proton or compatibility-tool version.
- Whether the issue happened on first launch, after shader caching, or in later launches.
- For a launch hang: gray or white screen, approximate wait time, whether an “Application hung” message appeared, and whether pressing B changed anything.
- For stutter: Resolution Scaling, DLAA, TSR or other upscaling choice, Frame Generation, Ray Reconstruction, output resolution, and frame-rate target.
- Whether racing, hubs, on-foot movement, or all locations are affected.
- For degradation: time from launch, number of races, whether closing the game or Steam restored performance, and whether a full Deck restart was required.
Attach a short video or timestamped performance-overlay capture only if it shows the symptom clearly. The key is to describe the transition—what was smooth, what changed, and after how long—rather than reporting only “low FPS.”
Dead ends to avoid
- Do not force-close every first launch. You may be interrupting shader compilation and losing the clearest evidence of what happened.
- Do not treat one FPS number as a diagnosis. A hub-only hitch and a whole-session collapse require different notes and may have different causes.
- Do not re-enable several advanced features at once. You will not know which change brought the stutter back.
- Do not assume an accessory is required. The documented faults do not establish that a dock, display, storage upgrade, cooler, power device, or input accessory fixes them.
- Do not label the long-session issue a confirmed memory leak. Restart-based recovery is a temporary workaround reported by players, not proof of the underlying mechanism.
When the Deck is probably not the root cause
If the game launches after the shader wait, resumes after B dismisses the EOS state, and races remain smooth while only hubs hitch, the evidence points toward game-side overlay, streaming, or frame-pacing behavior rather than a general hardware failure. Conversely, immediate stutter in every area with Resolution Scaling and DLAA enabled is consistent with the developer’s documented trigger. A slowdown that appears only after a repeatable duration should be reported as a long-session regression, especially when a relaunch temporarily restores performance.
Until a later update changes these behaviors, the most dependable approach is a clean software stack, patience on the first shader compile, Resolution Scaling Off, a conservative 30 FPS/TSR baseline, separate race-and-hub testing, and detailed logs for any delayed degradation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
