aparapi crashes with latest NVidia drivers

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Get some version of aparapi, e.g. latest trunk (revision 1418) or latest 
release (January 23rd, 2013)
2. Run any program, e.g. the mandel sample
3. Observe

What is the expected output?
The program works

What do you see instead?
The program crashes

What version of the product are you using?
Tried latest trunk (revision 1418), release 
Aparapi_2013_01_23_windows_x86_64.zip, release aparapi-r904-opencl_1_1.zip

On what operating system?
Microsoft Windows Vista 64-bit
Microsoft Windows [Version 6.0.6002]

Please provide any additional information below.
I have an NVidia GTX670 with the latest drivers (version 331.65 as of today).

Anything using aparapi crashes, apparently in the same place in the NVidia 
OpenCL DLL:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007feec7227b6, pid=28564, 
tid=28632
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode 
windows-amd64 compressed oops)
# Problematic frame:
# C  [nvopencl.dll+0xa27b6]
#
# Failed to write core dump. Minidumps are not enabled by default on client 
versions of Windows
#
# An error report file with more information is saved as:
# D:\TEMP\aparapi_trunk\aparapi-read-only\samples\mandel\hs_err_pid28564.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Original issue reported on code.google.com by mikkotom...@netscape.net on 12 Nov 2013 at 5:44

Attachments:

• hs_err_pid28564.log

[GoogleCodeExporter]

I recently updated to Windows 8.1 (64-bit) and NVidia driver version 331.82. 
The problem no longer occurs.

Original comment by mikkotom...@netscape.net on 22 Nov 2013 at 11:03

[GoogleCodeExporter]

Whoops.

I was on vacation and only just saw this.  Looks like the later drivers fixed 
this.  

Thanks for coming back and letting us know. 

Gary

Original comment by frost.g...@gmail.com on 4 Dec 2013 at 3:36

• Changed state: WontFix