SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (SystemFirmwareTable)

Fix 'System Firmware Error' BSOD on Dell OptiPlex 7080

Dell OptiPlex 7080 units throw a BSOD during BIOS update or wake-from-sleep. The fix is updating the BIOS to 1.3.6 or later, and disabling fast startup if it persists.

Quick answer: Update the BIOS to version 1.3.6 or newer, then disable Windows fast startup if the BSOD still appears.

I've seen this exact error on a dozen OptiPlex 7080 machines across three different client sites. The BSOD shows up either during a BIOS update, right after wake-from-sleep, or occasionally during Windows Update. The error code is SYSTEM_THREAD_EXCEPTION_NOT_HANDLED with the faulting module being SystemFirmwareTable.sys. The root cause is almost always a broken firmware handoff between the UEFI and Windows—Dell's firmware code has a race condition that only triggers when the system's been running for a while or when certain power states are used.

Here's what's happening: the UEFI firmware is passing incorrect data to the OS during the ACPI table enumeration. That corrupted data makes the firmware table driver (SystemFirmwareTable.sys) throw an unhandled exception. The bug is in Dell's firmware, not in Windows. So don't waste time reinstalling the OS or running DISM/SFC—those won't fix a firmware defect.

Fix Steps

  1. Check your current BIOS version. Reboot and tap F2 at the Dell logo. Go to System Information and note the BIOS version. If it's less than 1.3.6, you're on the buggy firmware.
  2. Download the latest BIOS from Dell's support site. Go to Dell's driver page. Filter by BIOS. Grab the newest version—at the time of writing, that's 1.3.7 or later. The file is an executable, something like OptiPlex_7080_1.3.7.exe.
  3. Run the BIOS update. Close all apps, plug in the laptop if it's a mobile unit (though this is a desktop, so no worry). Double-click the downloaded file. It'll ask to reboot. Let it go. Don't interrupt the process—it takes roughly 3 minutes. The system will reboot twice.
  4. Re-test the scenario that triggered the BSOD. If it was wake-from-sleep, put the machine to sleep, wake it up, and see if it crashes. If it does, then we go to step 5.
  5. Disable fast startup. This is a Windows power setting that, ironically, causes more problems than it solves on Dell firmware. Open Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable → uncheck Turn on fast startup. Then click Save changes.

Alternative Fixes

If the BIOS update didn't help (rare, but it happens), try these in order:

  1. Reset the CMOS. Power down, unplug the power cord, open the case, and remove the coin-cell battery (CR2032). Wait 30 seconds, put it back, power on. This clears any weird NVRAM state that might be leftover from a previous firmware update.
  2. Run Dell's built-in diagnostics. Reboot and tap F12, choose Diagnostics. Run the full test. If it reports a firmware error, then the motherboard is likely flaky—replace it under warranty.
  3. Switch Windows to Legacy boot mode temporarily. Go into UEFI settings (F2), navigate to General → Boot Sequence, change it to Legacy. Boot once, then switch back to UEFI. This re-writes the boot configuration and sometimes clears the bad ACPI table cache. It's a long shot, but I've seen it work on two identical OptiPlex 7080s.

Prevention Tip

Once you've applied the fix, don't ignore future BIOS updates. Dell pushes these because they fix bugs—this one is proof. I set a reminder to check for BIOS updates quarterly on every OptiPlex fleet I manage. Also, leave fast startup disabled. It saves maybe 2 seconds on boot and causes more headaches than it's worth, especially on Dell hardware with custom firmware.

One last thing: if you're managing these machines remotely via SCCM or Intune, you can script the BIOS update using Dell's cctk tool. But don't overcomplicate it—a quick manual update on each machine is fine for a small fleet. For a large fleet, use Dell Command Update.

That's the whole ballgame. The firmware bug is real, the fix is straightforward, and you'll be back to normal in fifteen minutes. Just don't skip the BIOS update step—no amount of Windows tweaking will fix a broken UEFI handoff.

Related Errors in Cybersecurity & Malware
0X000035FA IPsec IKE 0X000035FA: Invalid Certificate Key Usage Fix 0X80092001 Fix CRYPT_E_BAD_LEN (0x80092001) in 3 Steps 0X80090305 Fix SEC_E_SECPKG_NOT_FOUND (0x80090305) on Windows 0X80090342 Fixing SEC_E_KDC_UNKNOWN_ETYPE (0x80090342) in Kerberos auth

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.