Razer Core X only properly connects on boot - sometimes | Razer Insider

Razer Core X only properly connects on boot - sometimes

  • 30 November 2022
  • 0 replies
  • 51 views

I bought a Razer Core X about 6 months ago, and then got an EVGA 3060 Ti FTW3 to go with it. I have a Dell XPS 9310 laptop running Windows 11. The XPS has completely up-to-date firmware. Although the Razer Core X is Thunderbolt 3, the XPS is Thunderbolt 4, fully certified, all PCIe lanes and all that jazz. It should work great.

The entire time I've had the Core X, it doesn't work properly if you just connect it to the laptop with the laptop already on.

  • It may go into a cycle of connecting and disconnecting - this shows up in the Windows Event Viewer and the Thunderbolt Control Center.
  • The GPU fan may kick in on high and never "connect" in the Thunderbolt Control Center. Windows Event Viewer will show a power source change.
  • Sometimes nothing happens.
  • Sometimes the Thunderbolt Control Center will show that the Core X is connected, but Windows doesn't seem to see the GPU.

I have had this experience with the included TB3 cable, and a certified TB4 cable I have. I also have tested and replicated the same behavior with a Dell Precision 5550 running Windows 10 with current firmware, although that is a TB3 device and I'm not sure if it has the same compatibility.

That said - if I get into the scenario where the Thunderbolt Control Center shows the Core X but Windows doesn't see the GPU - all I have to do is reboot, and the vast majority of the time, it works. It then works perfectly for the entire time both are on, and often through future reboots. There's never a hiccup, never a crash, blue screen, anything. I've honestly been surprised by how well it works when it does work.

For a while I just sort of accepted that maybe this is just how it works - but I just saw some YouTube videos of people having laptops, they plug the eGPU in, and it just works the first time, every time, no problem.

Is there anything I can do to correct this? Is it potentially a warranty issue I should be taking to Razer?

0 Replies

Be the first to reply!

Reply