162956 - 1.1b crashes win 2000 professional sp3

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[wtopp]

when using 1.1b on win2000 professional sp3 i get several os crashes to a blue
screen of death each day.  this never happens if mozilla isn't running.  i've
got a dual processor box so threads may be involved if this isn't commonly seen.

the blue screen:

STOP:0x0000001E (0xC0000005,0xBFF1D846,0x00000000,0x0000005C)
Address BFF1D846 base at BFF04000, DateStamp 3cdaccb4-Ntfs.sys

i can't force this and cannot correlate it with any component of the browser.

b

Comment 1

[Sam J. Fleet]

Okay!  Try to keep on playing around to see if you can find the pattern.  I 
know it doesn't do any good but sometime the discovery come when it is 
unexpected.

Comment 2

[Jason Drew]

Don't know if this is exactly the same symptom, but I have been experiencing 
occasional total crashes of the OS only when using Mozilla. I don't get a blue 
screen of death: Windows 2000 (SP 3) just _completely_ hangs. Can't access 
other apps, and after a few seconds even the mouse pointer won't respond. 
Machine reset is the only option. This is happening pretty regularly: once a 
day maybe. All other applications on my system are very well behaved, it's just 
Mozilla.

Mozilla build ID: 2002061104
OS: Windows 2000 Professional, Service Pack 3
Single AMD Duron CPU, pretty standard stuff ...

No apparent links to the crashes, just doing general browsing on standard html 
pages. I have just one hunch: *maybe* I was using the mouse scroll wheel each 
time the browser hanged. But really not sure - I'll report that if it turns out 
to be the case.

Sad to say, I'm posting this from IE to avoid another crash.

Comment 3

[Matthias Versen [:Matti]]

-> invalid

An application can't crash win2k/Nt/XP without installing a device driver.
(and mozilla doesn't install additional device drivers)

A complete hang or Blue screen is a problem in a driver (~90% graphic card) or a
hardware problem.

We know that the newest ATI drivers will cause a hang (winXP can detect this
problem but not win2k)

It doesn't matter if other browser are working...