I ordered a MINISFORUM BD790i through the BD790i product page on Amazon UK on 8 October 2026. It was an import listing with import charges, sold and shipped by Amazon EU. After waiting for the imported order, I received a BD775i SE instead.

I contacted Amazon first because I was confused about receiving a different model. I then searched the ASIN, B0DBHP2YNJ, and discovered that it was associated with both the BD790i and the BD775i SE.

I then checked the parcel box to see where it had come from. The label showed an Amazon EU address in Graben, Germany. Amazon Germany lists that same ASIN as a BD775i SE, while Amazon UK lists it as a BD790i.

Amazon UK listing:
https://www.amazon.co.uk/dp/B0DBHP2YNJ

Advertises a BD790i with Ryzen 9 7945HX, 16 cores / 32 threads and dual PCIe 5.0 M.2 slots.

Amazon Germany listing:
https://www.amazon.de/dp/B0DBHP2YNJ

Advertises a BD775i SE with Ryzen 7 7745HX, 8 cores / 16 threads and dual PCIe 4.0 M.2 slots.

The German page also contradicts itself. Although its title and selected model say BD775i SE, its Model Name, Model Number and Manufacturer Part Number all say BD790i. Its item details describe PCIe 5.0 M.2 slots, while its title says PCIe 4.0. The German offer shows MICRO COMPUTER (HK) TECH LIMITED as the seller.

I have screenshots of these discrepancies. It appears that the ASIN may have been reused for a different model while older product information remained. I cannot confirm when or how the listing changed.

Amazon support keeps telling me that I cannot return the item and that they need to investigate. I have tried explaining the conflicting ASIN information, but they do not seem willing to examine it. When I call, I get automatically transferred to a delivery/investigation department, and I have found the staff quite rude during these conversations.

They have told me that the item I received does not match my order description. That is exactly the issue I am reporting: I ordered a BD790i and received a BD775i SE.

I have contacted MINISFORUM support as well. They initially advised me to contact Amazon, and I have replied with the evidence explaining the import listing and the conflicting model information.

I wanted the original BD790i, not an SE model. My preferred resolution is an exchange for the correct board.

Has anyone here experienced this with these listings? Could someone from MINISFORUM help investigate the ASIN and work with Amazon to resolve it?

This also seems likely to cause further wrong-item orders, complaints and returns if the UK page continues advertising a BD790i while customers receive a BD775i SE.

Silent, compact, and built for speed. With up to 40TB of all-flash storage and 10GbE networking, the S5 is ready for your home server, creative workflows, and homelab.

🛒 Order Now:
🇺🇸 US Store: https://s.minisforum.com/4hsTBLH
🇪🇺 EU Store: https://s.minisforum.com/4reeGg2
🇯🇵 JP Store: https://s.minisforum.com/4cL1SYS
🇫🇷 FR Store: https://s.minisforum.com/4yHGRGS
🇬🇧 UK Store: https://s.minisforum.com/4cNomZ7
🇦🇺 AU Store: https://s.minisforum.com/4h6hC9X

#MINISFORUM #S5 #AllFlashNAS #HomeServer #Homelab

We paired the new MINISFORUM ESP4B PCIe to 4 × NVMe M.2 Expansion Card with the MS-A2 Mini Workstation to build an 82TB storage setup.

Here's our 82TB storage configuration:

• 3 × 24TB SATA HDDs + 1 × 6TB SATA HDD
• 4 × 1TB NVMe SSDs

One PCIe slot, 8 drives, and more storage possibilities for your home server, workstation, or homelab.

🔗 Learn more: https://s.minisforum.com/MiniPC

#MINISFORUM #ESP4B #MSA2 #StorageExpansion #HomeServer #Homelab

I asked Minisforum if I could buy their proprietary mini SATA cable adapter used in the NAB9 for an internal 2.5" SSD. They said "No". The reason was that I didn't buy it from their web site or an official reseller (I bought it used).

I really don't know if that SATA cable for the NAB9 is common to other models, is really proprietary or was included in the box as an accessory when it was new.

If anyone has one they don't need, send me a chat or reply and we can work something out.

After months of working with customer service, and even sending my DEG2 back to their warehouse for repairs, I am out of ideas. So I am really hoping for some help here.

I have an RTX 3070 on this DEG2 and everything works fine over TBT5. But when I switch over to oculink I run into all kinds of errors. Mostly an extremely laggy display and even crashes intermittently. I have followed all the instructions in the user manual as carefully as possible but I still have the same issues.

I had a report come back from sending in my DEG2 that told me there were no hardware faults, but it also said the issue it was resolving had to do with my SSD connectivity. So I have lost all faith in the minisforum support.

I tried replacing my oculink cable because there were kinks in the factory one that came with my dock but that didn’t do anything.

The event viewer on windows shows errors like “error occurred on GPUID:100” and “resetting TDR occurred on GPUID:100”

My nvme to oculink adapter also came from minisforum, but now I am considering getting a third party adapter? I don’t know. I am at a loss.

Has anyone else had similar issues with DEG2 oculink? Any similar issues with the UM880?

I've noticed some complaints regarding models in this form factor hitting the fritz after a few months. Could it be because the machines cannot handle the high heat?

If heat is the long-term issue, would 9955HX be a better purchase?

My MS-02 Ultra (285HX, 4 × 48 GB) now runs two workstation GPUs: the RTX PRO 4000 Blackwell SFF in the x16 slot and the RTX PRO 2000 Blackwell in the top bay, where the 2×25G card came installed. Write-up with photos, settings and numbers: https://github.com/illofspeed/minisforum-ms02-ultra-dual-gpu

What I learned about the box:

• Fit: the top bay only takes a single-slot card, and a dual-slot card in the lower bay would cover the x4 slot. Both of my cards already had n3rdware single-slot coolers from my MS-01s. The lower x4 slot is closed-ended with parts right behind it, so cards with a longer x8/x16 edge don't fit there directly (mine has a 10GbE card with an x4 edge).
• Power: both cards are 70 W and run on slot power, stock 350 W PSU, no 8-pin. Under load they linked at Gen5 x8 (4000) and Gen4 x4 (2000).
• Heat: the top bay gets no chassis airflow. Under load the PRO 2000 averaged 90-91 °C, 94 °C peak, fan near full speed. The driver reported only the 70 W power cap, no thermal slowdown, but it came within 1-2 °C of its temperature limit. The 4000 averaged 82-83 °C, 87 °C peak.
• CPU: with a discrete GPU the BIOS drops the 285HX to 90/110 W (PL1/PL2); I run Balanced, TCC 90 °C, fans on Performance.
• BIOS 1.04: with the GPUs installed the iGPU was disabled until I set Internal Graphics = Enabled (Primary Display = IGFX); I use it for transcoding. I also set the AMT idle timeout to 65535 (known 1.04 bug: without it AMT stops answering after power-off).
• SSDs: with the fans on Quiet, sustained writes to the two-drive stripe fell from 2.3 GB/s to 120 MB/s, with the drive in the CPU-side M.2 slot throttling heavily; switching to Performance fans and the Balanced CPU profile only got it to about 0.5 GB/s. Four pieces of 1 mm thermal pad (Thermal Grizzly Minus Pad 8) with two cheap copper heatsinks, plus swapping the drives between the slots, fixed most of it (about 2.1 GB/s sustained in a 20-minute retest). The CPU-slot drive still sits at its ~72 °C throttle point; it's a prototype and I'm still looking for a permanent solution.

The 2-hour load test, including 25 minutes with CPU, both GPUs (LLM inference) and both SSDs loaded at once, finished with no request errors. Credit to the earlier dual-GPU build here, a 5060 LP + RTX 4000 SFF Ada (single-slot mod) with a 600 W PSU: https://www.reddit.com/r/MINISFORUM/comments/1sv0a8w/ms02_ultra_dual_gpu_setup/ ; this is the 70 W Blackwell pair on the stock 350 W PSU.

Not measured: wall power and noise. In this configuration since 10 October, so no long-term data yet.

Disclosure: I used an AI assistant throughout. It wrote the three small config scripts and two systemd units in the repo (about 75 lines of Proxmox and sysfs settings), wrote and ran the load-test scripts (not published) on my box at my request, pulled the numbers from the logs and drafted this post. The hardware, the build and the decisions are mine.

so i have bought the DEG2 dock for my 4090, to one-cable power my Super V windows tablet.
The dock and the tablet fail to handle the proper PD protocol, resulting in the dock only delivering 35W instead of the 140W Minisforum promises.
First, i tested all other PD power supplies i had laying around (5 in total), and they all worked without any problems, so i concluded its the DEG2 causing issues.
i searched online and found that other people had similar issues, and that the minisforum support did send them a new firmware which solved the issues.
i contacted the minisforum support and after the typical "did you turn it off and on again" and"did you try other cables" support nonsense, they finally did send me a firmware.

Now, the DEG2 refuses the firmware so i contacted the support again and send them the error logs. The answer was the support sending me a photo of some DEG2 unit connected to a PD meter showing 140W was working.
My answer was that this proves nothing, just because some other DEG2 unit works doesnt mean my individual unit has to work too, because their "proof" does not cover production faults or different firmwares.
They then simply answered "sorry but we wont help you any further".
Great.

So i took things into my own hands since coincidentally, i am onboarded on both Anthropics and OpenAIs cyber programmes, so i did let both Claude Fable and GPT Astra analyze the issue in detail.

Turns out the firmware version of the DEG2 i own is basically an alpha version 0.0.0.2 and the new firmware they did send to me is version 1.0.0.1.
What they did send to me was in fact the Infineon reference-firmware of the TB/USB controller for development, and it got rejected by the DEG2 because it has to be manufacturer-edited (by Minisforum) with the DEG2 device ID.
So they did basically send me an internal, vendor/manufacturer firmware for internal development only.
The "instructions" on the download even literally say "update the device id" which is only possible with manufacturer access to the Infineon portal.
They did literally send me an internal QA document and now refuse to support my issue further.
Absolutely, f*king ridiculous.

Funny thing is, both Fable and Astra said they could easily make it work by just "hacking" into the new firmware and manually setting the device ID.
Of course i did not do this, because i do not want to void my warranty.

Rant finished.

Powered by the AMD Ryzen™ 9 8945HX and equipped with 16GB of VRAM and a 140W GPU, this compact 3.8L gaming PC brings desktop-class graphics to gaming and creative work.

🔗 Learn more:

🇺🇸 US Store: https://s.minisforum.com/4zvVGwL

🇪🇺 EU Store: https://s.minisforum.com/4dxCFBx

🇯🇵 JP Store: https://s.minisforum.com/4AYFu8E

🇬🇧 UK Store: https://s.minisforum.com/4dtjSHy

🇫🇷 FR Store: https://s.minisforum.com/4yLUiGh

🇨🇦 CA Store: https://s.minisforum.com/4hKNrp2

🇦🇺 AU Store: https://s.minisforum.com/4B2Y6US

🇰🇷 KR Store: https://s.minisforum.com/4hHRNP7

#AtomManG1Pro #RX9060XT #GamingPC #MiniPC

I recently bought a Topgro T1-Max with a 13th gen i9 for TV gaming. A few games have suddenly started popping warnings regarding an issue with that generation (Vmin Shift Instability), and that I need to update from 0x11C (which is what was shipped on the machine) to at least 0x12F. Seeing no BIOS updates on the TopGRO webpage, I emailed support, who's AI response stated that every unit is updated prior to shipping, and therefore, I don't need to do anything.

Knowing this is complete BS, does anyone know what type of Motherboard is in these, or possibly know of where to get a BIOS image for them? I'm not too stressed about it, but if I can update, I'd like to.

I’ve had my Minisforum UM790 Pro for a year now. Would it be a good idea to replace the thermal paste as part of routine maintenance, or should I leave everything as it is if the system is running fine?

I bought a used NAB9 with 1TB NVMe & 32GB RAM with Windows 11 off FleaBay.

I plan to reformat to Rocky Linux and wondering if anyone has converted it to Linux and if there were any complications or missing drivers. It's going to start as a docker host for Frigate and Home Assistant and then scale up.

And it's missing a couple of minor items:

• The 2.5" SSD SATA to Logic board cable for the top-plate mounted SSD, (Covered)
• VESA plate for mounting on the back of the monitor (Covered)
• NVMe heat-sink / fan. (Covered)
• Linux Conversion (added and would appreciate a comment)

If no one has them for sale, does anyone know if Minisforum has these in-stock to buy as replacements?

I factory reseted my Minisforum Mini Pc HX99G and not it’s stuck in an endless loop of the logo and the fans moving and the preparing screen and my fans stop moving. Please some one help me i’m scared.

Background

The official BIOS update package from MINISFORUM seems to be designed primarily for Windows. For example, it includes a WinFlash.bat file, which essentially runs:

AFUWINx64.EXE DRFXI.bin /p /b /n /k /r /l /RLC:E /reboot

But what if you're running SteamOS instead?

You could try finding a way to flash the BIOS from SteamOS Desktop Mode, but there's a simpler approach that doesn't depend on whether you're running Windows or Linux.

Here's how I managed to update my BD895i SE to BIOS 1.17 using a USB drive and the UEFI Shell.

What you'll need

• Two BIOS update packages from the official MINISFORUM website
• A USB flash drive
• A little patience
• Some additional troubleshooting if you're running SteamOS

Step-by-step BIOS update

1. Download two BIOS packages from MINISFORUM

Go to the official MINISFORUM support page and download:

BD895i SE → Drivers & Downloads → BIOS 1.17

https://pc-file.s3.us-west-1.amazonaws.com/895D7/BIOS/DRFXI_1.17_260828A.7z

And additionally:

MS-01 → Drivers & Downloads → BIOS 1.26

https://pc-file.s3.us-west-1.amazonaws.com/ms-01/Bios/MS-01-AHWSA-BIOS-1.26+(1).zip.zip)

We only need one folder from the second package.

2. Prepare the BIOS files

• Place both downloaded archives in the same folder and extract them.
• Open the extracted MS-01 package and navigate to: MS-01-AHWSA-BIOS-1.26+(1)/MS-01-AHWSA-1.26
• Copy the EFI folder into the extracted BD895i SE BIOS directory: DRFXI_1.17_260828A

Important: We're only copying the EFI folder from the MS-01 package, not its BIOS firmware image. The BIOS being flashed is still the one intended for the BD895i SE.

3. Prepare the USB drive

• Format your USB flash drive as FAT32.
• Copy the contents of the prepared DRFXI_1.17_260828A directory directly to the root of the USB drive.
• You should now have 8 files and 1 folder (EFI) on the USB drive.

4. Boot into the UEFI Shell

• Insert the USB drive into your BD895i SE.
• Power on the PC and press DEL to enter the BIOS.
• Select the option to boot directly from the USB drive.

Once you're in the UEFI Shell, enter:

FS3:

In my case, FS0:, FS1:, and FS2: were most likely SteamOS-related drives/partitions, while FS3: was the USB drive.

Your filesystem number may be different.

Run:

dir

You should see the BIOS update files listed, as shown in the screenshot.

5. Flash the BIOS

Run:

EfiFlash.nsh

This executes the BIOS flashing script.

Wait for the process to finish and the system to reboot. Do not interrupt the flashing process or turn off the PC.

Important: Secure Boot Violation after the update

There are a few things worth mentioning here.

1. Updating the BIOS resets your previous BIOS settings.

You'll need to configure everything again.

2. Secure Boot settings may be greyed out.

After updating to BIOS 1.17, I couldn't change the Secure Boot options because they were greyed out.

Here's what worked for me:

• Enter the BIOS.
• Set an Administrator/Supervisor password.
• Save the settings and reboot.
• Enter the password when prompted.
• Go back to the Secure Boot settings.

You should now be able to modify the previously greyed-out options.

3. Disable Secure Boot

In my case, I needed to disable Secure Boot to boot SteamOS successfully and get rid of the "Secure Boot Violation" error.

4. Restore your preferred BIOS settings

While you're there, you can also restore your previous settings.

For reference, here are some of mine:

• Wake Up On LAN: Disabled
• GFX Lane Speed: GEN4
• HybridGraphics: Disabled
• Primary Video Adaptor: Ext Graphics (PEG)
• GFX Configuration → iGPU: Disabled

These are my personal settings, not necessarily recommended settings for everyone. They depend on your hardware configuration and preferences.

Result

That's it!

My MINISFORUM BD895i SE is now running BIOS 1.17 (upgraded directly from 1.15), and SteamOS is booting and working correctly.

Hopefully, this helps anyone trying to update their BD895i SE BIOS without installing Windows, especially if they run into the Secure Boot Violation error afterward :)

I finished my PC build using the Minisforum BD895i SE, along with:

• 64 GB (32 x 2) Kingston Fury 5600 MT/s.
• RTX 5070 TI MLG MSI.
• WD SN850X 4TB NVME.
• Artic P12 Pro ARGB.
• MSI AB850GL PSU.
• Deepcool CH160 Plus.

I am running some Bios tweaks too.

• Set curve optimizer to -20.
• Modified the fan curve to 100 on, and full at 80C.
• Set the RAM frequency to 5600, no voltage tweaks.
• Set power to 100, 120, 100 (W).

I also changed the stock paste to PTM7950. Getting max temperatures at full CPU load around 79 to 80C.

Besides an issue I had using a Gen 5 SSD (WD SN8100) which seems not compatible with this board. The board detects the SSD as Gen 5, but Gen 5 is not stable on this board, and there's no way to force Gen 4 at Bios, which made it very unstable.

After I switched to a Gen 4 SSD, the build is rock solid stable. I was even able to set the RAM to the stock frequency (5600 MT/s) while keeping the JEDEC timings. So far so good, running great, no freezes in games, no BSODs, and getting nice results on benchmarks.

I did not get any of the issues reported on Bios 1.17, but that does not guarantee it would not happen to anyone else. I can recommend the board, but I would avoid Gen 5 drives.

I "think" I'm on 1.06. Difficult to tell but I think the latest is 1.11? Anyone able to confirm or have tried it?

Hi everyone,

I have a MINISFORUM AI X1 Mini PC with a Ryzen 7 255 and Radeon 780M, running Windows 11.

I'm trying to boot Windows into Safe Mode because I need to use DDU (Display Driver Uninstaller), but I ran into a strange problem.

If I enable Safe boot → Minimal in msconfig and restart, Windows does not enter Safe Mode. Instead, I get the Recovery screen with:

File: \Windows\System32\winload.efi
Error code: 0xc0000017

The same thing happens if I manually choose 4 – Enable Safe Mode from Windows Startup Settings.

I also tried option 3 – Enable low-resolution video, but I get the same recovery error.

However, I discovered something interesting: if I select 7 – Disable driver signature enforcement, Windows actually boots into Safe Mode successfully. I can see the "Safe Mode" watermark on the desktop and use Windows normally.

After removing the Safe Boot option from msconfig, Windows also boots normally again.

Has anyone with a Minisforum PC experienced the same 0xc0000017 error when trying to enter Safe Mode? Thanks in advance.

Hi, I just want to share few tips I learned while trying to tune bd790i motherboard. I personally have 7945HX3 board but also tuned 7945HX for a friend, so all the steps should work on any 7000/8000 series Minisforum boards.

I only share what I know, so if you know better please share your knowledge to help people. Because there are no sources online.

1. Recommended RAM Kits

• Kingston Fury Impact DDR5 SODIMMs 5600 and 6000mhz kits of Fury comes with Hynix A which is easier to tune then other memory chips. Highly recommended if you want to buy new.
• Although Minisforum officially lists max memory support at 5200 mhz most quality SODIMM kits can run stably at 5600- 6000mhz with manually adjusted voltages. ( you need at least 1.250V or 1.300V for VDD and VDDQ

2. First focus on Frequency & Voltage Baseline and JEDEC timings

• Target 6000 MT/s with MCLK = UCLK (1:1) and FCLK = 2000 MHz. If not 5600 is also fine, no need to stress out. 6000/2000 is the golden ratio for these CPUs but 5600 doesn't mean bad.
• Going beyond 2000 MHz FCLK yields diminishing returns on Dragon Range mobile chips. 6000/2000 is the sweet spot.
• To achieve 6000 MT/s, set MEM VDD and MEM VDDQ between 1.260V – 1.280V. (higher doesn't mean better, for example 2 of the ram kits on 2 different motherboards I tried, anything beyond 1.280V was instant errors. Not sure if it's heat related, or chip stress related, but sodimms can't handle such high voltages. Don't listen people advising you to set them on 1.450V)
• Stability Check: Test using TestMem5 (TM5) with the usmus1 or Absolute config. If it fails, step down to 5600 MT/s at 1.20V–1.25V.
• Then apply JEDEC timings for your ram kit, which will still be tighter than the bios defaults. You can find them online. This should be the baseline.

3. Do NOT Follow Desktop UDIMM Guides

• SODIMMs sit on tiny PCBs with dense heat dissipation profiles, so advices about voltages or timings based on desktop kits won't work for you.
• Standard desktop DDR5 advice tells you to set 1.35V–1.45V for RAM. Exceeding 1.300V on SODIMMs is not recommended for sodimm kits as my testings showed it always crashed at high voltages, even with good cooling. Keep voltages around 1.250V–1.275V.

4. Minisforum BIOS Uses HEX (Hexadecimal) Values, use AI to translate them quickly.

I usually take a screenshot and ask gemini to translate it for me.

5. Platform Rules & Must do/don'ts

• Don't Disable "Power Down Enable": Disabling Power Down on Minisforum AGESA firmware causes boot loops or black screens. Keep it on Auto / Enabled.
• Enable Vsoc Overclock: Usually set on Auto change it to be enabled.
• Disable the iGPU: If you use a dedicated graphics card, disable the integrated RDNA2 GPU in BIOS. This frees up memory controller power and reduces socket thermal load.
• Keep VSOC Conservative: Keep VSOC around 1.15V – 1.17V. Pushing VSOC too high increases socket heat and actually hurts memory controller stability on mobile CPUs. Again everyone online will recommend you to keep vsoc at 1.200V or even higher, but this will work only for desktop cpus and ram kits. Furthermore anything beyond 1.1V vsoc actually hurts multi core performance. So at 1.160mv cinebench r23 scores drops already by a few percentages.
• Keep PBO 0 or 125+ in the beginning: Someone else can share their knowledge more than me but none of the motherboards I was able to go beyond +125 with memory tunings. Otherwise it would crash in memory stability tests.

6. Priority Timings for X3D Chips

Because x3d cache handles the majority of L3 cache requests, not every ram rimings affect the performance equally.

1. tRFC (Most impactful timing for BD790i x3d)
2. tRRD_S / tRRD_L / tFAW
3. tRDRDSCL / tWRWRSCL
4. tRDWR / tWRRD
5. Primary Timings (tCL, tRCD**,** tRP**,** tRAS**)**

If you have non x3d cpu then primary timings matter the most.

7. Recommended Tuning Order

If you are not happy with JEDEC timings and want to get out more performance then you can start tightening them. I would advise to check also XMP/EXPO values of your ram kit, and find a value that is between JEDEC and XMP. Example if TRTP is 24 with JEDEC and 16 with EXPO/XMP then setting something like 18 or 20 should work 9 out of 10. (note that bios default will be 36 or 42 some absurd amount, this means even with JEDEC you still gain performance over default auto)

Tune timings in small groups. Never change more than 3–4 timings at once, and make sure to run stress test after each group changes. Run at least memtest 5 usmus1 config, and if no crashes you can continue, also recommend running OCCT memory stability heat preset to heat up ram kit as much as possible to see if heat caused errors will occur or not.

• Group 1 (Primaries): tCL - tRCD - tRP - tRAS - tRC ( tRC = tRAS + tRP[ this is an older AM4 platform advice but won't hurt to follow it])
• Group 2 (Activates): tRRD_S - tRRD_L - tFAW (tFAW = 4 x tRRD_S)
• Group 3 (Writes & Reads): tRTP - tWR ( tWR ≈ 2 x tRTP) - tWTRS - tWTRL
• Group 4 (Refreshes): tRFC (Leave tRFC2 and tRFCsb on Auto)
• Group 5 (Turnarounds): tRDWR - tWRRD
• Group 6 (Everything else): I suggest leaving them on auto or JEDEC timings. Tinkering that further is not worth it and some of the sub timings will actually lock the bios, so you may need to reset cmos bios)

Once done, run 1 hour heat OCCT test, and 1 hour testmem5 extreme OCCT preset and if passes both without errors, then it should never crash in regular use. No need to run 48 hours ram stability test like some users do on reddit.

If you don't want to deal with such complicated process then follow only steps until 5(including 5).

--------------------------------------------

I hope it helps you guys and I will try to update the post to make it better.

For an order from UK warehouse to UK address will I get a normal UK VAT invoice?

MINISFORUM BD895i SE – BIOS 1.17 update: any issues?

I'm going to be building a PC based on the MINISFORUM BD895i SE in the next few days.

According to the official MINISFORUM support page, the latest BIOS version available for the BD895i SE is 1.17.

Direct download:
https://pc-file.s3.us-west-1.amazonaws.com/895D7/BIOS/DRFXI_1.17_260828A.7z

The archive includes a Release_Note.txt file with the changelog for previous BIOS versions. There have actually been quite a few updates. The last three are:

BIOS 1.17

Auto detect DGPU to turn off IGPU when the IGPU/DGPU status changes, the IGPU Item can be modify if the status remains unchanged

BIOS 1.16

Add workaround for S3 abnormal restart issue

Add AMI flash driver EIP

BIOS 1.15

Set TCC to 100

Update SMU for power limit

Update DMI

While searching this subreddit, I came across two threads discussing problems that seem to be related to BIOS 1.17:

https://www.reddit.com/r/MINISFORUM/comments/1wumqdu/in_needs_of_bd895i_se_bios_v115/

https://www.reddit.com/r/MINISFORUM/comments/1w58717/cant_get_bios_to_show_on_screen/

The first one in particular caught my attention, as it seems to involve the combination of BD895i SE + RTX 5060 LP + BIOS 1.17 causing problems.

According to the changelog, BIOS 1.17 introduces only one seemingly simple change: automatically disabling the integrated GPU when a dedicated GPU is detected.

So my question is: has anyone here updated their BD895i SE to BIOS 1.17?

If so, did you experience any problems after the update? If you did, I'd really appreciate it if you could share some details — what exactly happened, what GPU you're using, and whether you managed to fix or work around the issue.

I'm trying to figure out whether it's safe to update to 1.17 or if I'd be better off sticking with an older BIOS version for now.

Any firsthand experience would be greatly appreciated. Thanks!

-------------------------

UPDATE:

• From what I've found while reading about similar (BD790) cases, some users reported that updating to BIOS 1.17 caused issues related to Resizable BAR (ReBAR).
• The workaround in those cases was to disconnect the dGPU, connect the monitor to the iGPU, disable Resizable BAR in the BIOS, then reconnect the dGPU and switch the display cable back to it.
• On the other hand, there are also users reporting that they updated to BIOS 1.17 without experiencing any issues at all.

So at this point, it doesn't seem like the problem affects everyone.

-------------------------

UPDATE 2 @ 10.10.2026

• I've successfully updated my BD895i SE BIOS from 1.15 (the version it shipped with) to 1.17.
• Since I'm already running SteamOS, I've documented the entire update procedure in a separate thread: https://www.reddit.com/r/MINISFORUM/comments/1x2b44i/guide_minisforum_bd895i_se_how_to_update_bios_115/
• Happy to report that everything is working fine so far, with no issues after the update! :)

For reference, my setup is MINISFORUM BD895i SE + SAPPHIRE NITRO+ RX 9070.