A lot of crashes with windoews V8

I keep getting crashes with V8 and 8.1. Non have got a PL crash report just in windows. Problem Event Name: CLR20r3
Problem Signature 01: DxO.PhotoLab.exe
Problem Signature 02: 8.1.20004.434
Problem Signature 03: fb6dbcaa
Problem Signature 04: DxONET.CorrectionEngine
Problem Signature 05: 8.1.20004.434
Problem Signature 06: 67055519
Problem Signature 07: 16a8
Problem Signature 08: 2
Problem Signature 09: System.NullReferenceException
OS Version: 10.0.26100.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 4354
Additional Information 2: 435482d30722f29daf475b85c4cc8253
Additional Information 3: 4a09
Additional Information 4: 4a098ff5402d9d4643dc0a395395359b

I don’t even really know whats causing them as I am not really aware of the problem until its not there! Some times as today it was minimized and went, having to be reloaded when needed. This is W11 and NVIDIA fully updated. Am I the only none?

video card and driver version? Is windows otherwise fully up to date?

NVIDIA system information report created on: 10/23/2024 21:51:04
NVIDIA app version: 10.0.3.163
Operating system: Microsoft Windows 11 Home, Version 10.0.26100
DirectX runtime version: DirectX 12
Driver: Studio Driver - 565.90 - Oct 15, 2024
CPU: AMD Ryzen 9 3900X 12-Core Processor
RAM: 32.0 GB
Storage (3): SSD - 1.8 TB,SSD - 1.8 TB,+1 more

Graphics Card
GPU processor: NVIDIA GeForce RTX 4070
Direct3D feature level: 12_1
CUDA cores: 5888
Graphics clock: 2520 MHz
Resizable bar: No
Memory data rate: 21.00 Gbps
Memory interface: 192-bit
Memory bandwidth: 504.048 GB/s
Total available graphics memory: 28622 MB
Dedicated video memory: 12282 MB GDDR6X

I recently updated to PhotoLab 8.1
Updated windows and Nvidia driver
As doing some simple edits of my grand daughter and the system crashed during export.
Removed some of the edits and was then able to export.

It’s difficult geing onto suport when no crash logs and in my case I have no idea why thr crashes. No other program is doing it. Just have to hope 8.2 gets better.

I just had the experience of having my computer freeze while resizing a control point in PL8.1 (Windows 11). The mouse cursor worked but wouldn’t change back from the resize icon for at least a minute. When it did change back to an arrow, I noticed that the Image Viewer was in the process of refreshing, but nothing on screen was being redrawn. Ctrl+Alt+Del took about a minute to have an effect. When I canceled that action, Windows reported that PL8 had stopped responding. I restarted PL8 and have had no further problems so far. While I’ve only worked on a few images, I’ve made extensive use of local adjustments and ViewPoint 5’s ReShape tool.

The problem will probably get fixed eventually, as has happened with previous releases.

Even with updated video drivers and Win 11 up-to-date, I’m getting frequent freezes/crashes with PL8.1 while using local adjustments (mainly control points and control lines). While experimenting with the placement of these adjustments and dragging various sliders, PL becomes unresponsive. It takes a while - working on two difficult images has been long enough to experience the problem. Trying to figure out how exactly to reproduce this so that I can report a bug. Probably a memory leak or a bunch of them. Unfortunately, I’ve already spent much of my evening submitting bug reports for PL8, so am starting to think of it as a waste of time. :pensive:

Well I can add to the bugs:

I can’t get the grid in the Warp tool VP5 to respond to mouse clicks or drags! About 90% of the time it is totally unresponsive even though the underlying image is warped. I can’t even change the size of the grid.

No help from DxO even though I logged a bug report.

A late comment.
Did you google the problems? First one seems to be related to the framework.

George

If the problem is manifested in DxO software, then I’m content with reporting the bugs and how to reproduce them. They can do the rest.

The warp grid works fine for me, except that the arrow keys won’t move the selected points/areas. Shift+Arrow works for the most part, but can’t be used to return the selection to its original position. So many bugs, all I can do is report them and move on.

The problem exists on the computer of @John7 , not on yours or mine.
Google on the event name points to the .Net framework. So it seem logic to check that and not all the other drivers.

George

Oh, I see. Yes, you’re right, George. John, making sure that .NET is up-to-date on your computer is an important next step. (Just run Windows Update and check for updates.) If the CLR event continues to occur, then it could be corrupt files: using the sfc and dism commands as administrator can check for that and fix issues. Similarly, cleaning up temporary files on the computer (disk cleanup utility in Windows) might help. There’s still a chance this is a PhotoLab problem, but ruling out local computer issues is needed.