Project

General

Profile

Bug #12525

Unhandled exception : Darktable 2.6.0.win64 on Ryzen 1600 with Radeon 560D win10home 64-bit

Added by Hans NEHER 16 days ago. Updated 13 days ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
General
Target version:
Start date:
01/05/2019
Due date:
% Done:

0%

Affected Version:
git stable branch
System:
Windows
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Gentlemen,

Hope this is the correct spot to post an 'unhandled exception' which prevents Darktable 2.6.0. win64 from functioning?

Installed the above on an elderly dual core intel cpu notebook with win10 home and runs fine; then installed on the newer and faster AMD desktop as per above and find an unhandled exception error. Rebooted, same result : log-file attached.

The error is listed as : darktable.exe caused an Access Violation at location 00007FFA7012C6BA in module amdocl64.dll Reading from location 0000000000000020.

By all means ask if you need more info, but please realise that I'm a user, w/o much knowledge beyond (double) clicking.

Looking forward, met vriendelijke groet (dutch for 'with friendly greeting),

Hans

By the way : "Affected Version" is apparently - given the red asterisk - a required answer : would be helpful if newest versions 2.6.0 and 2.6.1 were available in that list? if one can't update the list all that often could whoever maintains this bug reporting system please add 'newest' as an entry, and - assuming users update regularly - it would be helpful if the newest version was at the top of the list?

H.

darktable_bt_7KW0UZ.txt Magnifier - log file (4.71 KB) Hans NEHER, 01/05/2019 12:20 AM

darktable_bt_J7GVUZ.txt Magnifier - new logfile after radeon driver update (4.72 KB) Hans NEHER, 01/05/2019 01:22 AM

History

#1 Updated by Hans NEHER 16 days ago

Updated Radeon driver from 18.12.2 to latest 18.12.3, restarted Darktable, same problem - see new log file.
Puzzling : Radeon update now advises to update from 18.12.3 to 18.12.2 - that's a downgrade?

Regarding Affected Version : downloaded latest from Darktable website, hence not sure why I'm asked whether git stable or master branch?

#2 Updated by Ulrich Pegelow 13 days ago

From the crash report we can see that the error happens in the OpenCL driver, supposedly at an early stage of initialization. Besides of trying alternative versions of the driver you may also run darktable with option --disable-opencl.

Also available in: Atom PDF