Strange problem - only seems to occur with ImgBurn

[Carol Haynes]

I have been using the latest build of ImgBurn since it was released without problems but recently I have encountered a problem when there is an error during burning.

 

A couple of time ImgBurn has reported device not ready on my drives. I tell it to stop burning and not to bother closing the disc but ImgBurn doesn't return control, the disc keeps spinning and the drive door is locked. Also at this point the mouse moves in fits and starts and during shutdown audio is badly broken up - presumably a process related to the problem is hogging CPU time but I can't see anything in the Task Manager. There are no event log entries relating to this.

 

The only solution is a reboot but I have found that at this point the drives disappear from my BIOS completely and are not present when Windows loads!

 

The only way to get the drives back is to switch the computer off, unplug it and leave it until capacitors have had time to discharge and then start it up again. The drives reappear and then work fine.

 

I have repeated this a number of times burning discs with ImgBurn but even though I occasionally get a similar error sometimes with Nero it doesn't lock up the drives and returns control correctly.

 

Anyone any idea what is going on?

 

My setup is:

 

ASUS A8N32-SLI Deluxe Mobo

AthlonXP 64 X2 4600 processor

2Gb DDR Crucial RAM

Dual GeForce 7300 graphics cards in SLI mode

Creative Audigy 2ZS Platinum

Hauppauge TV PCI card

2 x 160Gb WD Caviar PATA drives (Master and Slave on IDE 0)

2 x Pioneer DVR-111 DVD-R DL drives (Master and Slave on IDE 1)

1 x 320Gb WD Caviar SATA-II drive

Various USB devices (scanner, printer, 3 external Seagate hard drives, multicard reader, keyboard)

 

Thanks for any help.

[volvofl10]

process of elimination , does this happen with BOTH of the pioneer drives, or only on one paticular drive ?

[mmalves]

Do you remember the exact error message you're getting?

 

Make sure your Pioneer burners are using the latest firmware available. Also make sure you're using the latest drivers available for the chipset/storage of your motherboard.

 

What brand/type of media are you using? Verbatim and Taiyo Yuden manufacture the best blanks so try with them too.

[LIGHTNING UK!]

It's not ImgBurn that's not releasing control, it's something further down the line... the controller drivers or some 3rd party filter driver.

[Carol Haynes]

It's not ImgBurn that's not releasing control, it's something further down the line... the controller drivers or some 3rd party filter driver.

 

Any idea how to troubleshoot this? Also why does it not happen with Nero?

 

Sorry I don't really know much about the mechanics of buring apps or how they relate to other filters/controller drivers.

 

This seemed to arise after I installed a demo version of TuneBite but I have removed that now and I can't see anything left in the devices list (including hidden and system).

 

In answer to other questions:

 

Yes it seems to lock out both drives - so it seems to be affecting the IDE 1 channel - however even when the DVD drives are not present Windows reports the interface to be working correctly ???

 

Media types: almost exclusively Verbatim DVD+R x 16 and DVD+R DL x8 inkjet printable discs.

 

Pioneer firmware is the latest version (and hasn't changed in the last year to my knowledge).

 

Sorry I can't remember the exact error message I was getting - it was about waiting for the drive to become ready (and this was about 20% through the burn process).

[dontasciime]

change your IDE cable on Pioneers to another 80 wire one for starters, test your memory with Memtest + and switch off ECC for memory in bios. Actually change IDE on hard drives as well to rule it out but at same time as replacing the Pio drives cable

 

Then look at changing the drive, still does it, then look to change psu Change PSU if total W out is less than 550W and 22 to 28 A on the 12V line.

[Carol Haynes]

change your PSU for starters

 

Why? I have an Antec NeoHE 550W modular PSU which is less than 18 months old, good quality, expensive and morethan adequate for the job ???

[dontasciime]

I edited b4 you posted but still do not rule out a Good brand name PSU causing trouble, specially when you have 2 hd 2 writers 2x gfx 2 x gfx fan cpu fan, god knows how many case fans they all suck juice and not all psu can last. I have gone through about 20 PSU in last 5 years.

 

check 12 v line in a program called "Everest" when running say SETI or any program that uses high cpu if it fluctuates down to 11.36v 11.47v then your psu is on its way out

[LIGHTNING UK!]

You can post a filter drivers list via the Tools menu. Copy it to the clipboard and paste it here.

 

You might also be able to update to the newer nforce drivers via the nvidia site.

 

What I really need to see though is the log with the error. See if you can find it via the 'Help' menu.

[Carol Haynes]

You can post a filter drivers list via the Tools menu. Copy it to the clipboard and paste it here.

 

You might also be able to update to the newer nforce drivers via the nvidia site.

 

What I really need to see though is the log with the error. See if you can find it via the 'Help' menu.

 

Did a stress test - 12V line fluctuates from 11.71 to 12.16

 

Re. error log - unfortunately I reinstalled ImgBurn and the old error log was wiped. I will post one again if I can generate the error.

 

Filter list is as follows:

 

 

===============================================

Filter Driver Load Order - ImgBurn v2.4.2.0

===============================================

 

Upper Device Filter: redbook

Upper Class Filter: GEARAspiWDM

Device: CD/DVD-ROM Device

Lower Class Filter: cdrbsdrv

Lower Class Filter: PxHelp20

Lower Device Filter: imapi

 

Filter Name: redbook

File Name: C:\WINDOWS\system32\DRIVERS\redbook.sys

File Version: 5.1.2600.5512 (xpsp.080413-2108)

File Description: Redbook Audio Filter Driver

Product Name: Microsoft

[Carol Haynes]

Turned out to be a failing motherboard. It no longer POSTS (even to the point of Beep codes with all peripherals removed except for CPU, memory and single graphics card). Luckily I had a spare identical motherboard so I installed it will all the other hardware unchanged and it now works fine.

 

Thanks everyone for the helpful suggestions.