Skip to content

die-to-die thermal delta between primary die and secondary die emergency throttle

A Blackwell B200 module detected an unsafe temperature difference between its two dies and entered emergency throttling. The delta points to uneven cooling or contact, not ordinary workload-wide thermal saturation. This entry explains how to confirm the cause, apply the fix, and separate it from adjacent blackwell failures.

Quick answer

die-to-die thermal delta between primary die and secondary die emergency throttle means A Blackwell B200 module detected an unsafe temperature difference between its two dies and entered emergency throttling. The delta points to uneven cooling or contact, not ordinary workload-wide thermal saturation. Preserve the first preceding error, then run the targeted control below.

Hardware#blackwell#b200#dual#die#thermal#delta

What this failure is

The literal signature is "die-to-die thermal delta between primary die and secondary die emergency throttle". It is a hardware failure associated with Blackwell, Grace Hopper, NVLink fabrics, and liquid cooling. The line identifies the failing operation or subsystem, while the surrounding evidence decides whether it is the initiating fault or a downstream symptom.

Live diagnosis, no signup

Is this what broke your run? Paste your log.

You're reading about die-to-die thermal delta between primary die and secondary die emergency throttle. Paste your own crash log or traceback below and get the real root cause for YOUR run, not this generic entry. No account, no card. Logs are masked at ingress and never saved to account history.

training_logs.txt
No log to hand? Try one:
3 free diagnoses/day

Want 14 days of full access?

Request a free trial code for unlimited diagnoses, alerts, history, and follow-up questions. No credit card.

Request 14-day trial

Why it happens (the mechanism)

A Blackwell B200 module detected an unsafe temperature difference between its two dies and entered emergency throttling. The delta points to uneven cooling or contact, not ordinary workload-wide thermal saturation. The failure becomes visible at this call site because the operation first requires the missing resource, valid state, healthy peer, or correct result. Earlier log lines and a known-good control carry more causal value than the final wrapper exception.

What you'll observe

  • The workload stops or loses forward progress after emitting "die-to-die thermal delta between primary die and secondary die emergency throttle".
  • A retry on the same configuration reproduces the failure because the causal state has not changed.
  • The outer framework exception can hide the rank, node, allocation, or dependency that failed first.
  • Increasing timeouts or reducing workload size can suppress the symptom without correcting the cause.

Common symptoms and what they mean

SymptomWhy it happens
die-to-die thermal delta between primary die and secondary die emergency throttleA Blackwell B200 module detected an unsafe temperature difference between its two dies and entered emergency throttling. The delta points to uneven cooling or contact, not ordinary workload-wide thermal saturation.
The same operation fails at a consistent stage of Blackwell, Grace Hopper, NVLink fabrics, and liquid cooling.The decisive evidence is the first log line that precedes "die-to-die thermal delta between primary die and secondary die emergency throttle" and differs from a healthy run.
The first related warning appears before the final exception and names the causal subsystem.A nearby failure remains a competing hypothesis until a control separates configuration, capacity, transport, and hardware causes.
A known-good control changes one variable and either reproduces or clears the failure.A Blackwell B200 module detected an unsafe temperature difference between its two dies and entered emergency throttling. The delta points to uneven cooling or contact, not ordinary workload-wide thermal saturation.

Which systems are affected

  • Blackwell, Grace Hopper, NVLink fabrics, and liquid cooling
  • production-shaped multi-accelerator workloads
  • containerized and bare-metal deployments of the same stack

How to confirm this is the problem

Apply the following checklist to a small reproduction: each box below is a positive signal that you are looking at this exact failure rather than a sibling in the same taxonomy.

  • Find the first occurrence of "die-to-die thermal delta between primary die and secondary die emergency throttle" and preserve at least 100 lines before it.
  • Identify which rank, node, device, or process emitted the first related warning.
  • compare both die sensors under idle and a controlled load, then inspect cold-plate contact, coolant flow, and module seating through the approved service path.
  • Repeat the same input after the targeted change and require the signature to disappear.
  • Resume from latest checkpoint on a thermally healthy GPU only after the control passes.

Example training logs (fingerprint)

training.log (synthetic fingerprint)
die-to-die thermal delta between primary die and secondary die emergency throttle

Timestamps and exact values vary across runs, but the pattern. An info-level start, an early WARN, an ERROR carrying the symptom. Is the actual fingerprint you should alert on. The Denpex platform flags this combination automatically.

The fix and the prevention pattern

The root cause is on this page and stays free. A free account adds the exact remediation steps, keeps your diagnoses instead of discarding them, and unlocks the fix on every entry in the encyclopedia.

Sign up free. Unlock the full analysis

No credit card · 3 free diagnoses · Instant access

Why the recommended fix works

drain the GPU and preserve per-die temperature, clock, power, and cooling telemetry before changing load or power state. This changes the condition in the causal diagnosis instead of hiding the outer exception. The repeated control proves ownership before recovery from latest checkpoint on a thermally healthy GPU.

Code examples

snippet
# Preserve evidence before restarting
dmesg -T | grep -iE 'NVRM|Xid|AER|NVLink|ECC'
nvidia-smi -q
dcgmi diag -r 3

# Find the exact signature in the complete log
rg -n -F -- "die-to-die thermal delta between primary die and secondary die emergency throttle" <log-file>

Adapt the snippet to your framework. The same pattern holds for PyTorch Lightning, Hugging Face Trainer, DeepSpeed, Megatron-LM, and vLLM training wrappers. Where the wrapper exposes a config flag (for examplelr_scheduler_type in Trainer), prefer the flag over the imperative API to keep the schedule declarative and reproducible.

Best practices by model family

Model / StackRecommendationNotes
First responsePreserve the first failureKeep the context before "die-to-die thermal delta between primary die and secondary die emergency throttle" so aggregation does not erase causality.
ConfirmationChange one variableUse a known-good node, rank, input, or configuration as the control.
RecoveryResume from latest checkpoint on a thermally healthy GPUResume only after the literal signature no longer appears in the same control.

With the fix vs without the fix

DimensionWith the fixWithout the fix
EvidenceFirst preceding error and one controlled comparisonOnly the final aggregated exception
Fixdrain the GPU and preserve per-die temperature, clock, power, and cooling telemetry before changing load or power state.Retrying the unchanged workload
Exit criterion"die-to-die thermal delta between primary die and secondary die emergency throttle" is absent in the repeated controlThe job happened to run once

Real engineering notes

Treat "die-to-die thermal delta between primary die and secondary die emergency throttle" as a search key and an investigation checkpoint, not as proof of every cause associated with the phrase. The high-value evidence is what changed immediately before it and whether the failure follows the workload, node, or configuration.

Visual fingerprint

Decision path for die-to-die thermal delta between primary die and secondary die emergency throttle
literal error captured
        |
        v
find first preceding failure
        |
        v
run one known-good control
        |
        +-- follows workload --> inspect input or configuration
        +-- follows node ------> inspect hardware or platform
        +-- disappears --------> validate the targeted fix
The control separates workload, configuration, and node ownership before recovery from latest checkpoint on a thermally healthy GPU.

Diagnose this failure in VS Code

Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.

Install the free VS Code extension

Root cause

  • A Blackwell B200 module detected an unsafe temperature difference between its two dies and entered emergency throttling. The delta points to uneven cooling or contact, not ordinary workload-wide thermal saturation.
  • The decisive evidence is the first log line that precedes "die-to-die thermal delta between primary die and secondary die emergency throttle" and differs from a healthy run.
  • A nearby failure remains a competing hypothesis until a control separates configuration, capacity, transport, and hardware causes.

The fix and how to prevent it

Unlock the full remediation runbook

14 days on the Scale plan, up to 50 diagnoses a day. Step-by-step remediation, the RMA evidence payload, and multi-node correlation on your own logs. No card, and it does not roll into a subscription.

We send a single-use code to that address. Company addresses only, the free diagnoses above stay open to everyone, and keeping trials to work email is how we keep them open.

Frequently asked questions

Twelve targeted questions that engineers and on-call staff most commonly ask about this failure.

What does "die-to-die thermal delta between primary die and secondary die emergency throttle" mean?
A Blackwell B200 module detected an unsafe temperature difference between its two dies and entered emergency throttling. The delta points to uneven cooling or contact, not ordinary workload-wide thermal saturation.
Is this line always the root cause?
No. It can be the direct failure or the point where an earlier failure becomes visible. The first preceding error and a controlled comparison decide which.
What should I collect before restarting?
Collect complete log context, the emitting rank or node, component versions, resolved configuration, and the diagnostic output shown above.
What is the fastest confirmation?
compare both die sensors under idle and a controlled load, then inspect cold-plate contact, coolant flow, and module seating through the approved service path.
How do I prevent it from recurring?
monitor per-die delta in addition to absolute temperature and qualify cooling uniformity after module or cold-plate service.

Don't just read the fix, diagnose your run

The encyclopedia tells you what went wrong. Denpex tells you what went wrong in YOUR training run. With your logs, your config, and your stack.