Hi Atom. I have tried the 0.09 version on the following machine:
Windows Vista 32 bit, driver 306.02, GTS250
I get the ERROR: cuModuleLoad() 209 only on -a 3 (all the other modes are fine). It was a clean new install of Oclhashcat-plus. Maybe the embedded statprocessor does not like 32 bit?
Edit: As a workaround, using the 32 bit Statprocessor to pipe in -plus works but still it needs to be fixed.
I doubt there is relation between 209 and the embedded statprocessor. The 32 bit might be an issue, but even on there I see no reason for it. Try to find the kernel cache from NVidia on Windows, delete them and try again.
(09-09-2012, 08:07 AM)atom Wrote: [ -> ]Try to find the kernel cache from NVidia on Windows, delete them and try again.
You lost me here. I don't know anything beside the kernels that are in the -plus/kernels folder. What kind of filename and extension do I look for?
If I delete the file m0000_a3.sm_11.ptx from the -plus/kernels/4318 folder, I get the ERROR: cuModuleLoad() 301.
The latest driver I can find from NVIDIA is 301.42 .
Where would I find higher?
I see that 304.79 is beta. Is that what I need?
Yes, that is what it took.
(I'm running Win7 64-bit, cudaHashcat-plus64.exe, and get the error with cudaExample0.cmd, cudaExample400.cmd, cudaExample500.cmd.)
For windows this driver is currently beta, right. So its just a question of time.
For linux its already in release state.
same problems -a 3 ERROR: cuModuleLoad() 209 with latest driver 306.2
i think its a bug
cuModuleLoad() 209 is totally different to cuModuleLoad() 301
thread stealer?
(10-04-2012, 01:13 PM)atom Wrote: [ -> ]cuModuleLoad() 209 is totally different to cuModuleLoad() 301
thread stealer?
Original post was about the 209 so no thread stealing here. I cannot personally continue this thread since I changed my GPUs on that machine. I am now using an ATI card and everything runs smoothly.
so what can i do to fix the error?
(10-04-2012, 03:18 PM)rolter09 Wrote: [ -> ]so what can i do to fix the error?
If you have the beta driver 306.02, I would change for the WHQL driver 306.23. If that's the one that you have then, I don't know beside making sure that you made a clean install of the drivers. There is a guide for that. You can google it.