Bug 498218 - Windows 10 crashes when Digikam is moved to secondary monitor
Summary: Windows 10 crashes when Digikam is moved to secondary monitor
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (other bugs)
Version First Reported In: 8.5.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-03 18:30 UTC by HubMiner
Modified: 2025-12-23 18:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Misc Settings screen (47.45 KB, image/png)
2025-01-03 20:35 UTC, HubMiner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description HubMiner 2025-01-03 18:30:06 UTC
Windows 10, 22H2, updated to latestpatches and NVidia drivers.
All other software is functional and stable.
GPU: NVidia 1660 TI + Intel HD Graphics 4000 (from CPU Intel i7 3770K).
Digikam version: 8.5.0
Nvidia drivers: 566.36

Scenario:
a clean run: no other software in foreground.
Open Digikam, the window shows on the primary monitor.
Move the windows to secondary monitor.
BSOD within seconds.

Stop code: SSTEM SERVICE EXCEPTION
What failed: dxgmms1.sys

The issue is consistently reproducable.
Comment 1 Maik Qualmann 2025-01-03 18:37:37 UTC
Please enable forcing software OpenGL for a test in the digiKam settings under Miscellaneous->System. Restart digiKam and try moving digiKam to another monitor again.

Maik
Comment 2 HubMiner 2025-01-03 20:35:06 UTC
Created attachment 177081 [details]
Misc Settings screen

Tested as instructed, crashed again.
Comment 3 HubMiner 2025-01-04 02:07:15 UTC
I addressed the issue for myself - the primaty monitor was plugged into HDMI port corresponding to the CPU integrated GPU.  
Having both monitors plugged into NVidia removes the crash: it occurs when the window is moved from the integrated GPU supported screen to NVidia supported screen.
Comment 4 caulier.gilles 2025-03-15 15:32:28 UTC
Hi,

digiKam 8.6.0 is just released:

https://www.digikam.org/news/2025-03-15-8.6.0_release_announcement/

Problem still exists with this version?

Thanks in advance

Gilles Caulier
Comment 5 caulier.gilles 2025-04-11 17:34:03 UTC
Hi,

The digiKam 8.7.0 pre-release for Windows have been rebuild from scratch today with many improvements and updates. Please test with this version to see if the problem is reproducible.

Link to download: https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier
Comment 6 caulier.gilles 2025-12-22 03:05:03 UTC
HubMiner,

Any feedback here using last stable digiKam 8.8.0 ?

Giles Caulier
Comment 7 HubMiner 2025-12-23 18:46:25 UTC
Greetings Giles!
TLDR: Still an issue.

Just for my favorite app team, I got on my knees and switched video cable just for the test! :)

# Versions
Digikam: 8.8.0
Windows: 11 / 24H2 26100.7462
Nvidia driver: recent: 581.80

# Hardware setup:
- Primary monitor is connected to CPU-integratred video.
- Secondary monitor is connected to NVidia GPU.
- No graphics issues with any other apps.

# TEST 1:

Open Nvidia Control Panel.
* As intended, it shows only one monitor connected to the Nvidia GPU.

PC is under a light load.  Start Digikam.
* Digikam opened on my default monitor that was connected to CPU-integratred video.  Observed for a few minutes: working fine, finished startup scan.

I dragged DK window to the secondary monitor (connected to NVidia GPU), idle for a few minutes.
* no issues.

While DK was on secondary monitor, I closed it (hoping to save its window position).
* no issues.


# TEST 2A:

Start DK (after it was closed on secondary/Nvidia monitor).
* DK window started on the secondary monitor.
I didn't interact with the window.
* After a few seconds, Windows crashed.


# TEST 2B:

Start DK again.
* Crashed again.  Approximate message: your device ran into problem and needs to restart...
* The message dissapeared too fast - I could not catch the driver name.


# TEST 3:
Reconnect both monitors to NVidia GPU and verify their visibility with NVidia Control Panel.
* success.

Start DK.
* success, the initial scan completed, running for 30 seconds.

Move DK to the primary window and close (to save position).

Start DK.
* success, the initial scan completed, running for 30 seconds.

An observation: while DK was starting, I was staring at Process Explorer.  It showed "C:\Program Files\digiKam\snoretoast.exe" ran for a few seconds and closed.  Probably some magic DK does under the hood.


Windows EventLog mentions log files around the same time - possibly related.  Please let me know if I can email them to you (I prefer not to post them in a public way).
I can try to record DubugView trace if it helps.


Thank you!