Closed Bug 165849 Opened 22 years ago Closed 22 years ago

Complete system freeze

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 162689

People

(Reporter: aries, Assigned: asa)

References

()

Details

(Keywords: crash)

Sometimes when randomly browsing, my computer will completly lockeup (windows 98
style).  No blue screen, just the classic mouse and keyboard freeze.  This
shouldn't happen under Windows XP.  When rebooted, Windows blames the problem on
my ATI Radeon 7200.  Here are my system specs:

AMD Athlon XP 1700+ on iWill XP333-R (ALi Magik 1 Chipset)
FIC at007 video card (Radeon 7200 GPU with 64 megs DDR RAM.  Using current ATI
reference video drivers)
256 MB Corsair 266 mhz PC-2100 RAM
Maxtor Diamond Max Plus 40 GB 7200 ata/133 hard drive
Creative Sound Blaster Audigy Gamer

I wish I could give you something more specific but all I can say is it just
randomly locks up.
Does this only happen when running Mozilla? If so, what build are you using?
This may indicate a hardware problem with your system or a driver problem and
not a bug in Mozilla.
Sorry I can't be more helpful, but we need something solid to work from.
I too am having the EXACT same problem. There are a few differences in the
hardware, but we both have the same radeon problem with the same freezing symptom.

Hardware:
Asus A7M266 Motherboard
AMD Athlon 1.2 GHz
256MB Crucial RAM DDR
Radeon 7200 ViVo 64MB DDR (retail)
built in sound
western digital hard drive
I believe he is commenting on Mozilla 1.1 release, which is what I'm running
too. I first tried the normal release download, and then i tried the nightly
build, but the problems occur in both.
hm, I'll add myself to the crowd (before I switched to Linux).

I've been experiencing lockups... didn't think it was Mozilla though...

WFM linux .. ha

ATI graphics card.
Windows XP with ????? build... think it was somewhere near 2002072xxx
Oh the keyword field for this bug needs to be changed from nothing to "crash"
What driver version are you using?  I see there are new drivers as of August 1.
 Here's the url: 
http://mirror.ati.com/support/products/pc/radeon7200/winxp/radeon7200winxpdrivers.html
I'm using the driver wxp-radeon-6-13-10-6118-efg, which is the exact one that 
you are speaking of.
That driver version is known to be buggy, as it happens...  see comments in bug
101055 starting at bug 101055 comment 70 
Depends on: 101055
Adding keyword 'crash' as per comment 5.
Keywords: crash
whoops, didn't realize the dependency changes. Is it dependent on bug 101055 or
is it a dupe of it?
It seems to me that it would be a duplicate, because others have had the same
exact problem but it was reported in another bug.
It seems to me that going back one previous driver for my radeon has solved the
problem. I am now at 6.13.10.6094... which was created 5/23/2002 also known as
Catalyst 2.1. I have been using Mozila 1.1 nightly build 2002082908 all day
without any problems. Looks to me like a Radeon driver bug.
My ATI card is "Powered by ATI" not "Built by ATI".  The card itself is built by
FIC.  I am glad I am not the only one with this problem.  Yeah mozilla is the
only application causing this problem, and I would assume it is a driver bug. 
But perhaps there is a fix that could be implemented on the mozilla side?

I am using Mozilla 1.1 final.  Before that I was using 1.0 release, and had the
same problem there.  This problem did not exist in .9.9 (when I began using
Mozilla as my default browser).  
Removing dependency.  Bug 101055 has been targeted as MacOS *ONLY*.

Also, since this is about Mozilla crashing with ATI drivers it's a duplicate of
162689 - which has, unfortunately, been resolved as INVALID since it's a video
driver issue not a Mozilla issue.

*** This bug has been marked as a duplicate of 162689 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
No longer depends on: 101055
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.