UNSOLVED

gustavort81e

updated

1 year ago

G

gustavort81e

1 Rookie

•

3 Posts

•

2 Points

0

96

November 5th, 2025 14:27

XPS 8920 won't POST after clearing NVRAM in UEFI Shell - no video, no USB power, no recovery

Hi everyone,
I own a Dell XPS 8920 (motherboard 0DF42J, Intel H270 chipset) and after running the command dmpstore -d -all in the UEFI Shell to clear EFI variables, the system stopped booting completely.

Current behavior:

  • System powers on, fans spin for a few seconds, then shut off.
  • CPU and PCH get warm.
  • No video output on any port (HDMI/DP).
  • USB ports have no power (keyboard and flash drive LEDs stay off).
  • No POST beeps, even with RAM removed.
  • Tried full CMOS reset (battery out + RTCRST jumper).
  • Tried Ctrl + Esc + BIOS_IMG.HDR / BIOS_IMG.RCV recovery on FAT32 USB — no response.
  • PSU tested separately and is fine.

It looks like the BIOS firmware enters a pre-POST loop — possibly due to a corrupted NVRAM block or ME initialization failure.

I’d really appreciate advice on:

  1. Any alternate method to trigger BIOS Recovery (jumper, specific USB port, key combo, etc.).
  2. Availability of a complete .bin image of BIOS v1.1.15 for flashing with a CH341A + SOIC8 clip.
  3. Confirmation from a Dell modder or engineer whether the 0DF42J board has a secondary recovery point or backup descriptor.

Thanks in advance for any insight or dump file that could help bring this board back to life.

—

  • anne_droid

    6 Operator

    •

    2559 Posts

    •

    9467 Points

    0

    0

    Posted November 6th, 2025 00:11

    Hi

    The internet reports ...

    (Although I note you have tried most, if not all the steps below)

    If a Dell XPS 8920 won't POST after clearing NVRAM via the UEFI shell—resulting in no video output, no USB power, and no ability to recover—it's likely a serious BIOS or firmware corruption issue, often caused by an incomplete NVRAM clear or a Management Engine (ME) initialization problem. Here are the recommended steps to attempt recovery:​

    Recovery Steps

    • Disconnect the power cable and remove the CMOS battery for at least one minute to clear residual power and further reset the NVRAM.​

    • Reinsert the CMOS battery, reconnect power, and try powering on the system.

    • If you see no change, perform a Real-Time Clock (RTCRST) jumper reset: Move the two-pin jumper from the password pins (PSWD) to the RTCRST pins for about 5 seconds, then return the jumper to the PSWD pins, reconnect the cover, and power on.​

    • If the system still won't POST, use the BIOS recovery procedure:

      • On a working PC, download the latest BIOS update for your XPS 8920 from Dell's support website.​

      • Extract the recovery image (BIOS_IMG.rcv) using the command line flag /writehdrfile and copy it to a FAT32-formatted USB drive’s root directory.

      • Insert this USB drive into the affected XPS 8920.

      • Power on the XPS 8920 and immediately hold down CTRL + ESC; if successful, you’ll see the BIOS recovery screen—select the “Recover BIOS” option.​

      • If CTRL + ESC does not work, unplug power, remove the CMOS battery for a longer period (~30 minutes), then retry with the USB recovery drive inserted.​

    • If none of these steps restore functionality, the motherboard may be physically damaged or irrecoverably corrupted, requiring replacement or professional servicing.​

    • Attempt booting with only minimal hardware: one stick of RAM, no peripherals, and disconnecting non-essential drives.​

    • Dell also recommends checking for POST LED error codes (e.g., amber blinking patterns) which may point to specific hardware faults.​

    • For firmware or board-level issues, technical servicing may be needed—the system may need a new motherboard or BIOS chip.​

    If these steps do not work, contacting Dell technical support is essential for next-level diagnosis or arranging repairs.​

    (edited)

      Kind Regards  

                                         

      anne_droid

     

    User uploaded image

     

  • gustavort81e

    1 Rookie

    •

    3 Posts

    •

    2 Points

    0

    0

    Posted November 6th, 2025 01:04

    Unfortunately I have tried all these steps I left it without the cmos all night, reset by jumper, the computer seems to turn on normal but it does not give video, It does not start the usb ports, the power light turns white after a minute it turns off by itself. I don't think there will be any way to escape a bios rewrite. I'm impressed that a desktop of this level doesn't have a fallback to uefi that is something accessible to all operating systems

    (edited)

  • anne_droid

    6 Operator

    •

    2559 Posts

    •

    9467 Points

    0

    0

    Posted November 6th, 2025 11:46

    Can I just double check

    XPS8920_1.0.23.exe  seems to be the latest version, not the 1.1.15 you mention. 

    Am I looking at the wrong device?

      Kind Regards  

                                         

      anne_droid

     

    User uploaded image

     

  • gustavort81e

    1 Rookie

    •

    3 Posts

    •

    2 Points

    0

    0

    Posted November 6th, 2025 14:35

    @anne_droid​ Yes I wrote it wrong sorry the most updated bios for xps 8920 and q 1.0.23

  • anne_droid

    6 Operator

    •

    2559 Posts

    •

    9467 Points

    0

    0

    Posted November 7th, 2025 09:37

    Hi

    The internet reports ....

    To rewrite or replace UEFI info after running the dmpstore -d -all command in Linux, you typically need to modify the EFI variables that dmpstore reads. The dmpstore command dumps the firmware's non-volatile variables (NVRAM), but it itself is a read-only dump tool.

    To actually write or replace the UEFI variables, you need a tool or command that can set EFI variables. The common approach is:

    1. Use an EFI application called setup_var.efi which can modify specific variables inside the UEFI setup binary blob. This tool lets you change values at specific offsets similar to what dmpstore displayed.

    2. Alternatively, use the UEFI Shell commands like setvar or possibly mm (memory modify) to directly modify memory or EFI variables. However, setvar is often used for setting basics variables for EFI booting, and mm is low-level memory edit.

    3. The EFI variable is a binary blob (like "Setup"), and the tools modify the binary content at certain offsets as shown by the dmpstore output.

    Steps to rewrite UEFI info after dmpstore dump:

    • Identify the variable and offset you want to modify from the dmpstore -d -all output.

    • Use setup_var.efi in UEFI shell to set this variable value at offsets.

    • The command looks like: setup_var <offset> <value> inside UEFI shell.

    • If using Linux, you can write EFI vars with Linux tools like efivar or efi-updatevar but need to be very careful.

    In summary, dmpstore is for dumping EFI variables but to rewrite them you need a specialized tool like setup_var.efi or Linux EFI variable interfaces to safely modify the NVRAM EFI variables from the shell. Always back up EFI variables before modification because wrong changes can brick firmware.

    This workflow reflects the usual method of inspecting with dmpstore and writing back with specialized EFI shell tools or Linux EFI variable utilities.​

    So perhaps a little research on HOW2 use setup_var.efi in a Linux Live situation, but I suspect that the system is probably bricked and I am missing the point with possible solutions.

      Kind Regards  

                                         

      anne_droid

     

    User uploaded image