Error4 reports
Fix CalledProcessError
in BitsAndBytes
✅ Solution
The "CalledProcessError" in bitsandbytes often arises from CUDA version mismatches or incomplete/incorrect installation of CUDA-related libraries required by bitsandbytes. Ensure your CUDA toolkit version (nvcc --version) matches the bitsandbytes CUDA version (e.g., bitsandbytes_cuda123 needs CUDA 12.3). Reinstall bitsandbytes using `pip uninstall bitsandbytes` followed by a targeted install: `pip install bitsandbytes --prefer-binary --extra-index-url=https://huggingface.github.io/bitsandbytes-wheels/` to fetch pre-compiled wheels compatible with your system.
Related Issues
Real GitHub issues where developers encountered this error:
CUDA SETUP: Required library version not found: libbitsandbytes_cuda128.dll?Jul 3, 2025
Got this issue after starting trainer - def replace_unet_modules(unet: diffusers.models.unet_2d_condition.UNet2DConditionModel, mem_eff_attn, xformers):May 6, 2025
Bitsandbytes Installation Hanging During Make Process on SageMaker (CUDA 12.4)Jan 21, 2025
Need support for installing bitsandbytes on Cuda121Jan 21, 2025
Timeline
First reported:Jan 21, 2025
Last reported:Jul 3, 2025
Need More Help?
View the full changelog and migration guides for BitsAndBytes
View BitsAndBytes Changelog