Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/69492970-fd84-8012-81ad-fad51507b9fe
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==== ### ==== Windows “Fast Startup” basically half-hibernates the system, and Thunderbolt devices hate that. Fix: # Control Panel → Power Options # “Choose what the power buttons do” # Click Change settings that are currently unavailable # Disable “Turn on fast startup” # Full shutdown → cold boot (not restart) A restart is often worse than a full shutdown for eGPUs. ===== On reboot, the TB controller sometimes doesn’t re-enumerate the eGPU. ===== Things to try: * Boot with the eGPU already connected and powered on * If that fails, try: - Boot without eGPU → log into Windows → then plug it in * Check Thunderbolt Control Center: - Make sure the eGPU is listed and marked as “Always Connect” or Authorized ===== The Legion Go’s Z1 Extreme iGPU + AMD desktop GPU is a known pain point. ===== Symptoms match what you’re seeing: works once, reboot breaks it. Try this: # Use DDU (Display Driver Uninstaller) in Safe Mode # Install ONE unified AMD driver, not separate iGPU/eGPU drivers - Usually the Adrenalin WHQL, not beta # After install: - Plug in eGPU - Let Windows finish detecting before rebooting If Windows Update sneaks in a driver afterward, it can silently break this again. ===== Windows loves to overwrite AMD drivers after reboot. ===== Check: * Device Manager → Display Adapters - If you see Microsoft Basic Display Adapter or a mismatched driver version, that’s your smoking gun. You may need to: * Disable automatic driver updates (at least temporarily) ===== This happens with some enclosures + TB4. ===== Quick test: * After reboot (when it “doesn’t work”): - Is the GPU still visible in Device Manager? - Yes, but error code (like Code 43)? → driver issue - No at all? → Thunderbolt enumeration / firmware issue
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)