# Training "never finishes" or system crashes using PyTorch - GPU has memory allocated but always has 0% utilization using DataLoader

**URL:** <https://discuss.pytorch.org/t/training-never-finishes-or-system-crashes-using-pytorch-gpu-has-memory-allocated-but-always-has-0-utilization-using-dataloader/170801>\
**Category:** data\
**Created:** [January 22, 2023, 2:16am UTC](https://discuss.pytorch.org/t/training-never-finishes-or-system-crashes-using-pytorch-gpu-has-memory-allocated-but-always-has-0-utilization-using-dataloader/170801 "2023-01-22T02:16:51Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![ptrblck](https://discuss.pytorch.org/user_avatar/discuss.pytorch.org/ptrblck/32/1823_2.png) [@ptrblck](https://discuss.pytorch.org/u/ptrblck)\
**Post date:** [January 31, 2023, 5:29am UTC](https://discuss.pytorch.org/t/training-never-finishes-or-system-crashes-using-pytorch-gpu-has-memory-allocated-but-always-has-0-utilization-using-dataloader/170801/32 "2023-01-31T05:29:10Z")

</div>

So far everything you’ve described points to a data loading bottleneck (including the GPU util. peaks when data is available). For a general advice on fixing data loading bottlenecks look at [this post](https://discuss.pytorch.org/t/how-to-prefetch-data-when-processing-with-gpu/548/19).

---

_[View the full topic](https://discuss.pytorch.org/t/training-never-finishes-or-system-crashes-using-pytorch-gpu-has-memory-allocated-but-always-has-0-utilization-using-dataloader/170801)._