If you start cmd.exe with administrator privileges and attach the following execution results, you may be able to get more details.
wevtutil qe Application /c:5 /f:Text /rd:true "/q:*[System[(EventID=1000)]]"
dir %appdata%\kicad
dir %LOCALAPPDATA%\CrashDumps
sfc /scannow
If you get WinDbg and provide the traceback information of the crash dump, you can visualize the sequence of function calls and the cause of the abnormal termination.
Install only WinDbg from here. (Win10) Windows SDK - Windows app development | Microsoft Developer
Select the file saved in the %LOCALAPPDATA%\CrashDumps folder with Open Crash Dump and run the following command to get more details:
k
!analyze -v
Ex.
In addition to the above, it would be helpful if you could also provide information about the operations and steps to generate a crash dump.
For example:
- In Windows Explorer, select an existing project file created with a previous version of KiCAD. (-> KiCad | master | English | Documentation | KiCad )
- Launch KiCAD from the Windows Start menu.
(-> KiCad | master | English | Documentation | KiCad ) - Launch another KiCAD program from the Windows Start menu.