computer reboots when inserting blank cdr 1

[chadroeder]

Hey gang, any help on this is appreciated.

The other day, I placed a blank cdr in my cdr drive (cyberdrive CW078D CD-R/RW) and BLAMMO! The comp. rebooted and after windows (eventually) restarted, and error message told me that windows has recovered from a serious error. Details are:

System has recovered from a serious error

Error signature:

BCCode : d1 BCP1 : 00000000 BCP2 : 00000002 BCP3 : 00000000
BCP4 : F7582C39 OSVer : 5_1_2600 SP : 1_0 Product : 256_1

Technical info about report:

C:\WINDOWS\Minidump\Mini022104-02.dmp
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WER1.tmp.dir00\sysdata.xml

This is the first time this has happened, and it only happens when inserting a blank cd-r. Cd's with data on them are read with no problems. I'm running XP Pro. The system runs fine otherwise. Thanks!

CR

 

[paparazi]

Hi
One of two things:
CDRW going bad?
or
Power supply weak, the initial spin up of the CDrom drive takes the most current from the PSU, at this power if the PSU cannot maintain a good regulated power output it may well cause a reboot.
Martin

Replying helps further our knowledge, without comment leaves us wondering.

 

[chadroeder]

Well, if the power-up was sucking too much energy, wouldn't that happen when i insert a data cd and it spins and reads it? It reads data cd's no problem. Or maybe the CDRW is going bad...

CR

 

[deeno]

Do you have your system configured to perform an action when a blank disc is inserted? Some programs are configured to automatically launch when a blank disc in inserted, maybe the program is actually causing the error. If you have something like this, try to bring up the program without a blank CDR...

good luck

 

[chadroeder]

Okay, so I swapped CD-RW's and when windows booted and attempted to install drivers for the new CD RW the comp shut off again, same deal as before...so it must be a software issue. Is there any way around a re-installation of windows?

CR

 

[deeno]

I doubt it's Windows that is actually causing the fault but I'm not sure what you mean by saying it locked up during the driver installation. I'm not aware of any active driver installation for a CDRW drive. What Windows version are you running?

So really you're not having the same problem as last time where the computer locked up on a insert of a blank disc. I'm still willing to bet this problem is caused by your burning software. Try to uninstall that and see what happens...

Good luck!!

deeno

 

[chadroeder]

Well, it's Windows XP pro. Initially, with the old burner, I uninstalled the driver for that burner, then rebooted. When windows detected new hardware, the computer shut off in the same way it did when inserting a blank disc. After installing a new burner, when windows detected the new hardware and began installing the driver for it, the computer shut down as before. The thing is, I can't even have the drive attached to the mobo without this problem occuring. So you think I should uninstall Nero and plug the drive back in? Thanks,

CR

 

[deeno]

At this point it sounds like anything is worth trying. To be honest, I can't recall ever having the New Hardware Found wizard come up for the installation of any kind of CD drive (unless of course it was an external drive or something).

Try removing Nero and see what happens. At this point who knows??

deeno

 

[chadroeder]

Thanks. Maybe my understanding is off here. I thought the found new hardware wizard would detect the device then install the drivers for it automatically, but maybe not. Anyway, I'll get rid of NERO then try it...I'll keep you posted.

CR

 

[bazzer55]

hi folks! i too have been receiving exactly same errror messages; with the exception of bcp1/bcp3 addresses; just to throw something in, i have no burner mounted; only a cdrom. interesting about the psu; mine is only a cheapy. other info i have gathered thus far suggests possible memory stick probs. my rig does not reboot however; and having refused microsoft's offer to report etc., i can carry on as normal. i shall notify my findings when (if!) i fix it........

 

[bcastner]

Stop d1 error:
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile

http://support.microsoft.com/?kbid=810093

 

[bazzer55]

....back again; and read bcastner's possible causes. you can put me down for the mismatched ram. i added a third stick of hynix memory, cl3 (it said on the label) and started getting the errors. i was not immediately suspicious because i was testing an old ti4400 in this old p3 rig as it had dx8.1 and my own system has dx9 and the card seemed to be causing breakups everywhere. eventually, i went to hynix' site and identified the stick by the chip descripton. it said: cl2/cl3 programmable!!! my bios was not changed from cl3, so, it appears that they spoke with forked tongue. to test the hynix i stuck it in alone on cl2 setting and the error messages were no longer! (the ti is ok too) hope this makes sense and adds a little to the human experience. comments welcomed.
regards

 

[chadroeder]

Well, I have to say, the RAM was initially one of the points I looked at...I did uremove the RAM, then rebooted, with the same result. Comp shut off...grey screen of death (XP pro, remember--no info till manual [hard] or automatic reboot, which points to the same error message as per 1st post)...I'm using Crucial RAM here, same specs as HP factory installed, and as I say, this sh*t never happened after initial installation of RAM (had the additional RAM for 2+ months)...I did install Alcohol 120% after Nero (but Nero had been installed and used to great success for many a moon, however, Alcohol had not been used, and as you may or may not know, this prog (alcohol) installs a "virtual" drive on your HD...) so anyway, I haven't had the time or nerve to re-connect the burner, nor have I uninstalled Nero...it just seems like way too much effort, although, this is how they get the bugs out, right? So maybe I'm doing something for the greater good of humanity with all this searching-for-answers-in-a-world-that-may-or-may-not
provide-any...although your responses are highly valued...I shall endeavor to ascertain the cause of this problem based upon the facts at hand and report back monday or tuesday with the results....God, are we just a bunch of guinea pigs for one another, or what? Sorry if I seem bitter, it's just, you know, well...

CR

 

[chadroeder]

Alrighty gang, good news. Uninstalled Nero and Alcohol. Reconnected. Comp recognized new drive. No shut off, no problems. My guess is that maybe there was a conflict between the two programs...but i don't know. So there we have it. So should I go ahead and re-install Nero? I might as well. Thanks for all your posts. Deeno, your hunch was correct, and I thank you.

CR

 

[deeno]

Brilliant!

I’d go ahead and try reinstalling Nero. It’s great burning software and is actually what I personally use. I’m not so sure that I’d reinstall Alcohol, though. I have never used that so I can’t make any recommendations about it.

You may check for updates on your Nero software.

Anyway, at least you now know how to make it work. If you decide to install Nero and Alcohol, it is possible that you won’t have any problems. If you do though, you should be able to figure out which one is causing the problem. Installing and uninstalling software really isn’t such a tedious task.

Good luck, and I’m glad things are working for you!!

deeno

 

[chadroeder]

Righteous. No, re-installing software is not such a big deal, but if you knew what I've been through during this petite crisis, well, you'd probably wish you'd never modified the original factory settings of your comp in the first place. Honestly, I don't know why we bought a factory made machine in the first place (probably because then, i didn't know what I know now, but it could all be bollocks) Anyhoo, hopefully there's a newer, better kernel out there just waiting to be installed. But alas, it's a work computer, and I have to take the flack when crap goes sideways. So I'll re-install Nero and continue about my business, and probably not deal with alcohol on this machine. Only question is, what do I do with the brand new burner that HP sent us after we bitched and moaned to the higher-ups because we didn't want to re-install windows? Should I go ahead and send the old "defective" drive back? It's a bit of a conundrum...on the one hand it's a victory because we bypassed tech support and got a new drive without doing a re-install of windows, but then again, since it appears to be a software conflict (and they're expecting us to send the old drive back regardless), do I...uh...do I...well, what do I do? Maybe this is the wrong forum...

CR

 

[deeno]

Just send back the original one... they generally don't care when it comes to this kind of stuff. They don't need to know the details of this problem...

deeno