1 Rookie
•
8 Posts
6
480
February 20th, 2026 23:45
Inspiron 13 5310 Firmware - 0.2.37.0 forced by Microsoft is bad, please fix Dell
Firmware - 0.2.37.0 was forced on the Inspiron 13 5310 via Microsoft updates within the past few weeks and now hundreds maybe thousands of laptops no longer work properly. Internet is filled with complaints. Find a solution on how to roll back the BIOS without bricking the PC.
This is Dell's problem, find a solution. If my client has to buy a new computer, I can promise you it won't be a Dell.
This has apparently been a problem for 6 months, but the newest firmware was never forced on people until this month:
This is not a faulty RAM issue, it's bad BIOS.
https://www.reddit.com/r/Dell/comments/1r6n7y2/dell_inspiron_13_5310_false_faulty_ram_error_due/
Rolling back the firmware doesn't always work.
DELL-Nat M
Community Manager
•
3.6K Posts
0
March 18th, 2026 16:46
Hi everyone,
If you are using an Inspiron 5310, please make sure your system is updated to the latest BIOS version, 2.40.0.
Once you have updated, feel free to share how things are working for you and whether it made a difference with the issue discussed in this thread.
DELL-ChrisM2
Community Manager
•
1.2K Posts
0
February 23rd, 2026 13:58
All, a GHN support case must be created for every Inspiron 13 5310 service tag number.
Click the blue GHN (Get Help Now) on the right to start a private live chat session. The GHN AI should not stop you from chatting with an agent. GHN agents should not turn you away if out of warranty. Share with them the private Service Tag, issues, this thread link, and all of your troubleshooting. This will in turn generate a unique Technical Support case for your unique Service Tag. Mention to the Dell Technical Support agent that they should read SFDC article =
000427561 No Boot or Memory Errors After Updating to BIOS Version 2.38.0 on the Inspiron 5310 and Vostro 5310
(edited)
user_7c535a
1 Rookie
•
1 Message
1
February 21st, 2026 20:46
DaveInAZ
1 Rookie
•
1 Message
2
February 21st, 2026 22:29
I have this problem from last summer - THE BIOS IS NO GOOD, IT CORRUPTS THE RAM TIMING. I was getting blue screens constantly every 2-6 hours. It also wouldn't pass the dell or microsoft ram test.
I thought my RAM went bad but I spent a good 3 hours of my life rolling the bios back to one from 2024 with a USB stick and having to keep changing bios settings to be able to roll back. I think most people can't do this.
DELL RECALL THIS BIOS!! I am so mad it is trying to reinstall it again.
BDHodge
1 Rookie
•
8 Posts
1
February 22nd, 2026 01:29
@DaveInAZ It's appalling the this BIOS issue has been known for 6-7 months and there's not an easy fix from within Windows. There should be a way to roll back the BIOS from within Windows. No one should have to boot to a flash drive and upgrade to one BIOS and then go into the BIOS and downgrade to another. Are you kidding me??
What's really bad is Dell gave this BIOS to Microsoft and they rolled it out to everyone. What happened to BIOS being an OPTIONAL update??
I'm so angry and it's not even my computer, it belongs to a client, but they're too far away, I can only work on it remotely. Windows works, it just reboots two to three or times a day.
Tesla1856
8 Wizard
•
17.5K Posts
1
February 22nd, 2026 16:10
That is why I keep UEFI-Firmware Capsule Updates DISABLED in BIOS options.
I'll provide the extra effort and work to do them myself ... to avoid situations like this.
It's old school, but I still tend to hang-back a bit on BIOS-Firmwares, and still generally only update when I must or for a good reason.
(edited)
falconhoof
1 Rookie
•
21 Posts
1
February 23rd, 2026 00:39
Dear Dell management - per this other thread here, it is important for proper containment actions to be implemented ASAP. Please confirm it is no longer being sent out?
You should make sure that you have stopped breaking laptops with a known problem.
It seems it's still going out if posts are to be believed, and attempts to change BIOS still show re-install of 2.37.0 by Windows.
Nobody wants a community-driven "solution" and a revoked BIOS file with maybe a 50% success rate, but folks trying it at this stage have a paperweight on their desk and literally nothing left to lose. I was shopping for a new computer in-between attempts to recover my 5310.
I'm sure the engineers are having a royally <Prohibited word or character substitution used. See the Forum Code of Conduct. DELL-Admin> week/month/quarter(s) so management needs to get them more help and reprioritize other deadlines so they actually have the time & resources to address this problem.
Please and thank you.
(edited)
falconhoof
1 Rookie
•
21 Posts
0
March 18th, 2026 18:31
@DELL-Nat M Thank you. Any advice for those who managed to stabilize on an older BIOS (2.30 for me after 2.37-->2.38 recovery file on USB --> 2.30 via .exe file) and whether it's OK to go directly to 2.40 from 2.30?
Anything to avoid? I'm debating whether I want to risk trying it.
Also, the folks on the other thread (RAM issues starting at 2.34, continued to 2.37) reported at least one person who was unable to recover their laptop, so clear tips / recommendations to have it go as smoothly as possible would be appreciated.
DELL-Nat M
Community Manager
•
3.6K Posts
1
March 19th, 2026 13:18
@falconhoof
Hi, per the engineering team, there should be no issue updating directly from BIOS 2.30 to 2.40. Based on internal logs, BIOS 2.40 has improved stability for approximately 90% of affected systems.
Please keep in mind that system behavior can vary depending on individual configurations, hardware upgrades, and installed software, so we recommend proceeding at your own discretion.