Closed Bug 302373 Opened 19 years ago Closed 19 years ago

XP Crashes when running FF 1.0.6 and a music cd is inserted and starts to play.

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: bigtony, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.6

After installing FF 1.0.6, when a Music CD is inserted into a cd drive and
begins to play, Windows reboots.  
I've used QCD cd player and WinAmp and both crash.  I uninstalled FF and get no
crashes.  I reinstalled FF 1.0.4 and no crashes.  Upgraded again to 1.0.6 and
the crashing occurs again.  I turned OFF autoplay on the CD drive, and it had no
effect on the crashes.  If the CD is already in the drive when the system boots,
playing it does not cause a crash.

Reproducible: Always

Steps to Reproduce:
1. Install FF 1.0.6
2. Insert music CD
3. either autorun or start the cd and the system crashes.

Actual Results:  
XP Reboots.
Question to reporter: is firefox actually running when the crashes occur?
Also woudl be nice to have a talkback id, please read
http://kb.mozillazine.org/Talkback
Firefox is a user space application and has nothing to do with the windows auto
run service. It can not cause windows to bsod and reboot, the crashes must be
coincidential. 

Marking invalid as this can not be a firefox bug.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Yes, the crash occurs only when Firefox is running.  
ONLY using v1.0.6 I'm currently back to running 1.0.4 and it's fine.  I tried
again to upgrade to 1.0.6 and the crashing started again. Crashes with both
WinAMP and Quintessintial CD Player.

I'll be installing Talkback asap.  thanks.  I'm not sure how much it will help,
the system does a complete reboot. No BSOD.  Nothing.  Running XP with all the
latest SPs.
>Firefox is a user space application and has nothing to do with the windows auto
>run service. It can not cause windows to bsod and reboot, the crashes must be
>coincidential. 

>Marking invalid as this can not be a firefox bug.

Again, when running 1.0.4 the system is FINE.  Upgrading to 1.0.6 causes the
system to REBOOT when inserting a music cd and autoplaying.  NOTHING else was
updated. I have uninstalled 1.0.6 and reinstalled 1.0.4 and it's FINE again. 
RE-did the upgrade to 1.0.6 and the crashes occured again.  I get NO BSOD.   See
my other comments.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
You dont get a bsod because windows is set to automatically restart on failure,
if you change that setting you will see the bsod. When you do get an error
message add it to this bug, although even if firefox triggers the crash it is
not responsible, it will likely be a fault in one of your device drivers which
firefox happens to trigger and not something that can be fixed in firefox.

There is some good documentation on MSDN and other places about debugging
windows system crashes.
>------- Additional Comments From bugzilla@jaimem.org.uk  2005-08-01 05:58 PDT
-------
>You dont get a bsod because windows is set to automatically restart on failure,

BINGO!  Thank YOU!  I should have known that.  Apparently it's with the
AFS2K.SYS driver - notoriously bad.  The odd thing is that it didn't start until
I used FF 1.0.6.  I can make it crash every time.  Thanks again.
More info:

This was an issue with the AFS2K.SYS driver from Oak Technologies.  Version
3.1.14 is NOT compatible with XP and causes the crash.  I'm still not sure why
it only occured when FF 1.0.6 was installed and running.  Updating AFS2K.SYS to
version 3.1.18 fixed the problem.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → FIXED
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Invalid as not a firefox bug and no fix was made to the firefox code.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.