Just curious if anyone else has come across behaviour like this?
...
The only way to recover the system is to turn off the computer, remove power completely and leave it long enough for all capacitors in the system to discharge. When it starts up again everything is fine.
Any ideas?
-Carol Haynes
The only times I've had ImgBurn go toes up on me is when trying to:
1) write to poor quality discs.
2) write to a disc at too fast a speed.
3) some kind of ASPI layer conflict from other software.
In all the above, never has it required removing power from the system to fix. If ImgBurn didn't want to exit then killing it with TaskManager let me open the drive, (I think anyway, it's been a while since ImgBurn has failed, 2+ months and 100+ discs).
However, I have had previous faults that cause the same kind of problem, (and in almost all cases that I remember), it was caused by an interface cable coming loose, (not necessarily for the burner).
Since upgrading my system, reinstalling the OS and using only TY DVD-Rs I've not had any problems at all with ImgBurn, (and it's the only thing I use).
It used to be that any kind of optical writer was to be positioned as the
master on any IDE controller. I don't know if that still holds true or not but I do know that if my BenQ DW1540 is not the master then I have pretty much no hope of writing a good disc, {was on the same bus with a Sony AW-G170A (Optiarc 7170) as master}. My old NEC 3520 and 2500 were pretty iffy as slaves also.
Nowadays I have a Pioneer 212 (SATA) and the Sony AW-G170A (IDE), the Sony is on the only IDE bus as master with a 400GB HDD as slave.
You could try changing your IDE cabling so that you have the one DVD-DL as master on each bus with the HDDs as slave.
Have you checked the System Event Log? You might find more info, (errors/warnings), in there.