I got some of the CUDA 5.5 and gave them a chance. After starting the two tasks
PM0037_001C1_330
PM0037_001C1_322
immetiately a Computing Error occured and they crashed with a Windows error.
I stopped the remaining tasks CUDA 5.5 now.
Arthur
I know I am a part of a story that starts long before I can remember and continues long beyond when anyone will remember me [Danny Hillis, Long Now]
Dependency Walker is giving it a clean bill of health this time
This is good news, thank you!
Quote:
Daniel's parents got an (0xc0000005) - invalid instruction - error
Huh? Any clue?
BM
No, sorry. Traditionally you'd compile a debug version with symbols exported, and distribute the matching .pdb file - the debugger should then print callstacks, function names, faulting code address, addresses referenced etc.
Found only at two subdirectories of f:\NVIDIA\DisplayDriver\344.60\Win8_WinVista_Win7_64\
DLL Name: cudart64_55.dll
Not found at all
DLL Name: cufft64_55.dll
Look at your app_version listing from last time. Einstein distributes CUDA DLLs with additional version information in the names, and renames them on copying to the slot directory. That bit's OK.
(assuming the app_version is essentially unchanged - I didn't catch one myself, again)
New Windows 64Bit CUDA 5.5
)
New Windows 64Bit CUDA 5.5 app version 1.55 is out for Beta test.
BM
BM
I got some of the CUDA 5.5
)
I got some of the CUDA 5.5 and gave them a chance. After starting the two tasks
PM0037_001C1_330
PM0037_001C1_322
immetiately a Computing Error occured and they crashed with a Windows error.
I stopped the remaining tasks CUDA 5.5 now.
Arthur
I know I am a part of a story that starts long before I can remember and continues long beyond when anyone will remember me [Danny Hillis, Long Now]
Thanks for the
)
Thanks for the report.
Deprecated for further analysis.
BM
BM
Apparently I successfully
)
Apparently I successfully eliminated the dependency for libwinpthread, but there's still something wrong.
Any idea which of these DLLs can't be found/loaded?
BM
BM
Dependency Walker is giving
)
Dependency Walker is giving it a clean bill of health this time, apart from some API-MS-WIN files which I think can be ignored.
Daniel's parents got an (0xc0000005) - invalid instruction - error from
PM0037_001C1_330_0
RE: Dependency Walker is
)
This is good news, thank you!
Huh? Any clue?
BM
BM
Found in
)
Found in c:\Windows\System32
Found only at two subdirectories of f:\NVIDIA\DisplayDriver\344.60\Win8_WinVista_Win7_64\
Not found at all
I got Windows errors within 15 seconds of running time on tasks tried on all three of my windows 7 nvidia GPU hosts.
representative exit status -1073741819 (0xffffffffc0000005)
RE: RE: Dependency Walker
)
No, sorry. Traditionally you'd compile a debug version with symbols exported, and distribute the matching .pdb file - the debugger should then print callstacks, function names, faulting code address, addresses referenced etc.
RE: Found only at two
)
Look at your app_version listing from last time. Einstein distributes CUDA DLLs with additional version information in the names, and renames them on copying to the slot directory. That bit's OK.
(assuming the app_version is essentially unchanged - I didn't catch one myself, again)
RE: Huh? Any clue? I do
)
I do have one (linking issue). New version will be published tomorrow.
BM
BM