Minisforum MS-01 BIOS
- Thread starter the-last-englishman
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Unable to update from V1.26 to V1.27 (5/28/2025) any thoughts to fix this?
Has anyone else used the 5/28/2025 version?
I'm in the right directory as shown above but AfuEfiFlash.nsh starts AfuEfix64.efi and then reports an error.
Has anyone else used the 5/28/2025 version?
I'm in the right directory as shown above but AfuEfiFlash.nsh starts AfuEfix64.efi and then reports an error.
Thanks Wadup. Could you look inside the Bios 1.27 file and confirm that it is missing the AfuEfix64.efi file before I use the version from the 1.26 inserted into the 1.27. Was this file missing in the earlier version of 1.27?
the readme for the bios states the following so iam not sure everyone wants to update :
This BIOS Improved stability.
If you have had problems with crashes, restarts, and hangs before, you can flash this BIOS.
If your problem still happens.
1. You may need downgrade memory speed to 4400.
There have a menu in Onboard Devices Setting.
This BIOS will take more idle power consumption.
Linux: 14.5W-> 17.5W
Windows: 14.5W -> 22W
(Data tested with 32G 5200Mhz RAM x 2 and 1xPCIE4.0 SSD)
（Recommend)
2. Disable Overclocking Lock: Advaned -> CPU configuation ->Overclocking Lock:[ Disable]
Reduce the maximum CPU frequency:
Advaned -> CPU configuation ->Turbo Ratio Limit Options.
P-Core Trubo Ratio Limit Ratio0: 51
P-Core Turbo Ratio Limit Ratio1: 51
E-Core Trubo Ratio Limit Ratio0: 40
E-Core Turbo Ratio Limit Ratio1: 40
E-Core Turbo Ratio Limit Ratio2: 40
E-Core Turbo Ratio Limit Ratio3: 40
Save and reboot enter into BIOS. Advaned -> CPU configuation ->Turbo Ratio Limit Options. Check is it max frequency has been reduced.
Reboot into System. Try is it more stable.
If all of this cannot solve problem, you may need do a request RMA.
This BIOS Improved stability.
If you have had problems with crashes, restarts, and hangs before, you can flash this BIOS.
If your problem still happens.
1. You may need downgrade memory speed to 4400.
There have a menu in Onboard Devices Setting.
This BIOS will take more idle power consumption.
Linux: 14.5W-> 17.5W
Windows: 14.5W -> 22W
(Data tested with 32G 5200Mhz RAM x 2 and 1xPCIE4.0 SSD)
（Recommend)
2. Disable Overclocking Lock: Advaned -> CPU configuation ->Overclocking Lock:[ Disable]
Reduce the maximum CPU frequency:
Advaned -> CPU configuation ->Turbo Ratio Limit Options.
P-Core Trubo Ratio Limit Ratio0: 51
P-Core Turbo Ratio Limit Ratio1: 51
E-Core Trubo Ratio Limit Ratio0: 40
E-Core Turbo Ratio Limit Ratio1: 40
E-Core Turbo Ratio Limit Ratio2: 40
E-Core Turbo Ratio Limit Ratio3: 40
Save and reboot enter into BIOS. Advaned -> CPU configuation ->Turbo Ratio Limit Options. Check is it max frequency has been reduced.
Reboot into System. Try is it more stable.
If all of this cannot solve problem, you may need do a request RMA.
I recently upgraded to 1.27 (as well as repasted and repositioned) and my heat in my cabinet increased by a lot. Stable 38C to 50C
I downgraded to 1.26 and disabled some stuff (Max battery mode, no turbo, no wifi, reduced voltage) in the BIOS to seei if that helps.
I downgraded to 1.26 and disabled some stuff (Max battery mode, no turbo, no wifi, reduced voltage) in the BIOS to seei if that helps.
First; thanks for all the comments here! It's really amazing to read all the small findings, to get some ideas on where and what to look for, when troubleshooting issues with the MS-01 (which is an amazing piece of machine/server - when it's stable..). Here is some of my recent findings related to kernel/process crashes, and findings on temperature - hopefully it can help!
BIOS 1.27 AND suggested adjustments in BIOS possibly solved random crashes
I can confirm that BIOS 1.27 (MS-01-AHWSA-V1.27_4_28_V2.zip), in addition to follow the steps mentioned in "0-READ-ME.txt" (downgrade memory speed to 4400, disable overclocking lock and reduced max CPU frequency/turbo ratio limit option), seem to have fixed my seemingly random kernel and process crashes on Proxmox 8.4.1.
Based on my current research, most crashes/debug traces pointing towards memory corruption (which according to memtest86+ after 18 hours is healthy.. but good thing I ran it, cause that was where I noticed the high temperatures). Since performing the adjustments suggested in "0-READ-ME.txt", I've not experienced any issues. It's now been 8 days without any issues (I follow the journal logs/kernel closely using loki), whereas I previously experienced processes crashing "randomly" earlier, like pvestatd crashing.
PS: I also noticed that process crashes/issues did not start before I loaded the server to about 20% average CPU (based on Proxmox metrics from pvestatd, which ironically was one of the process resulting in regular "general protection fault").
I also have two (2) MS-01 still on 1.26 without any issues (yet), but they are loaded less (between 1-8 %), and CPU is running way cooler, e.g. mean values celsius 55-63C (mean) on less loaded nodes vs 76-80C (mean) and spiking to 90-99C on the MS-01 with 20-25% load (still do/identical to on 1.26 BIOS).
My hardware configuration
For reference, I have four (4) MS-01 with the Intel i9-13900H configuration, upgraded RAM to 96GB on each, with added 2x NVMe (using all three M.2 slots, on different speeds), and using both the vPro NIC (226-LM) and both 10Gb NICs (X710). No added expansion card.
High temperatures (CPU)
As mentioned, I've ran memtest86+ for about 18 hours (on BIOS 1.26), and while the results was a "PASS" every time (see screenshot below), I also noticed the high temps, sometimes over 90C, which got me a bit worried (CPU is rated to 100C max, AFAIK). For now, the MS-01 "servers" are physically located in the basement, with about 18-23C room temperature (summer in Norway..), only with stock options for fan/thermal paste, etc. (not replaced thermal paste.. yet).
I've installed lm-sensors and correlated the package/core IDs with output from node_exporter to closer monitor the temperatures (using Prometheus) for each P/E-core, and noticed only "minor to none difference" for temperature on both P/E-cores, both on 1.26 and after 1.27 at approx. same CPU-load - but the crashes stopped!
For some more reference, here is last 24h, sorted on mean temp on each core, first on a node with ~20% CPU load avg. (now on BIOS 1.27 with adjustments suggested in, not experiencing any crashes anymore).
And another node with ~1-3% CPU load avg (on BIOS 1.26, but not experienced any crashes yet).
And just to compare temperatures on 1.26 vs 1.27, I've highlighted "temp6" (from node_exporter, which correlates to P-core 4 in lm sensor), I don't see much difference (time ~16-18 is with BIOS 1.26, then it crashed, and ~20:45+ is on BIOS 1.27). IMO, no changes in temperature, but the crashes stopped, which was my main issue on the node.
And from the logs on the node the experienced crashes, here is a quick overview of count on "critical" and "coredump" from journal. Also note that issues seemed to escalate after upgrading to kernel 6.8.12-11-pve vs previously 6.8.12-10-pve, but then later I experienced issues on all 6.8-kernels (tried multiple versions), even tried rolling back to 6.5.13. But then, after BIOS 1.27 + adjustments was performed 2025-06-26, I've not seen any crashes (yet).
And for reference, from 0-READ-ME.txt, BIOS 1.27 for Minisforum MS-01, extracted from MS-01-AHWSA-V1.27_4_28_V2.zip:
BIOS 1.27 AND suggested adjustments in BIOS possibly solved random crashes
I can confirm that BIOS 1.27 (MS-01-AHWSA-V1.27_4_28_V2.zip), in addition to follow the steps mentioned in "0-READ-ME.txt" (downgrade memory speed to 4400, disable overclocking lock and reduced max CPU frequency/turbo ratio limit option), seem to have fixed my seemingly random kernel and process crashes on Proxmox 8.4.1.
Based on my current research, most crashes/debug traces pointing towards memory corruption (which according to memtest86+ after 18 hours is healthy.. but good thing I ran it, cause that was where I noticed the high temperatures). Since performing the adjustments suggested in "0-READ-ME.txt", I've not experienced any issues. It's now been 8 days without any issues (I follow the journal logs/kernel closely using loki), whereas I previously experienced processes crashing "randomly" earlier, like pvestatd crashing.
PS: I also noticed that process crashes/issues did not start before I loaded the server to about 20% average CPU (based on Proxmox metrics from pvestatd, which ironically was one of the process resulting in regular "general protection fault").
I also have two (2) MS-01 still on 1.26 without any issues (yet), but they are loaded less (between 1-8 %), and CPU is running way cooler, e.g. mean values celsius 55-63C (mean) on less loaded nodes vs 76-80C (mean) and spiking to 90-99C on the MS-01 with 20-25% load (still do/identical to on 1.26 BIOS).
My hardware configuration
For reference, I have four (4) MS-01 with the Intel i9-13900H configuration, upgraded RAM to 96GB on each, with added 2x NVMe (using all three M.2 slots, on different speeds), and using both the vPro NIC (226-LM) and both 10Gb NICs (X710). No added expansion card.
High temperatures (CPU)
As mentioned, I've ran memtest86+ for about 18 hours (on BIOS 1.26), and while the results was a "PASS" every time (see screenshot below), I also noticed the high temps, sometimes over 90C, which got me a bit worried (CPU is rated to 100C max, AFAIK). For now, the MS-01 "servers" are physically located in the basement, with about 18-23C room temperature (summer in Norway..), only with stock options for fan/thermal paste, etc. (not replaced thermal paste.. yet).
I've installed lm-sensors and correlated the package/core IDs with output from node_exporter to closer monitor the temperatures (using Prometheus) for each P/E-core, and noticed only "minor to none difference" for temperature on both P/E-cores, both on 1.26 and after 1.27 at approx. same CPU-load - but the crashes stopped!
For some more reference, here is last 24h, sorted on mean temp on each core, first on a node with ~20% CPU load avg. (now on BIOS 1.27 with adjustments suggested in, not experiencing any crashes anymore).
And another node with ~1-3% CPU load avg (on BIOS 1.26, but not experienced any crashes yet).
And just to compare temperatures on 1.26 vs 1.27, I've highlighted "temp6" (from node_exporter, which correlates to P-core 4 in lm sensor), I don't see much difference (time ~16-18 is with BIOS 1.26, then it crashed, and ~20:45+ is on BIOS 1.27). IMO, no changes in temperature, but the crashes stopped, which was my main issue on the node.
And from the logs on the node the experienced crashes, here is a quick overview of count on "critical" and "coredump" from journal. Also note that issues seemed to escalate after upgrading to kernel 6.8.12-11-pve vs previously 6.8.12-10-pve, but then later I experienced issues on all 6.8-kernels (tried multiple versions), even tried rolling back to 6.5.13. But then, after BIOS 1.27 + adjustments was performed 2025-06-26, I've not seen any crashes (yet).
And for reference, from 0-READ-ME.txt, BIOS 1.27 for Minisforum MS-01, extracted from MS-01-AHWSA-V1.27_4_28_V2.zip:
Code:
This BIOS Improved stability.
If you have had problems with crashes, restarts, and hangs before, you can flash this BIOS.
If your problem still happens.
1. You may need downgrade memory speed to 4400.
There have a menu in Onboard Devices Setting.
This BIOS will take more idle power consumption.
Linux: 14.5W-> 17.5W
Windows: 14.5W -> 22W
(Data tested with 32G 5200Mhz RAM x 2 and 1xPCIE4.0 SSD)
（Recommend)
2. Disable Overclocking Lock: Advaned -> CPU configuation ->Overclocking Lock:[ Disable]
Reduce the maximum CPU frequency:
Advaned -> CPU configuation ->Turbo Ratio Limit Options.
P-Core Trubo Ratio Limit Ratio0: 51
P-Core Turbo Ratio Limit Ratio1: 51
E-Core Trubo Ratio Limit Ratio0: 40
E-Core Turbo Ratio Limit Ratio1: 40
E-Core Turbo Ratio Limit Ratio2: 40
E-Core Turbo Ratio Limit Ratio3: 40
Save and reboot enter into BIOS. Advaned -> CPU configuation ->Turbo Ratio Limit Options. Check is it max frequency has been reduced.
Reboot into System. Try is it more stable.
If all of this cannot solve problem, you may need do a request RMA.
How is down clocking the ram and CPU an acceptable solution? The system is advertised with a certain spec, whoopsie you have to run it at under advertised capability to be stable.
It's not, and I fully agree; the MS-01 should be able to perform at advertised specs, without any issues (especially crashes). But after several weeks of issues/random reboots, kernel panic/process dumps (and follow-ups on each trace), etc., I'd rather take a stable system, shaving off some of the "peak performance", pending reply from Minisforum on this matter, or in hope for a better solution.
My "message" was simply to inform that I've not seen any issues (yet) after BIOS 1.27 and following the downgrades on memory speed and turbo ratio options (in contrast to running on BIOS 1.26, where issues occurred every day/week)
Can someone share the Bios 1.26 and 1.27 plx? All the download links that I found in the forum and on other sources pointing to the minisforum website lead to a dead end. I'm still running on 1.24 and with instability and would love to improve the situation.
The zip-files was to big to upload here. I can share the `MS-01-AHWSA-V1.27_4_28_V2.zip` and `AHWSA.1.26_241014.zip` if you like, but I don't know if this breaks any rules (e.g. public files links using Dropbox), but I can ping you directly (if you like).
I've also confirmed that this official directlink works (as of right now): https://pc-file.s3.us-west-1.amazonaws.com/ms-01/Bios/MS-01-AHWSA-V1.27_4_28_V2.zip (which is from https://www.minisforum.cn/pages/product-info > MS-01 > Drivers & Downloads > BIOS 1.27)
Just FYI, the MD5s/checksum for the ZIP-files files directly from Minisforum (which I've used on all my four MS-01) are:
Code:
[I] esod@mbp24 ~> md5 ~./*ms-01*/*.zip
MD5 (.../2024-10-22 ms-01 bios 1.26/AHWSA.1.26_241014.zip) = 17d88baf613f86c9facdda2d147f0968
MD5 (.../2025-04-03 ms-01 bios 1.27/MS-01-AHWSA-V1.27_4_28_V2.zip) = 9eee2e219172312069962f8ce7218b64ahh thank you soo much for sharing. just fyi in case someone here is wondering. that bios 1.27 zip now includes the AfuEfix64.efi file
I have just installed 1.27, hoping to resolve some NVME issues I am having. I have slimmed down the Ms-01 to just one NVME, a 2TB Samsung.
It reports zero errors in its smart-log, and a long smartctl test completes successfully.
Running nixos on luks-encrypted btrfs runs OK for a while, and then I start getting reports of errors, and then it hangs.
Booted up on a USB drive, and ran a full check of the filesystem: zero errors. BTRFS shows zero errors. Smartctl shows zero errors, but after a day or so, booted up on the USB drive, when I try to `dd` the /dev/nvme0 contents off to a nas file for safe keeping, it transfers about 450GB of data and then gets some errors, fails at resetting the controller, and the nvme is catatonic.
The reason I am running just one SSD in the system is because when I had a pair, mirrored, proxmox install, I ran proxmox for several weeks and then one day just happened to look at the zfs filesystem state and it was degraded because one NVME had completely disappeared. On reset, it came back, re-silvered, and was somewhat happy. I was hoping that at least one NVME controller would remain good.
I no longer run proxmox on this, as I would occasionally discover that various things in the kernel were panicing, and the kernel just put a stack backtrace, and I guess hoped? Not sure what the point is of panic but continue. Anyway, there would be days and days of occasional things panicing, and eventually something would panic which had some resource locked and I would notice it and reboot.
Been running nixos on it for a few months, and it was reasonably stable, until just recently when things would lock up, due to the NVME controller getting into bad, reset-resistant state.
Anyway, wish me luck!
It reports zero errors in its smart-log, and a long smartctl test completes successfully.
Running nixos on luks-encrypted btrfs runs OK for a while, and then I start getting reports of errors, and then it hangs.
Booted up on a USB drive, and ran a full check of the filesystem: zero errors. BTRFS shows zero errors. Smartctl shows zero errors, but after a day or so, booted up on the USB drive, when I try to `dd` the /dev/nvme0 contents off to a nas file for safe keeping, it transfers about 450GB of data and then gets some errors, fails at resetting the controller, and the nvme is catatonic.
Code:
[75293.353614] BTRFS info (device dm-1): last unmount of filesystem 51ac9b4e-90ff-4196-8460-387b3f9f7f46
[75977.611275] nvme nvme0: I/O 257 (I/O Cmd) QID 4 timeout, aborting
[75977.611315] nvme nvme0: I/O 258 (I/O Cmd) QID 4 timeout, aborting
[75977.611492] nvme nvme0: Abort status: 0x0
[75977.611512] nvme0n1: I/O Cmd(0x2) @ LBA 496707584, 2560 blocks, I/O Error (sct 0x0 / sc 0x7)
[75977.611545] nvme nvme0: Abort status: 0x0
[75977.611566] I/O error, dev nvme0n1, sector 496707584 op 0x0:(READ) flags 0x80700 phys_seg 26 prio class 2
[76007.817107] nvme nvme0: I/O 257 QID 4 timeout, reset controller
[76091.805904] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[76091.813186] nvme0n1: I/O Cmd(0x2) @ LBA 496705024, 2560 blocks, I/O Error (sct 0x3 / sc 0x71)
[76091.813216] I/O error, dev nvme0n1, sector 496705024 op 0x0:(READ) flags 0x80700 phys_seg 27 prio class 2
[76111.821478] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[76111.822318] nvme nvme0: Disabling device after reset failure: -19
[76111.831760] Buffer I/O error on dev nvme0n1, logical block 62088128, async page read
# nvme list -v
Subsystem Subsystem-NQN Controllers
---------------- ------------------------------------------------------------------------------------------------ ----------------
nvme-subsys0 nqn.1994-11.com.samsung:nvme:990PRO:M.2:S7KHNJ0X108474H nvme0
Device SN MN FR TxPort Asdress Slot Subsystem Namespaces
-------- -------------------- ---------------------------------------- -------- ------ -------------- ------ ------------ ----------------
nvme0 S7KHNJ0X108474H Samsung SSD 990 PRO 2TB 0B2QJXG7 pcie 0000:01:00.0 nvme-subsys0
Device Generic NSID Usage Format Controllers
------------ ------------ ---------- -------------------------- ---------------- ----------------I no longer run proxmox on this, as I would occasionally discover that various things in the kernel were panicing, and the kernel just put a stack backtrace, and I guess hoped? Not sure what the point is of panic but continue. Anyway, there would be days and days of occasional things panicing, and eventually something would panic which had some resource locked and I would notice it and reboot.
Been running nixos on it for a few months, and it was reasonably stable, until just recently when things would lock up, due to the NVME controller getting into bad, reset-resistant state.
Anyway, wish me luck!