Reference only

Windows error 1455: paging-file exhaustion is not CUDA out of memory

This Windows error concerns committed system memory. It should not be treated as VRAM exhaustion or proof that a safetensors file is corrupt merely because it appears during model loading.

Symptoms and scope

This Windows error concerns committed system memory. It should not be treated as VRAM exhaustion or proof that a safetensors file is corrupt merely because it appears during model loading.

Error fragments for search; IDs, values and filenames may vary:

The paging file is too small for this operation to complete
os error 1455

Source-supported context

Microsoft names 1455 ERROR_COMMITMENT_LIMIT; its page-file guide relates the commit limit to RAM plus page files. A separate Windows note describes allocation failures while an automatic page file grows, so system-managed sizing alone does not prove adequate headroom. ComfyUI issue #7069 records the error but no verified repair. Source 1 Source 2 Source 3 Source 4 ComfyUI startup options

Cases to distinguish

1. The page file is disabled, too small, short on disk space, or too slow to grow during an allocation burst.

2. Several memory-heavy processes bring committed memory close to the system limit.

3. Loading multiple models, or using an offload mode that keeps weights in CPU memory, can increase system-memory pressure; other offload modes may behave differently.

Diagnostic sequence

The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.

Step 1. Inspect the committed-memory figures in Task Manager and free space on the page-file disk.

Step 2. Save work, stop unnecessary generation instances and memory-heavy applications, then record the peak on the same small workflow.

Step 3. Compare peak committed memory with the commit limit, then inspect Windows virtual-memory settings and page-file disk space. System-managed sizing can still lag a rapid allocation; record the original configuration before any change and restart when Windows requests it.

Step 4. If headroom remains insufficient, reduce simultaneous models or workload size. Do not use cleanup scripts that indiscriminately remove system files or active outputs.

Completion check

Error 1455 disappears, committed memory retains headroom and the task progresses. A new CUDA OOM belongs to a separate GPU diagnostic branch.

Limitations and cautions

There is no single page-file size appropriate for every machine. Paging consumes disk and affects performance; it is not equivalent to adding physical RAM or VRAM.

Original sources

Sources and English wording rechecked 2026-09-25. No Windows configuration change, memory benchmark, GPU run or repair guarantee is supplied.

Didn't solve it?

Check the next possible cause

The same symptom can come from a different cause. Work through these related entries in order.

  1. CUDA out of memory: separate model loading, sampling and VAE decodingCUDA out of memoryIdentify the stage that requested GPU memory before reducing the workload. Advertised VRAM, weight-file size and the memory available to this particular task are different quantities.
  2. No space left on device: check caches, temporary files and output volumesNo space left on deviceA target output disk can have free space while a download cache, temporary directory, container writable layer or another mounted filesystem is full.
Paste your full log into the error finder

Was this page helpful?

Anonymous. Only a yes/no counter is stored; no account, IP address or device details.

Sources & references

Microsoft error-code, page-file and slow-growth guidance plus pinned ComfyUI startup options rechecked 2026-09-25. Issue #7069 is an individual report; no Windows or GPU repair was run by this site.

01Windows page file introductionSource checked: 2026-09-2502Windows error code 1455Source checked: 2026-09-2503Windows slow page-file growthSource checked: 2026-09-2504ComfyUI issue #7069 (individual report)Source checked: 2026-09-2505ComfyUI v0.37.0 startup optionsSource checked: 2026-09-25

Report an issue · 5865a114-cb70-54bf-8e4b-e6a7afb9f03f