PoB closes (crashes?) when I take a screenshot (LeftWin+PrtScr)

[Eqatrpfvvzzih]

Check version

• [X] I'm running the latest version of Path of Building and I've verified this by checking the changelog

Check for duplicates

• [X] I've checked for duplicate open and closed issues by using the search function of the issue tracker

Screenshots of crash/graphical issue, version and options menu

What are your system specifications and configuration?

OS Name Microsoft Windows 11 Home Adapter Description NVIDIA GeForce GTX 1060

Keyboard: Description HID Keyboard Device Driver C:\WINDOWS\SYSTEM32\DRIVERS\KBDHID.SYS (10.0.22621.1, 72.00 KB (73,728 bytes), 2022-05-07 7:19)

Description USB Input Device Driver C:\WINDOWS\SYSTEM32\DRIVERS\HIDUSB.SYS (10.0.22621.2506, 76.00 KB (77,824 bytes), 2023-10-30 0:08)

Laptop: System Manufacturer ASUSTeK COMPUTER INC. System Model TUF GAMING FX504GM_FX80GM

How to reproduce the issue

Press LeftWin+PrtScr key combination. (I.e. take a screenshot.)

If you select (focus) any other application, for example Firefox or Notepad++, pressing LeftWin+PrtScr causes the normal thing: taking a screenshot, and keeping the application untouched. If you select (focus) Path of Building (and, inside Path of Building, probably any view, for example a tree of some build), then pressing LeftWin+PrtScr causes 2 things: the screenshot is taken (it is okay), and Path of Building closes (disappears) (that is not okay). Before disappearing the cursor becomes (for a fraction of second) to hourglass.

My Windows Taskbar is configured so "Automatically hide the taskbar". When I select (focus) an application, then it occupies the whole screen.

In the past, I have taken several screenshots inside (older version of) Path of Building. {Why does one need taking screenshot? - Because my PC (vide card) is not so strong. PoB uses rather high GPU amount. When I run Path of Exile, then I used to minimize other GPU-demanding applications.}

Character build code

No response

[Wires77]

I'm unable to reproduce this on my Windows 11 laptop unfortunately. If you open Event Viewer > Windows Logs > Application do you see an error there?

[Nightblade]

@Eqatrpfvvzzih are you still having this problem?

[VenomousInc]

I am on Windows 10 and I can confirm I crash when taking a screenshot. Event Viewer:

Faulting application name: Path of Building.exe, version: 0.0.0.0, time stamp: 0x65fd9292 Faulting module name: Path of Building.exe, version: 0.0.0.0, time stamp: 0x65fd9292 Exception code: 0xc0000409 Fault offset: 0x00000000000100cd Faulting process ID: 0x12dc Faulting application start time: 0x01daf0cae45f2f98 Faulting application path: C:\Program Files (x86)\Path of Building\Path of Building.exe Faulting module path: C:\Program Files (x86)\Path of Building\Path of Building.exe Report ID: 92175cd3-b079-408a-b6e5-3eea15dfe0c5 Faulting package full name: Faulting package-relative application ID:

[Paliak]

Any pob related .dmp files in %AppData%\Local\CrashDumps? Is the file written correctly to disk?

[VenomousInc]

There's a .wer and a .dmp file assciociated

[Paliak]

Are you okay with sharing either here or more privately through discord? Also sorry i meant to ask if the screenshot file is saved correctly.

[VenomousInc]

Edit: Screenshot correctly goes to clipboard, then i get the windows loading cursor for half a second, and then 2 or 3 seconds later it closes out. Also it only happens when the Application is focused, I can hover over stuff and screenshot it with another window in focus.

If it's easier we can move to Discord, I'd rather be walked through pulling the useful data if possible though. I've not used WinDbg before but I gave it a go:

0:000> !analyze -v

---

• *
• Exception Analysis *
• *

  ---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1249

Key  : Analysis.Elapsed.mSec
Value: 10118

Key  : Analysis.IO.Other.Mb
Value: 1

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 20

Key  : Analysis.Init.CPU.mSec
Value: 374

Key  : Analysis.Init.Elapsed.mSec
Value: 9971

Key  : Analysis.Memory.CommitPeak.Mb
Value: 103

Key  : FailFast.Name
Value: FATAL_APP_EXIT

Key  : FailFast.Type
Value: 7

Key  : Failure.Bucket
Value: FAIL_FAST_FATAL_APP_EXIT_c0000409_Path_of_Building.exe!Unknown

Key  : Failure.Hash
Value: {bcb2102a-0d81-512e-c111-089a04aaf2c5}

Key  : Timeline.Process.Start.DeltaSec
Value: 879

Key  : WER.OS.Branch
Value: vb_release

Key  : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: Path of Building.exe.16184.dmp

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: 000000a80cb4de88 -- (.cxr 0xa80cb4de88) rax=0000000100000010 rbx=00007ffc7c3a23ff rcx=0000000000000000 rdx=000000000010000b rsi=000004e8fffffb30 rdi=000004d0fffffb30 rip=00007ffc7c496e9c rsp=0000000000000000 rbp=000000a80cb4e170 r8=0000000000000019 r9=0000000000000000 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=000000a80cb4e000 r14=000000a80cb4fbb0 r15=00007ffc7c350000 iopl=0 nv up di pl nz na pe nc cs=0000 ss=0000 ds=0000 es=0000 fs=0000 gs=0000 efl=00000000 ntdll!_xmm+0x6d9c: 00007ffc7c496e9c 0100 add dword ptr [rax],eax ds:0000000100000010=???????? Resetting default scope

EXCEPTION_RECORD: 00007ffc7c46d210 -- (.exr 0x7ffc7c46d210) ExceptionAddress: 0000000000040002 ExceptionCode: 000a0008 ExceptionFlags: 00000000 NumberParameters: 2085063320 Parameter[0]: 00000000001e001c Parameter[1]: 00007ffc7c478c58 Parameter[2]: 00000000002a0028 Parameter[3]: 00007ffc7c478c28 Parameter[4]: 0000000000360034 Parameter[5]: 00007ffc7c478bf0 Parameter[6]: 000000000020001e Parameter[7]: 00007ffc7c478bd0 Parameter[8]: 00000000001c001a Parameter[9]: 00007ffc7c478bb0 Parameter[10]: 00000000001a0018 Parameter[11]: 00007ffc7c478b90 Parameter[12]: 0000000000220020 Parameter[13]: 00007ffc7c478b68 Parameter[14]: 0000000000320030

PROCESS_NAME: Path of Building.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000007

FAULTING_THREAD: 000017e4

STACK_TEXT:
000000a80cb4d790 00007ff68dd90095 : 000000a80cb4e170 00007ff68dd85fc0 0000002000001000 0000000001000000 : Path_of_Building+0x100cd 000000a80cb4d7c0 00007ff68dd8601a : 0000000000069000 0000000000003000 0000000000000000 00000000ffffffff : Path_of_Building+0x10095 000000a80cb4d7f0 00007ffc7a0734a7 : 0000000000000000 00007ff68dd85fc0 0000000000000000 000000a80cb4d990 : Path_of_Building+0x601a 000000a80cb4d820 00007ffc7c3f5898 : 000000a80cb4da60 00007ffc7c496e9c 0000000000000000 000000a80cb4d9f8 : KERNELBASE!UnhandledExceptionFilter+0x1e7 000000a80cb4d940 00007ffc7c3dce56 : 00007ffc7c4c473c 00007ffc7c350000 000000a80cb4da60 00007ffc7c380e7b : ntdll!RtlUserThreadStart$filt$0+0xa2 000000a80cb4d980 00007ffc7c3f292f : 0000000000000000 000000a80cb4df60 000000a80cb4e940 0000000000000000 : ntdll!_C_specific_handler+0x96 000000a80cb4d9f0 00007ffc7c3a2554 : 0000000000000000 000000a80cb4df60 000000a80cb4e940 0000000000000001 : ntdll!RtlpExecuteHandlerForException+0xf 000000a80cb4da20 00007ffc7c3a22a7 : 0000000000000000 000000a80cb4e7e0 0000000000000000 000000a80cb4e170 : ntdll!RtlDispatchException+0x244 000000a80cb4e130 00007ffc79f7b699 : 000000a80cb4ea10 00007ffc3c4ed588 000000a80cb4eac0 000000a80cb4eb28 : ntdll!RtlRaiseException+0x1d7 000000a80cb4e920 00007ffc55a15267 : 000000a80cb4eac0 000000a80cb4eae8 0000000000000000 0000000000000000 : KERNELBASE!RaiseException+0x69 000000a80cb4ea00 00007ffc3c3e3e95 : 0000000000204021 0000000000000000 00007ffc3c4adda8 0000000000000000 : VCRUNTIME140!_CxxThrowException+0x97 000000a80cb4ea60 00007ffc3c3dc75b : 0000000000000019 0000000574547200 000000a800000001 0000000000000019 : SimpleGraphic+0x43e95 000000a80cb4eb60 00007ffc3c3de026 : 0000000000000000 000001e75757b560 0000000000000000 0000000000000000 : SimpleGraphic+0x3c75b 000000a80cb4ed10 00007ffc3c3fd34f : 000001e74fee85e0 000001e74fee85e0 000001e74feb27c8 0000000000000010 : SimpleGraphic+0x3e026 000000a80cb4f6f0 00007ffc3c3ee394 : 000001e74feb27c8 000001e74feb2858 000001e74feb27b0 000000000000003e : SimpleGraphic!RunLuaFileAsWin+0x990f 000000a80cb4f720 00007ffc3c3f3a9d : 000001e74feb79f0 000001e74feb79f0 0000000000000001 000001e74fea5590 : SimpleGraphic+0x4e394 000000a80cb4fa00 00007ff68dd83455 : 000001e74feb79f0 000000a80cb4fad9 000001e74feb27b0 000001e74fec48bb : SimpleGraphic!RunLuaFileAsWin+0x5d 000000a80cb4fa30 00007ff68dd85d36 : 0000000000000000 0000000000000001 0000000000000000 0000000000000000 : Path_of_Building+0x3455 000000a80cb4fb40 00007ffc7a497374 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : Path_of_Building+0x5d36 000000a80cb4fb80 00007ffc7c39cc91 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x14 000000a80cb4fbb0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x21

STACK_COMMAND: ~0s ; .cxr ; kb

SYMBOL_NAME: path_of_building+100cd

MODULE_NAME: Path_of_Building

IMAGE_NAME: Path of Building.exe

FAILURE_BUCKET_ID: FAIL_FAST_FATAL_APP_EXIT_c0000409_Path_of_Building.exe!Unknown

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {bcb2102a-0d81-512e-c111-089a04aaf2c5}

Followup: MachineOwner

[Paliak]

I meant the raw file as i could then load it into a debugger with debug symbols with SG. Though what you posted helps as well.

[VenomousInc]

I tried to upload the .wer file but it won't let me - can I send it to you via discord?

[Paliak]

Yup feel free to message me paliak or localidentity for an invite to the POB discord.