1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

XP Pro + SP1 + InCD = Blue Stop Screen

Discussion in 'Windows XP' started by PeteC, 2002/10/15.

Thread Status:
Not open for further replies.
  1. 2002/10/15
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Can anybody shed any light on this problem with InCD - each time I use it all is apparently well until the CD-RW is ejected and the PC halts with a blue stop screen. Occasionally it will blue screen part way through a write.

    Usual message is - this is the latest:

    STOP: 0x0000008E (0xC0000005, 0xCF28CF18B, 0xF1F7390C,0x00000000)

    Sometimes accompanied by :

    BsUDF.Sys - Address F28CF18B base at F28A1000, Date Stamp 3a62f48c

    Burner is Asus CRW-4816A (same problem on Yamaha CRW 2100E on second PC, same OS,and occasionally on HP Laptop with Toshiba combo drive, also XP Pro + SP1)}

    Software is Nero + InCD, both the latest versions
    Autoplay is turned off as far as it can be for the CD-RW drive as suggested by Ahead Tech dept
    Windows CD burning is disabled - think InCd does this anyway.
    Sometimes data is written to the CD-RW, but not always.

    Nero works just fine

    Mainboard is Ausus A7V333 with AMD Athlon 1800+ XP processor and 1 Gig of Ram. Swap file is fixed and on dedicated partition.

    If it's of any help Zone Alarm (latest free version), Diskeeper and NAV 2003 + Utilities 2002 installed + network for laptop.

    TIA
     
  2. 2002/10/15
    Abraxas

    Abraxas Inactive

    Joined:
    2002/08/16
    Messages:
    2,361
    Likes Received:
    3
    A STOP 8E error usually indicates faulty RAM or RAM configuration, but that does not seem to be your case if you get the error only with InCD.

    BsUDF.sys is no doubt an InCD driver. Though Nero and InCD are often bundled, they are separate and quite different programs.

    If you have not updated your InCD to the latest version, I would uninstall your present one and install the update:

    http://www.ahead.de/en/index.html#download

    In any case, since you think you have the latest version, a reinstallation is worth a try. If you have a version that is fairly new, and XP compatible, you might try going back a version or two.

    The antiquated UDF format uses a lot of system resources---you may also try shutting down as much as possible while burning.

    If you have run the Norton Win Doctor recently, you might try an undo of the changes it made. That app is infamous for removing needed registry entries, and it even unregistered some of my software.
     
    Last edited: 2002/10/15

  3. to hide this advert.

  4. 2002/10/15
    Paul

    Paul Inactive

    Joined:
    2002/01/29
    Messages:
    1,293
    Likes Received:
    1
    These CDRW BSOD's are hard to fix... But hear's a couple of suggestions.
    On my W2K machine at work if I eject a CDRW by right clicking the desktop CDRW icon I get a BSOD. I have to right click the InCD icon in the taskbar and click eject. I haven't had this problem at home on my XP machine, but it's worth a try if you haven't or don't do this.
    The second suggestion is dependant on what you have running on your IDE port? If you run the writer with another CDROM I assume the writer is the master and the CDROM is the slave? If so, reverse this so the writer is slaved to the CDROM. I had months of problems with the CDRW not being recognized by windows about 50% of the time and also stability issues with the writer till I did this change. Never looked back since.

    P.
     
    Paul,
    #3
  5. 2002/10/16
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Abraxas, Paul - thanks!

    I think I have fixed the problem :) :) !!

    Last night the problem was churning away in my mind - and keeping me awake, but I remembered an article on XP and Via 4 in 1 drivers in PCW, which said that Win XP con's you when load the Via drivers. What is does, apparently, is agrees to load the drivers and then doesn't! The workaround is to run the Via setup.exe in Win 2000 compatability mode. I did this and the install was certainly different from previous occasions and Nero's info tool now tells me that I have the Viaide drivers, etc loaded (previously they were MS drivers). Nero tech said to update Via - I obviously thought I had!

    I have spent all morning trying to 'break' the system without a single blue screen - formatting, copying, deleting, reformatting etc, etc. So fingers crossed!

    On the other PC which is Intel 815E chipset I could get no joy so deleted InCD and loaded up Roxio's Direct CD 3.05 - this too is running fine.

    I have some doubts re the compatability of InCD with XP

    To answer the points you made -

    Abraxas - I was getting Stop 8E errors on both pc's so dodgy RAM (mine is all Crucial) seems unlikely. BsUDF.sys is an InCD file and both versions of Nero and InCD are the latest. I have used Win Doctor lately - will be more careful in future, but it has not caused a problem in the past - AS FAR AS I KNOW!

    Paul -I don't have a CDRW icon - not a feature of InCD (?), only the taskbar icon. Writers are slaves on both machines.

    Thanks for your help both - I hope the problem is solved - If not 'I will return' as I recall one famous WW2 American General of the same name (Clark) saying (No, I'm not THAT old!)
     
  6. 2002/10/16
    Abraxas

    Abraxas Inactive

    Joined:
    2002/08/16
    Messages:
    2,361
    Likes Received:
    3
    Glad you are set, and thanks for posting back. The problem was a little deeper than InCD, I guess.

    It's good to hear that Nero techs gave you the right information.
     
  7. 2002/10/16
    Paul

    Paul Inactive

    Joined:
    2002/01/29
    Messages:
    1,293
    Likes Received:
    1
    Interesting about the install of the VIA drivers. Might check that out on my XP/Aopen VIA chipset M/B.
     
    Paul,
    #6
  8. 2002/10/17
    Paul

    Paul Inactive

    Joined:
    2002/01/29
    Messages:
    1,293
    Likes Received:
    1
    Pete,
    Have just tried the experiment on XP Pro SP1 with W2K compatability mode used on the installation of the VIA 4.43v install package. The original IDE VIA Bus Master IDE Controller driver, presumably from this installation package was version 5.1.3597.0 from Microsoft.
    Installing the Via drivers in W2K compatability mode mode installed version 5.0.2195.120 (18/10/2001) 5.0.2195 being W2K gold release. My mouse became a bit jittery after this. I then rolled back the driver from the available options and the driver revision returned to 5.1.2600 (XP gold release). Installing the VIA 4-in1 package but not in compatability mode now has this VIA IDE driver back to 5.1.3597.0 (1/7/2001) where I started from.
    Basically I think the correct drivers are installed for XP with the 4-in1 installation. But your problem has been masked (rather than fixed) not by the correct XP driver being installed but by the W2K version being installed instead. I think you have another hardware or most probably a software issue somewhere. But if the W2K VIA driver fixes the problem then your laughing!
     
    Paul,
    #7
  9. 2002/10/17
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Paul
    I was laughing - no longer!
    Read your post and did my own spot of investigating. You are correct, but did you note that Via 4-in-1 in win2k compatability mode installed Via drivers, but in 'XP' mode installs MS generic drivers.

    Anyway after that exercise I was back to the blue screen syndrome again, even with Win2K drivers.

    Read on the Ahead site that InCD is not compatible with Via chipsets, but it looked as if that part of the site had not been updated for a while.

    I mentioned that I had disabled all the Autoplay options through My Computer for the CDRW drive. Ran Ahead's info tool again and it said Autorun was on. Went into the Registry and disabled Autorun as had been requested by Ahead tech some time ago.

    InCD now appears to work, but a CDRW disc is not mounted until Explorer is opened or drive clicked on. That's no great problem I guess, but after ejecting CDRW the drive sometimes disappears. When re-inserting the disc I sometimes get the message 'Please insert a Disc'!

    The real pain is that the DVD/CDrom drive no longer autoruns.

    Do you know of a way to disable autorun on the CDR only?There's only a single entry in the Registry so I guess there is not.
    Any suggestions for a replacement for InCD - Direct CD does not run without crashing the other PC with same OS and I do not want to lose Nero.

    I guess I must get back on to Ahead tech again, but without any great hopes.
     
  10. 2002/10/17
    Abraxas

    Abraxas Inactive

    Joined:
    2002/08/16
    Messages:
    2,361
    Likes Received:
    3
    Since InCD is a completely separate program, it can be uninstalled without losing Nero, if that is what you are asking.

    I've found it expedient to dump packet writing altogether and simply use multisession ISO for burning. It is a more common format and the CD's can be read on friends' machines without a packet reader, with all of the problems that that installation can entail, needing to be added.

    Back in the days when I used it, I used DirectCD and Nero together without any problems. The problem is really finding a standalone version of DirectCD since it is usually bundled with the entire package with Creator.
     
    Last edited: 2002/10/17
  11. 2002/10/18
    Paul

    Paul Inactive

    Joined:
    2002/01/29
    Messages:
    1,293
    Likes Received:
    1
    Pete,
    Have you tried swapping the CDRW and CDROM so the RW is the master. Worth a try?
    Today I installed a Writer on a friends XP machine. A VIA hybrid chipset motherboard I think. Anyway I installed Nero 5.9.9.14 and InCD 3.37. Then I had problems with both Nero and InCD. I then deleted the burner in the device manager, rebooted and the BSOD started just after windows started installing the drive. Tried EVERYTHING, Changing the master/slave config, removed the IDE cable from the writer and got the BSOD this time on the CDROM!! Ripped the cable out of both. uninstalled them in the device manager etc. What I found after thinking what the @#$%! was going on, was that I needed to disable XP's built-in burning software. My computer/right click on the CDRW icon/select properties/recording, and untick "Enable CD recording for this drive ". I don't think Nero/InCD disable it. Anyway that fixed the problem.
     
  12. 2002/10/18
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Abraxas

    I guess you're right - I should dump it, but I'm surprised that reputable software companies put out stuff that isn't really compatible with current OS's.

    The reason I want to use the CDRW facility is for my backups - for a long time I searched for a backup program which would do incremental backups to CDRW - I have a Zip drive but Iomega backup is a real pain - it can take 10 mins or so to initiate (even on USB drive) before it actually does anything. I then found that Backup within XP could be used with a CDRW if you had InCD (or similar) - that was my current aim, but perhaps no more.

    Looks like it would be less hassle to continue to use XP backup to backup to the second HDD (important data is on first HDD) and then copy that backup to CDR. I'm waiting a reply from Ahead tech - might be helpful, but I rather think not!

    As for CDR writing I have no problem with that - must have burnt 500 - 600 cd's this year for use on other PC's and Nero is fine for that - more than could be said for Adaptec (now Roxio) Easy CD.

    Thanks for your time and interest!
     
  13. 2002/10/18
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Paul

    Sorry to hear you have problems too!!

    Windows burning is disabled - I've checked that out. Whether or not I did that a long tima ago or InCD did it I don't know.

    Might try putting CDRW to master, but I'm pushed for time at present. See my post to Abraxas for present thinking, etc
     
  14. 2002/10/19
    Paul

    Paul Inactive

    Joined:
    2002/01/29
    Messages:
    1,293
    Likes Received:
    1
    I'm of the belief that using packet writing software is the way to go for software and data backups. I mirror 2 or 3 CDRW's for security incase one disk gets corrupt, scratched or I do something stupid like hit the format button by mistake (done that). I've had no problems with nero incd or roxio's direct CD apart from the hardware issue I mentioned. I still think your problem is hardware/configuration related.
    Multisession on a CDR is certainly an option though.
     
  15. 2002/10/24
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Paul

    After a few days away I followed your suggestion and made the CDRW Master - now InCD appears to work just fine! Just a few inconsistencies (?) with the disk eject after a large write (400Mb), but we get there in the end. MS Backup/Restore appear to work.

    Incidentally I noticed that with CDRW as Slave DMA was OFF, but with CDRW as Master DMA is ON (according to Nero Infotool). This may explain the BSOD's ?? Autorun/play is also ON.

    This has worked on both my PC's with different CDRW's. I haven't experimented further with the laptop, but I'm not too bothered with InCD on that and it remains uninstalled on that m/c.

    Thanks for the suggestions re mastering - fingers crossed from now on!
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.