And I use last nvidia drivers.

App info like yours will not work because in it's current state the app does not run on devices other than #0.
It runs via wrapper which removes --device option when passed from BOINC manager, because the app itself does not understand that and will refuse to run.

The "195" error is a separate problem, it means the wrapper is unable to run the main program, usually because it exits with error on startup. Find the main executable (enigma_cuda_1.07.....exe) inside the project folder and try to run it via command line, perhaps it'll show something about the reason why it's refusing to run.

---

M4 Project homepage
M4 Project wiki

Hi, in cmd I can run app and it say: tree file names required and quit. Can you send me what I may exact try to run to check if it works?
My PC have two 1080Ti´s in one PC, can it be this problem nor not?

Try one of the quick test .bat files from this package: https://s3.eu-central-1.amazonaws.com/enigma4/test_runs/2.0_test.zip

---

M4 Project homepage
M4 Project wiki

Hi, after run bat file(s) it found my gpu 1080Ti w comp. capab 6.1 and after that boinc-cuda.exe crash without any errors and at cmd is shown only pause text. Any other ideas please? Want to run Enigma on my fast GPU ...

Any other idea what can be bad?

@Dzordzik, please check the code returned by the program. Add these lines to the bat file after the line that runs the enigma-cuda.exe:

@echo.
@echo Return code = %errorlevel%
pause

The success code is 0, other codes are errors.

After run m4 bat Enigma app crash, in cmd return code -1073741795

My m4 bat looks like this:
enigma-cuda.exe -M M4 -f b:g438:AA:AAAA -t b:g438:ZZ:ZZZZ -n 1 -a -g 013 00trigr.u534 00ugr.u534 m4_test72_31
@echo.
@echo Return code = %errorlevel%
pause

Is it right?

Have installed VS C++ redistr. 2010, 12, 13 and 15, x86 and 64b too. My OS Win7 64bit any my GPUs was 2x GTX 1080Ti FE that was stable and wo problems at other projects including GPUGrid or Primegrid.

Cards wo SLI for info but it doesn´t matter I think.

here is what Microsoft says about this error:

https://support.microsoft.com/en-us/help/3174417/fix-programs-that-are-built-in-visual-c-2013-crash-with-illegal-instru

I´m not programmer but here is something about AVX instructions, can be this problem because my old Xeon not support AVX? My CPU is Dual Xeon X5950.

A new build of enigma-cuda.exe is available. This build:

1) does not use AVX or SSE instructions (the speed is the same);
2) has a new command line option, -d <cuda device number> (0-based indexing).

The source and new binaries are here: https://github.com/VE3NEA/enigma-cuda

A new build of enigma-cuda.exe is available. This build:

1) does not use AVX or SSE instructions (the speed is the same);
2) has a new command line option, -d <cuda device number> (0-based indexing).

The source and new binaries are here: https://github.com/VE3NEA/enigma-cuda

Will the new build of enigma-cuda.exe, be implemented on the enigma server, or is there a cheat sheet for dummies ?

Will the new build of enigma-cuda.exe, be implemented on the enigma server, or is there a cheat sheet for dummies ?

I'll update the apps on the server later today. GPU workunits generator will be stopped for around ~1h right before update.

---

M4 Project homepage
M4 Project wiki

Will the new build of enigma-cuda.exe, be implemented on the enigma server, or is there a cheat sheet for dummies ?

I'll update the apps on the server later today. GPU workunits generator will be stopped for around ~1h right before update.

Thanks for update.

App version updated to 1.08. It ships with new wrapper that translates --device passed by BOINC manager to -d
Seems to be working, at least with -d 0.

Note for app_info users: 1.08 wrapper won't work combined with previous versions of the app. New app will still work with 1.07 and older wrappers, but won't support --device / -d

---

M4 Project homepage
M4 Project wiki

Update to 1.08 is working well, 2 old Xeon rigs & 1 Dual-Core Processor can run GPU WU. Thanks.

For me the GPU app still only works on one GPU, allowing two WU's to run only runs them both on the same GPU which leaves any other GPU's doing nothing. For me at least nothing has changed :(

For sh#%s & giggles I even tried to changing the command to -d 1 in the job_160.xml file and another time tried pausing the WU and changing it in job.xml file in the slot directory but with the same result. As far as boinc is aware all is working as it should be with a WU running on each device but in reality there both being crunched by the same GPU.

For me the GPU app still only works on one GPU, allowing two WU's to run only runs them both on the same GPU which leaves any other GPU's doing nothing. For me at least nothing has changed :(

For sh#%s & giggles I even tried to changing the command to -d 1 in the job_160.xml file and another time tried pausing the WU and changing it in job.xml file in the slot directory but with the same result. As far as boinc is aware all is working as it should be with a WU running on each device but in reality there both being crunched by the same GPU.

I also did not have much luck with running 2 GPUs, but hopeful that the OpenCL/ATI version of GPU app will allow you to run
both NV & ATI GPUs cards in same rig.

For sh#%s & giggles I even tried to changing the command to -d 1 in the job_160.xml file

This won't work, as the wrapper adds -d on the fly to the command line that's already in the job file and it always does that, defaults to GPU 0.
Which host id is that ? The wrapper writes command line used to run app to the stderr, so it can be seen online in result details.

You could try it outside of the BOINC, just copy the files from slot folder running GPU app somewhere, and create a test bat file:

wrappergpu_1.08_windows_x86_64__cuda_fermi.exe --device 1
pause

the wrapper will read the job file and should add the number passed after --device to command line.
I've just tested it and it does that on my system, but I do not have second GPU.

---

M4 Project homepage
M4 Project wiki