142257 - Win2000 system crashes with 2002050306

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[David Gerard]

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2)
Gecko/20020503
BuildID:    2002050306-1.0 branch

This system has been stable for the last month I've been using it
(rebooting every few days), and since I put 2002050306 it's crashed
every few hours. As in, the whole system freezes.

I don't know how, but this is the only new piece of software I'm using.
And Mozilla is always open when it goes down.

Yes, I know it's not good to run with administrator powers all the
time :-)

I don't have anything more specific or a way to duplicate it. But if
others have seen this, please note it here ...

Comment 1

[Matthias Versen [:Matti]]

Mozilla can't freeze win2k. (only win9x)
Mozilla itself can freeze but you can always kill it with the task-manager
This is a problem with your system.

Comment 2

[David Gerard]

When you're running as Administrator, a buffer overflow (for example) in an
application certainly can take down an NT system. That's why ISS is such a
security nightmare :-)

My own first guess would indeed be hardware issues, but that it happened only
with the installation and running of 2002050306 made me wonder, and file this
just in case. I'll try other builds and see if anyone else has experienced it.
If no other reports, I'll invalidate it in a few days, OK?

Comment 3

[David Gerard]

I'm going to assume it was coincidence, hardware overheating or pixies on Mars.
Marking invalid.

Comment 4

[Malcolm Ferguson]

I'm seeing something similar to this problem too with 2002041711.  It seems
related to the display driver or display resources, and is causing me many blue
screens.  Win2K is definitely crashable.

When I installed RC1, I've enabled the quick launch.  Since then, I've seen a
big increase in the number of BSODs.  At least two a day.  I'm assuming it's
related to Mozilla as I've been seeing "weird" behaviour from it too.  

Once Mozilla has been running for a few hours (e.g. half a day), it starts
getting really unresponsive and then it gets problems redrawing itself.  At this
point, windows from other applications also start having problems, e.g.
see-through title bars, areas not redrawing when exposed from behind other
windows.  If I try to exit Mozilla, there's a high change (> 80%) that my
machine will BSOD as Mozilla shuts down.  

This actually happened to me about 10 minutes ago with a KMODE_EXCEPTION in
something like nvdisp.dll (one of nVidia graphics driver DLLs).  This last crash
blew away settings, such as my home page, language preferences and advanced
windows scripting (allow webpages to open unrequested windows, etc).  

System:
Win2K AS SP2
Dual P-3 850
384MB
Leadtek GeForce 256 DDR - signed nVidia driver v2.3.1.2

Comment 5

[Matthias Versen [:Matti]]

Mozilla can not cause a BSOD because mozilla doesn't use kernel mode drivers.
Mozilla can only trigger this BSOD but the real Problem is a hardware problem or
drivers that are running in the "kernel mode" (Graphic card drivers, Network
drivers...)

Comment 6

[David Gerard]

Yeah, but effectively that's the same thing. Bad apps can take down an NT-based
OS perfectly well if running as administrator.

OK, someone else is seeing it. Do we wait for a third before reopening it as a
genuine problem, if a difficult one? Would anyone care for a list of all the
drivers on this system?

Comment 7

[Steve Chapel]

> Once Mozilla has been running for a few hours (e.g. half a day), it starts
> getting really unresponsive and then it gets problems redrawing itself.

This behavior sounds a lot like bug 133132, which I experience on Windows 98. If
the problem gets better after clearing the Memory Cache, or images start turning
black-and-white (not grayscale, literally just black and white), it's probably
the same problem.

If two more people vote for bug 133132 it will be confirmed.

Comment 8

[Matthias Versen [:Matti]]

No it's not the same thing.
If you get BSOD you should fix your hardware. 
Mozilla can trigger a BSOD because : 
It use many RAM (faulty RAM), heavy Disk useage (problems with PCI on Via systems)
There is no difference if you run it as user or as admin.
No bad APP can take down a Win2k system only bad drivers or bad hardware.

If you get a freeze you can always kill mozilla with the taskmanager... 

BTW: I'm running Mozilla many hours/day on my 3 different win2k systems without
BSOD. 

Comment 9

[David Gerard]

Reopening because others are seeing it. (I closed it because I'd seen no

other reports of it.)



"There is no difference if you run it as user or as admin.

 No bad APP can take down a Win2k system only bad drivers or bad hardware."



- this statement is simply incorrect, in my real life experience with dodgy apps. Run as user a suitably app will die horribly, run as admin it can indeed take down the system.

Comment 10

[Steve Chapel]

> No it's not the same thing.
> If you get BSOD you should fix your hardware.

I was referring to the redrawing problem, not the BSOD.

Comment 11

[Matthias Versen [:Matti]]

-> invalid

Mozilla can't cause a BSODh

Comment 12

[David Gerard]

Rubbish it can't.

Comment 13

[Matthias Versen [:Matti]]

Mozilla doesn't use a kernel mode driver
Mozilla doesn't use strange registry settings
You get a out of mem warning if Mozilla allocates too many memory

(there is no difference if you run it as User or Admin. you MUST install a
kernel mode driver for a BSOD. An application running as administrator can't
cause this.
You can kill the system as administrator if you change strange registry settings
or remove/change system files but mozilla doesn't do this)

You can't compare Mozilla with IIS.

-> invalid

reopen it if you have clear steps to reproduce it or if you can add more
infomations.