Key_medium_error

Hi , i have problem to burn cd with Nero , in fact to be able to burn a cd i have to reboot and Don’t open any apllication , if i open just 1 or 2 Nero i have a buffer underrun , i have installed latest Nero update , i have a Athlon 1.4 , 40 Gb 256 DDR ram
when i try to understand with the Nero log error i see KEY_MEDIUM_ERROR just before the buffer underrun , what is that ?
this is the log below
Thank’s
azerty

1502-3120-0137-0581-0083-9350

Windows XP 5.1
IA32
WinAspi: File ‘Wnaspi32.dll’: Ver=4.60 (1021), size=45056 bytes, created 10/09/1999 12:06:00
ahead WinASPI: File ‘C:\Program Files\ahead\Nero\Wnaspi32.dll’: Ver=2.0.1.50, size=131072 bytes, created 25/06/2002 16:34:54
Nero Version: 5.5.10.0
Recorder: <IOMEGA ZIPCD 650 USB> Version: I1.1 - HA 2 TA 0 - 5.5.10.0
Adapter driver: <> HA 2
Drive buffer : 2048kB
Bus Type : default (0) -> ATAPI, detected: ?
CD-ROM: <SAMSUNG DVD-ROM SD-616F>Version: F101 - HA 1 TA 0 - 5.5.10.0
Adapter driver: <atapi> HA 1
Bus Type : default (0) -> ATAPI, detected: ATAPI

=== Scsi-Device-Map ===
DiskPeripheral : ST340810A atapi Port 0 ID 0 DMA: On
CdRomPeripheral : SAMSUNG DVD-ROM SD-616F atapi Port 1 ID 0 DMA: On
CdRomPeripheral : CyberDrv CW038D CD-R/RW atapi Port 1 ID 1 DMA: On

AutoRun : 1
Excluded drive IDs:
CmdQueuing : 1
CmdNotification: 2
WriteBufferSize: 83886080 (83886080) Byte
ShowDrvBufStat : 0
EraseSpeed : 0
BUFE : 0
Physical memory : 255MB (261616kB)
Free physical memory: 35MB (36520kB)
Memory in use : 86 %
Uncached PFiles: 0x0
Use Static Write Speed Table: 0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Enabled (1)
Wizard: Off

26.1.2003
CD-ROM (ISO)
05:11:54 #1 Text 0 File Isodoc.cpp, Line 7328
Iso document burn settings

Determine maximum speed : FALSE
Simulate : FALSE
Write : TRUE
Finalize CD : FALSE
Multisession : TRUE
Multisession type: : Start multisession
Burning mode : TAO
Mode : 1
ISO Level : 1 (Max. of 11 = 8 + 3 char)
Character set : ISO 9660
Joliet : TRUE
Allow pathdepth more than 8 directories : TRUE
Allow more than 255 characters in path : TRUE
Write ISO9660 ;1 file extensions : TRUE

05:11:54 #2 Text 0 File Reader.cpp, Line 115
Reader running

05:11:54 #3 Text 0 File Writer.cpp, Line 123
Writer IOMEGA ZIPCD 650 USB running

05:11:54 #4 ISO9660GEN -11 File geniso.cpp, Line 4519
First writeable address = 0 (0x00000000)

05:11:54 #5 Text 0 File Burncd.cpp, Line 3790
Turn on Track-At-Once, using CD-R/RW media

05:11:54 #6 Text 0 File ThreadedTransferInterface.cpp, Line 659
Setup items (original item values)
0: TRM_DATA_MODE1 (CTransferItem)
2 indices, index0 (150) not provided
original CD pos #0 + 46672 (46672) = #46672/10:22.22
relocatable, CD pos for caching/writing not required/required, no patch infos

05:11:55 #7 Text 0 File DlgWaitCD.cpp, Line 202
Last possible write address on media: 335974 (74:41.49)
Last address to be written: 46671 (10:24.21)

05:11:55 #8 Text 0 File DlgWaitCD.cpp, Line 207
Write in overburning mode: FALSE

05:11:55 #9 Text 0 File DlgWaitCD.cpp, Line 1419
Recorder: IOMEGA ZIPCD 650 USB;
CDRW code: 00 97 22 60; OSJ entry from: Daxon Technology, Inc.
ATIP Data:
Special Info [hex] 1: D1 00 C6, 2: 61 16 3C (LI 97:22.60), 3: 4A 29 32 (LO 74:41.50)
Additional Info [hex] 1: 02 3A A0, 2: 5A A6 14, 3: 00 00 00 (invalid)

05:11:56 #10 Text 0 File ThreadedTransferInterface.cpp, Line 811
Prepare recorder IOMEGA ZIPCD 650 USB for write in TAO
DAO infos:

MCN:
TOCTYPE: 0x0 Session Closed, CD not fixated
Tracks 1 to 1:
TRM_DATA_MODE1, 2048/0x0, ISRC “”, FilePos 0 307200 95891456

05:11:56 #11 Text 0 File ThreadedTransferInterface.cpp, Line 839
Removed 2 run-out blocks from end of track 1.

05:11:56 #12 Text 0 File ThreadedTransferInterface.cpp, Line 659
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 (CTransferItem)
2 indices, index0 (150) not provided
original CD pos #0 + 46672 (46672) = #46672/10:22.22
relocatable, CD pos for caching/writing not required/required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 46670 blocks [IOMEGA ZIPCD 650 USB ]

05:11:56 #13 Phase 36 File dlgbrnst.cpp, Line 1649
Burn process started at 4x (600 KB/s)

05:11:56 #14 Text 0 File ThreadedTransferInterface.cpp, Line 1952
Verifying CD position of item 0 (relocatable, CD pos, no patch infos, orig at #0): write at #0

05:12:34 #15 SCSI -1013 File Cdrdrv.cpp, Line 1393
SCSI Exec, HA 2, TA 0, LUN 0, buffer 0x02620000
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: 0x09
CDB Data: 0x2A 0x00 0x00 0x00 0x1B 0x3F 0x00 0x00 0x1F 0x00 0x00 0x00
Sense Data: 0x71 0x00 0x03 0x00 0x00 0x00 0x00 0x13
0x00 0x00 0x00 0x00 0x0C 0x09

05:12:34 #16 MMC -1013 File Writer.cpp, Line 331
Buffer underrun

05:12:34 #17 Text 0 File ThreadedTransfer.cpp, Line 219
all writers idle, stopping conversion

05:12:40 #18 CDR -201 File WriterStatus.cpp, Line 194
Invalid write state

05:12:40 #19 TRANSFER -18 File WriterStatus.cpp, Line 194
Could not perform EndTrack

05:12:40 #20 Text 0 File Mmc.cpp, Line 12011
<IOMEGA ZIPCD 650 USB > start Close Session

05:14:01 #21 Phase 38 File dlgbrnst.cpp, Line 1649
Burn process failed at 4x (600 KB/s)

05:14:01 #22 Text 0 File Scsicmd.cpp, Line 406
SCSI not using temporary buffers
20 out of 20 temporary buffers allocated

Existing drivers:
File ‘Drivers\CDRALW2K.SYS’: Ver=5.1.1.210, size=23721 bytes, created 31/03/2002 00:49:18
File ‘Drivers\ASPI32.SYS’: Ver=4.60 (1021), size=25244 bytes, created 10/09/1999 12:06:00
File ‘Drivers\atapi.sys’: Ver=5.1.2600.1106 (xpsp1.020828-1920), size=86912 bytes, created 29/08/2002 09:27:50 (Adapter driver for src)

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

if that’s a via chipset on your motherboard you may try installing the latest via 4in1 busmaster drivers. according to the log dma is enabled for your burner so that shouldn’t be the problem.

Hi netman , i just do what you said and still same problem … i have the new log if you want .
Thanks anyway

According to your log, it says that there is 35MB of free RAM. That MAY be why.

Its also possible that there are a lot of programs running in the background. Check your system tray (group of icons in lower right) for unnecessary programs, exit them then try to burn.

Also you seem to have a USB burner IOMEGA ZIPCD 650 USB, USB has a fairly slow transfer rate (USB 2 has a very good transfer rate compared to USB1), but since your burning at 4X that shouldnt be a problem.

Hope this helps.

yes he say that But at the moment i burn this cd i have only 2 application opened ( to make Nero work i have to reboot and close All application ) , i have checked with control task manager only 10 % of my CPU was in use when i tried to burn this cd , in fact it’s like Nero “think” he don’t have enough free memory while i have enough free memory . maybe if we understand why Nero think i only have 35 Mb free on my Ram when this is not true we can understand what is the problem…
about Iomega cd burner i use a external to test because i first have this problem with my intenal cd burner and both have same problem .
what can make Nero think i only have 35 Mb free on Ram when this is not the case acording to my task manager ??? ( i only have this problem since 2 week , i used Nero since a while with this PC before )

What about virtual memory? If you dont have much space on the hard drive partition where Windows is installed (usually C Drive) then sometimes that can make a difference.
When you go to task manager, go to the performance tab and see what the PFUsage graph is at.

Also the fragmentation of the hard drive may cause problems. Do you use disk defragmenter?
(Start->Programs->Accessories->System Tools->Disk Defragmenter)
If youve a large hard drive, and it needs de-fragmenting, then it may take a while.

Also are you burning from hard drive to burner or DVD-Drive to burner? (On-The-Fly) If your doing it on-the-fly, try imaging it to the hard drive first.

But first off, lets do some troubleshooting. You said that it didnt happen util 2 weeks ago. What did you do 2 weeks ago that could have caused it? Did you install a huge mess of programs? If so then that could cause fragmentation. (RE:top of second part of current post)

i think i remember reading somewhere that KEY_MEDIUM_ERROR could mean that the type of media u’re using is incompatible somehow w/ the drive, but i don’t remember the specifics about it. i also seem to remember that flashing the drive to its latest firmware solved the problem. maybe u should try this if u haven’t done so. also, have u tried different types/brands of cds?

Originally posted by Savannah
[B]What about virtual memory? If you dont have much space on the hard drive partition where Windows is installed (usually C Drive) then sometimes that can make a difference.
When you go to task manager, go to the performance tab and see what the PFUsage graph is at.

Also the fragmentation of the hard drive may cause problems. Do you use disk defragmenter?
(Start->Programs->Accessories->System Tools->Disk Defragmenter)
If youve a large hard drive, and it needs de-fragmenting, then it may take a while.

Also are you burning from hard drive to burner or DVD-Drive to burner? (On-The-Fly) If your doing it on-the-fly, try imaging it to the hard drive first.

But first off, lets do some troubleshooting. You said that it didnt happen util 2 weeks ago. What did you do 2 weeks ago that could have caused it? Did you install a huge mess of programs? If so then that could cause fragmentation. (RE:top of second part of current post) [/B]

Hi Savanah , about virtual memory i have set it to the maximum few months ago already , about defragmentation i have my PC since just 1 year so i don’t think it’s already time for that ( it’s a 40 Gb )
no i don’t try to burn “on the fly” i tried t burn a 200 Mb file who are in my hard drive .
the program i installed 2 weeks ago was removed just in case ( it was daemon toll and isobuster )
also i think i had a brutal reboot ( my pc was too busy and cannot reboot , i made a manual reboot ) maybe this caused a damage ?
Thank’s

Originally posted by AZImmortal
i think i remember reading somewhere that KEY_MEDIUM_ERROR could mean that the type of media u’re using is incompatible somehow w/ the drive, but i don’t remember the specifics about it. i also seem to remember that flashing the drive to its latest firmware solved the problem. maybe u should try this if u haven’t done so. also, have u tried different types/brands of cds?

yes i tried 2 different labelled cd .

I dont think a manual reset would cause problems like this as Ive had to do that when me and a mate were stuffing around with Remote Assistance. Winamp caused my PC to crawl with RA going!

I did a quick google search and came up with this link.
http://docs.sun.com/db/doc/802-5747-9S/6i9g26k64?a=view
In there, is states ‘KEY_MEDIUM_ERROR Indicates that the command terminated with a non-recovered error condition that was probably caused by a flaw on the medium or an error in the recorded data.’

Also from Neros website
http://www.nero.com/en/content/helptool/249.htm it reccomends a firmware update.

AZImmortal - Seems you were spot on with the firmware suggestion :wink:

So hopefully this helps.

Originally posted by Savannah
[B]I dont think a manual reset would cause problems like this as Ive had to do that when me and a mate were stuffing around with Remote Assistance. Winamp caused my PC to crawl with RA going!

I did a quick google search and came up with this link.
http://docs.sun.com/db/doc/802-5747-9S/6i9g26k64?a=view
In there, is states ‘KEY_MEDIUM_ERROR Indicates that the command terminated with a non-recovered error condition that was probably caused by a flaw on the medium or an error in the recorded data.’

Also from Neros website
http://www.nero.com/en/content/helptool/249.htm it reccomends a firmware update.

AZImmortal - Seems you were spot on with the firmware suggestion :wink:

So hopefully this helps. [/B]

i don’t think it’s a medium problem because i tried with 2 different label CD .
about updating firmware as problem is the same with my internal cd burner and with my external cd burner so do you think he can be a firmware update problem ? ( i ask that because i don’t really know something about that i just read that he can be “dangerous” to do this kind of update )
Thank’s

thanx for doing the research Savannah ;). i knew i remembered reading about the same problem at some other time and that the problem was solved by flashing to the newest firmware, but i had no sources to back me up or confirm.

about whether flashing is dangerous or not, the potential is there to permanently disable ur drive, but this only happens when the drive is incompletely flashed or the firmware u’re trying to flash with is corrupt somehow. both are fairly unlikely to happen, and seeing as how u seem to be unable to burn cds with ur burner anyhow, the drive is already figuratively “dead” in its abilities to perform, so i’d assume u would buy a new burner anyway if u can’t get working ;).

Originally posted by AZImmortal
[B]thanx for doing the research Savannah ;). i knew i remembered reading about the same problem at some other time and that the problem was solved by flashing to the newest firmware, but i had no sources to back me up or confirm.

about whether flashing is dangerous or not, the potential is there to permanently disable ur drive, but this only happens when the drive is incompletely flashed or the firmware u’re trying to flash with is corrupt somehow. both are fairly unlikely to happen, and seeing as how u seem to be unable to burn cds with ur burner anyhow, the drive is already figuratively “dead” in its abilities to perform, so i’d assume u would buy a new burner anyway if u can’t get working ;). [/B]

ok i just try to do it but when i try i have a message who say " this application cannot be executed"
this is the link where i find the .exe update http://www.cyberdrive.de/en/download.php?op=viewdownload&cid=3
and this is the model of my cd burner CD-RW CW038D
i find 2 files inside the zip folder , one is for execute into a folder and the second under DOS as i don’t know how to execute a file under DOS i tried the other one .
btw doing that is normaly a update of my firmware of the driver not flashing the Bios of my PC ? i ask that because the name of the 2 file sound like a Bios update :
Dos Update - BIOS120c.exe
Windows Update - Wbios120c.exe

there’s instructions on that website link that u just gave:
Unzip the files into a folder and execute the WBIOS120C.exe file under Windows OS or execute the BIOS120C.exe file under DOS. Follow the on-screen instructions.
so u can just use the windows one if u don’t know how to use dos.

also, u said:

btw doing that is normaly a update of my firmware of the driver not flashing the Bios of my PC ? i ask that because the name of the 2 file sound like a Bios update

i’ll assume that by “driver” u mean ur cd-rw drive and by “Bios of my PC” u mean the bios of ur motherboard, in which case yes, it will update the firmware of ur drive, not the bios of ur motherboard. i’m not sure why they decided to put “bios” into the firmware names.

Well I suppose they did that because a motherboard BIOS ‘tells’ the motherboard and addons how to work, sort of,
and a firmware ‘tells’ the burner how to work as well.

Only a remote possibility.
Or it might all just be hot air. :confused:

i think they need a new english translator at cyberdrive :bigsmile:.

lol, that to. :smiley:

Just a thought after reading all of this,

“dima” should be made aware of the Nero v5.5.10.0 bug (has problem in CD identification and other software bugs) which yield different problems with hardware (CD-RW hardware, blank CD brands and PC systems)

Also, does “dima” have AntiVirus software running (TSR) which should be disabled while burning. They (Nero) suggested that this was not necessary anymore, or is it?
:slight_smile: :eek:

Originally posted by AZImmortal
there’s instructions on that website link that u just gave:
Unzip the files into a folder and execute the WBIOS120C.exe file under Windows OS or execute the BIOS120C.exe file under DOS. Follow the on-screen instructions.
so u can just use the windows one if u don’t know how to use dos.

Hi , that’s what i tried but as i said i had a message who said "this application cannot be executed " .

Originally posted by pcbugfixer
[B]Just a thought after reading all of this,

“dima” should be made aware of the Nero v5.5.10.0 bug (has problem in CD identification and other software bugs) which yield different problems with hardware (CD-RW hardware, blank CD brands and PC systems)

Also, does “dima” have AntiVirus software running (TSR) which should be disabled while burning. They (Nero) suggested that this was not necessary anymore, or is it?
:slight_smile: :eek: [/B]

Hi , i think it’s not only a Nero problem because i also try with Easy CD Creator and i also have a buffer problem
i have a new motherboad ( a Gigabyte ) since 1 month and problem begin since 2 week , you think this can be the origin of the problem ? ( first 2 weeks with my new motherboard i burned CD without any problem )
Thank’s