[Note I have gone through and changed the title of this thread. It was originally called "Strange problem with ImgBurn (I think)" but ultimately turned out to be a motherboard problem]
Just curious if anyone else has come across behaviour like this?
Over the last few days I have had a number of occasions where ImgBurn has failed to burn an ISO image to a DVD5 disc. In each case it has siad the device was not ready halfway through the burn. The operation cancelled but the drive kept spinning and nothing would eject the disc except for a system restart. Upon restarting the BIOS cannot detect my DVD drives !! If Windows starts there are all sorts of problems not least of which is that the system is unusable because there is obviously an interrupt hogging a large proportion of the CPU time - eg. the mouse moves only in fits and bursts. The drives don't appear in the devices list (but the IDE interface does and it says it is working normally!).
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.
At first I thought it was a hardware problem but I can burn the same image on the same drive using Nero. On one occasion a DMA/CRC error was reported by Nero but it was handled properly and the device unlocked.
Is it possible for an instruction to a controller to block access to drives in this way until capacitors are discharged?
I don't think it can be a dying IDE controller because I have my hard discs on the same controller and have had no issues at all with them. Granted they are on channel 0 and the two DVD-R DL are both on channel 1 so maybe it is a problem with one channel. However, it is strange that I only seem to have this problem with ImgBurn. Could it just be a bug in the handling of one unusual error type? I have noticed in the past the ImgBurn doesn't handle errors totally gracefully and often takes a long time to release a disc - even just for a simple bad block error.
Any ideas?
Just curious if anyone else has come across behaviour like this?
Over the last few days I have had a number of occasions where ImgBurn has failed to burn an ISO image to a DVD5 disc. In each case it has siad the device was not ready halfway through the burn. The operation cancelled but the drive kept spinning and nothing would eject the disc except for a system restart. Upon restarting the BIOS cannot detect my DVD drives !! If Windows starts there are all sorts of problems not least of which is that the system is unusable because there is obviously an interrupt hogging a large proportion of the CPU time - eg. the mouse moves only in fits and bursts. The drives don't appear in the devices list (but the IDE interface does and it says it is working normally!).
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.
At first I thought it was a hardware problem but I can burn the same image on the same drive using Nero. On one occasion a DMA/CRC error was reported by Nero but it was handled properly and the device unlocked.
Is it possible for an instruction to a controller to block access to drives in this way until capacitors are discharged?
I don't think it can be a dying IDE controller because I have my hard discs on the same controller and have had no issues at all with them. Granted they are on channel 0 and the two DVD-R DL are both on channel 1 so maybe it is a problem with one channel. However, it is strange that I only seem to have this problem with ImgBurn. Could it just be a bug in the handling of one unusual error type? I have noticed in the past the ImgBurn doesn't handle errors totally gracefully and often takes a long time to release a disc - even just for a simple bad block error.
Any ideas?







Sorry, I hadn't intended to be a prophet of doom ... Glad you had a spare.

- carpe noctem