Had the same issue. 8.0.3
version is the current and latest supported version of the library for CUDA 10.1
. However, tensorflow is build for the earlier version, so you have to use that instead.
To elaborate, if you check this page: https://www.tensorflow.org/install/source_windows#tested_build_configurations
+----------------------+----------------+-----------+-------------+-------+------+
| Version | Python version | Compiler | Build tools | cuDNN | CUDA |
+----------------------+----------------+-----------+-------------+-------+------+
| tensorflow_gpu-2.3.0 | 3.5-3.8 | MSVC 2019 | Bazel 3.1.0 | 7.6 | 10.1 |
+----------------------+----------------+-----------+-------------+-------+------+
so, unless you build the TF locally - you have to use the supported version of cudnn
.
That being said, however, if you check latest TF releases:
https://github.com/tensorflow/tensorflow/releases
you will then see the following TensorFlow 2.4.0-rc1
note:
TensorFlow pip packages are now built with CUDA11 and cuDNN 8.0.2.
You can use the release candidate version of TF, but then, you also have to upgrade CUDA to 11 (I am guessing version 11.0 since no postfix is mentioned) and use the cuDNN v8.0.2 (July 24th, 2020), for CUDA 11.0
.
Just tested - this setup works. You just have to make sure to install numpy
version 1.19.3
in order to avoid the problem mentioned in these threads
RuntimeError: The current Numpy installation fails to pass a sanity check due to a bug in the windows runtime
https://developercommunity.visualstudio.com/content/problem/1207405/fmod-after-an-update-to-windows-2004-is-causing-a.html