Tweet
FAQ: How to interpret your burning error code
Bad burns happen - that's a fact. Why? That's the great unknown.
However, our burning log tells us all. Here's a sample from a Nero log:
I have highlighted the key numbers in the error code. So what does it mean, and what are the suggested remedies?
Well, first, you should read the Golden Rules of Burning. This should solve 99% of all burning problems.
But to interpret these codes and have a handy reference of how to fix them, you should see the ATAPI errors explained page.
In this case, we have the code **030c00, which is a "write error". Of course it's a &*^%$ write error, you say - the damn thing did not complete!! What the heck does that mean?
Well as you can see on the ATAPI errors explained page, the 03 section refers to media errors. This is your first clue. If you scroll down to **030c00, you'll see 3 key remedies - in this case #4 (check DMA), 5 (media issues) and 6 (drive issues). Click on them and follow the instructions.
Simple!
There's an error and a number of suggested remedies for every error code that can possibly be generated by your burner.
So, next burn error you get, have a look at your burn log - Nero logs are located at C:\Program Files\Ahead\Nero\NeroHistory.log - and follow-up on the error code on the ATAPI errors explained page.
Then, if you are still stumped, come on in to the forums and we'll see if we can lend a hand.
Happy burning and fewer burn errors!
Regards
Bad burns happen - that's a fact. Why? That's the great unknown.
However, our burning log tells us all. Here's a sample from a Nero log:
Code:
10:03:54 PM #24 SCSI -1135 File Cdrdrv.cpp, Line 1447 SCSI Exec, HA 1, TA 1, LUN 0, buffer 0x01AA0000 Status: 0x04 (0x01, SCSI_ERR) HA-Status 0x00 (0x00, OK) TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND) Sense Key: 0x[COLOR=red]03[/COLOR] (KEY_MEDIUM_ERROR) Sense Code: 0x[COLOR=red]0C[/COLOR] Sense Qual: 0x[COLOR=red]00[/COLOR] CDB Data: 0x2A 0x00 0x00 0x08 0xE5 0xA0 0x00 0x00 0x20 0x00 0x00 0x00 Sense Data: 0x71 0x00 0x03 0x00 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0x00 0x0C 0x00 10:03:54 PM #25 DVDR -1135 File Writer.cpp, Line 333 [COLOR=red]Write error[/COLOR]
Well, first, you should read the Golden Rules of Burning. This should solve 99% of all burning problems.
But to interpret these codes and have a handy reference of how to fix them, you should see the ATAPI errors explained page.
In this case, we have the code **030c00, which is a "write error". Of course it's a &*^%$ write error, you say - the damn thing did not complete!! What the heck does that mean?
Well as you can see on the ATAPI errors explained page, the 03 section refers to media errors. This is your first clue. If you scroll down to **030c00, you'll see 3 key remedies - in this case #4 (check DMA), 5 (media issues) and 6 (drive issues). Click on them and follow the instructions.
Simple!
There's an error and a number of suggested remedies for every error code that can possibly be generated by your burner.
So, next burn error you get, have a look at your burn log - Nero logs are located at C:\Program Files\Ahead\Nero\NeroHistory.log - and follow-up on the error code on the ATAPI errors explained page.
Then, if you are still stumped, come on in to the forums and we'll see if we can lend a hand.
Happy burning and fewer burn errors!
Regards
