160337 - printing in nt4 sp5 causes system to reboot

Status: VERIFIED DUPLICATE of bug 168385

(Core :: Printing: Output, defect)

Description

[Will Holcomb]

When I go to http://www.webdav.org/deltav/WWW10/deltav-intro.htm and print the
page, the printing will go about 50% and the system will flash a bsod and go
straight into a reboot.

Other pages will print fine.

I did nothing other than log in and go to that page and print and the same thing
happened.

This is a school system and I do not have another machine running nt to test it
on, so I cannot give very much information on what is running since I am not an
administrator.

I am running Mozilla 1.1a (Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1a)
Gecko/20020611)

Comment 1

[Olivier Cahagne]

wfm using build 2002073004 on Win2k (trunk).

Comment 2

[R.K.Aa.]

bug 157544 was similar

Comment 3

[Michael Lefevre]

reporter (Will): can you reproduce this bug with a recent build of mozilla (for
example, 1.2beta)? if so, please comment again with details. if not, please
resolve this bug as WORKSFORME. thanks.

Comment 4

[Scott Kitterman]

I am also having this or a very similar problem.  I think that Bug 168385 is
similar, so I don't know for sure which is causing my crashes.  I have Mozilla
1.1 running on three computers.  The crash happens on two that are both Win2K
(one SP2 and one SP3) that are printing to a Xerox WC 390 through my wireless
network.  The crash does not happen on the one that is Win98SE that has the WC
390 connected to LPT:1.  

This does not consistently happen for me.  It seems to happen more often with
longer pages and also more often when the computers (both laptops) are farther
away from the the hub (lower bandwidth/larger latency).  From what I was
experiencing, I thought that perhaps this was related to 169689.  I just,
however, experienced the same crash (on the WIN2K sp 2 machine) using a recent
(11/01/02) nightly build (Build ID: 2002110104), which I think has the fix for
169689 in it.

The blue screen says:

*** STOP: 0x0000001E (0xC0000005, 0x8046A7A2, 0x00000000, 0x1515150F)
K_MODE_EXCEPTION_NOT_HANDLED

*** Address 8046A7A2 base at 80400000, DateStamp 3ad7ad60 - ntoskrnl.exe

I also have the small (64KB) memory dump that I can attach if that would be helpful.

I know there are a lot of bugs to be stomped, but this one is very close to
having my wife going back to IE and I'd really rather avoid that.

If you need help testing or more information, I'm willing to help.  I just wish
I were enough of a programmer to try and figure this one out myself.

Comment 5

[Scott Kitterman]

I tried it again with the current (2002111108) nightly build.  The printer I am
using (Xerox WC 390) has two driver versions for Win2K available on their web
site.  I tried them both (1.1.1 and 1.1.2) and reliable crashed the system as
described.  When I print the Mozilla start page is one that crashes.  

I'm going to post this comment to 166249, 160337, and 168385 because it may be
relevant to one or more of these bugs.

I am open to suggestions on additional testing I can do to help nail this down.

Comment 6

[Max Kanat-Alexander]

I am going to mark this as a duplicate of bug 168385, and update bug 168385 with
some of the information here. If bug 168385 becomes resolved, and this is not
fixed, then please re-open this bug.

*** This bug has been marked as a duplicate of 168385 ***

Comment 7

[sujay]

verified.