Trying to run CUDALucas on Windows 8 CP

Rodrigo · 2012-03-03, 16:49

I installed the Windows 8 Consumer Preview yesterday, and the first things I did were to try running Prime95 (v26) and CUDALucas 1.2 on it.

Prime95 is churning away without a hitch. However, I'm not getting CUDALucas to work. Every time I start it, I get the following error:

Quote:

cudaSafeCall<> Runtime API error : CUDA driver version is insufficient for CUDA runtime version.

Background information that might yield some clues:

The program ran fine on the Windows 8 Developer Preview, and in fact is doing so right now.
I didn't have to do anything special to get it to run on the DP. I simply opened a command prompt, changed to the right directory on the original (Windows 7) partition, and ran the executable.
In contrast to Win7 and the DP, I'm running the Consumer Preview on a virtual hard disk (VHD file) rather than its own primary partition, as I'd already maxed out the number of such partitions allowed (the computer also has a factory-set 100MB "system" partition as well as a 12GB recovery partition).

Any ideas? I can't imagine that the CP is so fundamentally different from the DP as to break CUDALucas.

Rodrigo

Karl M Johnson · 2012-03-03, 17:07

My best guess based on the error is that the ForceWare is of lower version that actually supports the toolkit/sdk used to compile CUDALucas.

Rodrigo · 2012-03-03, 17:54

So, is there anything I can do about this?

I'm not a developer, so I'm not sure what you're saying... Mainly I'm trying out the CP from a user-experience perspective.

Rodrigo

Karl M Johnson · 2012-03-03, 18:45

If you fail at installing latest NV drivers, then I guess you'll have to wait for NV to release drivers, which support sdks/toolkits with which CUDALucas was compiled.
That's my best guess.

Rodrigo · 2012-03-04, 06:09

Hmm, now that you mention it, I suspect that it's precisely the fact that the newest NVidia drivers did get installed when Windows 8 CP was installed this week, that may be causing the problem. My Win7 and Win8 DP systems have older GPU drivers (from 8/2011), and I haven't gotten around to updating those. (Sometimes, procrastination helps.)

Rolling back to previous drivers via Device Manager is not a possibility when the system has no previous drivers to roll back to.

Also, I noticed that the Windows/System32 and Windows/SysWOW64 driver folders for those two OSs have several files that the corresponding folders for the CP do not, including some DLLs that appear to be related to CUDA. But I hardly dare to "mix and match" drivers by injecting these older ones in with the newer set.

Rodrigo

Dubslow · 2012-03-04, 06:15

Nvidia's drivers should be backwards compatible... but I suppose with an OS beta problems are to be expected.

Rodrigo · 2012-03-04, 06:29

That's the weird thing about it -- CUDALucas is working in the Developer Preview (a pre-beta version), but not in the Consumer Preview (a beta). You'd think it would be the other way around.

Could it have something to do with the fact that I'm running the CP off a VHD, or not really?

Rodrigo

Dubslow · 2012-03-04, 06:52

Not particularly likely, but weirder things have happened.

Karl M Johnson · 2012-03-04, 09:34

I suspect that it's a bug, and the error about cuda version may be irrelevant.

Rodrigo · 2012-03-04, 17:55

Karl,

Do you mean, a bug in Windows 8?

I did some Googling about this last night, but nothing useful turned up. Found some registry fixes for Windows 7, but the keys they reference don't show up in the Win8 registry.

Will keep looking.

Rodrigo

Karl M Johnson · 2012-03-04, 20:32

Either a bug in Windows 8 (highly unlikely), or a bug in ForceWare/CUDA toolkits/SDKs. The latter is more probable.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Prime95 vs. CUDALucas	storm5510	Software	10	2022-04-18 05:11
Don't DC/LL them with CudaLucas	LaurV	Data	131	2017-05-02 18:41
settings for cudaLucas	fairsky	GPU Computing	11	2013-11-03 02:08
Windows 32bit vs 64bit mfaktc/cudalucas	bcp19	GPU Computing	20	2012-03-11 01:24
Windows 7 Windows Update & Prime95 issue!!!	Unregistered	Information & Answers	14	2010-04-10 21:47

2012-03-03, 17:07	#2
Karl M Johnson Mar 2010 411₁₀ Posts	My best guess based on the error is that the ForceWare is of lower version that actually supports the toolkit/sdk used to compile CUDALucas.

2012-03-03, 17:54	#3
Rodrigo Jun 2010 Pennsylvania 3AE₁₆ Posts	So, is there anything I can do about this? I'm not a developer, so I'm not sure what you're saying... Mainly I'm trying out the CP from a user-experience perspective. Rodrigo

2012-03-03, 18:45	#4
Karl M Johnson Mar 2010 3·137 Posts	If you fail at installing latest NV drivers, then I guess you'll have to wait for NV to release drivers, which support sdks/toolkits with which CUDALucas was compiled. That's my best guess.

2012-03-04, 06:09	#5
Rodrigo Jun 2010 Pennsylvania 2·3·157 Posts	Hmm, now that you mention it, I suspect that it's precisely the fact that the newest NVidia drivers did get installed when Windows 8 CP was installed this week, that may be causing the problem. My Win7 and Win8 DP systems have older GPU drivers (from 8/2011), and I haven't gotten around to updating those. (Sometimes, procrastination helps.) Rolling back to previous drivers via Device Manager is not a possibility when the system has no previous drivers to roll back to. Also, I noticed that the Windows/System32 and Windows/SysWOW64 driver folders for those two OSs have several files that the corresponding folders for the CP do not, including some DLLs that appear to be related to CUDA. But I hardly dare to "mix and match" drivers by injecting these older ones in with the newer set. Rodrigo

2012-03-04, 06:15	#6
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3·29·83 Posts	Nvidia's drivers should be backwards compatible... but I suppose with an OS beta problems are to be expected.

2012-03-04, 06:29	#7
Rodrigo Jun 2010 Pennsylvania 2·3·157 Posts	That's the weird thing about it -- CUDALucas is working in the Developer Preview (a pre-beta version), but not in the Consumer Preview (a beta). You'd think it would be the other way around. Could it have something to do with the fact that I'm running the CP off a VHD, or not really? Rodrigo

2012-03-04, 06:52	#8
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3×29×83 Posts	Not particularly likely, but weirder things have happened.

2012-03-04, 09:34	#9
Karl M Johnson Mar 2010 110011011₂ Posts	I suspect that it's a bug, and the error about cuda version may be irrelevant.

2012-03-04, 17:55	#10
Rodrigo Jun 2010 Pennsylvania 2·3·157 Posts	Karl, Do you mean, a bug in Windows 8? I did some Googling about this last night, but nothing useful turned up. Found some registry fixes for Windows 7, but the keys they reference don't show up in the Win8 registry. Will keep looking. Rodrigo

2012-03-04, 20:32	#11
Karl M Johnson Mar 2010 411₁₀ Posts	Either a bug in Windows 8 (highly unlikely), or a bug in ForceWare/CUDA toolkits/SDKs. The latter is more probable.