machine reboots when audio CD is inserted in DVD/CD ROM

[Guest]

I am running XP Pro, with a Yamaha CRW-F1E and Sony DRU-800A installed on the
secondary IDE channel of the motherboard. Recently, the machine started
acting up. Not always, but about half the time (i.e. this is a reoccuring
phenomenon) my PC just up and reboots when I put the CD into the drive.
Either drive. Weird thing is, it only does it with audio CDs. Whenever I
insert a CD or DVD ROM, I never get the problem.

Does anyone have any idea what I should be looking for? I've tried many
things already, but no luck.

I saved the files created for the "send to Microsoft", when upon reboot the
"your system just recovered from a serious system error" window popped up.
If anyone can or is willing to help out, I can email those files to him/her.
I figured this might be more fruitful than waiting for something to show up
on the MS website, especially if the problem is something of my doing (albeit
unkowingly).

Any help would be GREATLY appreciated.

My email address is: filmdude@austin(delete this spamfilter).rr.com

Thanks!

 

[Trax]

|>I am running XP Pro, with a Yamaha CRW-F1E and Sony DRU-800A installed on the
|>secondary IDE channel of the motherboard. Recently, the machine started
|>acting up. Not always, but about half the time (i.e. this is a reoccuring
|>phenomenon) my PC just up and reboots when I put the CD into the drive.
|>Either drive. Weird thing is, it only does it with audio CDs. Whenever I
|>insert a CD or DVD ROM, I never get the problem.
|>
|>Does anyone have any idea what I should be looking for? I've tried many
|>things already, but no luck.

That would be your music program causing problems
Start\Run DRWTSN32 <enter> The application list should show where to
start.

Right click on your CD, properties, autoplay - edit your music to do
nothing until you can get this fix'd

|>I saved the files created for the "send to Microsoft", when upon reboot the
|>"your system just recovered from a serious system error" window popped up.
|>If anyone can or is willing to help out, I can email those files to him/her.
|>I figured this might be more fruitful than waiting for something to show up
|>on the MS website, especially if the problem is something of my doing (albeit
|>unkowingly).
|>
|>Any help would be GREATLY appreciated.
|>
|>My email address is: filmdude@austin(delete this spamfilter).rr.com
|>
|>Thanks!

 

[David Candy]

Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.

If you can't start after enabling verifier
choose Last Known Good Configuration at the Failed Boot menu (which will
start without verifier).


You will be creating a crash dump file in c:\windows\minidump every blue screen. Make sure you are set to record minidumps (Small Memory Dumps) - type it in Help to see how.

Then

If you have the XP SP2 Security Update CD (else see
http://www.microsoft.com/whdc/­devtools/debugging/symbolpkg.m­spx
)


Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS

Download
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

Load the crash dump file into windbg
and read what it says. You may need to tell it where the symbols are. Read it.
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)

If the above is too technical then email the crash dump files to davidc @ mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.

You can look up specific details here
http://msdn.microsoft.com/library/d..._ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp

If it indicates faulty memory might be the cause you can get a memory tester
here
http://oca.microsoft.com/en/wi­ndiag.asp


If it mentions a core windows system file, meaning it a MS fix is required,
upload a minidump to

http://oca.microsoft.com

Also try typing the main error code in Help while online (ie,
Stop 0x50
and also try in the 8 digit form
stop 0x00000050)
and if there are too many hits use a filename if available. Generally memory
addresses are different for each computer (as each computer has a different
mix of drivers) so parameters that are memory addresses aren't that useful for searching, but NTStatus codes are (plus you can look them up here http://cvs.sourceforge.net/viewcvs.py/mingw/w32api/include/ddk/ntstatus.h?rev=1.2).

 

[Guest]

Thanks to David and Trax for the super quick replies. I will investigate as
instructed, and get back with the results (hopefully positive ones) for
posterity.

Again, many thanks!