A2Razor

@Langlache I saw uncomfortably high hotspot temps too whenever I heavily loaded the laptop. Bordering on 105+c on the GPU, with the GPU core at 90c, and the CPU pegged at 95-97c. Never had the system reboot or power-off from this, yet it was constantly thermal throttling. My hotspot delta was in ~10-15c range. This is what triggered my ventures toying around with eGPU's, since the CPU temps or GPU temps on their own were fine. The cooler just seemed completely incapable of handling both concurrently -- and so I figured I'd just stop using the 6800M. Hadn't thought of this too much at the time, yet going back to der8auer's review of the Voyager, you'll notice the interesting temperature testing where he only runs Cinebench {only hits the CPU and does not touch the GPU, then concludes that the Voyager has great-cooling}. Whenever I'd called in and expressed concern over the temps, I too was just told that this was "normal" / working as intended. That the laptop was supposed to run at tjmax, and that this was by design. Wasn't happy with that answer, had no intention to use the machine that way, and ultimately gave up on it completely whenever I couldn't get the GPD G1 working for portability. I'll be curious to see how your replacement works out. I never bothered going the RMA route, since I even got some hands on with another person's Voyager, and it ran just as hot as mine. In my older posts, I mentioned that I tried re-pasting the laptop. I'd since then replaced all thermal pads and checked mounting pressure multiple times. Reinstalled the cooler so much that I eventually stripped a screw / had to replace one of the spring-screws in the vapor chamber.

Definitely- Browsers treating the inf as plain-text probably causing unnecessary confusion. Went ahead and changed the file classification so that they hopefully just throw up a download prompt.

Latest BIOS was installed before the first WHEA {on the 2080 Ti} was observed, and before trying the GPD G1. Never tested with versions prior to 1.38. I wound up moving to a different laptop {HP Fury G10} and benching the Voyager. Have had no issues since with drivers, crashing, thermals, or anything else. Hadn't checked back in over the holidays and was busy after / didn't get board notices apparently (apologies there). My contacts to support were entirely over the phone without a ticket opened to my understanding, or at least if a ticket was opened I wasn't provided any ticket / case number. These were done more in the format of calling in to ask if this was a known issue {it wasn't}, then asking for advice. I was told that it was probably my eGPU's and to check the cables and other computers if possible {the common stuff}, which I created this thread after to see if others had encountered similar / started testing. Details in this thread are pretty much everything I saw though. {nothing else to add} I'll re-test on Corsair's latest drivers when released, yet I doubt this will make a difference since I just tried Adrenaline 24.2.1 right-now for the sake of it. I suspect that this is more a problem on the chipset or BIOS side, since there are still WHEA's in the logs on NVidia cards in eGPU enclosures ... though the system and USB controller does not crash with an NVidia eGPU despite lots of warnings. The source / bus ID of the WHEA's comes from the eGPU itself and not the CPU integrated graphics or 6800M.

To keep this topic updated, I've had a chance to do some testing with various Thunderbolt docks on the GPD Win Max 2 and a Thinkbook with 6000 series AMD processors. Neither of these other systems exhibit the WHEA spam with said devices connected {completely error free}. I was also lucky enough to run into another person with a Corsair notebook during holiday travels ... which I can confirm generates the exact same errors as my own (e.g, it's not my machine specifically that's the problem here). This does seem to be specific to the Voyager, and a problem across all a1600 notebooks on the current FW / BIOS.

Make sure that you go through the hoops with support if you've not already... You'll likely wind up with the silent treatment like I have [dead end], yet nagging them is apparently the only way that we're ever going to get this addressed. I'd also like to echo that point that there are other monitors of similar specs in the game price class. All of those monitors (the alternate choices / the competition), have the ability to disable Deep Sleep, and DO NOT have the blank post display issue that the Xeneon does. I've infact already replaced my monitor and given up on ever using my Xeneon ... which just sits in a closet at this point. Reviewers may be giving Corsair a pass ... which I honestly do not understand at all. Yet it's a SEVERE problem to not see the display until an OS is loaded and drivers are loaded. Eventually every computer user will wind up in a situation that they either need to install an OS, access BIOS, or heaven forbid that something breaks / goes wrong. I literally was corrupting my install, because I was shutting off the machine in the middle of a check disk {requiring input that I could not see}. -- If you're still in the return window, I'd seriously consider it unless support gives you an in-writing confirmation that a fix will come. I'll do my part in bumping this yet again.

Forgot to add, yet important probably: -- The system will hard-crash or reboot EVEN IF there is no 3D Application using the G1, and even if the 7600M is disabled through the device manager. -- WHEA flood happens, just like with the other non-USB4 eGPU enclosures. -- I've tested using Corsair's drivers hybrid style (mixing drivers), and also the latest at the time of the post (23.11.1). I've also tried disabling the 6800M in the laptop, on the off-chance that this is something wonky with AMD's X-Connect and many devices. ASUS A16 w/ 7600S, not G16. Typo earlier. Both tried devices were Ryzen 7000 {7735HS and 7940HS).. This may be isolated to Ryzen 6000 and not the Voyager. Will try to rule that out...

To add to this thread, since I’m still trying to solve the thermal issues with my A1600 (unsuccessfully) and am still exploring options such as eGPU’s (to reduce heat-load)-- I picked up a GPD G1 as a portable external GPU. Expecting an “AMD Partnered and Developed” solution to have less issues {true USB4 support} on an AMD-Laptop, I was surprised to find that the G1 is completely-incompatible with the Voyager. -- The Voyager randomly will not start [blackscreen, keyboard lit], and will post loop (keep rebooting) if the G1 is connected during power up. The only way to end the loop is to unplug the G1. -- Under the device manager, the USB Connection Manager driver (UCM-UCSI ACPI Device) will keep vanishing and re-appearing from the device list. The OS does constant re-detection, and the device is picked up and dropped every 1-2 seconds. The laptop routinely makes ‘beeps’ and freezes for a few seconds unless the device is disabled {e.g, "UCM-UCSI ACPI Device"}... If the device is disabled and no drivers are loaded, then the rapid detection seen in the Device Manager halts {as do the beeps}. -- The laptop will hard-crash or reboot at-random, even if the above device is disabled. Occasionally the crashes are so severe that the only way to power off the laptop is to take off the bottom cover and live disconnect the battery! Note: The G1 is completely stable on a Minisforum MiniPC, and an ASUS G16 AMD Advantage laptop. So it's not that the G1 is defective. Corsair -- any help? We don’t seem to have fully functional USB4 support, or Thunderbolt. Are we going to receive more firmware / BIOS updates to fix issues like these? Windows 10 and 11 were tested, no difference.

8 months later update: I've since replaced my motherboard with an ASUS X670E-E {coupled with 7800X3D}, RMA'd the graphics card -- same problem --, and finally replaced my MSI 4090 with an ASUS (at a loss) -- due to TPU users being convinced this was isolated to MSI. (it's not) Contact with NVidia and DrHDMI support has gone silent {no fix}. Is this end of the line / time to sell the monitor {feels like it}? Doesn't seem Corsair is pushing updates, and support similarly has gone cold. Neither MSI nor ASUS provided any support, everyone is just pointing the blame at everyone else. --I've gone back to my old display for the last several months due to having to 'hard power' the machine when it gets stuck during boot (because I can't see what Windows is doing until drivers are loaded). Figure one last bump here in hopes of reaching someone. Feeling pretty betrayed as a fan of the Corsair brand.

Also want to add that this driver situation has to change. Corsair needs to get AMD to provide official support from drivers downloaded straight from AMD. A laptop that provides "official" drivers 6+ months old is not an advantage by any definition of advantage. This is not the case for NVidia hybrid laptops, and it should not be the case for AMD laptops. If some random person can create a custom INF and load the latest drivers with them completely functioning ... then there's no reason that AMD can't get those drivers working out-of-the-box. They need to invest effort here.

Everything works actually on 23.7.1 and 23.7.2 with a custom monitor INF. {see this thread linked here } When I say everything, that includes dGPU mux switching and Thunderbolt eGPU passthrough [hybrid style on APU]. -- Be aware that power management behavior is buggy though. On my end it's funky even with the official Corsair drivers ... sometimes exceeding profile TDP unless manually clamped via SPPT, BIOS Custom Plan settings, or by manually cycling the laptop fan profile [iCUE or hotkey] until it kicks in properly. Addendum: Since I said that eGPU is "working" (quotes) -- also bringing up this other thread . Working minus WHEA spam, yet my notebook does that on all configurations.

Came across this project on github, which was able to suppress those WHEA's ... yet this only works under Windows 10 and not 11. There's no performance impact from the warnings, yet the flood pushes all other events out of the log through constant log rotations every few hours, and that chews up disk writes. It really does seem that the system is stable with the docks connected {including in hot plugging them}, so I'm not quite sure what's going on there.

I purchased and ran a test with a thunderbolt SSD enclosure and saturated the link on an NVMe connected drive. No errors were encountered at 40gbit with the drive-test, so in my specific case I believe this is a firmware issue of some sort and not a defective CPU. Bought the machine a bit over a month ago... I started testing eGPU's in the last week of ownership of the return window (bought through Amazon) and did not notice the PCI-E link error spam (WHEA's) until I actually looked in the Event Viewer ... since I wasn't having any problems stability wise that prompted me to inspect the logs. The whole use of eGPU enclosure is because I can't get the thermals under control (without some exotic TIM used like Liquid Metal + Nickel plating the cooler or PTM}, or crippling the machine's performance in completely disabling boost. All in all I'm not a happy customer {should've returned it}, and I agree with you on the price point of the machine that something is really wrong here. I do notice that the downloads section of the site was finally updated {that's good}, yet the laptop has serious issues that zero-reviewers tested or touched on for some unknown reason. Maybe we're just unlucky and have lemon units, yet I doubt it. I went in to this not expecting any of what I'm encountering, and the silence on Corsair's part (plus lackluster customer support in not filling me in on the thermal compound [simple questions] asked on the phone -- just saying that the temps are fine} has me regretting the purchase big time. All I can really say there. Couple that with no answer in the thread on the topic of replacement fans, and the refusal to sell a replacement bottom panel for trying to fix the thermal situation. Hope that they turn this situation around, this is not how to build a brand image.

I ultimately opted to attempt a repaste with just MX6. The fans did not need removal to get at the vapor chamber, I did not peal off the pads for measurement and just reused -- but it looked pretty thick. Keep the screws separated, they are not all the same. Looked like just thermal paste (gray in color with a hefty application and lots of spillover) on the CPU and GPU dies. Repaste did not have much if any effect (within margin of error), so if you're going to attempt this make sure that you use something really premium.

Tested with Sonnet 750 Breakaway Box & Razer Core X. EVGA 2080 Ti and Reference Radeon 6800 XT. I've tried disabling the audio device, and in the case of the 2080 Ti, its onboard USB Controller, along with forcing MSI or plain Interrupts with the devices involved. Have also tried using a 1ft Thunderbolt cable, as well as multiple brands of active and passive cables, including dropping the link speed to 20gbit. Does not change the event frequency. Disconnecting eGPU instantly halts the spam. I've also attempted clean copies of Windows 10 and 11, it happens on both. Each card and each enclosure has been tested functional (no warnings) with the same cables on a GPD WIN Max. Main positive is that despite the WHEA spam, the system seems to be stable, since I've been using the enclosures non stop while docked with no software crashes or driver crashes. Anyone else that's tested eGPU docking on their Voyager? Are you seeing similar in your Event Viewer?

Additional note: I've not tried undervolting the CPU or GPU, yet I'm aware that both can be undervolted. Since I use the machine for software development, I'd really prefer not to risk instability doing such.