What build do you have? There are quite a few. We have a very stable 8.4.1 build at the moment but it has some feature limitations so best to engage with Peplink to see if that is appropriate for you.
I believe the fix will be in a later 8.5.0 build, not the release build.
I really don’t know if it has ever gotten sorted out, Peplink support rolled me back to 8.3.0 on my MBX. So at least my network doesn’t crash now, but it seems like there are still serious unresolved issues in newer firmware versions that have still not gotten attention. Slightly concerning as this issue is going on a YEAR old now…I put my original ticket in with PL in November of 2023…
Word on the street that I got today is they have a fix, and its 8.4.1 build 5877, with 8.5 builds forthcoming. We have not been able to download and test this build yet, but fingers crossed.
That build is the one I referred to above, it has been stable so far (a few weeks), but it has some caveats about where it can be used (specific features not present), so you’ll need to engage with Peplink support to ensure that build is appropriate for your deployment.
A special build of 8.5.0 is coming to test changes in that version, but that is not confirmed fixed yet.
@Bryn ,
Thank you for your help and really appreciated that you help to advice other to create a ticket to allow Support team to check.
Hi All,
Please create a ticket to allow Support team to review.
Thank you
Hello all,
I wanted to update this thread with my experience as this issue is still alive and well.
Deployed two Balance 310 Fiber 5G devices running 8.5.0 build 5884. Shortly after both devices locked up and were hard down, requiring power cycles to restore them. I contacted Peplink who told me to enable watchdog and try interim build 8.5.0s057 build 5919. I upgraded to 8.5.0s057 build 5919 on one device, and it was locked up again within 24 hours. Once again, I contacted Peplink who have provided yet another interim build, this time 8.5.0s053-build5913. I’ve just applied this version to both Balance devices. Peplink won’t share any bug details other than stating this is a kernel level issue.
I haven’t tried the 8.4.1 version mentioned above, but I will do this next if instability continues.
To add insult to injury these two devices are deployed in a POC we are doing with a Fortune 500 account. Extremely disappointed.
What I’ve done when deploying or “fixing” 310 5G’s is to install fw 8.5.0s057 build 5919 which contains what I understand to be a microcode update, then after it finishes, I immediately install 8.5.0s013 build 5902.
Since doing this, all of the units in my fleet (I’d have count but i have around 20) are now all 50 to 60 days of uptime with zero issues. Previously the max we could get was 32 days. I’m not calling it “fixed” until I see the 12 month+ uptimes of my other non-310-5G units, but this is looking optimistic.
8.5.0s013 build 5902 does not have the issue, but it does have some feature limitations and is different to other 8.5.0 builds.
8.5.0s057 build 5919 is much much more stable than older builds but not 100% fixed.
@james.cancel @Noah_Helterbrand ,
Along the way when we work on the B310 5G/Fiber 5G issue, we have released multiple firmware’s and it may confused everyone here on which firmware need to be use. Do allow me to clarify and provide more info on this. For this reply, I’m not discussing the 8.3.0/8.4.0/8.4.1 firmware info and we do have stable special firmware released in those firmware. Let us keep it simple and If you have issue using the previous firmware , please upgrade the devices using the followings firmware :
Recommended is using the 8.5.0s053 because it’s supporting all the Cellular module SKU just in case you have mixing SKU B3105G/Fiber 5G product.
Please create a ticket for support team to check if you have any concerns because different deployment have different environment influences, if we did not isolate those influences, it will confuse everyone here and cause confusion here.
@sitloongs Thanks for your response. In my case, I am running the 5G enabled 310. You say 8.5.0s053 is the improvement firmware. Does this mean the kernel issue is fixed or is it still a known bug in this version? I have a ticket open with support as well.
The firmware 8.5.0s013/8.5.0s053 fixed the device lockup issue. For anyone have the similar issue, please have your device running with the firmware and it should running fine and stable. We have collected the feedback from the many users and the test labs as well, the firmware work well. 
I quick checked your ticket and it running 8.5.0s053 so should running fine now. Support team will help you monitor the device as well.
Hello @sitloongs,
Are these fixes included in the new Firmware 8.5.1 release versions?
Happy to Help,
Marcus 
Marcus,
No they aren’t, the fixes in s013/s053 are not present in the 8.5.1 releases
What about for the MBX Mini?
Hello @sitloongs,
Do you need to use a particular version of this special-release firmware for improved stability in deployments where we are not using the internal cellular modems (are disabled)?
Will we need a special release of Firmware 8.5.1 (and future editions) for locations with the B310 5G models?
Appreciate your assistance,
Marcus
Only B3105G/Fiber 5G are reported having the issue and need to use the posted firmware.
We will update when I get the latest info
Do we have a 8.5.1 stable version? It has a couple of features I would like to use.
Same…I’m not sure why the “special build” fixes were not just merged into the 8.5.1 GA. A lot of things about this issue hasn’t made sense, especially them never publicly acknowledging it while still shipping devices despite it being a severe problem. And this issue is nearly a year old now.
Hi All,
We’ve just had this issue appear for the first time on 2 of our deployed 3105G units.
What changed? We stopped using Synergy hosts for cellular and used the built-in cellular modem and suddenly they both freeze after having run for almost 12-months without a problem.
Have updated to the special firmware and enabled Wathdog feature.
I have several varieties of the 3105g models around and it does appear heat is the issue for us. The hits get so hot, a hard reboot is required to regain control.
We installed ac powered mini fans to keep the devices cool and have not had the issue happen since.
Running 8.5.1 currently (just upgraded 2 weeks ago) and still going strong. I have been through all of the firmware releases and none have solved the issue. The fans, so far, have.