Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Thunderbird Crash Reporter opens everytime !

  • 6 replies
  • 2 have this problem
  • 1 view
  • Last reply by Ponyone

more options

After updating to Thunderbird 102.0 the Crash reporter opens every time I open the program. I use multiple profiles and this causes me to have to deal with the Crash Reporter multiple times a day. Today I updated to 102.1 and it STILL is causing the Crash reporter to open.

And on top of that none of the extensions like the Tbsync and Provider for Caldav are working. I have used this program for close to 15 years and never had issues until now. No other programs I use are crashing and I have run DISM and SFC.

Faulting application name: thunderbird.exe, version: 102.0.1.0, time stamp: 0x62c4ab96 Faulting module name: combase.dll, version: 10.0.22621.105, time stamp: 0x143d0f52 Exception code: 0xc0000005 Fault offset: 0x00000000000c4c33 Faulting process ID: 0x0x432C Faulting application start time: 0x0x1D891FF515F7C09 Faulting application path: C:\Program Files\Mozilla Thunderbird\thunderbird.exe Faulting module path: C:\WINDOWS\System32\combase.dll Report ID: a318a45d-5bfa-42fc-baf9-368a731298b6 Faulting package full name: Faulting package-relative application ID:

After updating to Thunderbird 102.0 the Crash reporter opens every time I open the program. I use multiple profiles and this causes me to have to deal with the Crash Reporter multiple times a day. Today I updated to 102.1 and it STILL is causing the Crash reporter to open. And on top of that none of the extensions like the Tbsync and Provider for Caldav are working. I have used this program for close to 15 years and never had issues until now. No other programs I use are crashing and I have run DISM and SFC. Faulting application name: thunderbird.exe, version: 102.0.1.0, time stamp: 0x62c4ab96 Faulting module name: combase.dll, version: 10.0.22621.105, time stamp: 0x143d0f52 Exception code: 0xc0000005 Fault offset: 0x00000000000c4c33 Faulting process ID: 0x0x432C Faulting application start time: 0x0x1D891FF515F7C09 Faulting application path: C:\Program Files\Mozilla Thunderbird\thunderbird.exe Faulting module path: C:\WINDOWS\System32\combase.dll Report ID: a318a45d-5bfa-42fc-baf9-368a731298b6 Faulting package full name: Faulting package-relative application ID:

Chosen solution

After 150 Crash Reports submitted in 18 days Thunderbird finally fixed the issue with update 102.0.3 !!!

Read this answer in context 👍 0

All Replies (6)

more options

So after dozens and dozens of times having to deal with the Crash Reporter since my first post Thunderbird was finally updated to 102.0.2 and I was excited and hopeful! But NO... still crashing every time I open Thunderbird.

The issue seems to be with Windows 11 Version 22H2 (22621.169) as my desktop on Windows 10 has no issues.

Faulting application name: thunderbird.exe, version: 102.0.2.0, time stamp: 0x62c892aa Faulting module name: combase.dll, version: 10.0.22621.105, time stamp: 0x143d0f52 Exception code: 0xc0000005 Fault offset: 0x00000000000c4c33 Faulting process ID: 0x0x1AA8 Faulting application start time: 0x0x1D895F5B0ED0A35 Faulting application path: C:\Program Files\Mozilla Thunderbird\thunderbird.exe Faulting module path: C:\WINDOWS\System32\combase.dll Report ID: 70c1ed5d-6706-48fe-8b52-38bb77507a75 Faulting package full name: Faulting package-relative application ID:

more options

Crash Reporter dialogue opens, but the program does not crash. Same with you? I too have multiple profiles. I just close the crash reporter box by clicking the X.

more options

@smlinderman yes, the dialog opens and I usually click Restart Thunderbird but neither the Restart or the Quit Thunderbird buttons actually do what they say. By closing it without sending the details of the crash they will not do anything. the more folks send the data the sooner they fix it.

So far I have sent 107 crash reports since July 2, 2022!!

more options

One possible solution which worked for me on Win 11 TB 102.0.2 Goto TB profile folder and delete crash reports folder. Restart TB. Hope being helpful.

more options

Thanks @lampros I moved the Crash Reports folder out of the TB Profile folder in Appdata>Roaming and that did stop the Crash Reporter dialog from opening but it still is reporting it as an application error in Windows Event Viewer.

Thunderbird recreated the Crash Reports folder but it did not recreate the "pending" and "submitted" folders so it did not know here to put the reports so it submits it as a Windows error to Microsoft. If those folders are recreated in the newly recreated Crash Reports folder then the Crash Reporter dialog shows up again and submits the error reports to Mozilla instead of Microsoft.

Faulting application name: thunderbird.exe, version: 102.0.2.0, time stamp: 0x62c892aa Faulting module name: combase.dll, version: 10.0.22621.105, time stamp: 0x143d0f52 Exception code: 0xc0000005 Fault offset: 0x00000000000c4c33 Faulting process ID: 0x0x4D8C Faulting application start time: 0x0x1D8977C58F68C2F Faulting application path: C:\Program Files\Mozilla Thunderbird\thunderbird.exe Faulting module path: C:\WINDOWS\System32\combase.dll Report ID: d06309e0-2086-4198-83af-f605d2f91f53 Faulting package full name: Faulting package-relative application ID:

Fault bucket 1359605020366949760, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0

Problem signature: P1: thunderbird.exe P2: 102.0.2.0 P3: 62c892aa P4: combase.dll P5: 10.0.22621.105 P6: 143d0f52 P7: c0000005 P8: 00000000000c4c33 P9: P10:

Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.aa6854c2-5208-49b2-b01a-d75f11023be.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.88bf6958-e88f-4eed-ced-4f7b79bf5f5a.tmp.WERInternalMetadata.xml WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20220714_1_EC_0_inject.etl \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0fb5c28c-7a67-4f41-b154-2eb9afe4a1f9.tmp.etl WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.42b3606b-41a9-43d4-a1a8-2f577eb3761d.tmp.etl \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6aa9542e-9987-414f-8433-b3487a409afd.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.986a9c99-3ae6-4a6b-ae67-9e2c4a7a2287.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f18b4e06-0ff6-4067-83de-2443c5d3b3d7.tmp.xml

These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_thunderbird.exe_5688a86263e450439f25b6c8410d05d44272253_1976c38c_feb0b862-e87d-4b77-b465-b523ff4a6ab4

Analysis symbol: Rechecking for solution: 0 Report Id: d06309e0-2086-4198-83af-f605d2f91f53 Report Status: 268566528 Hashed bucket: dec3b0e17c9e8d2b22de499001cf4d80 Cab Guid: 0

more options

Chosen Solution

After 150 Crash Reports submitted in 18 days Thunderbird finally fixed the issue with update 102.0.3 !!!