Closed dacowan closed 4 years ago
betting this is the fancyzone bug. @enricogior, thoughts?
@dacowan open the Event Viewer and check if under Windows Logs -> Application there is an error that reference PowerToys.exe or fancyzones.dll. Thanks.
Is this what you need?
Faulting application name: PowerToys.exe, version: 0.20.0.0, time stamp: 0x5f24295b
Faulting module name: fancyzones.dll, version: 0.20.0.0, time stamp: 0x5f24245d
Exception code: 0xc0000005
Fault offset: 0x0000000000049f80
Faulting process id: 0x18d4
Faulting application start time: 0x01d66ab300ea9246
Faulting application path: C:\Program Files\PowerToys\PowerToys.exe
Faulting module path: C:\Program Files\PowerToys\modules\FancyZones\fancyzones.dll
Report Id: 75c924bd-20c8-44f2-b531-9de0602e4fa2
Faulting package full name:
Faulting package-relative application ID:
Fault bucket 1675987067522569254, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: PowerToys.exe
P2: 0.20.0.0
P3: 5f24295b
P4: fancyzones.dll
P5: 0.20.0.0
P6: 5f24245d
P7: c0000005
P8: 0000000000049f80
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER64D8.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6537.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6548.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6557.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6577.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_PowerToys.exe_70c89a9d86636c17e47cefe528634462831f3d_5d6c46e5_ac890c32-576e-432c-955a-5365a532ff3b
Analysis symbol:
Rechecking for solution: 0
Report Id: 8cbdc3e1-a74d-47f8-96ab-294272285a5a
Report Status: 268435456
Hashed bucket: cdfb3a9999c4467e47424d5bafd4d426
Cab Guid: 0
Version=1
EventType=APPCRASH
EventTime=132410561719667611
ReportType=2
Consent=1
UploadTime=132410561721327610
ReportStatus=268435456
ReportIdentifier=ac890c32-576e-432c-955a-5365a532ff3b
IntegratorReportIdentifier=8cbdc3e1-a74d-47f8-96ab-294272285a5a
Wow64Host=34404
NsAppName=PowerToys.exe
OriginalFilename=PowerToys.exe
AppSessionGuid=000014cc-0001-001b-5e9c-aa4fb46ad601
TargetAppId=W:0000739a5c7852efdabc700dd2fe329d77d800000904!000042b6053146d810855f326d7917d3d23b36ba8ab7!PowerToys.exe
TargetAppVer=2020//07//31:14:23:23!e5e66!PowerToys.exe
BootId=4294967295
ServiceSplit=14
TargetAsId=587
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=cdfb3a9999c4467e47424d5bafd4d426
Response.BucketTable=4
Response.LegacyBucketId=1675987067522569254
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=PowerToys.exe
Sig[1].Name=Application Version
Sig[1].Value=0.20.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5f24295b
Sig[3].Name=Fault Module Name
Sig[3].Value=fancyzones.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=0.20.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5f24245d
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000049f80
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19041.2.0.0.256.4
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=a9da
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=a9dace5168903a778ea8e42a5378febe
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=df88
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=df8876e5ce3cf6d763717800874a083c
UI[2]=C:\Program Files\PowerToys\PowerToys.exe
LoadedModule[0]=C:\Program Files\PowerToys\PowerToys.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[5]=C:\Windows\System32\msvcp_win.dll
LoadedModule[6]=C:\Windows\System32\ucrtbase.dll
LoadedModule[7]=C:\Windows\System32\combase.dll
LoadedModule[8]=C:\Windows\System32\RPCRT4.dll
LoadedModule[9]=C:\Windows\System32\shcore.dll
LoadedModule[10]=C:\Windows\System32\msvcrt.dll
LoadedModule[11]=C:\Windows\System32\SHLWAPI.dll
LoadedModule[12]=C:\Windows\System32\USER32.dll
LoadedModule[13]=C:\Windows\System32\win32u.dll
LoadedModule[14]=C:\Windows\System32\GDI32.dll
LoadedModule[15]=C:\Windows\System32\gdi32full.dll
LoadedModule[16]=C:\Windows\System32\ADVAPI32.dll
LoadedModule[17]=C:\Windows\System32\sechost.dll
LoadedModule[18]=C:\Windows\System32\SHELL32.dll
LoadedModule[19]=C:\Windows\System32\ole32.dll
LoadedModule[20]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[21]=C:\Windows\SYSTEM32\RstrtMgr.DLL
LoadedModule[22]=C:\Windows\SYSTEM32\msi.dll
LoadedModule[23]=C:\Windows\SYSTEM32\ncrypt.dll
LoadedModule[24]=C:\Windows\System32\bcrypt.dll
LoadedModule[25]=C:\Windows\System32\IMM32.DLL
LoadedModule[26]=C:\Windows\SYSTEM32\NTASN1.dll
LoadedModule[27]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[28]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[29]=C:\Windows\SYSTEM32\windows.storage.dll
LoadedModule[30]=C:\Windows\SYSTEM32\Wldp.dll
LoadedModule[31]=C:\Windows\System32\clbcatq.dll
LoadedModule[32]=C:\Windows\System32\Windows.Web.dll
LoadedModule[33]=C:\Windows\System32\iertutil.dll
LoadedModule[34]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[35]=C:\Windows\System32\taskschd.dll
LoadedModule[36]=C:\Windows\System32\XmlLite.dll
LoadedModule[37]=C:\Windows\system32\uxtheme.dll
LoadedModule[38]=C:\Windows\System32\MSCTF.dll
LoadedModule[39]=C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_6af46268c19e4980\nvsmartmax64.dll
LoadedModule[40]=C:\Windows\System32\AppXDeploymentClient.dll
LoadedModule[41]=C:\Program Files\PowerToys\modules\FancyZones\fancyzones.dll
LoadedModule[42]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.19041.388_none_faefa0077613d9c8\gdiplus.dll
LoadedModule[43]=C:\Windows\SYSTEM32\dwmapi.dll
LoadedModule[44]=C:\Program Files\PowerToys\modules\FileExplorerPreview\powerpreview.dll
LoadedModule[45]=C:\Program Files\PowerToys\modules\ImageResizer\ImageResizerExt.dll
LoadedModule[46]=C:\Program Files\PowerToys\modules\KeyboardManager\KeyboardManager.dll
LoadedModule[47]=C:\Program Files\PowerToys\modules\Launcher\Microsoft.Launcher.dll
LoadedModule[48]=C:\Program Files\PowerToys\modules\PowerRename\PowerRenameExt.dll
LoadedModule[49]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.1_none_b555e41d4684ddec\COMCTL32.dll
LoadedModule[50]=C:\Program Files\PowerToys\modules\ShortcutGuide\ShortcutGuide.dll
LoadedModule[51]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[52]=C:\Windows\SYSTEM32\dcomp.dll
LoadedModule[53]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[54]=C:\Windows\SYSTEM32\d2d1.dll
LoadedModule[55]=C:\Windows\SYSTEM32\DWrite.dll
LoadedModule[56]=C:\Program Files\PowerToys\modules\ColorPicker\ColorPicker.dll
LoadedModule[57]=C:\Windows\System32\WinTypes.dll
LoadedModule[58]=C:\Windows\SYSTEM32\PROPSYS.dll
LoadedModule[59]=C:\Windows\System32\CFGMGR32.dll
LoadedModule[60]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[61]=C:\Windows\System32\Windows.FileExplorer.Common.dll
LoadedModule[62]=C:\Windows\SYSTEM32\edputil.dll
LoadedModule[63]=C:\Windows\System32\Windows.StateRepositoryPS.dll
LoadedModule[64]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[65]=C:\Windows\System32\cldapi.dll
LoadedModule[66]=C:\Windows\System32\FLTLIB.DLL
LoadedModule[67]=C:\Windows\System32\appresolver.dll
LoadedModule[68]=C:\Windows\System32\USERENV.dll
LoadedModule[69]=C:\Windows\System32\SLC.dll
LoadedModule[70]=C:\Windows\System32\Bcp47Langs.dll
LoadedModule[71]=C:\Windows\System32\sppc.dll
LoadedModule[72]=C:\Windows\System32\OneCoreCommonProxyStub.dll
LoadedModule[73]=C:\Windows\System32\OneCoreUAPCommonProxyStub.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=19041
OsInfo[3].Key=ubr
OsInfo[3].Value=388
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=4
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=220681608
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.388.19041.0-11.0.200
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=130948
OsInfo[19].Key=svolsz
OsInfo[19].Value=1862
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=191206
OsInfo[22].Key=bldtm
OsInfo[22].Value=1406
OsInfo[23].Key=bldbrch
OsInfo[23].Value=vb_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.19041.388.amd64fre.vb_release.191206-1406
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Enterprise
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=fconid
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=PowerToys Runner
AppPath=C:\Program Files\PowerToys\PowerToys.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=9F1A27BF5EC9DBC88EEA3AE0AA7FAACA
MetadataHash=-1845843497
@dacowan yes, thank you. We are in the process of releasing 0.20.1, when it will be available please verify if the problem is still happening. Thanks.
Tested 0.20.1 -- sorry guys, same thing.
Faulting application name: PowerToys.exe, version: 0.20.1.0, time stamp: 0x5f2ad542
Faulting module name: fancyzones.dll, version: 0.20.1.0, time stamp: 0x5f2acfd2
Exception code: 0xc0000005
Fault offset: 0x0000000000049fb0
Faulting process id: 0xa054
Faulting application start time: 0x01d66bc9f4c28c9c
Faulting application path: C:\Program Files\PowerToys\PowerToys.exe
Faulting module path: C:\Program Files\PowerToys\modules\FancyZones\fancyzones.dll
Report Id: 851f131e-c858-4959-9bd9-86a4ec1d7489
Faulting package full name:
Faulting package-relative application ID:
Fault bucket 1947178984030438370, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: PowerToys.exe
P2: 0.20.1.0
P3: 5f2ad542
P4: fancyzones.dll
P5: 0.20.1.0
P6: 5f2acfd2
P7: c0000005
P8: 0000000000049fb0
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FE2.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5060.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5080.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5080.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50B0.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_PowerToys.exe_6c42a24c477968bab5477f2a494228eacf1e46_abb9280c_fde7ab14-b772-4e4f-8c88-ee899601a51b
Analysis symbol:
Rechecking for solution: 0
Report Id: 851f131e-c858-4959-9bd9-86a4ec1d7489
Report Status: 268435456
Hashed bucket: 0dde4cfc96eb64742b05c4f8293d83e2
Cab Guid: 0
@dacowan
can you enable the crash dumps installing the registry key I've attached? Extract the zip file and then double click on the .reg file.
I will generate the crash dump in C:\crashdumps`, reproduce the crash and then zip the crashdumps
folder and posted here.
Thanks.
Well, you're lucky you got the crashdump... after a couple of reboots, it's not happening now :/ It seems to be running OK now.
I lied. It's not. I reverted back to 0.18
Hi @dacowan the crash dump helped, we have possible fix, would you mind installing this private build? (it's not signed)
Sorry - no success.
Faulting application name: PowerToys.exe, version: 0.20.1.0, time stamp: 0x5f314a8a
Faulting module name: fancyzones.dll, version: 0.20.1.0, time stamp: 0x5f314a23
Exception code: 0xc0000005
Fault offset: 0x0000000000047f10
Faulting process id: 0x4bc8
Faulting application start time: 0x01d66f33fef1b897
Faulting application path: C:\Program Files\PowerToys\PowerToys.exe
Faulting module path: C:\Program Files\PowerToys\modules\FancyZones\fancyzones.dll
Report Id: 7642e82a-fc64-4d11-93fd-61094c98c6e5
Faulting package full name:
Faulting package-relative application ID:
@dacowan still the same crash, thanks.
It seems to be timing dependent, I think. If I reboot the system, and log in immediately (while Windows is still spinning up in the background) - it loads successfully. If I leave the system to warm up and then log in, it crashes.
@dacowan does it only happen when you reboot the machine? If you restart PT after the crash does it run fine until the next reboot?
No, it crashes on manual restart. crashdumps.zip
@enricogior did your team have a chance to look at the dump?
I don't know if this is still necessary... I haven't had this issue since upgrading to 0.21.1
@crutkas yes we did, but it was misleading, it's the same problem that is effecting the Watson reports for FZ and SG, the call stack is missing or bogus.
Closing the issue since @dacowan didn't have this problem in the new releases. Please reopen if it happens again. Thanks.
ℹ Computer information
📝 Provide detailed reproduction steps (if any)
✔️ Expected result
❌ Actual result