1.44 - Explorer.exe crashes when combined with Edge window

from Stardock Forums

A new behaviour today: Explorer.exe keeps crashing after it's combined with an Edge window. Affects Edge RTM and Edge Dev versions.

The windows combine fine, but when tabs are switched, Explorer crashes with the following error in the Application Log: (event ID 1000), and eventually redraws itself (Desktop, Taskbar, etc)

Faulting application name: explorer.exe, version: 10.0.19041.610, time stamp: 0xab30c679

Faulting module name: ucrtbase.dll, version: 10.0.19041.546, time stamp: 0x43cbc11d

Exception code: 0xc0000409

Fault offset: 0x000000000007287e

Faulting process ID: 0x1654

Faulting application start time: 0x01d6c30738182e9b

Faulting application path: C:\WINDOWS\explorer.exe

Faulting module path: C:\WINDOWS\System32\ucrtbase.dll

I've tried to work out whether anything new is present, but there doesn't seem to be - this was working OK all day yesterday.

Ah - a bit more testing shows that any time Edge is Grouped at all, any switch to or from it restarts Explorer even when explorer isn't part of that group.

Affects both the Stable 87.0.664.47 and the Dev 88.0.702.0 versions of Edge... at least today!

groupy
12,076 views 8 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. Have you tried Groupy V1.45? https://forums.stardock.com/502398 . Please try it and report back.

Thanks
Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

Which version of Windows are you using?

The only option that comes to mind that could impact explorer would be the option to hide the windows from the taskbar.  Do you have this enabled?

Also do you consider yourself a technically advanced user who might be able to run Windbg to capture a dmp file from the crash if given instructions?  It would be best to use the 1.45 beta for that that basj has linked to.

Siege of Centauri
Reply #3 from Stardock Forums Top

Just retraced yesterday's steps and yep! Had enabled the "one button for all windows" option in Groupy. Unticking that fixes the issue.

Quoting Neil, reply 2

Also do you consider yourself a technically advanced user who might be able to run Windbg to capture a dmp file from the crash if given instructions?  It would be best to use the 1.45 beta for that that basj has linked to.
End of Neil's quote

No, but I do consider myself a useful idiot who's been trained to take a crash dump on occasion :)

I can't grab a dump from the machine with the problem, but can install Groupy on a different one and try to repro - as a trial user for now, I don't think I can get 1.45 beta through the described pathways yet.

Reply #4 from Stardock Forums Top

Fixed the no-access-to-1.45 issue by upgrading ;) - will give it a try. I'll PM a link to the Explorer dump when done.

Reply #5 from Stardock Forums Top

Quoting treestarnk, reply 4

Fixed the no-access-to-1.45 issue by upgrading ;) - will give it a try. I'll PM a link to the Explorer dump when done.
End of treestarnk's quote

Hi! Just checking whether the crash dump was useful? I can't see the PM I (think I) sent anymore, so please PM me for a link to the dump if still needed.

Thanks!

Reply #7 from Stardock Forums Top
Quoting treestarnk, reply 3

Just retraced yesterday's steps and yep! Had enabled the "one button for all windows" option in Groupy. Unticking that fixes the issue.

End of treestarnk's quote

If it's not too much and if you don't mind can you tell us where that setting is?? "one button for all windows"

 

Reply #8 from Stardock Forums Top

Quoting Ncruze, reply 7

If it's not too much and if you don't mind can you tell us where that setting is?? "one button for all windows"
End of Ncruze's quote

I believe he is referring to this one

Thank you,

Basj,
Stardock Community Assistant

+1 Loading…