Hello,
I just watched Level1’s Bellink GTR7 video (RIP GTR7) and I wanted to post this to help anyone else out that may have one and are having issues with random reboot/crashes.
I received my BeeLink GTR7 (7840) unit last week and I love the little guy as it is an astounding what Beelink was able to pack into this will package but like many of you out there that have also received their GTR7. It quickly went from awesome fun to bad times due to random issues or problems. One of the biggest issues most users are having is the random rebooting/crashing problems and I, like many of you have experienced that on my unit.
What has been discovered on this issue is that most of the common reboot/crashing that is occurring comes down to a problem with the power management of the APU/Memory SOC while the system is at idle. Specifically, the C6 power state is not working as it should and causing issues with core parking, memory parking (didn’t know this was a thing with DDR5) and hardware power control on the peripherals like the NIC’s and Bluetooth controller. It is a two-part problem with the current AMD drivers and some issues within the currnet BIOS.
BeeLink has acknowledged this issue and is currently working on BIOS update (no ETA given) that will address the broken power settings in the current BIOS (namely the TDP option for the APU that actually doesn’t work when setting to anything other 65w), other power related options that are either missing or are not working as intended as well as an update to the memory training process to help with memory detection and stability.
They have also stated in their forum that they are expecting an updated driver package from AMD sometime around July 26th for the 7840/7940 APU’s. Whether it is the official release or just an updated OEM beta driver, we don’t know.
In the meantime, I have put together a little something that hopefully will allow you to start enjoying your new little toy while we wait for all the proper fixes. I have provided steps and settings below for the GTR7 that have worked for many others to resolve the random rebooting/ crashing. These settings have worked for my unit which has now been reboot/crash free for 48 hours but please note, they are not an official fix nor has Beelink given any advice or suggestion for any of these provided changes. I found these through my own testing and forum searches and have put together this list in a single, central location where I believe will be the most helpful. These settings are only for Windows currently as I am not that versed with messing within the guts of Linux (nor do I have the time or brain power available).
BIOS:
-
Advanced>ACPI Settings: Disable “Enable ACPI Auto Config” and set both options below that appear to Disable and Suspend Disable
-
Advanced> AMD CBS>NBIO Common Options>GFX Configuration: Set iGPU to UMA_Specified. Set UMA Frame Buffer Size to a static size. You choose what you want or what you can afford to give to the GPU for memory. Suggested 2GB or 4GB. (This supposedly helps with keeping both DIMM’s awake).
Windows:
-
Disable hibernate: Open CMD/Terminal and enter in command: powercfg hibernate off (Must run terminal/cmd as administrator)
-
Disable hardware power savings: Easiest way to do this is open device manager, then you must open the affected hardware’s properties page by double clicking on them and then under the Power Management tab. Uncheck “Allow the computer to turn off this device to save power”. Do this for both of the NICs, the Intel Wi-Fi 6 AX200 NIC and Intel Wireless Bluetooth adaptor. Note if you have any of these devices disabled, then you can ignore them.
-
Disable sleep and CPU low power/core parking. Go to Control Panel\All Control Panel Items\Power Options\Edit Plan Settings. Here change “Put the computer to sleep” to Never. Then just under that setting, click on the link “Change advanced power settings”. Click on the + to open Processor Power Management then say for Minimum Processor state and here enter in 10%.
After you have changed these settings, reboot using run prompt and type in shutdown -r which bypasses the Windows quick reboot and performs a full clean reboot. Once it comes back up, test it out and since this issue usually occurs at idle, I suggest letting the unit sit just at the desktop for a while and see if your system reboots anymore. After it has been sitting for a while with no reboots, push it for a bit with a benchmark, game or anything that is going to make it work, then let it go back to idle for a while.
Hopefully this will help some of you out and if anyone has any additional settings, they found to add to this list that also work. Please add them in.