Crashes

[Thanatica]

SIB++ has been crashing ever since I installed it years ago, but only ever when I click the start button on the secondary screen which is positioned above my primary screen.

I've had different kinds of monitors, all positioned above the primary monitor. My primary monitor has always been 4K @ 250%, but my secondary monitor has been a ultrawide @ 125%, a 1440p monitor @150% and now a 4K monitor @200%. So the type of monitor doesn't cause it to crash.

I've also gone through several major Windows 10 updates, all the way from the RTM release to the 20H2 update. So the exact Windows version also doesn't matter.

 

I think I've reported this issue before. But it's really starting to kind of irritate me. SIB++ has gone through so many updates and it still crashes... And when it does, it takes down the whole explorer.exe process, costing me a couple of seconds to wait for that to respawn, which is especially irritating when I only wanted to reach the shutdown button.

Can this problem please be solved with some kind priority?

[Tihiy]

It certainly should be. Provide a crash dump (https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps or procdump)

[Thanatica]

I tried to follow that article, and created `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\explorer.exe` without any further settings. The defaults are fine with me. However, a crash dump is not being stored in `%LOCALAPPDATA%\CrashDumps` after a crash.

It might be presumptious of me to add explorer.exe, but I don't know what other process it would be. I don't know what do to next. Can you provide more details on how to get Windows to make a crashdump for SIB++?

Also, btw, in order to make it crash, of course I had a more difficult time to make it crash. Just frantically clicking the start buttons did it. At the time of posting this issue, a crash after clicking the secondary start button was pretty much 100% reproducible on my pc. But that was in the afternoon. Maybe in the morning it's different somehow. I don't know what to make of that, but maybe you do.

Edited April 28, 2021 by Thanatica

[Tihiy]

Crash info can be found via search 'View all problem reports' - then find latest crash for Windows Explorer and copy technical info here

Also try this? https://support.citrix.com/article/CTX118614

Edited April 28, 2021 by Tihiy

[Thanatica]

On 4/28/2021 at 11:43 AM, Tihiy said:

Crash info can be found via search 'View all problem reports' - then find latest crash for Windows Explorer and copy technical info here

Also try this? https://support.citrix.com/article/CTX118614

Here's one:

Source
Windows Explorer

Summary
Stopped responding and was closed

Date
‎28-‎04-‎2021 09:51

Status
Report sent

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:    C:\Windows\explorer.exe

Problem signature
Problem Event Name:    AppHangB1
Application Name:    explorer.exe
Application Version:    10.0.19041.928
Application Timestamp:    bc61eb13
Hang Signature:    f410
Hang Type:    134217728
OS Version:    10.0.19042.2.0.0.256.48
Locale ID:    2057
Additional Hang Signature 1:    f41059ebfeab8429f3b790afec2e77a6
Additional Hang Signature 2:    f428
Additional Hang Signature 3:    f4283016ddebc49996cb4cf3be60a191
Additional Hang Signature 4:    f410
Additional Hang Signature 5:    f41059ebfeab8429f3b790afec2e77a6
Additional Hang Signature 6:    f428
Additional Hang Signature 7:    f4283016ddebc49996cb4cf3be60a191

Extra information about the problem
Bucket ID:    570a794a6725abc3718d06b4e58fbabd (1264674444376259261)

The link you shared shows the same information again, which I already said doesn't generate any crashdumps.

[Tihiy]

Yeah, because it's not a crash, but a hang. Hang can be captured with

procdump -h explorer.exe