Does the issue occurs when the laptop is connected to the charger? Or battery? Or both?
Are there any hubs, docking station, printers or other devices plugged in to your laptop? If yes, kindly share us the exact model.
Can you share your OS and BIOS version?
Could you let us know what games you’re playing? Are they AAA titles, lower-end games, or particularly GPU or CPU-intensive games?
Could you please provide us some CPU benchmarking output screenshots or video showing the temperatures and the CPU use percentiles. This way we can further determine the temperature signatures of the laptop. You may use any available benchmarking tool/program equivalent to Cinebench​/HWmonitor​ (for windows) in Linux if you’re using.
Steps before running the tests:
reset the BIOS to optimal defaults
– To do this, keep pressing F2 after powering on the laptop, then press F9 to Load Optimal Defaults and F10 to Exit and Save Changes.
I find this section hilarious… if using a printer causes my laptop to hit 100c and throttle… I might have the wrong laptop…
All that really should be needed is the Cinebench results showing that core X is at 100c and Core y is at 80 on a full core load… getting throttled to 3.6ghz within 15 seconds… and a score will below even the “troubled” review units.
My laptop arrived at the repair centre today .
I had to send it because I need to also have the bottom cover replaced and that’s a bit more to do and we don’t have a tutorial yet.
That is odd. Can’t run it on a linux only Laptop.
Maybe I’ll install the Phoronix Benchmark-suite on mine for testing.
But so far, I don’t feel I have thermal issues.
Because Cinebench R23 runs on both windows and linux - so you can get an accurate comparison of your score/thermals across both.
And because if you want to RMA, the support team is aware of the expected results when using R23.
And lastly, it took 30 seconds to setup R23 so that I could see expected score vs actual score.
The cool thing about Linux is freedom - you have the freedom to use Phoronix - but if no one else is using it - you dont really have an accurate comparison to other F16s.
The root cause is the TV generates random UUIDs for UPNP network discovery every few minutes. That means it poses as a new device. This caused windows to add it to the device list (Device Association Framework, aka DAF) as a new device. This means now 1000s of devices (which is the same device) filled the device tree causing it to enumerate forever. Thus the “deadlock”.