GTX 1080 ti no CUDA detected

[Anomander43]

Looking at my GPU-Z report it's not detecting OpenCL / CUDA/ PhysX

The thing is that adobe premiere pro seems to also not detect the CUDA so I'm not convinced the problem is in the GPU-Z, rather it's some settings/driver thingy.
I've tried using DDU and installing the latest drivers with not success. Since I'm also using NVCleanstall, I thought it might be a problem in a component that I didn't include so I installed all the driver stuff, but that didn't help either. Also tried the DCH driver just in case.
In addition tried installing nvidia cuda toolkit to see if that would change anything, but no luck there either.
Any ideas what I could try or where might the problem be?

Thanks in advance for any helpful suggestions!

 

[Vya Domus]

In the Nvidia control panel there should be an option to enabled CUDA, I doubt that's the problem but make sure it's enabled.

 

[Anomander43]

I'm guessing you mean under "Manage 3D settings", if that's the case, yes, as you said that once is basically enabled by default:

 

[xrobwx71]

What have you done to troubleshoot or fix it?

If you haven't already, download DDU- Follow the directions ie running it in Safe Mode, and use it to uninstall the drivers completely. Download the latest and re-install.

 

[oobymach]

Also could try dif driver, try the latest studio one to see if that fixes.

GeForce Driver Results | NVIDIA

Download the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>

www.nvidia.com

 

[Anomander43]

What have you done to troubleshoot or fix it?

If you haven't already, download DDU- Follow the directions ie running it in Safe Mode, and use it to uninstall the drivers completely. Download the latest and re-install.

Yep, I wrote in my initial post that I did that, but thanks for checking either way.

Also could try dif driver, try the latest studio one to see if that fixes.

GeForce Driver Results | NVIDIA

Download the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>

www.nvidia.com

Just tried that. Latest version 430.86. No effect

 

[xrobwx71]

Yep, I wrote in my initial post that I did that, but thanks for checking either way.

Sorry about that, I guess I completely missed it.

 

[Anomander43]

Sorry about that, I guess I completely missed it.

No worries.
I've got a small update from my latest research.
I've tried using CUDA-Z (like GPU-Z, but for CUDA statistics).
It doesn't start, but in the Event Viewer I'm getting an error:

Spoiler: error

Faulting application name: CUDA-Z-0.10.251-64bit.exe, version: 0.10.251.0, time stamp: 0x55bbfc0c
Faulting module name: nvcuda.dll, version: 26.21.14.3086, time stamp: 0x5ce5bb67
Exception code: 0xc0000005
Fault offset: 0x000000000036c8ae
Faulting process id: 0x2df4
Faulting application start time: 0x01d6d239f4d4c4df
Faulting application path: E:\Downloads\CUDA-Z-0.10.251-64bit.exe
Faulting module path: E:\Downloads\nvcuda.dll
Report Id: ac104cba-5669-423a-af43-0d6cdca15ffc
Faulting package full name:
Faulting package-relative application ID:

I also went so far to try v399.24 of the drivers (DDU again of course).

Spoiler: error

Faulting application name: CUDA-Z-0.10.251-64bit.exe, version: 0.10.251.0, time stamp: 0x55bbfc0c
Faulting module name: nvcuda.dll, version: 24.21.13.9924, time stamp: 0x5b907e02
Exception code: 0xc0000005
Fault offset: 0x0000000000320775
Faulting process id: 0xca8
Faulting application start time: 0x01d6d23c0c0704be
Faulting application path: E:\Downloads\CUDA-Z-0.10.251-64bit.exe
Faulting module path: C:\WINDOWS\system32\nvcuda.dll
Report Id: 38fb6486-5192-4d91-8b61-96fccac7bb4a
Faulting package full name:
Faulting package-relative application ID:

I had a look at that C:\WINDOWS\system32\nvcuda.dll file. It turns out it has a certificate that's signed by an untrusted signer. (Microsoft Digital Media Authority 2005)

I took the nvcuda.dll file from a friend of mine who is using the latest drivers and replaced it with his. Now the CUDA-Z is throwing an error

Then I reverted to my old dll file and now it has more certificates (my old sha1 and his which was sha256).

I guess I'll keep digging little by little, but I'm not very knowledgeable about this stuff so any help is still very welcome.

 

[FreedomEclipse]

Im on the latest set of drivers with my 1080Ti and cuda shows just fine.

there has to be some sort of issue with your administrator or user account privileges which is preventing the installation of that part of the drivers. Im not saying that there is - but its a possiblity

 

[xrobwx71]

No worries.
I've got a small update from my latest research.
I've tried using CUDA-Z (like GPU-Z, but for CUDA statistics).
It doesn't start, but in the Event Viewer I'm getting an error:


I also went so far to try v399.24 of the drivers (DDU again of course).

I had a look at that C:\WINDOWS\system32\nvcuda.dll file. It turns out it has a certificate that's signed by an untrusted signer. (Microsoft Digital Media Authority 2005)
View attachment 179552

I took the nvcuda.dll file from a friend of mine who is using the latest drivers and replaced it with his. Now the CUDA-Z is throwing an error
View attachment 179550

Then I reverted to my old dll file and now it has more certificates (my old sha1 and his which was sha256).
View attachment 179553

I guess I'll keep digging little by little, but I'm not very knowledgeable about this stuff so any help is still very welcome.

Nice job digging and researching. Here are a couple of things to try. https://www.ionos.com/digitalguide/server/configuration/resolving-0xc0000005-errors/

 

[Anomander43]

Thanks for the suggestion! Managed to fix it by kinda reinstalling windows.

Using the media creation tool and keeping all my files and apps. So not sure what exactly was the problem in the end, but guess it was some Windows stuff. @FreedomEclipse might be right that it was some sort of permissions. In the end I've tinkered with Windows settings quite a lot.
One warning tho, save your browser sessions locally especially if you're using chormium edge, I lost like 50 tabs

 

[Rei]

Are you using OEM prebuilt PC? While it's working now, my take is that you should use DCH driver type if you PC is prebuilt by OEMs, otherwise, use the standard driver type for PC that you built yourself.
You also don't seem to be using the latest or correct driver either. If you are using you graphics card primarily for gaming then you should use the Game Ready Driver which the current latest is version 460.79, otherwise use the Studio Driver with the latest version being 457.30 if you are using your graphics card for production-type stuff. While these driver types work interchangeably, they are also optimized for a specific set of task. You might have other issues down the line if you don't use the correct driver type & version.

 

[Anomander43]

Nah, it's not OEM prebuilt. It' custom by me. Actually I think I've found out the cause of the problem. Haven't tried reproducing it again, because I'm afraid it might be annoying to revert, although it shouldn't be at all.
I think it's because I've tried a tool from the guru3d forum, build by a user named mbk1969. The thing is called "Windows: Line-Based vs. Message Signaled-Based Interrupts. MSI tool.". So basically I switched my GPU to MSI mode. I checked the "msi" box next to my nvidia card.

And by a quick google search I came up to this link:
Message Signaled Interrupts? | NVIDIA GeForce Forums
Where if you search for "CUDA", will come up on this text

Driver fails to initialize when MSI interrupts are enabled The Linux NVIDIA driver uses Message Signaled Interrupts (MSI) by default. This provides compatibility and scalability benefits, mainly due to the avoidance of IRQ sharing. Some systems have been seen to have problems supporting MSI, while working fine with virtual wire interrupts. These problems manifest as an inability to start X with the NVIDIA driver, or CUDA initialization failures.

So basically I think that was it. Seems like reinstalling windows through the tool, resets that. Don't ask me why I did it, I just like trying stuff, although it might break things down
It's all experience and knowledge in the end.
Thank to everybody who tried helping me with this!

 

[Rei]

Nah, it's not OEM prebuilt. It' custom by me. Actually I think I've found out the cause of the problem. Haven't tried reproducing it again, because I'm afraid it might be annoying to revert, although it shouldn't be at all.
I think it's because I've tried a tool from the guru3d forum, build by a user named mbk1969. The thing is called "Windows: Line-Based vs. Message Signaled-Based Interrupts. MSI tool.". So basically I switched my GPU to MSI mode. I checked the "msi" box next to my nvidia card.

View attachment 179708

And by a quick google search I came up to this link:
Message Signaled Interrupts? | NVIDIA GeForce Forums
Where if you search for "CUDA", will come up on this text


So basically I think that was it. Seems like reinstalling windows through the tool, resets that. Don't ask me why I did it, I just like trying stuff, although it might break things down
It's all experience and knowledge in the end.
Thank to everybody who tried helping me with this!

Good for you if you got it fixed. Still, since your PC isn't OEM pre-built, you shouldn't use the DCH driver type since your hardware is not optimized for it. Use the standard driver type instead. And if you are using your PC more for production/studio type workload & less for gaming, use the Studio Driver instead of Game Ready Driver & vice versa as the driver will optimize the GPU for a specific type of workload.