FAQ: The burning with Nero failed - some clues to why

[cynthia]

The burning with Nero failed - some clues to why

Error code:

Nero reports that the burn has failed. It gives you a chance to save or print out an log file. Save that log file on your hard disk. You will need it.

Problem:

You now have a bad burn - a coaster - in your hand and you really don't know what went wrong. Even if you have burned several other discs with success or this is your first burning - you both have entered the same club with the name - "what to do?".

Solution:

Something is not working out right. It can depend on the following issues:

• You don't have DMA enabled
• Your burner don't support your media
• You are burning at to high rate
• Some settings in Nero are wrong
• You are using the wrong type of disc
• Nero has a bug

So take your log file and compare it with the following issues to what could have gone wrong with your burning. Just remember that the examples may very well be different than your own setup in your log file. The basic issues should be the same.

And please - if you are new to burning - use a -RW or a +RW disc. It will be cheaper for your. When you know that your setup is done and you have burned your first disc without problems - then you can start using -R or +R discs

First part of the log file from Nero

Windows XP 5.1
IA32
WinAspi: File 'Wnaspi32.dll': Ver=4.71 (0002), size=45056 bytes, created 2002-07-17 10:03:20
ahead WinASPI: File 'C:\Program Files\Ahead\Nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 2004-10-26 17:35:34
Nero API version: 6.6.0.6
Using interface version: 6.3.1.4
Installed in: C:\Program Files\Ahead\Nero\
Application: ahead\Nero - Burning Rom
Recorder: <_NEC DVD_RW ND-1300A> Version: 1.0B - HA 1 TA 0 - 6.6.0.6
Adapter driver: HA 1
Drive buffer : 2048kB
Bus Type : default (0) -> ATAPI, detected: ATAPI

=== Scsi-Device-Map ===
DiskPeripheral : IC35L080AVVA07-0 atapi Port 0 ID 0 DMA: On
DiskPeripheral : SAMSUNG VG36483A (6.48GB) atapi Port 0 ID 1 DMA: On
CdRomPeripheral : _NEC DVD_RW ND-1300A atapi Port 1 ID 0 DMA: Off
CdRomPeripheral : JLMS XJ-HD163 atapi Port 1 ID 1 DMA: On
DiskPeripheral : ST3160023A 3.06 hpt374 Port 2 ID 0 DMA: Off
DiskPeripheral : Maxtor 6Y120P0 YAR4 hpt374 Port 2 ID 1 DMA: Off
DiskPeripheral : ST380021A 3.19 hpt374 Port 2 ID 2 DMA: Off
DiskPeripheral : Maxtor 6Y120P0 YAR4 hpt374 Port 2 ID 3 DMA: Off
OtherPeripheral : HPT RCM DEVICE hpt374 Port 2 ID 0 DMA: Off
OtherPeripheral : HPT RCM DEVICE hpt374 Port 3 ID 0 DMA: Off

=== CDRom-Device-Map ===
_NEC DVD_RW ND-1300A G: CDRom0
JLMS XJ-HD163 F: CDRom1
=======================

1. Do you have DMA enabled for your burner?

DiskPeripheral : IC35L080AVVA07-0 atapi Port 0 ID 0 DMA: On
DiskPeripheral : SAMSUNG VG36483A (6.48GB) atapi Port 0 ID 1 DMA: On
CdRomPeripheral : _NEC DVD_RW ND-1300A atapi Port 1 ID 0 DMA: Off
CdRomPeripheral : JLMS XJ-HD163 atapi Port 1 ID 1 DMA: On

On IDE channel # 1 and as a master is a hard disk connected
On IDE channel # 1 and as a slave is is a hard disk connected
On IDE channel # 2 and as a master is a DVD burner connected
On IDE channel # 2 and as a slave is a DVD-ROM reader connected

The problem here is that the burner don't have DMA enabled - it's shows up as "DMA: Off". The right setting should be "DMA: On".

To fix this: How to enable DMA?

How to connect the devices

Normally you should have your hard disk on IDE channel 1 and your burner set as master on IDE channel 2 and if you also have a DVD-ROM or a CD-burner - connect it as slave on IDE channel 2.

Also check the pin-settings back on your reader/burner. Are they set right in the master/slave position? The master is the one at then end of the cable and the slave in the middle (between your motherboard connection and the last connection).

2. Do you have the latest version of Nero installed?

Nero API version: 6.6.0.6

This tells you which version of Nero you have installed on your PC. Visit the update link to find out if there is any new updates for your version of Nero. The updates are free.

Updates for Nero.

3. Do you have the latest firmware version installed?

DVD burners optimize their ability to write to different brands of DVDs by internal "write strategies" that control the laser power and pulse settings to maximize its accuracy with each different dye formula, reflector density and plastic doping chemistry for each brand of blank DVD disc.

When a disc is inserted, the drive reads the factory media ID off the disc and queries its internal list of known disc brands and write strategies. If the disc is listed, then it uses the write strategy for that disc.

If a write strategy for a particular disc brand is not present in the drive's firmware, it tries to estimate how best to write to the disc by writing to the small re-writable "power calibration" area on each unknown disc type to see which power setting might produce best results for the unknown disc brand.

In some cases, the firmware is unable to produce reliable burning with a particular disc brand, and rejects the disc as having a "power calibration error" or "illegal disc" or a similar error. This error is generally not related to disc quality issues, but is simply a result of the drive not having the latest firmware in it that lists the particular disc brand.

From time to time, drive makers test additional brands of DVD discs and then update their firmware with new write strategies for those newly tested discs, enabling their drives to work with more brands of DVD discs.

All DVD writer owners need to frequently check with their drive manufacturer to see if there is a new firmware upgrade available for their drive. That way they can expect to enjoy working with more brands of discs, and more reliably with the discs that they already can use.

How do I know which firmware version that is installed in the burner? Use AKA Flashman's tool to find out your current version. You can also see it in this part of the log file:

Recorder: <_NEC DVD_RW ND-1300A> Version: 1.0B - HA 1 TA 0 - 6.6.0.6

This burner has firmware version 1.0B installed.

Look at your brands website to download the latest version or search for firmware at the firmware page or DVD-Makers.com.

[cynthia]

Second Part of the log file from Nero:

Is the media you are using working with your burner?

11:58:29 AM #18 Text 0 File Cdrdrv.cpp, Line 8315
---- DVD Structure: Physical Format Information (00h) ----
Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD-R (2), Part Version: 5
Disc Size: 120 mm, Maximum Rate: (F h)
Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: recordable
Linear Density: 0,267 um/bit, Track Density: 0,74 um/track
Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
End Physical Sector Number of Data Area: 0 h
End Sector Number in Layer 0: 0 h
Data in Burst Cutting Area (BCA) does not exist
Start sector number of the current Border-Out: 0 h
Start sector number of the next Border-In: 0 h
Media Specific [16..63]:
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

The problem with the above is that the field "Media Specific" is empty - the media codes on your disc is not covered by the burners firmware. They don't understand each other and the burner is trying to use a generic write strategy for the disc. In most cases it will not work out and you end up with a "power calibration error" or "illegal disc" or a similar error.

This error is generally not related to disc quality issues, but is simply a result of the drive not having the latest firmware in it that lists the particular disc brand.

The solution is to find another firmware that covers your brand of discs or to change to another brand of discs that are already covered in your firmware.

For a good burn it should look something like this: (forget about the numbers and characters - they are only valid for this example and you should have a completely different set of numbers and characters).

04:14:32 #13 Text 0 File Cdrdrv.cpp, Line 8332
---- DVD Structure: Physical Format Information (00h) ----
Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD+RW (9), Part Version: 2
Disc Size: 120 mm, Maximum Rate: (F h)
Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: re-writable
Linear Density: 0,267 um/bit, Track Density: 0,74 um/track
Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
End Physical Sector Number of Data Area: 26021F h
End Sector Number in Layer 0: 0 h
Data in Burst Cutting Area (BCA) does not exist
Disc Application Code: 0 / 0 h
Extended Information indicators: 0 h
Disc Manufacturer ID: RICOHJPN
Media type ID: W11
Product revision number: 1
Number of Physical format information bytes in use in ADIP up to byte 63: 57
Media Specific [16..63]:
00 00 00 52 49 43 4F 48 - 4A 50 4E 57 31 31 01 39 ...RICOHJPNW11.9
23 00 8A 86 68 02 26 00 - 8A 86 70 02 28 00 8A 86 #...h.&...p.(...
6A 02 28 22 12 10 E0 00 - F0 00 00 00 00 00 00 00 j.("............

But these discs worked before - I just bought a new package:

Having previously had successes with cheap media is no indication they're not the cause of the problem.

Their "quality control" is often not as good as other more expensive media, and you can easily end-up with a bad disc or even a bad batch of discs.

If your burning end with an error in the final burning stage it's normally a sign of bad media.

Good media to use could be Ritek, Verbatim, Fuji, Maxell. You find an overview and discussion about blank media and quality regarding different brands at digitalFAQ.com.

You can find a list of compatible media for your burner at VideoHelp.com.

To see who actually made the disc and the manufacture ID that you're trying to use - you can use the program DVD Identifier. This program offers a reliable method of accurately identifying the disc's REAL manufacturer. This information will also help you in determining which discs are most suitable for your DVD recorder when you compare the information from this program to what others have to say about your burner and player.

Other good advices regarding burning:

• Make sure your DVD-R/-RW or DVD+R/+RW is sound and clean: A small speck of dust, a scratch or fingerprint can be the difference between a successful burn and a coaster.
• It is recommended to not use your computer for other tasks while burning (some even recommend re-booting before a burn, and even stopping any background programs like anti-virus...)
• Don't use a screen-saver.
• Compress the movie/data a bit more, so that the media edge is not being used (on bad media, the edge can be defective and not written to or read properly).
• Try a lower burn speed (if you were using 2x or higher).
• Your hard-drive(s) is heavily fragmented. Make sure to defragment it regularly.

Last Part of the log file from Nero:

Existing drivers:
File 'Drivers\ASPI32.SYS': Ver=4.71 (0002) built by: WinDDK, size=16512 bytes, created 2002-07-17 09:05:10
File 'Drivers\PXHELP20.SYS': Ver=2.02.62a, size=20016 bytes, created 2003-10-28 11:02:00 (Prassi/Veritas driver for win 2K)

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

This part lists drivers that could create a conflict with the drivers Nero uses.

If they exist in your log file - they are either from currently installed programs or badly uninstalled programs.

Error codes from Nero:

The most common errors during a burning is the one I will list and describe in the following posts.

You can also find a list of error codes in this page from CD Speed.

If you can't solve your burning problems after that you have tried with this guide - post your log file from Nero in the forums section DVD Burning and Backup.


Nero's guide on how to read the log file:

There are two rather old guides on how to read the log files from Nero. They are written for version 5.

A log file from a successful burning.
A log file from a unsuccessful burning.

[cynthia]

Booktype/bitsetting Error

Error code:

5:04:03 PM #32 Text 0 File DVDR.cpp, Line 5348
Drive: SONY DVD RW DRU-710A
Book Type request: DVD+R
Book Type setting not supported for the loaded disc type

Error-free code:

8:23:44 PM #22 Text 0 File DVDR.cpp, Line 5023
Drive: BENQ DVD DD DW1620
Book Type request: DVD-ROM
Changing the book type was done succesfully

Problem:

You are trying to bookmark/use bitsetting on a -R/-RW disc or your burner don't support this feature. If you don't know what this is about - visit cdfreaks.com or DVDplusRW.org. You can also read about it in blutachs FAQ.

Solution:

• Use +R/+RW discs
• Update your firmware
• Update Nero

[cynthia]

Power Calibration Error

Error code:

4:18:59 AM #25 CDR -1106 File Writer.cpp, Line 301
Power calibration error

4:18:59 AM #26 Text 0 File ThreadedTransfer.cpp, Line 229
all writers idle, stopping conversion

4:18:59 AM #27 Text 0 File ThreadedTransfer.cpp, Line 223
conversion idle, stopping reader

4:18:59 AM #28 Text 0 File DVDR.cpp, Line 1847
EndDAO: Last written address was 31

4:18:59 AM #29 Phase 38 File APIProgress.cpp, Line 253
Burn process failed at 4x (5,540 KB/s)

Cause:

Power Calibration is controlled by the recorder.

Before any write operation, all recorders must do a 15 step power test to determine the optimum power for writing to the CD; this is called "Optimum Power Calibration"(OPC). During the write, it continues to do this test to get the best write throughout the whole CD; this is called "Running Optimum Power Calibration" (ROPC).
This whole process is controlled by the recorder, though initiated by programs such as Nero. There is an area on the inner part of the CD for the test and test data info to be stored. You can use this area up to 999 times.

If you receive the "Power calibration error" or "Power calibration area is (amost) full" error message, the cause will be either poor media, poor power, or a defective recorder.

Solution:

This error can be caused in conjunction with some (cheap) medias, try to burn them alternative with lower speed or switch to another brand of discs.

If you cant solve this error by using recommend medias, pls. try out these steps , if they fail, drive is defect, you should claim it immediate to your dealer.

Update the firmware of your recorder. Please check the manufacturer's website for the latest version.

It is recommend that device should be connected to secondary IDE port as master. Dont use fast ATA 133/166/233 and 266, unit should connected with delivered UDMA-2 cable(40pin)

Try different configurations, such as taking the CD-ROM to the primary IDE bus as slave and have only the recorder connected to the secondary IDE bus as master.

First deinstall all your burnersoftware(s), also clean registry*.
(*it is recommend to use cleaning tools from NERO:
General Clean Tool http://www.nero.com/en/631940828445001.html
Registry Checker and DriverClean tool http://www.nero.com/en/631938356417810.html
InCD Clean Tool http://www.nero.com/en/631938356212815.html
Nero 5 Clean Toolnero clean tool http://www.nero.com/en/631938364095950.html )

Install actual mainboard driver (Busmaster/ Chipset driver). Contact in this case manufacturer of your mainboard. For test you can also try to burn without DMA mode, ( only possible under Windows XP and Windows 2000 ) in the device manager - "IDE ATA/ ATAPI controllers", you can switch from DMA to PIO mode. Pls. notice: If problems caused by NFORCE Chipset drivers, you should better reinstall MS standard IDE drivers.

More than one installed burnersoftwares can cause problems (**some softwares replace ASPI driver by their own! ) so install only one, especially actual trial release of NERO [ http://www.nero.com ] and check burn project again.

**If needed, install actual ASPI Driver (contact manufacturer of your burnersoftware e.g. www.nero.com )

Use our recommended medias , with other medias there`s no guarantee, they will be written correctly and with maximum speed.

For Problems with InCD, pls. contact Nero support. Be informed device works only with InCD, Mt.Rainier (e.g. directCD) is not supported.

You can deactivate for test (only with Windows XP) "IMAPI CD-Burning COM Service", go to menu "start" > "settings" > "administration" > "services", search "IMAPI CD-Burning COM Service", rightclick and deactivate "starttyp".

[cynthia]

Write error

Error code:

7:56:02 PM #26 Text 0 File Cdrdrv.cpp, Line 1284
19:56:02.906 - SONY DVD RW DRU-710A\H1 T0 : Queue again later

7:59:58 PM #27 SCSI -1135 File Cdrdrv.cpp, Line 1432
SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x0A6D0000
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x03 (KEY_MEDIUM_ERROR)
Sense Code: 0x0C
Sense Qual: 0x00
CDB Data: 0x2A 0x00 0x00 0x04 0xA4 0x20 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0A
0x00 0x00 0x00 0x00 0x0C 0x00

7:59:58 PM #28 CDR -1135 File Writer.cpp, Line 311
Write error

Problem:

Solution:

Check that your DMA is enabled.

[cynthia]

Communication failure

Error code:

Problem:


Solution:

Old IDE controller drivers - This is the most common cause of this error message. You must have the latest drivers for your IDE controller card to prevent it. (It´s the same for SCSI cards). Go to the website of the manufacturer of your controller card and obtain the latest drivers. Such as Intel, VIA, SIS, etc.

DMA settings - You may have DMA disabled for your CD-/DVD-ROM and recorder devices. You should enable this feature. If you have old drivers (even if you have the latest in some cases), DMA may not be properly supported, even though you can enable it. You should try with DMA disabled if you still have problems having enabled it.

Enable or disable DMA:
To enable DMA in Windows 2000/XP, simply go to your 'Control Panel --> Systems --> Hardware --> Device Manager'. Double click on the 'IDE ATA/ATAPI Controllers'. Right click on the 'Primary IDE Channel', go to 'Properties --> Advanced Settings' and change ´Transfer Mode´ to 'DMA if available'. Do the same for the secondary IDE channel.
For Windows 9x and ME, go to your 'Control Panel --> System --> Device Manager --> CD-ROM' and under the devices 'Properties --> Settings' enable or disable DMA.

Driver conflicts - You may have (or had) other CD recording software installed on your system. Their drivers can cause conflicts with our software when trying to communicate to the recorder. Please remove any other recording program you may have on your system and be sure all their drivers are removed as well.

Poor IDE cables - In many cases, with the recorders supporting UDMA, you must use 80pin IDE cables. 40pin IDE cables work with the recorder, but when it comes to the actual recording process, there may be problems. You may just have an IDE cable that is in poor condition and need to replace it, too. Or try a different connector on that IDE cable as the connector could be the cause.

CSEL - If your devices are jumpered with CSEL, your controller could be having trouble with this setting. It's best to change it, so that you have your devices jumpered as master or slave. Refer to the manual on your CD-ROM, DVD-ROM and recorder devices for how to do this.
top

[cynthia]

SCSI target error

Error code:

Problem:


Solution:

Normally caused by CD-R or CD-RW media the recorder is unable to work with. Or the media could be defective, dirty or just not compatible with the recorder.

Cables are known to cause this: loose cables, damaged cables, loose power connectors, etc.

Defective recorders are known to cause this. Test with another demo software to rule out software as the cause. If two software programs have the same symptom, your recorder may need service.

If the drive is being polled by another software's driver, it could hang the bus. Uninstall any other CD recording software you may have had on your system, as well as Nero. Then use Registry cleaner software to clean you registry. At last try a fresh install of our latest Nero release.

[cynthia]

Focus servo failure

Error code:

Problem:

The "Focus servo failure" message is a hardware error.

Solution:

Poor media - Try more than one brand of CD-R media to rule this out as cause.

Poor power - The power to your recorder could be fluctuating. If you have an internal recorder, try a different power connector and make sure it's not being shared by any other devices. If you have an external recorder, if possible, remove it from the external chassis and connect it to your system as an internal recorder. If this resolves your issue, you need to replace or repair the power source in your external chassis.

Optical head is dirty, needs alignment, or recorders circuit board has an open coil - please contact your recorder manufacturer to service your unit.

[cynthia]

No seek complete

Error code:

22:00:48 #28 SCSI -1093 File Cdrdrv.cpp, Line 1178
SCSI Exec, HA 3, TA 1, LUN 0
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x03 (KEY_MEDIUM_ERROR)
Sense Code: 0x02
Sense Qual: 0x00
CDB Data: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Sense Data: 0xF1 0x00 0x03 0xFF 0xFF 0xFF 0xF0 0x12
0x00 0x00 0x00 0x00 0x02 0x00

22:00:48 #29 SCSI -1176 File Cdrdrv.cpp, Line 1178
SCSI Exec, HA 3, TA 1, LUN 0
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x72
Sense Qual: 0x04
CDB Data: 0x5B 0x01 0x02 0x00 0x00 0x03 0x00 0x00 0x00 0x00 0x00 0x00
Sense Data: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x12
0x00 0x00 0x00 0x00 0x72 0x04

22:00:48 #30 Text 0 File dlgbrnst.cpp, Line 1711
Set remaining time: 0:00,000 (0ms) -> OK

22:00:48 #31 CDR -1093 File WriterStatus.cpp, Line 167
No seek complete
SONY DVD RW DRU-510A\H3 T1

22:00:48 #32 TRANSFER -24 File WriterStatus.cpp, Line 167
Could not perform end of Disc-at-once

22:00:48 #33 Text 0 File dlgbrnst.cpp, Line 1711
Set remaining time: 0:00,000 (0ms) -> OK

22:00:48 #34 Phase 38 File dlgbrnst.cpp, Line 1853
Burn process failed at 4x (5.540 KB/s)

Solution:

90% of the time this type of error message is caused by poor media, poor power to the recorder, or an optical head needing cleaning, or a drive needing to be serviced.

But it's only 90% of the time. On a rare occasion I've seen this caused by driver conflicts. Either from other software, or drivers for the IDE Controller.

Old firmware on the recorder - Go to the recorder MFG's website to obtain the latest firmware for your recorder. (You may be able to obtain it from this link as well: http://forum.rpc1.org/dl_all.php)

Poor media - Try more than one brand of media. For example: TDK, Verbatim, Imation, Yamaha, HP, etc.

Poor IDE cable or incorrect cable - For higher end recorders these days if you use the 40pin cable you can have all sorts of unusual symptoms. It would be best to use an ATA-133 80 wire cable.

Driver conflicts - If you have or had another CD recording software installed on your system, its drivers could be conflicting with our software. This is rare for this symptom, but it does occur. Uninstall any other recording software and make sure all its drivers have been removed with it. Then reinstall Nero and make sure to use the latest version we have posted on our website.

Defective recorder - The optical head on your recorder may need cleaning or servicing. Or it's possible the circuit board on your recorder has an open coil or blown diode or resistor. Any of these could cause the error. Only solution would be to send the drive in for service to the recorder manufacturer.

[cynthia]

Buffer underruns

Error code:

Problem:


Solution:

Go to Nero's 'File --> Preferences --> Ultrabuffer' and increase the buffer.

Run "ScanDisc" and "Defrag" on your hard drive. This minimizes the possibility of "Buffer Underrun" errors.

Close any program running in the background (e.g. anti-virus programs). You can do this manually by using the 'Ctrl-Alt-Del'. For Win95/98/ME: Just close all programs except for Systray and Explorer. For Windows 2000/XP systems use Ctrl-Alt-Del, go to Task Manager and close all programs. But sometimes for Windows 2000 and XP it´s not enough to close all programs in the background. A good program to help in these cases is “EndItAll”; please search for it at for example http://www.google.com/.

Try different media brands. The one that you are using may not be compatible with your recorder.

Update the firmware version on your recorder. Please check the manufacturer's website for the latest release.

Try using a different data source (different hard drives, CD-/DVD-ROMs or network drives) to see if it is corrupted or too slow.

Test your drive speed or use a simulation in order to obtain the optimal speed for your system and recorder. If not the maximum possible write speed of the recorder is kept as default.

Please update to our latest Nero release from our website.
Update to Nero 5.5: Nero Burning ROM
Update to Nero 6 Reloaded: Updates Nero 6 Reloaded

Important notes
Upgrades to the latest versions of Nero 5.5 are free of charge.
The Nero 5 serial number does not work for Nero 6/Nero 6 Reloaded.
To upgrade to Nero 6 Reloaded from a previous version - 5.0 or 5.5 - you have to buy the program.

[cynthia]

Reset occurred

Error code:

21:45:33 #24 Text 0 File DVDPlusRW.cpp, Line 615
Start write address at LBA 0
DVD high compatibility mode: Yes

21:48:01 #25 SCSI -500 File Cdrdrv.cpp, Line 1432
SCSI Exec, HA 2, TA 0, LUN 0, buffer 0x00C00000
Status: 0x02 (0x03, SCSI_ABORTED)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0x2A 0x00 0x00 0x05 0x1E 0x60 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02

21:48:02 #26 SCSI -1114 File Cdrdrv.cpp, Line 1432
SCSI Exec, HA 2, TA 0, LUN 0, buffer 0x0CC81A00
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x06 (KEY_UNIT_ATTENTION)
Sense Code: 0x29
Sense Qual: 0x00
CDB Data: 0x2A 0x00 0x00 0x05 0x1E 0x60 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0A
0x00 0x00 0x00 0x00 0x29 0x00

21:48:02 #27 CDR -1114 File Writer.cpp, Line 311
Reset occurred

21:48:02 #28 Text 0 File ThreadedTransfer.cpp, Line 228
all writers idle, stopping conversion

21:48:03 #29 Text 0 File ThreadedTransfer.cpp, Line 222
conversion idle, stopping reader

21:48:03 #30 SCSI -1046 File Cdrdrv.cpp, Line 1178
SCSI Exec, HA 2, TA 0, LUN 0
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x30
Sense Qual: 0x06
CDB Data: 0x5B 0x01 0x05 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Sense Data: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0A
0x00 0x00 0x00 0x00 0x30 0x06

21:48:03 #31 Phase 127 File APIProgress.cpp, Line 276
Generating DVD high compatibility borders

21:48:03 #32 Phase 129 File APIProgress.cpp, Line 276
Generating DVD borders completed successfully

21:48:03 #33 Text 0 File DVDR.cpp, Line 5441
Drive: DVDRW USB 16X
Book Type request [BTC]: DVD+R
Changing the Book Type was finished successfully, return code 0

21:48:03 #34 Phase 38 File APIProgress.cpp, Line 276
Burn process failed at 4x (5 540 KB/s)

21:48:03 #35 Text 0 File AudioCompilationImpl.cpp, Line 867
DRM: DRM burn session terminated.

21:48:03 #36 Text 0 File AudioCompilationImpl.cpp, Line 896
DRM: Closing entire DRM handling. Bye.

21:48:05 #37 SCSI -1196 File Cdrdrv.cpp, Line 1178
SCSI Exec, HA 2, TA 0, LUN 0, buffer 0x0B8A6600
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x02 (KEY_NOT_READY)
Sense Code: 0x3A
Sense Qual: 0x02
CDB Data: 0xFA 0x01 0x00 0x00 0x00 0x00 0x00 0x04 0x00 0x00 0xAA 0xFF
Sense Data: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0A
0x00 0x00 0x00 0x00 0x3A 0x02

Existing drivers:
File 'Drivers\PXHELP20.SYS': Ver=2.02.62a, size=20016 bytes, created 31/03/2004 17:15:49 (Prassi/Veritas driver for win 2K)
File 'Drivers\InCDfs.SYS': Ver=4, 2, 15, 0, size=92672 bytes, created 07/07/2004 13:47:20 (InCD4 driver for win NT/2K/XP)
File 'Drivers\InCDpass.SYS': Ver=4, 2, 15, 0, size=28672 bytes, created 07/07/2004 13:48:00 (InCD4 driver for win NT/2K/XP)
File 'Drivers\InCDrec.SYS': Ver=4, 2, 15, 0, size=7680 bytes, created 07/07/2004 13:50:18 (InCD4 driver for win NT/2K/XP)

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

Solution:

If you do a search on SCSI Command Errors, you will find that many others have had the same issue as yours with USB Recorders, regardless of the software used. Meaning, it occurs with Nero, CD Creator, RecordNow, etc.

And the error message varies from SCSI Command Error, Bus Rest, etc...

In most cases, users have found that updating the drivers for the USB Controller resolves the issue. Other found a new External Chassis for the Recorder resolved the issue. And we provided a work around in our MMC.DLL file that causes our software to reissue the command till the recorder is free and accpets, instead of timing out so soon after a lack of response from the device. This resolved the issue for some, but not for others. This MMC.DLL file is part of Nero 6.6.0.3 and above builds.

Try to disconnected all USB devices except for the external DVD burner.

As a last resort, after trying the above solutions and others, they finally connect as an internal to the system and all issues are resolved.

[cynthia]

Not enough memory

Error code:

8:23:18 AM #2 Phase 114 File APIProgress.cpp, Line 263
DVD-Video files reallocation completed (no file modified)

8:23:19 AM #3 Phase 111 File APIProgress.cpp, Line 263
DVD-Video files sorted

8:23:19 AM #4 Text 0 File ThreadedTransfer.cpp, Line 505
Tried to get 48128 KB of memory

8:23:19 AM #5 TRANSFER -5 File ThreadedTransfer.cpp, Line 506
Error: not enough memory

8:23:19 AM #6 NEROAPI 7 File Burncd.cpp, Line 2975
Error:\nCannot connect TRF.

8:23:19 AM #7 Text 0 File AudioCompilationImpl.cpp, Line 828
DRM: DRM burn session terminated.

8:23:19 AM #8 Text 0 File AudioCompilationImpl.cpp, Line 857
DRM: Closing entire DRM handling. Bye.


Existing drivers:

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

Solution:

You have a basic problem with your Windows swap file - it's to low. How much free disk space do you have on your hard disk?

Try these two things:

1. Reboot - can free up some space in your memory or swap file - you could have too much applications running at the same time.
2. Add some swap space. How to do: right clic on desktop --> properties --> advanced --> performances --> advanced --> modify --> choose a memory size x1.5 than the RAM size (e.G i choose 512 for initial and 512 for max).

[cynthia]

DVD-Video files reallocation failed


Error code:

Windows XP 5.1
IA32
WinAspi: File 'Wnaspi32.dll': Ver=4.71 (0002), size=45056 bytes, created 2002-07-17 11:03:20
ahead WinASPI: File 'C:\Program\Ahead\Nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 2004-10-26 18:35:34
Nero Version: 6.6.0.12
Internal Version: 6, 6, 0, 12c
(Nero Express)
Recorder: <_NEC DVD_RW ND-3520AW> Version: 3.04 - HA 1 TA 0 - 6.6.0.12
Adapter driver: HA 1
Drive buffer : 2048kB
Bus Type : default (0) -> ATAPI, detected: ATAPI
CD-ROM: <_NEC DVD_RW ND-3520AW>Version: 3.04 - HA 1 TA 0 - 6.6.0.12
Adapter driver: HA 1

=== Scsi-Device-Map ===
DiskPeripheral : IC35L080AVVA07-0 atapi Port 0 ID 0 DMA: On
DiskPeripheral : SAMSUNG VG36483A (6.48GB) atapi Port 0 ID 1 DMA: On
CdRomPeripheral : _NEC DVD_RW ND-3520AW atapi Port 1 ID 0 DMA: On
CdRomPeripheral : JLMS XJ-HD163 atapi Port 1 ID 1 DMA: On
DiskPeripheral : ST3160023A 3.06 hpt374 Port 2 ID 0 DMA: Off
DiskPeripheral : Maxtor 6Y120P0 YAR4 hpt374 Port 2 ID 1 DMA: Off
DiskPeripheral : ST380021A 3.19 hpt374 Port 2 ID 2 DMA: Off
DiskPeripheral : ST3250823A 3.02 hpt374 Port 2 ID 3 DMA: Off
DiskPeripheral : Maxtor 6Y120P0 YAR4 hpt374 Port 2 ID 4 DMA: Off
OtherPeripheral : HPT RCM DEVICE hpt374 Port 2 ID 0 DMA: Off
OtherPeripheral : HPT RCM DEVICE hpt374 Port 3 ID 0 DMA: Off

=== CDRom-Device-Map ===
_NEC DVD_RW ND-3520AW E: CDRom3
JLMS XJ-HD163 F: CDRom1
=======================

AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 74448896 (0) Byte
ShowDrvBufStat : 0
BUFE : 0
Physical memory : 511MB (523760kB)
Free physical memory: 223MB (228536kB)
Memory in use : 56 %
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

6.5.2005
UDF/ISO kompilering
06:01:17 #1 Phase 112 File dlgbrnst.cpp, Line 1832
DVD-Video files reallocation started

06:01:17 #2 DVDREALLOC -21 File DVDVideoCompilation.cpp, Line 1183
Required file 'VIDEO_TS.VOB' is not present

06:01:17 #3 Phase 115 File dlgbrnst.cpp, Line 1832
DVD-Video files reallocation failed


Existing drivers:
File 'Drivers\ASPI32.SYS': Ver=4.71 (0002) built by: WinDDK, size=16512 bytes, created 2002-07-17 10:05:10
File 'Drivers\PXHELP20.SYS': Ver=2.02.62a, size=20016 bytes, created 2003-10-28 12:02:00 (Prassi/Veritas driver for win 2K)
File 'Drivers\atapi.sys': Ver=5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), size=95360 bytes, created 2004-08-04 07:59:42 (Adapter driver for rec)

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

Solution:

Install the freeware program IfoEdit - and in that program press "open" and locate the VIDEO_TS.IFO file in the folder where you have your DVD files. See screenshot below:



Then press this button:

Now you'll get a decision to make. Would you like IfoEdit to correct the sectors in all IFO files in that directory, then press 'Yes'. (This is the usual use). Or if you just want to check the sectors of the current loaded IFO file, then press 'No'. I always choose the 'Yes' option.



After pressing 'Yes', IfoEdit will load every IFO file, and check the sector addresses. If one or more are wrong, IfoEdit will show you which addresses have been changed:



If no wrong sector addresses have been found, then IfoEdit does not re-save the IFO file. After that is done and you are back to the main menu - close the program and you are finished with this step.

In all instances, just to make sure IfoEdit works correctly, you should always restart IfoEdit before doing this 'Get VTS Sectors' thing if you want to do it on several folders with saved DVDs.

If you encounter that IfoEdit reports this:

There's something wrong!
The Ifo Endsector does not match the file size.

The solution to this problem is that you should do the same procedure with IfoEdit again - open up the VIDEO_TS.IFO file and press the button 'GET VTS sectors'.

[cynthia]

Message file not found

Error code:

Windows XP 5.1
IA32
WinAspi: -
ahead WinASPI: File 'C:\Program Files\Ahead\Nero\Wnaspi32.dll': Ver=2.0.1.59, size=160016 bytes, created 12/16/2003 8:18:06 PM
Nero API version: 6.3.1.15
Using interface version: 6.3.1.4
Installed in: C:\Program Files\Ahead\Nero\
Application: ahead\Nero - Burning Rom

=== Scsi-Device-Map ===
DiskPeripheral : WDC WD400BB-75CAA0 atapi Port 0 ID 0 DMA: On
CdRomPeripheral : LITEON DVD-ROM LTD163 atapi Port 1 ID 0 DMA: On
CdRomPeripheral : PLEXTOR DVDR PX-716A atapi Port 1 ID 1 DMA: On

=== CDRom-Device-Map ===
LITEON DVD-ROM LTD163 D: CDRom0
PLEXTOR DVDR PX-716A E: CDRom1
=======================

AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 40894464 (0) Byte
ShowDrvBufStat : 0
BUFE : 0
Physical memory : 254MB (260912kB)
Free physical memory: 138MB (141876kB)
Memory in use : 45 %
Uncached PFiles: 0x0
Use Static Write Speed Table: 0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

17.5.2005
NeroAPI
10:36:28 PM #1 Text 0 File NeroBurnCommon.cpp, Line 78
Message file not found


Existing drivers:

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

Solution:

Your Nero software failed to install properly or was corrupted by the installation of another software.

Use the Nero Clean tool to uninstall the software from your system: http://www.nero.com/eng/Clean_Tools.html

Then install Nero latest version. Don't use your installations disc - download the latest one here: http://www.nero.com/eng/nero-up.php

Then add your serial number after the installation.

[cynthia]

Specified host adapter invalid

Error code:

Windows XP 5.1
IA32
WinAspi: -
ahead WinASPI: File 'C:\Program Files\Ahead\Nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 10/26/2004 4:35:34 PM
Nero API version: 6.6.0.2
Using interface version: 6.0.0.0
Installed in: C:\Program Files\Ahead\Nero\
Application: ahead\Nero - Burning Rom
Recorder: Version: A105 - HA 1 TA 1 - 6.6.0.2
Adapter driver:  HA 1
Drive buffer : 1312kB
Bus Type : default (0) -> ATAPI, detected: ATAPI

=== Scsi-Device-Map ===
DiskPeripheral : WDC WD2500JB-53EVA0 atapi Port 0 ID 0 DMA: On
CdRomPeripheral : LITE-ON DVD SOHD-16P9S atapi Port 1 ID 0 DMA: On
CdRomPeripheral : HL-DT-ST DVDRAM GMA-4020B atapi Port 1 ID 1 DMA: On

=== CDRom-Device-Map ===
LITE-ON DVD SOHD-16P9S D: CDRom0
HL-DT-ST DVDRAM GMA-4020 E: CDRom1
=======================

AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 83886080 (0) Byte
ShowDrvBufStat : 0
BUFE : 0
Physical memory : 1022MB (1047340kB)
Free physical memory: 713MB (730480kB)
Memory in use : 30 %
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

13.8.2005
NeroAPI
1:09:51 AM #1 Phase 111 File APIProgress.cpp, Line 276
DVD-Video files sorted

1:09:52 AM #2 Text 0 File Reader.cpp, Line 127
Reader running

1:09:52 AM #3 Text 0 File AudioCompilationImpl.cpp, Line 842
DRM: StartDrmRecording(RealRec:1, ImageRec:0, Copies:1)
DRM: Beginning burn process.

1:09:52 AM #4 ISO9660GEN -11 File geniso.cpp, Line 3286
First writeable address = 0 (0x00000000)

1:09:52 AM #5 ISO9660GEN -11 File geniso.cpp, Line 3286
First writeable address = 0 (0x00000000)

1:09:52 AM #6 Text 0 File Burncd.cpp, Line 3117
Turn on Disc-At-Once, using DVD media

1:10:19 AM #7 Text 0 File DlgWaitCD.cpp, Line 256
Last possible write address on media: 2298495 (510:46.45, 4489MB)
Last address to be written: 2286111 (508:01.36, 4465MB)

1:10:19 AM #8 Text 0 File DlgWaitCD.cpp, Line 268
Write in overburning mode: NO

1:10:19 AM #9 Text 0 File DlgWaitCD.cpp, Line 2309
Recorder: HL-DT-ST DVDRAM GMA-4020B, Media type: DVD-R
Disc Manufacturer: CMC MA - G. AE1
Disc Application Code: 64, Disc Physical Code: 193

1:10:19 AM #10 Text 0 File DlgWaitCD.cpp, Line 430
>>> Protocol of DlgWaitCD activities: <<<
=========================================
Compilation cannot be written on that medium type.
(Medium in drive: DVD-ROM. Medium required by compilation: DVD-R/RW, DVD-RAM.)

1:10:19 AM #11 Text 0 File ThreadedTransferInterface.cpp, Line 844
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 ()
2 indices, index0 (150) not provided
original disc pos #0 + 2286112 (2286112) = #2286112/508:1.37
relocatable, disc pos for caching/writing not required/ required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2286112 blocks [HL-DT-ST DVDRAM GMA-4020B]
--------------------------------------------------------------

1:10:19 AM #12 Text 0 File ThreadedTransferInterface.cpp, Line 1047
Prepare recorder [HL-DT-ST DVDRAM GMA-4020B] for write in CUE-sheet-DAO
DAO infos:
==========
MCN: ""
TOCType: 0x00; Session Closed, disc fixated
Tracks 1 to 1:
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 4681957376, ISRC ""
DAO layout:
===========
__Start_|____Track_|_Idx_|_RecDep_|_CtrlAdr_
0 | lead-in | 0 | 0x00 | 0x41
0 | 1 | 0 | 0x00 | 0x41
0 | 1 | 1 | 0x00 | 0x41
2286112 | lead-out | 1 | 0x00 | 0x41

1:10:19 AM #13 Phase 24 File APIProgress.cpp, Line 276
Caching of files started

1:10:19 AM #14 SCSI -601 File Cdrdrv.cpp, Line 1177
SCSI Exec, HA 1, TA 1, LUN 0, buffer 0x02556000
Status: 0x81 (0x06, SCSI_INVALID_HA)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0xAD 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x08 0x04 0x00 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02

1:10:19 AM #15 Text 0 File Burncd.cpp, Line 4004
Cache writing successful.

1:10:19 AM #16 Phase 25 File APIProgress.cpp, Line 276
Caching of files completed

1:10:19 AM #17 Phase 36 File APIProgress.cpp, Line 276
Burn process started at 2x (2,770 KB/s)

1:10:19 AM #18 SCSI -601 File Cdrdrv.cpp, Line 1177
SCSI Exec, HA 1, TA 1, LUN 0, buffer 0x02556000
Status: 0x81 (0x06, SCSI_INVALID_HA)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0xAD 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x08 0x04 0x00 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02

1:10:19 AM #19 SCSI -601 File Cdrdrv.cpp, Line 1177
SCSI Exec, HA 1, TA 1, LUN 0, buffer 0x02554AE0
Status: 0x81 (0x06, SCSI_INVALID_HA)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0x5A 0x00 0x05 0x00 0x00 0x00 0x00 0x00 0x48 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02

1:10:19 AM #20 CDR -601 File ThreadedTransferInterface.cpp, Line 1583
Specified host adapter invalid
HL-DT-ST DVDRAM GMA-4020B\H1 T1

1:10:19 AM #21 Phase 38 File APIProgress.cpp, Line 276
Burn process failed at 2x (2,770 KB/s)

1:10:19 AM #22 Text 0 File AudioCompilationImpl.cpp, Line 867
DRM: DRM burn session terminated.

1:10:19 AM #23 Text 0 File AudioCompilationImpl.cpp, Line 896
DRM: Closing entire DRM handling. Bye.

1:10:19 AM #24 SCSI -601 File Cdrdrv.cpp, Line 1177
SCSI Exec, HA 1, TA 1, LUN 0
Status: 0x81 (0x06, SCSI_INVALID_HA)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02

1:10:19 AM #25 SCSI -601 File Cdrdrv.cpp, Line 1177
SCSI Exec, HA 1, TA 1, LUN 0
Status: 0x81 (0x06, SCSI_INVALID_HA)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0x1E 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02

1:10:19 AM #26 SCSI -601 File Cdrdrv.cpp, Line 1177
SCSI Exec, HA 1, TA 1, LUN 0
Status: 0x81 (0x06, SCSI_INVALID_HA)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02

1:10:19 AM #27 SCSI -601 File Cdrdrv.cpp, Line 1177
SCSI Exec, HA 1, TA 1, LUN 0
Status: 0x81 (0x06, SCSI_INVALID_HA)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0x1E 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02

1:10:19 AM #28 SCSI -601 File Cdrdrv.cpp, Line 1177
SCSI Exec, HA 1, TA 1, LUN 0
Status: 0x81 (0x06, SCSI_INVALID_HA)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02

1:10:19 AM #29 SCSI -601 File Cdrdrv.cpp, Line 1177
SCSI Exec, HA 1, TA 1, LUN 0
Status: 0x81 (0x06, SCSI_INVALID_HA)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0x1E 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02


Existing drivers:

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

Solution:

Update your Nero to the latest version.
Update the installed firmware.

Credit: bdigit