View Single Post
Old 08-24-2020, 08:50 PM   #3
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,863
Karma: 6120478
Join Date: Nov 2009
Device: many
According to your Report.wer.txt file the actual faulting module is Qt5Core which is a Qt module.

Some very basic things to try...

1. You said you installed the 64 bit version of Sigil. Is this a 64 bit version of Windows 10?

2. Perhaps it is a permissions issue? Have you tried running it as admin?

3. Try setting the SIGIL_DEBUG_LOGFILE environment variable to be a path to debug.txt file you create someplace Sigil and you have write permission to see if it logs any errors.

4. Have you tried backing up your Sigil Preferences folder and doing a fresh install and launch with no sigil.ini file. Corrupted sigili.ini files can and do cause crashes on launch.

5. Using the most up to date video driver is also worth trying.

Perhaps a Windows user can be more help here.
KevinH is offline   Reply With Quote