Discuss problems with the laptop and Razer Core X.
Discuss problems with the laptop and Razer Core X.
I have secured the ASUS TUF Dash, Intel i7-12650H, with 64GB RAM and an RTX 3070 Razer Core X (non RGB). This setup arrived this week after a long wait. I installed the GPU into the Razer Core X, making sure it was properly seated and all power connectors were secure. Since my laptop features Thunderbolt 4, that wasn’t an issue. After connecting everything and powering on the device, the Razer Core detected the connection and initiated fans and lighting. It began charging my computer, displaying "Core X" under USB devices in Device Manager, yet the GPU itself wasn’t visible in display adapters as expected. I plan to add photos or relevant videos to this post. I’ve been working on troubleshooting, but since this is my first experience with Windows 11, I suspect the problem lies there. I don’t have any other Thunderbolt-compatible devices at home for testing, as my iPad doesn’t handle it well. I’ve verified my drivers are current—GPU and drivers are up to date—and attempted to install the Thunderbolt drivers from Intel’s site. The installation failed with a fatal error (0x80070643), which appears to be corruption-related. This occurred during the MSI package setup. I’ll share the log file if I can reproduce or recreate the issue. One aspect that stands out is how the system behaves differently with other devices: when I connect a non-Thunderbolt device, the setup struggles significantly. Even with a Thunderbolt cable, my third monitor hasn’t connected yet. My patience is wearing thin, and I’m unsure what steps to take next. The original laptop wouldn’t support a second monitor either, which adds to the frustration. I’ve tried using Thunderbolt 3 cables and switched HDMI outputs, followed the troubleshooting steps on Razer’s site, and checked various forums, but nothing resolved it. The Thunderbolt log file is attached if needed.
After discussing with Amazon, it appears from their documentation that similar data from the log file suggests the .NET framework may be damaged. Both Amazon and I believe this could stem from a driver problem or a partial corruption of the .NET component. If anyone has further insights based on what we've discussed, please share—I'm keen to hear.
I sent back the device because it appears the Core X had damaged drivers and couldn't be repaired. Since the product was sold on Amazon and the warranty had expired, Razer didn't want to assist.