Thunderbird crashed upon closing all data and accounts gone



14 years ago
13 years ago


(Reporter: Donna, Assigned: Scott MacGregor)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I closed Thunderbird and disconnected the internet which led to the computer
automatically restarting itself.  When restarted there was a fatal error
message. Nothing seemed wrong so I closed the message (contained lists of
numbers). When I opened Thunderbird it prompted me to set up an account - there
is no sign of exisitng account information - I have 4 email accounts. I have
lost complex message filtering for many discussion groups and saved emails that
were very important. I have also lost the address book which I was extensively
working on a few hours ago.  I tried doing a system restore to a few days
previous but it made no difference so I undid the restore.  

Reproducible: Didn't try

Steps to Reproduce:
1. There is nothing to reproduce as it is all gone.  I don't want to set it all
up again in case I lose it again.

Actual Results:  

Expected Results:  
Should have opened with all exisiting data, settings and saved messages.

Approximately 2 days ago I downloaded a theme which is no longer there.

I have just found this in the Event Viewer:

Event Type:	Information
Event Source:	Save Dump
Event Category:	None
Event ID:	1001
Date:		8/02/2005
Time:		9:21:10 AM
User:		N/A
Computer:	THOMMO
The computer has rebooted from a bugcheck.  The bugcheck was: 0x1000008e
(0xc0000005, 0x00000001, 0xf53d19f0, 0x00000000). A dump was saved in:

This is the following entry:

Event Type:	Error
Event Source:	System Error
Event Category:	(102)
Event ID:	1003
Date:		8/02/2005
Time:		9:21:25 AM
User:		N/A
Computer:	THOMMO
Error code 1000008e, parameter1 c0000005, parameter2 00000001, parameter3
f53d19f0, parameter4 00000000.

For more information, see Help and Support Center at
0000: 53 79 73 74 65 6d 20 45   System E
0008: 72 72 6f 72 20 20 45 72   rror  Er
0010: 72 6f 72 20 63 6f 64 65   ror code
0018: 20 31 30 30 30 30 30 38    1000008
0020: 65 20 20 50 61 72 61 6d   e  Param
0028: 65 74 65 72 73 20 63 30   eters c0
0030: 30 30 30 30 30 35 2c 20   000005, 
0038: 30 30 30 30 30 30 30 31   00000001
0040: 2c 20 66 35 33 64 31 39   , f53d19
0048: 66 30 2c 20 30 30 30 30   f0, 0000
0050: 30 30 30 30               0000

Comment 1

14 years ago
ugh, I wonder if you had a system crash. Anyway, using the file system explorer,
search for Inbox.msf - that should find your user profile directories. I bet
that your data is all there, just in a  profile that's not used anymore...
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.