ERROR: clEnqueueReadBuffer() -5 - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Deprecated; Ancient Versions (https://hashcat.net/forum/forum-46.html) +--- Forum: Very old oclHashcat Support (https://hashcat.net/forum/forum-21.html) +--- Thread: ERROR: clEnqueueReadBuffer() -5 (/thread-150.html) |
ERROR: clEnqueueReadBuffer() -5 - c4p0ne - 10-07-2010 Simply Upgraded to the Nvidia Beta Drivers (which was probably a shitty move). Drivers: Nvidia 260.63 Beta OS: Win7 x64 MEM: 8G Card 1: Nvidia GTX 470 Card 2: Nvidia GTX 275 Config: OpenCL 1.0 CUDA 3.2.1 (2 matched) Any Ideas which don't require me to go back to the old drivers? RE: ERROR: clEnqueueReadBuffer() -5 - Rolf - 10-07-2010 OCLHC will not work with 260.xx beta drivers. It's normal(thanx to NV). RE: ERROR: clEnqueueReadBuffer() -5 - c4p0ne - 10-10-2010 (10-07-2010, 03:26 PM)Rolf Wrote: OCLHC will not work with 260.xx beta drivers. Just wondering if it is reasonable to think that this will work "on its own" again after NV releases stable 260.xx drivers, or will we have to wait for updated oclHashcat for this? RE: ERROR: clEnqueueReadBuffer() -5 - Rolf - 10-11-2010 Usually, it worked like that(with each new release of drivers current oclhc worked with them). However, knowing NV, they may make some serious changes(or implement serious bugs) in 260.xx . When the drivers get WHQL certificate, we'll see. RE: ERROR: clEnqueueReadBuffer() -5 - c4p0ne - 10-27-2010 (10-11-2010, 08:59 AM)Rolf Wrote: Usually, it worked like that(with each new release of drivers current oclhc worked with them). Well, updated to 260.99 [WHQL] and still fail. Oh well, I'm not going back to older drivers. Its a good thing I've got a few other utilities (e.g. EGB) that still work well with these updated drivers. Those will have to hold me until the issue is resolved. RE: ERROR: clEnqueueReadBuffer() -5 - satoshy86 - 10-27-2010 I have the same error on my laptop if i use -n 80, but if i use -n < 80, like 32, i have no error. RE: ERROR: clEnqueueReadBuffer() -5 - atom - 01-31-2011 latest nvidia driver and oclHashcat v0.25 fixes this |