Thaiphoon Burner

Thaiphoon Burner is a hardware utility built for one specific purpose. It reads and rewrites the SPD EEPROM firmware that lives on every memory module in your machine. Each DIMM ships with a small chip that stores its specifications, supported timings, voltage tables, and XMP profiles.

The motherboard reads that chip at boot to know what kind of memory it has. Thaiphoon Burner lets you read it back the same way, decode every byte of it, and if you choose, write changes back to it.

This is a tool for memory overclockers, hardware troubleshooters, and the kind of PC builder who wants to know whether their RAM is actually Samsung B-die or just labeled as such. The audience is narrow, but for that audience, no other utility in this category gets the same level of detail or the same depth of editing control.

Showshock Softnology has been developing it for over twenty years, and it is the tool overclockers reach for when they need to know what is actually inside a stick.

What SPD is and why this tool exists

SPD stands for Serial Presence Detect. It is a small EEPROM chip soldered onto every memory module since the late 1990s. It stores 256 or 512 bytes of structured data about the module. Manufacturer, part number, serial number, supported speeds, JEDEC timing tables, XMP profiles (Intel), EXPO profiles (AMD), legacy EPP profiles (NVIDIA), voltage requirements, and the date and lot the module was produced.

The BIOS reads it at every POST, picks a JEDEC profile, and configures the memory controller to match. If you enable XMP in BIOS, it reads the higher-speed profile from a separate region of the same chip.

The problem is that most tools that show “memory information” only show what the BIOS exposed at boot. Thaiphoon Burner talks directly to the SMBus and reads the SPD chip in real time, byte by byte. The output is far more granular than what you get from a tool like CPU-Z, which decodes a subset of the SPD into a readable summary.

Thaiphoon Burner gives you the entire dump, including fields the BIOS ignores and fields the manufacturer probably did not intend for you to inspect.

Identifying the memory IC under the heatspreader

If you have spent any time in the RAM overclocking community, you have heard people debate Samsung B-die vs. Hynix CJR vs. Micron Rev.E vs. SK Hynix M-die. These are the DRAM ICs inside the module itself, the chips under the heatspreader. They behave differently under overclocking. B-die loves tight timings at low voltage. Hynix likes higher voltage and tolerates higher frequencies. Micron sits somewhere in between depending on revision.

The manufacturer rarely tells you which ICs are inside a kit, and they often switch ICs mid-production without changing the part number. Thaiphoon Burner reads enough metadata from the SPD to identify the IC almost every time.

The report tells you the IC manufacturer, the die revision, the production date, and (if the kit was made by a reputable vendor) the specific part, down to the build week. This is the feature that sells the tool. Most users open it exclusively for this, save the report as text, and close the window.

For people working with AMD platforms, the report flows directly into Ryzen DRAM Calculator, which takes the IC type as input and suggests timing sets known to be stable on that silicon. The pairing of the two tools has been the standard Ryzen memory overclocking workflow since 2018, with AMD Ryzen Master often layered on top for tuning without rebooting into BIOS.

Reading and decoding XMP profiles

XMP (Extreme Memory Profile) is Intel’s standard for storing higher-speed presets in SPD beyond the conservative JEDEC defaults. When you enable XMP in BIOS, you are telling the motherboard to use the values from this section of the chip instead of the safe ones. Thaiphoon Burner decodes the XMP region in full.

You see every timing parameter (CAS, tRCD, tRP, tRAS, tRFC, all the way down to the obscure secondary and tertiary timings) along with the voltage and the maximum frequency the profile targets.

If your XMP is broken (some modules ship with corrupted XMP, others get scrambled by RGB lighting software touching the SMBus), the report makes the corruption visible. You see exact byte values, you see CRC mismatches highlighted, you see when a CL14 kit is claiming CL1 because of a flipped bit. Fixing that is the next step.

Editing SPD and the rewrite workflow

This is where things get serious. Thaiphoon Burner includes a hex editor for the raw SPD bytes and a higher-level timing table editor that converts human-readable timings into the correct binary representation. You can modify any field and write it back to the chip. Common reasons people do this include restoring a corrupted XMP profile from a known-good dump, copying a working SPD from one stick to another that came with bad firmware, raising the XMP voltage limit on a kit that the BIOS will not overvolt, or building a custom profile that the kit shipped without.

The write process flashes the EEPROM directly. There is no undo. If the dump is wrong or you misread which byte means which, the result is a module that no longer identifies correctly at POST, which usually means the system refuses to boot until you swap to a known-good stick. The fix exists (reflash with a good dump from a working stick), but it requires actually having a working stick and a system to boot, and it is the kind of mistake people learn from once. Back up the original SPD with the dump-to-file feature before writing anything. It takes one click.

There is no excuse for not doing it.

Risks and limitations

The risk of bricking a module is real but bounded. Bad writes affect that one module, not the rest of the system. Pull the offending stick, boot on a known-good one, and you have your machine back. The reflash procedure to restore is documented step by step in the usual overclocking forums.

The bigger limitation is software compatibility. The SMBus on modern motherboards is contested. Antivirus software, RGB lighting controllers, vendor utilities like ASUS Aura or Corsair iCUE, and even open-source RGB tools fight for exclusive access. If something else is talking to the SMBus when Thaiphoon Burner tries to read, the report comes back as garbage. You see wildly wrong values, missing fields, or read errors.

The fix is to stop the lighting service before reading, which scares newcomers off in exactly the way you would expect.

Driver requirements have also been a moving target. Thaiphoon Burner uses a kernel-level driver to access the SMBus, and depending on security settings (HVCI, Memory Integrity, vendor signing requirements), the driver may need to be allowed manually. For systems that take signing seriously, that is a real obstacle.

DDR5 support arrived but lagged the launch of the standard. If you are reading SPD on bleeding-edge modules, check that the build supports the relevant IC family.

The DDR4 support is rock-solid. DDR2, DDR3, and DDR4 are all decoded fully. PC SDRAM and the old DDR1 standard are also handled, which is occasionally useful for working on retro systems.

Conclusion

Thaiphoon Burner is for two kinds of users. The first is the memory overclocker who needs to know exactly which DRAM ICs are inside a kit before deciding how aggressively to push it. For this user, five minutes with the application reveals which silicon is actually inside the module, something no heatspreader sticker will tell you. Pair it with Memtest86+ for validation after timing changes, and you have the workflow the Ryzen and Intel overclocking communities have used for years.

The second is the troubleshooter dealing with a misidentified or corrupted module, where a bad SPD has caused booting issues, XMP failures, or instability that no amount of BIOS tweaking fixes.

That user accepts the risks that come with writing to EEPROM directly. Nothing else in this category goes as deep, and the niche has stayed niche enough that no one else has tried. If you ever need to touch SPD, this is where you end up.