Skip to main content

RAW files causing crash

Answered

Comments

29 comments

  • Brian Lawson Community moderator

    The first place to start is by Deleting Settings followed by Reset ON1 Photo RAW 2022.

    Delete Settings File

    0
  • Martin Evans

    I have had the same issue for ages. It is an unhandled exception. Photoraw 2020 works fine but all versions after that exhibit the same problem. I have reported it to support with crash dump analysis but they just offer to refund me. If you report it to support and get anywhere I'd love to hear from you.

    0
  • Brian Lawson Community moderator

    Ray, I'm able to use the few .nef files I have in my library. Would you care to share one of the files you are having trouble with? You'll have to upload the file to a web sharing site like Dropbox or WeTransfer then post the download link here.

    Have you gone through the Delete Settings and Reset ON1 Photo RAW steps yet? Those are always the first place to start when you start encountering problems with the program.

    0
  • Rick Sammartino Community moderator

    This is the same problem that I'm having. Photo Raw is flagging ALL of my olympus RAW files as corrupt one at a time and then it crashes. The only way to keep it from crashing is to point the browser at a folder without any RAW files in it.

    I've already contacted support and they decided there is a bug causing it. Don't know how long it will take to fix but I can't edit any RAWs at present unless I go back to 2022.1.

    0
  • Ray Alstrom

    Yes, I deleted settings and did a reset. I had this problem with random crashes on a handful of Nikon NEF raw files previous to version 2022.5, but since upgrading to 2022.5 it crashes on all NEF and Fuji RAF raw files. ON1 tech support was quick to process my ticket but the answer I received was a canned "we don't support your CPU or GPU, upgrade or replace your computer". That seems to be a common response these days - especially from Microsoft concerning Windows 11. I went through this when Luminar AI was released, which is why I switched to ON1 Photo RAW. However, it seems ON1 has taken the same path in software development. If you have less than an iCore 5 processor you can forget about running ON1 or Luminar AI or NEO. Technically, (I'm a retired IT guy with 40+ years of PC experience) there's coding instructions known as OpenVINO which requires that your processor be SSE4.1 or SSE4.2. Newer processors (even some iCore 3) have this but many older processors - including AMD don't. Only the newer AMD Ryzen processors do. I'm not a programmer, by any stretch of the imagination, but it's obvious that forcing SSE4.1 or higher in your software is not essential since the majority of photo processing  software don't. I have no problems with the latest versions of Adobe or PaintShop Pro, Luminar 4, ACDSee, DXO Labs, or other RAW editors. Bottom line is, I asked for a refund and got it promptly. It's a shame because I really like Luminar 4 and ON1 Photo Raw 2022 was like Luminar 4 on steroids. I guess I'll stick with my iteration of Luminar 4 for now - until I'm ready to retire my current computer.

    0
  • Brian Lawson Community moderator

    All the new AI features in both programs require much more processing power. If support has told you that your system isn't powerful enough then you have your answer.

    Comparing Photo RAW to Adobe's software is a false analogy as they do not make use of the GPU to the same degree as Photo RAW does. Most of their processing takes place on the CPU while most of Photo RAW's is on the GPU.

    0
  • Rick Sammartino Community moderator

    Ray, I don't know what you're talking about. My CPU is a quad core 2.66 that's 14 years old. Nobody is ignoring my service requests.

    0
  • Ray Alstrom

    Rick, I certainly hope your request gets handled - and fixed - because I'd love to start using ON1 Photo Raw 2022. Please post your results so I can continue following this thread and hopefully pickup where I left off with ON1. My experience with support, though prompt, was a quick wham bam can't help you man. Maybe ON1 just doesn't like AMD processors. Mine is an AMD Radeon 10 years old.

    0
  • Rick Sammartino Community moderator

    Support is aware that there is a bug that needs to be looked at.

    The 'Result' at present is that I'm waiting for a bug fix update. There is nothing to be done until that happens and there is no indication so far as to how long it will take. 

    0
  • Martin Evans

    I posted this problem to support with a crash dump analysis from 2022.1 6 months ago when I upgraded from 2022. One of the replies I got said "We've tracked down this crash in our analytics and have a ticket for further investigation."
    However, when I reported it again in 2022.5 I was told "Unfortunately, if a complete clean install of the program does not resolve this issue then this indicates that there is either an incompatibility with the computer and the software, or that some image files stored on your computer are incompatible or corrupt and are causing this crash." and offered a refund.

    If you look at the crash dump analysis it says "illegal instruction" so it is highly unlikely "your computer are incompatible".

     

    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************
    
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 15686
    
        Key  : Analysis.DebugAnalysisManager
        Value: Create
    
        Key  : Analysis.Elapsed.mSec
        Value: 239124
    
        Key  : Analysis.Init.CPU.mSec
        Value: 2062
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 74849
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 329
    
        Key  : Timeline.Process.Start.DeltaSec
        Value: 109
    
        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: 16.1.0.11631
    
    
    FILE_IN_CAB:  74fdc754-3430-4a5d-849d-33eff455c219.dmp
    
    CONTEXT:  (.ecxr)
    rax=000001eb8370f040 rbx=0000000000000d44 rcx=00000009e10fef68
    rdx=0000000000000000 rsi=000001eb8370f040 rdi=00000009e10ff180
    rip=00007ffe3322913f rsp=00000009e10fef10 rbp=000001ebf2b3d508
     r8=0000000000000000  r9=000001ebf2b3d500 r10=0000000000000000
    r11=000001ebf2463520 r12=0000000000000350 r13=00007ffe33226ad0
    r14=0000000000000d40 r15=000001eb82d89040
    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+0x48f:
    00007ffe`3322913f 660f382bc0      packusdw xmm0,xmm0
    Resetting default scope
    
    EXCEPTION_RECORD:  (.exr -1)
    ExceptionAddress: 00007ffe3322913f (ONPhotoRAW!ONRawDistort::distort+0x000000000000048f)
       ExceptionCode: c000001d (Illegal instruction)
      ExceptionFlags: 00000000
    NumberParameters: 0
    
    PROCESS_NAME:  ON1 Photo RAW 2022.exe
    
    ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
    
    EXCEPTION_CODE_STR:  c000001d
    
    STACK_TEXT:  
    00000009`e10fef10 00007ffe`33234913     : 000001eb`3ec18427 000001eb`82d89040 000001eb`00000d40 000001eb`82f6c040 : ONPhotoRAW!ONRawDistort::distort+0x48f
    00000009`e10ff080 00007ffe`331e6177     : 000001eb`ec3829b0 00000009`e10ff168 00000009`00000d40 00000009`e10ff268 : ONPhotoRAW!ONRawProxyBuilder::updatePreview+0x583
    00000009`e10ff220 00007ffe`3a4eb308     : 000001eb`ec38a100 00000000`00000000 000001eb`ec374d10 00000009`e10ff428 : ONPhotoRAW!ONPhotoRAWBuildProxy4+0x887
    00000009`e10ff390 00007ffe`3a51e096     : 00000000`00000001 000001eb`f16bf420 00000000`00000000 000001eb`f24c6150 : ONDocument16!MetaData::Initialize+0x8a58
    00000009`e10ff3e0 00007ffe`3a51e743     : 00000350`00000350 000001eb`00000001 00000350`00000301 000001eb`ec374d10 : ONDocument16!ONImageFormatGetPreviews+0x3f6
    00000009`e10ff510 00007ffe`33a32795     : 000001eb`ec5a2b10 000001eb`00000003 000001eb`ec374d10 00000009`e10ff7a8 : ONDocument16!ONImageFormatGetPreviews2+0x243
    00000009`e10ff5e0 00007ffe`33a3345c     : 00000009`e10ffb01 000001eb`ec5a2b10 00000000`00000fc0 00000000`00000300 : ONQtCore!ONPreviewSvcRunnable::getFastPreview+0x645
    00000009`e10ff760 00007ffe`33a3673d     : 000003df`6bc38ac3 00000000`00000001 00000000`ffffffff 000001eb`f221eff0 : ONQtCore!ONPreviewSvcRunnable::load+0x76c
    00000009`e10ffc80 00007ffe`3a60918e     : 00007ffe`3a8d9338 000001eb`00000000 000001eb`ebcb44d0 000001eb`ebcb4528 : ONQtCore!ONPreviewSvcRunnable::run+0x6d
    00000009`e10ffce0 00007ffe`3a605ee1     : 000001eb`ebcaead0 000001eb`ebcb4528 000001eb`ebcaead0 000001eb`ec2539a8 : Qt5Core!QThreadPoolPrivate::reset+0x1ae
    00000009`e10ffd70 00007ffe`a9957034     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Qt5Core!QThread::start+0x361
    00000009`e10ffda0 00007ffe`ab322651     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
    00000009`e10ffdd0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
    
    
    FAILED_INSTRUCTION_ADDRESS: 
    ONPhotoRAW!ONRawDistort::distort+48f
    00007ffe`3322913f 660f382bc0      packusdw xmm0,xmm0
    
    SYMBOL_NAME:  ONPhotoRAW!ONRawDistort::distort+48f
    
    MODULE_NAME: ONPhotoRAW
    
    IMAGE_NAME:  ONPhotoRAW.dll
    
    STACK_COMMAND:  ~51s ; .ecxr ; kb
    
    FAILURE_BUCKET_ID:  ILLEGAL_INSTRUCTION_c000001d_ONPhotoRAW.dll!ONRawDistort::distort
    
    OS_VERSION:  10.0.19041.1
    
    BUILDLAB_STR:  vb_release
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {6e58ca7b-15ea-bae0-1fed-abc27e317f86}
    
    Followup:     MachineOwner

     

    0
  • Zachary Fisher

    This is still an issue. Having the same problem.  Latest release doesn't fix it.  Error window now "The photo <photo path>.RAF is damaged and caused ON1 Photo RAW to crash.  This file will be ignored."  Then on1 will never look at it again.  It doesn't crash in any other software.

    0
  • Brian Lawson Community moderator

    Yes, as has been reported above in this thread there is a bug in the program. I would send tech support a report so they can get a better handle on how many users are being affected by it. The more folks that report it the more likely it will get a higher priority for being fixed.

    Photo RAW keeps a file named CorruptFiles.log in your user data for the program. These files are listed there so the program knows to not look at them again. You can trash the log file so the program can see them again but until the bug gets fixed they will most likely wind up being reported a corrupt once again. The path to that file is

    C:\Users\<user>\AppData\Roaming\ON1\ON1 Photo RAW 2022

    ~/Library/Application Support/ON1/ON1 Photo RAW 2022.

    0
  • Rick Sammartino Community moderator

    Just FYI, while, yes, you can clear the log file, the photos won't start working automatically and you'll just see blank previews. Refreshing doesn't help either. To get them to show up I had to move them out of their folder with Exporer (ie outside of ON1) and when moving them back again, that's when Photo Raw will re-read them as new files.

    0
  • Ray Alstrom

    The latest version 2022.5 did not address my issue (see my previous post in this thread). When opening any NEF or RAF file, ON1 crashes (ie., flashes then shuts itself down very quickly). Works fine with JPG or TIFF formats. I'm not a computer novice. I retired after 34 years working in IT. Granted, I'm not a programmer, but I do understand most concepts relating to software. As I've stated earlier, tech support tells me my computer is too old. I'll accept that and move on. The fact that ON1 won't work is not reason enough to invest in a new machine. I've got too much invested in this current setup. I like ON1 but they're not the only horse in the race. I'm back to using Skylum's Luminar 4 & Neo, though Neo runs a bit slow and that seems to be a common complaint. I do have to comment that I agreed to try Cyberlink PhotoDiirector 12 and runs very well on my "old" machine and offers the same AI features (except upsizing) as ON1 v2022.5

    0
  • Zachary Fisher

    Thanks for the tip on where the app stores the log info and how to get ON1 to read them again.  Appreciate the quick response as well.  I did report the bugs through the app.  I'm not all that willing to go much further than that at this time.  Hopefully they decide to look at this bug soon.

    If it helps anyone else.  I wasn't having this issue before the last couple of updates, so I rolled back to 2022.1 (16.0.1.11137).  I couldn't find any previous versions on the ON1 website (this should be added so people aren't getting "unofficial" copies from god knows where).  Luckily I sill had the old exe installer from Oct in my DL folder.  Up and running again on the old version.  Have viewed/edited several hundred files and its back to working fine with .RAF files.  

    0
  • Rick Sammartino Community moderator

    You're lucky if you only rolled back to 2022.1. I had to go to 2022.0, luckily I keep all of the installers. Still don't know why 2022.5 messed up perfectly good versions before it.

    On1 never has anything but the latest version available for download. If you need an older version all you have to do is ask them for it.

    0
  • Martin Evans

    Brian said:

    "Yes, as has been reported above in this thread there is a bug in the program. I would send tech support a report so they can get a better handle on how many users are being affected by it. The more folks that report it the more likely it will get a higher priority for being fixed."

    I have sent a very detailed bug report twice now. Clearly quite a number of people are experiencing this issue. At what point will On1 consider this needs to be higher priority? I'm stuck with 2022.0 and missing a number of features added since. I've tried all versions since 2022.0 and all have the same issue. Even a "Community moderator" is experiencing this issue and yet still it is not addressed.

    Such a shame as I really like PR.

    0
  • Rick Sammartino Community moderator

    We already know there is nothing wrong with the files. Trashing the corrupt file log just allows Photo Raw to rescan those photos, it doesn't do anything about fixing the problem. Consider yourself lucky if you can get into edit mode with those files. Still waiting for On1 to come up with a bug fix for this problem.

    1
  • Keith Heinrich

    Add my name to the list. I am reasonably tolerant of defects but this has made it unusable. In this day and age, such a serious defect is unacceptable. Here's hoping the sort it soon since I want to edit images and its just not fit for purpose right now.

    0
  • Keith Heinrich

    2022-07-25 3:36:12 ON1 - Event (-2) on line 1428 of ONImageFormat.cpp
    2022-07-25 3:36:12 ON1 - Event (-2) on line 1550 of ONPreviewSvcRunnable.cpp
    2022-07-25 3:36:12 ON1 - Failing over to LibRaw for file://localhost/Y:/2006/04/07/PICT0053.mrw.

    2022-07-25 3:36:12 ON1 - Event (-2) on line 1428 of ONImageFormat.cpp
    2022-07-25 3:36:12 ON1 - Event (-2) on line 1550 of ONPreviewSvcRunnable.cpp
    2022-07-25 3:36:13 ON1 - Event (-2) on line 1428 of ONImageFormat.cpp
    2022-07-25 3:36:13 ON1 - Event (-2) on line 1550 of ONPreviewSvcRunnable.cpp
    2022-07-25 3:39:44 ON1 - Event (1118) on line 4233 of ONPhotoRaw.cpp
    2022-07-25 3:39:44 ON1 - Event (1118) on line 508 of ONPhotoRaw.cpp

    And from there it seems to go into a spiral of death until it locks up and I reset it.

    0
  • Martin Evans

    Please report it to On1 Keith. The more that do hopefully it will persuade On1 to fix the issue. Also please let us know any response you get.

    0
  • Keith Heinrich

    Shall do.

    0
  • Ray Alstrom

    Here we are. Another update to ON1 a couple weeks ago and the issue still persists. I keep hoping a resolution is found, but I'm more or less resigned to the fact that ON1 isn't going to work for me. It's a shame because I like the program. At this point I'd settle for just knowing why a RAW file - whether Nikon, Fuji, Canon, etc., causes their software to crash. Certainly a weird issue given that none of their competitors software crashes opening RAW files.

    0
  • Rick Sammartino Community moderator

    Ray, it's not a a RAW file - whether Nikon, Fuji, Canon, etc., causing it to crash. It's a bug in the program that causes the RAW engine to fail when reading RAW files. It may be something to do with the new lens correction feature but it could just be a random bug somewhere. It's been 5 weeks now since tech support has been trying to find it.

    0
  • Keith Heinrich

    I've submitted a case along with some screen caps, the crash dump, the application log, the windows application log.

    In reviewing the information while preparing my submission, it appears it goes into a spiral of death with an exception and then loses contact with the Windows OS and locks up. It shouldn't be too hard for them to identify, sorting it out though I expect may take a while so they don't introduce more defects.

    Anyway its done. Hoping for a quick resolution otherwise I'll need to look at another product since there's photos need editing and right now this tool is just not worth opening to try and get anything done. 

    A great shame since I like it, but right now its like a Ferrari with a persistent engine fault. :(

    0
  • Martin Evans

    Rick, it's a shame tech support ONLY started looking for it 5 weeks ago as I reported it in 2022.1 and 2022.2 months ago. If tech support want to see it happening on my computer they could just have asked when I reported it twice and was instead dismissed as you can have a refund.

    I fear this won't be fixed in 2022 and then the only way to get the fix (if it comes) is by buying yet another version. I've paid for 2022 and have had no benefit from any of the updates as I'm stuck with 2022.0. This is pretty poor support especially now when so many people are suffering from it.

    0
  • Keith Heinrich

    I've been advised the best option for now is to reinstall the prior version. It looks like if there is a fix in the wind, its not happening any time soon.
    Unfortunately we do not have any immediate fixes, can only suggest reinstalling the previous version of ON1 PHOTO RAW 2022.1

     

    0
  • Keith Heinrich

    Martin Evans agree with your assessment. The log shows where the exception is thrown so it should be fairly simple to figure out why it happens. Claiming machine incompatibility is a weak defense. Here's hoping its just a thing that requires some better designed error handling code and not a whole redesign of the engine.

    0
  • Martin Evans

    I really don't understand why someone on the development team can't locate and fix this issue. In the crash dump analysis it clearly shows:

    FAILED_INSTRUCTION_ADDRESS: 
    ONPhotoRAW!ONRawDistort::distort+48f
    00007ffe`3322913f 660f382bc0      packusdw xmm0,xmm0

    So the problem is in the distort method of ONRawDistort in OnPhotoRaw.dll. As the DLL is called OnPhotoRaw it is likely that the code was written by an OnOne engineer.

    I was a software engineer for over 35 years and I'm sure I could have located this issue fairly quickly. I worked on in kernel device drivers for many years and was often faced with huge operating system crash dumps with no crash dump analysis tools at all and still managed to track down problems. This one is pretty well identified.

    I really feel let down by OnOne. I've invested a lot of money and time in PR and it is very frustrating as when it works it is a good photo editor.

    0

Please sign in to leave a comment.