Sigil crashes on startup (Win 7 64-bit)

seanos · 09-24-2012, 03:32 AM

It was working fine a few weeks ago; now it crashes shortly after starting up. It shows a new untitled.epub and then crashes.

My interface isn't in English, but the crash info is something like this:

Problem with signature:
Problem event name: APPCRASH
Program name: Sigil.exe
Program version: 0.5.3.0
Program time stamp: 4f491de4
Faulty module name: Sigil.exe
Faulty module version: 0.5.3.0
Faulty module time stamp: 4f491de4
Exception code: c0000094
Exception offset: 0000000000290b4d
OS version: 6.1.7601.2.1.0.256.4
Locale ID: 3081
Extra info 1: c2e2
Extra info 2: c2e238bcaa58aea1356cf1995affbd86
Extra info 3: c54a
Extra info 4: c54a1f08eb9fe6bccd249cc7d8772150

I can't figure out what has changed in the last few weeks. Reinstalling hasn't helped.

This computer is otherwise in good health.

EDIT: Beta 0.5.905 doesn't crash.

seanos · 10-02-2012, 01:19 AM

138 views but no advice. Ho hum.

I did manage to pin down 18 September as the last successful use of Sigil. What happened to it between then and the 24th is still a mystery. Looking at installed software these are the only things that might be candidates:

19/9 Android SDK Tools [hmm...seems an unlikely cause]
20/9 MSXML 4.0 SP3 Parser [Windows Update I think]
22/9 MSXML 4.0 SP3 Parser (KB2721691) [Windows Update again]

Is using 0.5.905 a viable idea?

Toxaris · 10-02-2012, 02:35 AM

The beta is pretty stable, but whether you should use it is your choice.

You could try uninstalling it with Revo, cleaning up all. Reboot and install again. It should not matter, but it might.

09-24-2012, 03:32 AM	#1
seanos Zealot Posts: 101 Karma: 12 Join Date: Apr 2010 Location: Melbourne, Australia Device: Kobo Sage, Kobo Aura H2O, LG V20	Sigil crashes on startup (Win 7 64-bit) It was working fine a few weeks ago; now it crashes shortly after starting up. It shows a new untitled.epub and then crashes. My interface isn't in English, but the crash info is something like this: Problem with signature: Problem event name: APPCRASH Program name: Sigil.exe Program version: 0.5.3.0 Program time stamp: 4f491de4 Faulty module name: Sigil.exe Faulty module version: 0.5.3.0 Faulty module time stamp: 4f491de4 Exception code: c0000094 Exception offset: 0000000000290b4d OS version: 6.1.7601.2.1.0.256.4 Locale ID: 3081 Extra info 1: c2e2 Extra info 2: c2e238bcaa58aea1356cf1995affbd86 Extra info 3: c54a Extra info 4: c54a1f08eb9fe6bccd249cc7d8772150 I can't figure out what has changed in the last few weeks. Reinstalling hasn't helped. This computer is otherwise in good health. EDIT: Beta 0.5.905 doesn't crash. Last edited by seanos; 09-24-2012 at 04:02 AM.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Latest version of calibre crashes on startup on Mac	alvareo	Devices	4	12-23-2011 12:34 AM
Calibre crashes in windows on startup	Jamz	Calibre	12	09-17-2010 02:58 PM
64-bit crashes on load	JaneFancher	Sigil	37	04-06-2010 12:01 AM
Calibre 0.6.10 GUI crashes on startup	Wagenius	Calibre	1	09-03-2009 01:53 AM
Calibre 0.5.0 crashes on startup	gilamon	Calibre	28	03-20-2009 12:42 AM

10-02-2012, 01:19 AM	#2
seanos Zealot Posts: 101 Karma: 12 Join Date: Apr 2010 Location: Melbourne, Australia Device: Kobo Sage, Kobo Aura H2O, LG V20	138 views but no advice. Ho hum. I did manage to pin down 18 September as the last successful use of Sigil. What happened to it between then and the 24th is still a mystery. Looking at installed software these are the only things that might be candidates: 19/9 Android SDK Tools [hmm...seems an unlikely cause] 20/9 MSXML 4.0 SP3 Parser [Windows Update I think] 22/9 MSXML 4.0 SP3 Parser (KB2721691) [Windows Update again] Is using 0.5.905 a viable idea?

10-02-2012, 02:35 AM	#3
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	The beta is pretty stable, but whether you should use it is your choice. You could try uninstalling it with Revo, cleaning up all. Reboot and install again. It should not matter, but it might.

Advert