That shouldn’t happen; failed assertions like that are always bugs, so please file an issue (it would be useful if you could add a @show around __nvdisasm[] there and list the contents of the folder it reports).
CUDA 11.3 is supported, but not selected by default, it’ll have used an artifact for 11.2 here. The just-released CUDA.jl 3.2 does fully support & default to CUDA 11.3 though.