# Bitsandbytes and CUBLAS\_STATUS\_NOT\_INITIALIZED error

**URL:** <https://discuss.huggingface.co/t/bitsandbytes-and-cublas-status-not-initialized-error/167455>\
**Category:** Beginners\
**Created:** [August 20, 2025, 5:22pm UTC](https://discuss.huggingface.co/t/bitsandbytes-and-cublas-status-not-initialized-error/167455 "2025-08-20T17:22:32Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [August 28, 2025, 12:41pm UTC](https://discuss.huggingface.co/t/bitsandbytes-and-cublas-status-not-initialized-error/167455/18 "2025-08-28T12:41:58Z")

</div>

> on Kaggle T4x2

To avoid errors by having PyTorch recognize only a single GPU in that environment:  
`os.environ["CUDA_VISIBLE_DEVICES"] = "0"`

Instead, when aiming to fully utilize all GPUs, [it’s preferable to explicitly rerun the script using a multi-GPU-compatible backend from Accelerate or similar tools](https://discuss.huggingface.co/t/model-size-and-vram-requirements/167761/4). This approach handles advanced operations internally, making it more complex. I believe Kaggle has documentation on this…

---

_[View the full topic](https://discuss.huggingface.co/t/bitsandbytes-and-cublas-status-not-initialized-error/167455)._