- #22
d3vil
Sorry for the late reply
Please contact us via email so that we can help you better :support-pc@bee-link.com
d3vil
Sorry for the late reply
Please contact us via email so that we can help you better :support-pc@bee-link.com
Any update on that issue?
d3vil
1.Adjust the fan speed: https://buildin.ai/lizong/share/0a7ed1b7-2548-4a5a-bb43-82e1ea366978
2.Overheating. If your PC is overheating, please check if the fan spins. You can also turn off the turbo boost. Adjust power settings: Adjust the power settings on your PC to optimize performance and reduce heat generation. Lowering the maximum processor state or using power-saving modes can help. Go to control panel —power option—change to High performance— change plan setting—advanced setting —processor power management— change both 100% to 99% , click save.
3.Remove the fan, clean it and apply a very small amount of nonconducting lubricant to the shaft and reassemble the unit.
It seems noone can send a Private Message because of broken reCaptcha protection settings. At least I can’t and some other people confirmed it.
@d3vil How did Beelink solve the problem once they admitted it’s the internal PSU problem?
I started email exchange with support-pc@bee-link.com, but so far it is only: try reinstalling WinRAR.
I’m beggining to wonder if it is not due to a design flaw. So a replacement unit, even new, will have the same problems.
I have been having these exact issues with my EQ14
I own two of these devices so I have tried a combination of swapping RAM and disks between machines and I have observed the following.
The EQ14 with the original M.2 SATA disk does not experience these shutdowns, and if it does, it is extremely rare and maybe after a couple of months. My other EQ14 which originally had 2 x NVMe running in ZFS would randomly crash so I experimented by having one disk at a time in each slot. From what I can see, the crashes are happening much quicker if only the x4 slot above the wi-fi card is occupied versus the x1 slot.
It does seem to me that there is a design flaw somewhere. The only real stable solution is to use an M.2 SATA. This is not something I would expect from such a product that advertises two M.2 slots that should be capable of handling an NVMe card. Perhaps @Beelink can look into this for us and maybe provide a BIOS patch