[turbonium]

First problem I've had with this great tool... When I reach the end of an ISO burn, either SL (Verbatim 8x -R) or DL (Ritek D01 +R), I get the pop-up that says "completed successfully". I hit OK, and just as ImgBurn starts "recognizing" the disc it just burned, the system hangs (frozen mouse pointer, no keyboard input accepted). Only recourse is a hard reset. If I tick "verify", the verify runs to 100% too, then the "success" pop-up, then the crash on rescanning the media.

I had thought this was associated with an Event Log message, "15: RSM cannot manage library CdRom0. The database is corrupt," but that went away after I stopped running Daemon Tools and removed the virtual DVD-ROM device it had installed. The last event id before the crash is now the normal "7036: The IMAPI CD-Burning COM Service service entered the stopped state."

I'm running XP Pro SP2 with all critical updates on an Asus P5WD2-Premium (955x), with a Pentium D 805, 2x512 MB Kingston HyperX DDR2-800
BenQ DW1655 burner, BCHB RPC1 (TDB) on the Intel onboard PATA channel
Logitech Mouseman Dual Optical USB
BTC CL6300 USB keyboard
Asus EN7600GT SILENT PCI-ex 16x
AEC6880 PATA RAID PCI with 2x Maxtor 250GB in RAID-1
Onboard SATA-II RAID (Interl ICH7R) with 2x Samsung SP2504C in RAID-0 (Boot drive)

I burn using the Admin account via SPTI.
Background apps include Skype, Asus PC Probe, Symantec antivirus, and driver utilities for the video card, PATA RAID volume, keyboard, mouse, and onboard sound.
My full tasklist looks like:



Lightning, any idea what would cause this? It's happened on about 8 of my 10 total burns with this setup--some are PgcEdit handoffs, others are burns straight from an .iso/.mds pair....it doesn't seem to matter which.

thanks,
Adam

[LIGHTNING UK!]

Well I'm pretty confident it's not a general bug so I hope you don't mind if I move this to the support forum.

When you see the program supposedly crashing, what does it say in the status bar?

That'll tell you roughly what it was trying to do the last time it sent a command to the drive.

The program is actually still working fine at these times, it's just waiting for a response to the command. As you've seen, when programs wait for I/O calls to finish processing, the entire system also waits.
If that call ever came back (either as an error or successful), I bet the machine would spring back to life.

You may have some nasty filter drivers installed that are screwing up the I/O path so that would be one of the things I'd check.

Take a look at 'Filter Driver Load Order v1.0.006' from http://www.bustrace....e_utilities.htm

[Nano]

Was your an upgrade from windows 2000?
If yes: what is the version number of your %windir%\system32\drivers\disk.sys

This post has been edited by Nano: 03 July 2006 - 09:59 AM

[turbonium]

Quote

Well I'm pretty confident it's not a general bug so I hope you don't mind if I move this to the support forum.

Sorry if I posted in the wrong spot!

Quote

When you see the program supposedly crashing, what does it say in the status bar?

I'll have to catch that on the next go; I can see it's probably critical to understanding the problem. Could it have been something like 'media has changed'?

Quote

You may have some nasty filter drivers installed that are screwing up the I/O path so that would be one of the things I'd check.

I see 'incdrm' v4.0.0.16 (some sort of Mount Ranier thing assoc. with Nero?), then redbook, then the benq drive itself, then 'imapi'...that's it.

Quote

Was your an upgrade from windows 2000?
If yes: what is the version number of your %windir%\system32\drivers\disk.sys

I did move from Win2K, but I can't remember if I did an upgrade. My root folder is named WINDOWS not WINNT, so maybe not. Anyway the disk.sys is v5.1.2600.2180

[LIGHTNING UK!]

It wasn't so much the wrong place, just it easier for me to double check I've fixed things if the bugs forum only has real (confirmed) bugs in it.

Ok well if you don't use incd, I'd uninstall it. Any additional driver the commands has to pass through before reaching the drive is another place for things to go wrong.

If you don't intend to use the built in windows burning stuff, disable imapi in services.

When you burn your next disc, press F8 before it normally hangs. That will enable some additional I/O debug logging.

I'll then be able to see exactly which command it's up to before the machine gets stuck.

[jmminphxaz]

15: RSM cannot manage library CdRom0. The database is corrupt .. blah, blah, blah.

The error is being generated by the Removable Storage Manager; and my guess is that if you upgraded from NT you will find RSM is an enabled service (start type Automatic), and unless you are part of a network (large) and have tape and disk archives (with people mounting tapes and disks for you based on system requests) you don't need it running. RSM causes all kinds of flaky errors and coaster generation.

SO ... in XP go START >> CONTROL PANEL >> ADMINISTRATIVE TOOLS >> SERVICES

Scroll down and find the service "Removable Storage"
Select it >> Right click and select PROPERTIES.
Midway down Use the drop down list to change the STARTUP TYPE to MANUAL.
Click APPLY
Then under SERVICE STATUS click STOP.
After the service stops, click OK and then exit the SERVICES tool.
Reboot just to keep everything happy. And you should have a whole disdain for M$oft.

I found this out a while back - I went from 50% RIDATA DVD+R D/L coasters to 0% coasters (unless I screw the iso up that is).

Hope it helps!

I would also (as suggested) follow the same steps and kill off the IMAPI CD-Burning COM Service unless you actually use it.