Crash dump analysis

I haven't been able to use PR 2022 since the very first version. I've reported it 3 times now but no resolution. I've just reported it again for PR 2023. PR 2023 marks a Nikon RAW image in a directory as corrupt and every time I browse to that folder another image is marked corrupt. PR 2023 also crashes a) sometimes without me doing anything and b) every time I try and edit a raw file. The crash dump can be found in c:\users\USERNAME\AppData\Roaming\ON1\ON1 Photo RAW 2023\AppCenter\crashes. I analysed it with windbg and it says an illegal instruction occurred in ONPhotoRAW.dll at OnRawDistort::distort+502. In the past all I've been offered is a refund. Why can't ON1 fix this issue when I've provided so much detail. I'm an ex developer and I'm pretty sure I could find this issue given the supplied information.

Note the crash is in an ON1 DLL and my video card drivers are up to date AND this is NOT a new issue. It has been around since 2022.1.

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\martin\AppData\Roaming\ON1\ON1 Photo RAW 2023\AppCenter\crashes\c493545d-26b1-4374-8286-b7b15e8476b4.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Version 19043 MP (3 procs) Free x64
Product: WinNt, suite: SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Debug session time: Sun Oct 16 13:40:05.000 2022 (UTC + 1:00)
System Uptime: not available
Process Uptime: 0 days 0:00:38.000
................................................................
................................................................
................................................................
..........................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(1c4c.f5c): Illegal instruction - code c000001d (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ffc`c030eef4 c3              ret
0:068> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3030

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 32138

    Key  : Analysis.IO.Other.Mb
    Value: 17

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 29

    Key  : Analysis.Init.CPU.mSec
    Value: 1140

    Key  : Analysis.Init.Elapsed.mSec
    Value: 37907

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 188

    Key  : Timeline.Process.Start.DeltaSec
    Value: 38

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 17.0.0.12912


FILE_IN_CAB:  c493545d-26b1-4374-8286-b7b15e8476b4.dmp

CONTEXT:  (.ecxr)
rax=000002db2b0fc4d4 rbx=000000fd192fee50 rcx=000000000000093c
rdx=000002db2b0fbb98 rsi=00007ffc6e87f1b0 rdi=000002db1ae10018
rip=00007ffc6e881712 rsp=000000fd192febd0 rbp=000000000000093c
 r8=0000000000000002  r9=0000000000000004 r10=0000000000000004
r11=0000000000000000 r12=0000000000000258 r13=000002db2ac94cb0
r14=000000000000093c r15=000002db2b0f96a0
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
ONPhotoRAW!ONRawDistort::distort+0x502:
00007ffc`6e881712 660f382bc0      packusdw xmm0,xmm0
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffc6e881712 (ONPhotoRAW!ONRawDistort::distort+0x0000000000000502)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME:  ON1 Photo RAW 2023.exe

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

EXCEPTION_CODE_STR:  c000001d

STACK_TEXT:  
000000fd`192febd0 00007ffc`6e88d3e5     : 00000000`00000001 000002db`2ac94cb0 000000fd`00000960 000002db`2addf2d0 : ONPhotoRAW!ONRawDistort::distort+0x502
000000fd`192fed40 00007ffc`6e7b806f     : 000002db`14ca95d0 000002db`2ac94cb0 000000fd`00000960 000002db`14ca95d0 : ONPhotoRAW!ONRawProxyBuilder::updatePreview+0x625
000000fd`192feee0 00007ffc`7026c218     : 00000000`00000000 000002db`28324550 000002db`1ab247e0 000000fd`192ff2f8 : ONPhotoRAW!ONPhotoRAWBuildProxy4+0xa9f
000000fd`192ff0d0 00007ffc`702a99ef     : 00000000`00000000 00000000`00000000 000002db`149a7ac0 000002db`28324550 : ONDocument17!MetaData::Initialize+0x96c8
000000fd`192ff2b0 00007ffc`702aa1ca     : 00000258`00000258 00000000`00000001 00000258`00000201 000002db`1ab247e0 : ONDocument17!ONImageFormatGetPreviews+0x40f
000000fd`192ff3f0 00007ffc`6f457ee1     : 000002db`28324550 00000000`00000003 000002db`1ab247e0 000000fd`192ff858 : ONDocument17!ONImageFormatGetPreviews2+0x2da
000000fd`192ff620 00007ffc`6f458df4     : 000000fd`192ffc01 000002db`28324550 000002db`28324500 000002db`28324500 : ONQtCore!ONPreviewSvcRunnable::getFastPreview+0x721
000000fd`192ff810 00007ffc`6f45c355     : 00000000`61989c39 00000000`00000000 000002db`1501a360 000002db`1b060ac0 : ONQtCore!ONPreviewSvcRunnable::load+0x6d4
000000fd`192ffd20 00007ffc`739865f6     : 00000000`00000000 000002db`00000000 00000000`00000000 00000000`00000001 : ONQtCore!ONPreviewSvcRunnable::run+0x65
000000fd`192ffdc0 00007ffc`73982cb1     : 000002db`1b060ac0 000002db`00000001 000002db`00000001 000002db`1b060ac0 : Qt6Core!QThreadPoolPrivate::reset+0x2c6
000000fd`192ffe80 00007ffc`bf007034     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Qt6Core!QThread::start+0x371
000000fd`192ffec0 00007ffc`c02c26a1     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
000000fd`192ffef0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


FAILED_INSTRUCTION_ADDRESS: 
ONPhotoRAW!ONRawDistort::distort+502
00007ffc`6e881712 660f382bc0      packusdw xmm0,xmm0

SYMBOL_NAME:  ONPhotoRAW+502

MODULE_NAME: ONPhotoRAW

IMAGE_NAME:  ONPhotoRAW.dll

STACK_COMMAND:  ~68s; .ecxr ; kb

FAILURE_BUCKET_ID:  ILLEGAL_INSTRUCTION_c000001d_ONPhotoRAW.dll!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {908f5d88-19a2-9d3b-e63c-af434ffa411b}

Followup:     MachineOwner
---------

Brian Lawson

Community moderator

October 16, 2022 14:00

There isn't anyone here who can do anything with that crash log. You have to send it to support.

-1

Martin Evans

October 16, 2022 14:11

As I said "I've just reported it again for PR 2023"

I'm not expecting many people to be able to do anything with the analysis but it all adds to the information that some people might find useful or be able to add to.

Rick Sammartino

October 16, 2022 14:47

This is the exact same problem that I was having when 2022.5 came out. I was NEVER able to get it to work and had to go all the way back to 2022.1 just to use the program.

Since then though, I have a new PC and with PR2023, while I've had a few corrupted files and still have crashes, the problem has reduced considerably.

On1 swears they are still working on the problem and it's likely there will be a 2022 final release so hopefully, there will be a fix in it.

Chay Wesley

October 18, 2022 16:12

The illegal instruction in that crash log is an SSE instruction. Some computer motherboards allow disabling processor support for SSE in their BIOS. It's a very long shot for sure, but you might check your computer's bios settings to make sure that SSE / AVX / AVX-2 instruction sets have not been disabled.

October 25, 2022 10:35

Sadly my BIOS did not support the disabling of SSE instructions and the latest PR update from today still marks Nikon RAW files as corrupt and crashes. It is coming up to a year since I first reported this.

Carl Traub

October 26, 2022 03:47

It's sad that with that much information you're still 'hoping' for a fix a year later. But it's not a surprise.

I've submitted 2 or 3 crash dumps, then emailed support to give descriptions of what I was doing when the crash occurred. They asked for my On1 log file, indicating that would give them more information, and stated "Thank you for your patience during this troubleshooting process."

I never heard from support again.

Crash dump analysis

Comments

Didn't find what you were looking for?