If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[WinXP] Blue screen on browser exit or new page loads with ATi Radeon 8500 and driver



15 years ago
13 years ago


(Reporter: Susuk Lim, Assigned: asa)


Windows XP

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401

On my configuration (noted below), I get a blue screen of death citing
ati2dvag.dll upon attempting to exit the 1.4a release of the browser.  This
happens on about half of the attempts, most frequently after extended use of the
browser.  Occasionally, surfing to a new webpage (any webpage) causes the
browser to freeze momentarily, unfreeze, then dump me to a blue screen, again
citing ati2dvag.dll as the problem driver.  No other application or prior
release of the browser causes either of these problems on my configuration.

Reproducible: Sometimes

Steps to Reproduce:
1.  Launch Mozilla 1.4a release.
2.  Surf around for a bit.
3.  Close the browser.

Actual Results:  
Browser will occasionally dump to a blue screen when surfing;  more often, it
will dump to a blue screen upon exit.

Expected Results:  
While surfing or when exiting, machine to function normally.

Relevant Configuration information:

Pentium 4 2.8GHz
Shuttle FB51 mobo (i845G chipset)
ATi Radeon 8500 128MB (retail)
1GB (2x 512MB) Corsair PC3200 RAM
Windows XP Pro SP1, all recent patches installed
Mozilla 1.4a release (buildID 2003040105)
Isn't this in the release notes?  This is a known bug in some versions of ATI
drivers... I know they claimed to fix it a few months back, but you have a
different (more recent, actually) driver version than that....

Nevertheless, this is a crash in the driver itself.. Does changing display
acceleration settings help?

Comment 2

15 years ago
The driver revision I used is the very latest available, released a week or two
ago (IIRC).  If they fixed the problem, it sure doesn't seem like they fixed all
of it.  =)
Well, they fixed it a few revisions back... I wouldn't be suprised if they have
managed to unfix it.

PLease report this to ATI. 
This is not Mozilla's fault (and it may work in other Mozilla builds and all
other application)

-> invalid
Last Resolved: 15 years ago
Resolution: --- → INVALID

Comment 5

14 years ago
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.