Closed Bug 288650 Opened 20 years ago Closed 20 years ago

Machine Check Exception (MCE) while "Loading message..." in status bar

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: dmaizer, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; he-IL; rv:1.7.6) Gecko/20050226 Firefox/1.0.1
Build Identifier: Version 1.0 (20041206) - Hebrew Localized Version

In my Inbox (Local Folders), when I click a certain large message I have
received (6943KB) - the preview pane shows its top, and then the "Loading
(reading?) message..." message appears at the status bar, and the green progress
bar starts to move in the status bar - BUT VERY SLOWLY - a pixel every few
seconds. After waiting for a minute or so - the WinXP blue screen of death
appears, claiming a Machine Check Exception has occurred, with the following info:

*** STOP: 0x0000009C (0x00000001, 0x8054DA70, 0xB2000000, 0x00000115)

and also claims a dump of physical memory has occurred.

How can I save this message aside (remove from Inbox) without previewing it?

Reproducible: Always

Steps to Reproduce:
1.See details above
2.
3.

Actual Results:  
Machine Check Exception - so I have to restart my PC.

Expected Results:  
ThunderBird should have just shown the message in the preview pane.

That's more than just a crash - the WindowsXP crashes because of previewing a
message ! I don't have ANY other problems in WinXP, and it is entirely
reproducible with the message that I have.
The Blue Screen is a problem with your system because Thunderbird is a userspace
application and can't cause a BSOD. It doesn't matter if you get this only with
Thunderbird and also only with this one message. It's always a driver/Hardware
problem.

(BTW: http://support.microsoft.com/?scid=kb%3Ben-us%3B329284&x=17&y=11 )

-> invalid
 
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.