How to Fix DGX Spark Kernal Panic on Boot: NVIDIA DGX Spark Recovery – Bypassing the Broken Windows USB Script
Incident Date: April 27, 2026 | Hardware: NVIDIA DGX Spark (GB10 Grace Blackwell)
Honestly – super frustrating to plugin and boot a $4,700 piece of equipment to get an immediate Kernel Panic. AND (insult to injury) to find our there is a bug in creating a USB Recovery Boot Drive from Windows! Thank god for Opus being able to basically write its own recovery disc from the Nvidia source lol. Though, I have to admit there’s definitely a certain anarchist glee in tearing apart a broken “official” enterprise script and just rebuilding it by hand with my good buddy Opus (all to make the machine do what it’s supposed to in the first place– looking at your NVISIA AI). Having a solid agent in your court always pay off in the end.
Set-Disk failure, tore apart the script source to identify the hidden UEFI validation markers, and mapped out the manual diskpart bypass to get the DGX Spark clustered and running.The Problem: Kernel Panic on First Boot
Out of the box, after completing the initial installation, the DGX Spark may fall into an immediate boot loop with the following kernel panic:
KERNEL PANIC! Please reboot your computer. VFS: Unable to mount root fs on unknown-block(0,0)
This occurs when the initramfs is corrupted or interrupted during the first-boot setup, leaving the kernel unable to locate the NVMe drive to boot the OS.
The Trap: NVIDIA’s Broken Recovery Script
NVIDIA provides a recovery image (e.g., dgx-spark-recovery-image-1.120.38.tar.gz) and a Windows script (CreateUSBKey.cmd / CreateUSBKey.ps1) to flash it to a USB drive. However, on many Windows systems and modern USB drives, the script crashes with a Set-Disk : Not Supported or InvalidOperation error.
The script attempts to force an MBR partition style using high-level PowerShell cmdlets that frequently fail on uninitialized or large-capacity drives, destroying the partition table without actually writing the recovery files.
The Solution: Manual USB Creation
By analyzing the failing .ps1 script, we can see that the DGX Spark’s UEFI validation checks for three specific things before it will accept a recovery USB:
- A FAT32 partition labeled exactly
BOOTME. - The partition must be marked as Active.
- A hidden text file at
EFI\BOOT\recovery.txtcontaining the wordRECOVERY.
Step-by-Step Manual Bypass
Open an Administrator PowerShell window and use diskpart to prepare the drive (replace X with your USB disk number):
diskpart list disk select disk X clean create partition primary size=31000 format fs=fat32 quick label=DGXRECOVERY assign letter=R exit
Next, extract the NVIDIA .tar.gz file and copy the contents of the usbimg.customer\usb\ folder to your newly formatted R:\ drive:
xcopy "C:\Path\To\Extracted\usbimg.customer\usb\*" R:\ /E /H /Y
Finally, apply the UEFI validation markers that the broken script failed to write:
# 1. Create the missing marker file "RECOVERY" | Out-File -FilePath "R:\EFI\BOOT\recovery.txt" -Encoding ASCII -NoNewline # 2. Set the partition active (bootable) Set-Partition -DiskNumber X -PartitionNumber 1 -IsActive $true # 3. Rename the volume label to BOOTME label R: BOOTME
Hardware Nuance: The Keyboard Issue
Result
Plug the USB into the DGX Spark, power on, and press Esc to enter the UEFI. Navigate to the Boot Override menu and select the USB drive. The DGX will validate the manually created markers, pass all checks, and restore the system to factory defaults.