The cuda60 version of application version 815 is now present on acemdlong for those of you with the latest driver or a Maxwell card.

Matt

Getting a lot of failures on app 815(Cuda60)

Realize the effort and focus of the 8.15 and cuda60 is probably for maxwell, but just wanted to ensure you knew WinXP seems to error out on every one of these tasks while Win7/8 is ok.

See below thread
http://www.gpugrid.net/forum_thread.php?id=3671

Jeremy, Could you try a project reset on the affected XP machines please? The error suggests the application's files haven't downloaded correctly

Matt

Different security architecture?

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Hi,

Just confirmation the new 8.15/cuda60 app on XP x86 with a GTX 650 ti crash with a popup message:
"The procedure entry point GetTickCount64 could not be located in the dynamic link library KERNEL32.dll"
Performed a project as suggested to no avail.

x86 bug?

cuda55 app was working fine.
Until the issue is resolved is there a way of identifying cuda60 tasks by name so I can write a script to abort them immediately?

Thanks

Downgrade video driver and you won't get Cuda 6

Downgrade video driver and you won't get Cuda 6

That is a way around it but surely there must be a bug in the application that is causing the failures in Windows XP machines. Some participants prefer the performance advantage of XP for crunching GPUGRID.

Matt,

I reset the project for both machine, and they are both still erroring out on every cuda60 WU. I went through the top 320 performing computers on the volunteer list last night, and did not find a single XP machine with drivers 334 or 335 that completed a cuda60 WU. The other XP machines just did not receive the WU's with the older drivers. Only a handful of the XP machines were on 334/335. The rest were on older drivers and just running the cuda55/42 WU's.

I am changing back to the 331 driver to avoid the cuda60 WU's for now. I can try the 335 driver again later if needed.

Thank you for the feedback and suggestion.

Regards,
Jeremy

Thanks for the error message. Should be enough to track down the problem. I've disabled the acemdlong cuda60 app for the moment.

Matt

Would it be possible to add a checkbox to the 'Run only the selected application' named 'Cuda 6' and one named 'Cuda < 6' ?
Using these choices should solve most probles with these version incompatibilities.

Alexander

I got the first tasks cuda 60 on March 19 and all were Calculate flawlessly. Already about 20 + already completed okay.
Times is about 25000sec, cpu 8500 but it can be for each user due to hw different one..
Good job GPUGRID, cheers

Would it be possible to add a checkbox to the 'Run only the selected application' named 'Cuda 6' and one named 'Cuda < 6' ?
Using these choices should solve most probles with these version incompatibilities.

Alexander

I agree. However, it looks like they want to use CUDA 6.0 on all the new work, so that would be only a temporary solution.

Try acemdbeta 812 or acemdshort 813 - these should fix the crash on 32bit Win XP.
Please report here!

Matt

Will this also be compatible for WinXP 64bit? From the leader list the top machines are using it.

Yep

Hi,

Updated 8.15-cuda60 on the short Q (win XP x86, gtx 650ti) appears to getting further however running very slowly with CPU utilisation <1% (typically 8-10%) (Currently a SANTI_MAR419cap310 after 2hrs 22min is only at 47%)

Ah, noticed I am still getting the error "..GetTickCount64 could not be located in KERNEL32.DLL" msg which pops up as soon as I start the task :(

Update - rebooted and performed a project reset to no avail.

Try the new version 820

I have just completed my first 8.20 short run on a GTX 660 under WinXP 32-bit.
No problems or restarts at all at 3 hours 7 minutes total elapsed time; good work.
(And please take some time off during the week.)

Name 990x-SANTI_MAR423cap310-45-84-RND7785_1
Workunit 5346410
Created 23 Mar 2014 | 15:20:02 UTC
Sent 23 Mar 2014 | 15:20:14 UTC
Received 23 Mar 2014 | 18:30:08 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 168614
Report deadline 28 Mar 2014 | 15:20:14 UTC
Run time 11,222.14
CPU time 1,951.00
Validate state Valid
Credit 18,300.00
Application version Short runs (2-3 hours on fastest card) v8.20 (cuda60)