I've had my replacement MS-01 for about five days. The replacement actually shipped from Newegg.
I'm still waiting on the replacement RAM from Crucial. All I've received are emails with a PDF of the replacement order, emails seem to be ignored. The PDF shows the replacement RAM isn't...
I got another email a few days ago asking for my order number. Nothing since then, but it might be due to the Chinese New Year. Has anyone had any response from their tech support team in the past couple of days?
My new MS-01 arrived along with more RAM. The first thing I tried was the old RAM and it wouldn't POST so that RAM is bad. Thinking it might have been the RAM that was the issue I put the new RAM in the new MS-01 and it worked. I think tried the new RAM in the non-working MS-01 and it still...
I've been meaning to buy a third one but was putting it off, so I've bought another one. I'll try the CMOS battery first but then if it's not that RMA the broken one. Hopefully it doesn't take long for replacement.
I have two MS-01s with I9-13900H CPUs and 96GB Crucial RAM. I had one of them drop out of the vCenter cluster and checking it found it was powered off. I powered it on and it wouldn't boot. I pulled the power cord and tried again without luck. Checking Hardware Information in AMT shows the...
I thought I had read that people were also experiencing the issue on their laptops, but maybe those laptops used desktop CPUs instead of mobile CPUs. If the mobile CPUs aren't affected then we're good.
I'm using ESXi 8 so need to see if there's a way to load the new microcode.
But the best solution would be for Minisforum to release an updated BIOS with the new microcode since it's a critical fix to prevent hardware failure.
Given that the microcode update is to prevent the CPUs from failing I really hope Minisforum extends the warranty on the affected devices if they aren't going to implement the microcode in the firmware.
Has anyone heard if Minisforum is working on getting out a BIOS update with the new microcode? I contacted support a while ago asking about it and never got a response.
In a previous post in this thread I mentioned that after a month or so without any issues one of my systems got a PSOD. When I rebooted I disabled all the E-cores. Later I rebooted the other system and disabled the E-cores on that one as well. So far no more PSOD.
I've been running two MS-01s with the I9-13900H CPUs and 96GB of RAM with ESXi 8 for a couple of months now without any issues until today when one pink-screened. I had the two overrides to allow leaving the efficiency CPUs enabled but the crash was due to "Fatal CPU mismatch" on "Hyperthreads...
No, it was definitely the RAM, as I said I tested each SODIMM individually and the replacement kits all worked. I tested the RAM before I added my PCIe cards and NVMe storage.
I've bought four of these 96GB kits from Crucial and two of them had a bad SODIMM. I bought my first MS-01 and 96GB kit and had a bad SODIMM so ordered a replacement and both in the second kit worked, then I bought a second MS-01 and another 96GB kit and that had a bad SODIMM but the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.