Jump to content

Photo 2 new install crashes when I try to open any image

AMonty
 Share

Recommended Posts

AMonty

AMonty

Posted
Posted

On my laptop, Photo 2 works fine when running under Windows 10 on the main partition. However I also have an encrypted (bitlocker) partition that I can dual-boot into, running Windows 10 Pro. On that, Photo 2 loads up fine, but then disappears (crashes and closes) whenever I try to open an image (have tried jpegs and pngs).

I presume the problem is not bitlocker as that should be invisible to apps. Maybe it's something to do with the W10 Pro installation vs the W10 home (where it works)?

Anyway, my system info:

         Operating System: Windows 10 Pro 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
                 Language: English (Regional Setting: English)
      System Manufacturer: LENOVO
             System Model: 82JU
                     BIOS: GKCN65WW (type: UEFI)
                Processor: AMD Ryzen 7 5800H with Radeon Graphics          (16 CPUs), ~3.2GHz
                   Memory: 32768MB RAM
      Available OS Memory: 28524MB RAM
                Page File: 6228MB used, 26903MB available
              Windows Dir: C:\Windows
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 120 DPI (125 percent)
       System DPI Setting: 120 DPI (125 percent)
          DWM DPI Scaling: UnKnown

 

And in the Windows Event Viewer I find: 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name=".NET Runtime" /> 
  <EventID Qualifiers="0">1026</EventID> 
  <Version>0</Version> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2024-08-29T07:57:55.6295256Z" /> 
  <EventRecordID>1837</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="0" ThreadID="0" /> 
  <Channel>Application</Channel> 
  <Computer>Legion5-W10-Pro</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>Application: Photo.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Runtime.InteropServices.SEHException at <Module>.Serif.Interop.Persona.UserInterface.DocumentRenderWindow.{ctor}(Serif.Interop.Persona.UserInterface.DocumentRenderWindow*, TabletContext*) at Serif.Interop.Persona.UserInterface.DocumentRenderControl.BuildWindowCore(System.Runtime.InteropServices.HandleRef) at System.Windows.Interop.HwndHost.BuildWindow(System.Runtime.InteropServices.HandleRef) at System.Windows.Interop.HwndHost.BuildOrReparentWindow() at System.Windows.Interop.HwndHost.OnSourceChanged(System.Object, System.Windows.SourceChangedEventArgs) at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.PresentationSource.UpdateSourceOfElement(System.Windows.DependencyObject, System.Windows.DependencyObject, System.Windows.DependencyObject) at System.Windows.PresentationSource.OnVisualAncestorChanged(System.Windows.DependencyObject, System.Windows.Media.AncestorChangedEventArgs) at System.Windows.UIElement.OnVisualAncestorChanged(System.Object, System.Windows.Media.AncestorChangedEventArgs) at System.Windows.Media.Visual.ProcessAncestorChangedNotificationRecursive(System.Windows.DependencyObject, System.Windows.Media.AncestorChangedEventArgs) at System.Windows.Media.Visual.AddVisualChild(System.Windows.Media.Visual) at System.Windows.FrameworkElement.set_TemplateChild(System.Windows.UIElement) at System.Windows.Controls.ContentPresenter+UseContentTemplate.BuildVisualTree(System.Windows.FrameworkElement) at System.Windows.StyleHelper.ApplyTemplateContent(System.Windows.UncommonField`1<System.Collections.Specialized.HybridDictionary[]>, System.Windows.DependencyObject, System.Windows.FrameworkElementFactory, Int32, System.Collections.Specialized.HybridDictionary, System.Windows.FrameworkTemplate) at System.Windows.FrameworkTemplate.ApplyTemplateContent(System.Windows.UncommonField`1<System.Collections.Specialized.HybridDictionary[]>, System.Windows.FrameworkElement) at System.Windows.FrameworkElement.ApplyTemplate() at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Grid.MeasureCell(Int32, Boolean) at System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef) at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Control.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at MS.Internal.Helper.MeasureElementWithSingleChild(System.Windows.UIElement, System.Windows.Size) at System.Windows.Controls.ContentPresenter.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.ContextLayoutManager.UpdateLayout() at System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Object) at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object) at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at Photo.Application.Main(System.String[])</Data> 
  </EventData>
  </Event>

 

Link to comment
Share on other sites
carl123

carl123

Posted
Posted

Try...

Edit > Settings > Performance

and untick Hardware Acceleration if it's on

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites
AMonty

AMonty

Posted
  • Author
Posted
13 minutes ago, carl123 said:

Try...

Edit > Settings > Performance

and untick Hardware Acceleration if it's on

Thank you. I just tried that now, same problem.

Further info:

Photo 2 and Windows 10 Pro are fully up to date. Photo 2 says version 2.5.3 and Windows Update says I'm up to date.

Link to comment
Share on other sites
carl123

carl123

Posted
Posted

In the same dialog try changing the renderer to warp (and restart APhoto)

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites
AMonty

AMonty

Posted
  • Author
Posted
8 minutes ago, carl123 said:

In the same dialog try changing the renderer to warp (and restart APhoto)

Thanks. The renderer dropdown is empty.

So I booted back into the W10 installation where Photo 2 works, and there are several entries in that dropdown, including warp.

Sounds like you're homing in on the problem. Any ideas why the dropdown is empty, and what to do about it? Seems strange since the hardware is identical, it's the same laptop.

 

Link to comment
Share on other sites
carl123

carl123

Posted
Posted
9 minutes ago, AMonty said:

So I booted back into the W10 installation where Photo 2 works

If it works there it looks like it installed OK

I'm afraid I don't know enough about an "encrypted (bitlocker) partition" to know what it's doing

So, I'll leave it to someone else to advise you further

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites
carl123

carl123

Posted
Posted

Sorry, once last thing

Try running it as Admin (right-click, Run as Administrator)

Just to eliminate that

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites
AMonty

AMonty

Posted
  • Author
Posted
18 minutes ago, carl123 said:

Sorry, once last thing

Try running it as Admin (right-click, Run as Administrator)

Just to eliminate that

Running as Admin didn't change things - dropdown still empty and still crashed.

However, the strange absence of anything in the renderer dropdown was the clue.

I figured if the hardware is identical, but it's working on one OS and not another, then maybe it's a driver. I found a more recent NVidia driver and installed it. After a reboot, the dropdown now has the same entries in it.

What's strange is that there were no entries at all before. The laptop has both integrated graphics (AMD) and dedicated graphics (NVidia). And updating just the NVidia driver has now made BOTH entries appear in the dropdown.

Anyway, problem solved. Thanks for your help in homing in quickly on it being a graphics/renderer problem.

Link to comment
Share on other sites
walt.farrell

walt.farrell

Posted
Posted

Good work on figuring it out, and yes, the empty Renderer dropdown is a solid clue for that situation :) 

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 
    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.