BSoD occurs when moving the level adjustment window between screens

[kwnobu]

Hello!
Please forgive me if there are some expressions that are not correct because I am translating Japanese text.

Bug Description
BSoD occurred when moving the layer level adjustment window of Affinity Photo2 to another screen.
I disabled the hardware acceleration function, but it had no effect.

Environment where the bug occurred

• Monitor1:LG 27UP650 (3840x2160, DisplayPort)
• Monitor2:Wacom Cintiq DTK-1660 (1920x1080, HDMI)
• Monitor3:LG 22MP68VQ (1920x1080, DVI)
• CPU: AMD Ryzen7 3700X
• GPU:AMD Radeon RX580 (DriverVersion:22.20.27.09-230330a-390451C)
• Memory:32GB
• OS:Windows11 Home (Version:23H2, Build:22631.2715, Lang:Japanese)
• Application:Affinity Photo2 (Version:2.3.0)
• Stop Code:UNEXPECTED_KERNEL_MODE_TRAP

How to reproduce the bug

1. Open a PSD file in Affinity Photo2.
2. Open the Levels Adjustment window.
3. Move the level adjustment window displayed in Monitor1 to Monitor2.
4. While the window is being moved, if the mouse cursor is on the Windows taskbar, the level adjustment window will move violently and BSoD will occur.

 

[kwnobu]

Here is the PSD file where the bug occurred

test.psd

[debraspicher]

"UNEXPECTED_KERNEL_MODE_TRAP"の原因が曖昧だから、かなりおかしい。マルチーモニタに関して画面のDPIの変わりに関するかな？ 普通にBSODはドライバかハードエアためによく起こりますし。イベントビュアーでのWindowsログにソースを調べることが可能性です。 その他に、原因はまだない場合にはBSODのダンプファイルを読めるアプリがあります:

イベントビューアについての情報：https://pc-kaizen.com/windows10-how-to-start-event-viewer

BSODダンプファイルの読みアプリは（日本語版はページの下であります）https://www.nirsoft.net/utils/blue_screen_view.html

あいにく、AMD GPUのドライバに関するはAffinityに問題がよくあります。しかし、ハードウェアアクセラレーションを無効しても問題が続くことが確かにおかしい。

[debraspicher]

I've reproduced this. This UI bug also occurs on my machine. There's no BSOD, however. The CPU and GPU %'s rise considerably when the UI fails to change DPI, meanwhile my fans can be heard...

自分のパソコンでもこのUIバグもあります。ＢＳＯＤが起こってません。UIのDPI変わりが落ちると, CPUとGPU％ももっと高くようになるし、ファンの音が聞こえます。
23.12.04_07-55-50-PM_NV12_1920x1080.mkv
 

[ashf]

以下の事を試してみてください:
Please try the things below

1.  環境設定のパフォーマンスでレンダラーを変えてみる
Change the Renderer in Preferences>Performance

2. 最新のRadeonドライバーを入れてみる
Install the latest Radeon driver.
https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-580

3. リセット(Ctrl押しながら起動)してみるか再インストールしてみる
Reset the settings by starting Affinity with Ctrl key or reinstall Affinity.

[kwnobu]

3 hours ago, ashf said:

以下の事を試してみてください:
Please try the things below

1.  環境設定のパフォーマンスでレンダラーを変えてみる
Change the Renderer in Preferences>Performance

2. 最新のRadeonドライバーを入れてみる
Install the latest Radeon driver.
https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-580

3. リセット(Ctrl押しながら起動)してみるか再インストールしてみる
Reset the settings by start Affinity with Ctrl key or reinstall Affinity.

Thank you for your reply.
I have tried everything and it did not work at all.
1. changed the renderer from "Default (Radeon RX580 Series)" to "WARP".
2. updated the Radeon driver to the latest "23.10.18.06-230824a-395307C-INTERNAL-AMD-Software-PRO-Edition".
3. Tried to reset AffinityPhoto by starting it with Ctrl key pressed

 

[ashf]

Affinityの再インストールは試しましたか？
Have you tried reinstalling Affinity?

[kwnobu]

4 hours ago, debraspicher said:

"UNEXPECTED_KERNEL_MODE_TRAP"の原因が曖昧だから、かなりおかしい。マルチーモニタに関して画面のDPIの変わりに関するかな？ 普通にBSODはドライバかハードエアためによく起こりますし。イベントビュアーでのWindowsログにソースを調べることが可能性です。 その他に、原因はまだない場合にはBSODのダンプファイルを読めるアプリがあります:

イベントビューアについての情報：https://pc-kaizen.com/windows10-how-to-start-event-viewer

BSODダンプファイルの読みアプリは（日本語版はページの下であります）https://www.nirsoft.net/utils/blue_screen_view.html

あいにく、AMD GPUのドライバに関するはAffinityに問題がよくあります。しかし、ハードウェアアクセラレーションを無効しても問題が続くことが確かにおかしい。

Thanks for the reply.
Attached is a screenshot of the image as confirmed by BlueScreenView.
I have also attached a screenshot of the crash log reference screen in the control panel as guided by the event viewer.
All of the dump files shown were generated while using AffinityPhoto.
Since "cdd.dll" and "dxgkrnl.sys" are crashing, it seems certain that it is GPU-related.
It also seems certain that it is occurring during DPI conversion.

[kwnobu]

37 minutes ago, ashf said:

Affinityの再インストールは試しましたか？
Have you tried reinstalling Affinity?

I have reinstalled the application and the problem continues.

再インストールを実施しましたが、引き続きバグは発生しています。

Edited December 5, 2023 by kwnobu

[Lee_T]

Hi kwnobu,

I'm afraid A BSOD can't be caused by an (user-mode) application, only a faulty driver/hardware.

"Bug check 0x7F typically occurs after you install faulty or mismatched hardware, especially memory, or if installed hardware fails."

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7f--unexpected-kernel-mode-trap

Lee

[debraspicher]

On 12/8/2023 at 4:48 AM, Lee_T said:

Hi kwnobu,

I'm afraid A BSOD can't be caused by an (user-mode) application, only a faulty driver/hardware.

"Bug check 0x7F typically occurs after you install faulty or mismatched hardware, especially memory, or if installed hardware fails."

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7f--unexpected-kernel-mode-trap

Lee

The "bug" itself is real, because I've reproduced the dialog issue a number of times without generating a BSOD. In most of those instances, my CPU was put under substantial load (lots of noise). There's video in this post. (not of the noise, though)

Well, at least until now there was no BSOD... I was working in Publisher just now and it opened on the wrong screen as things tend to do sometimes on Windows 10. I moved the Text Frame dialog back to my bottom screen, or at least tried to, and it did the jumpy screen tearing animation and I received the same BSOD:



I'll probably run Memtest just in case overnight, but that's too much of a coincidence to blame it 100% on hardware, imo. If I'm honest, the framework Affinity is built upon as it relates to multimonitor/multiDPI setups has been anything but smooth. I've reported numerous bugs on this over the years. (This isn't a rant, I'm just stating what is relevant to what I've experienced within the context of reporting issues with DPI scaling)

Taking a look at the BSOD, mine has the same parameters as OP:



Their BSOD below:


Microsoft describes this as the following:
S: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7f--unexpected-kernel-mode-trap



Funny enough, MS seemingly contradicts itself here on the same page...

More list of causes from Windows Report:
S: https://windowsreport.com/unexpected_kernel_mode_trap-windows-10/


It's worth mentioning I've noticed more recently my EV is littered with Unhandled Exceptions from Affinity software that it seems don't alert the user:


My own PC has only had 5 BSOD (earliest is back in Feb) occurrences this year. This is something I watch for because I am undervolting my PC. One for sure I caused by unplugging something (I forget what, it was very uneventful) and the other 3 were NVIDIA HDMI AUDIO related. Only the one is related to this. While I would not rule out defects in RAM or even my undervolt adding to or making myself more prone to BSOD, I doubt that both BSODs on very different machines can be put down to the same hardware failure. Absolutely software can cause BSODs, they're just typically driver-related and software is more rare. Also, since both OP and I have experienced it before moving panels between displays with the exact same visual defect, it seems reasonable there's a software correlation. Both OP and I are using AMD and NVIDIA GPUs, so it can't even be blamed on manufacturer-specific GPU drivers...

Ask yourself, why should moving a single panel cause the CPU to suddenly run at high load? I've never seen this issue on any machine. My own experience with multi-monitor setups otherwise has been generally seamless with Windows 10 (and I expect Windows 11/12 as well when I upgrade).

Edit: Memtest passed.