nu1mlock Posted August 31, 2007 Share Posted August 31, 2007 (edited) Hey guys! I've got a problem and I have no idea what could be wrong. Here's the deal: First of all, I was using a Pioneer 111D. A couple of weeks ago my problems began with not being able to burn DL discs sometimes. About one of three discs never made it through the burning process. I've always used Verbatim for my Xbox 360 backups. Then it got worse. When burning, ImgBurn errored out something about TOC and never got past the buffer-filling. Nothing got written to the disc but no matter how many times I re-tried that disc I always got the same error. When trying to burn the same disc on another computer it worked fine. More things started to happen - my burner recognized some +R as +DL and gave me the same error as on the DL-discs. I tried upgrade the firmware of the 111D to the latest official firmware and also the latest TDB-firmware but with no luck. I'm guessing the drive was f*cked, so I bought a new, Pioneer 112D instead. Well, now it gives me another error. This time, no matter what brand of +DL-discs I'm using I always get the same error (image below) and the same log from ImgBurn (code below). I was using Windows Vista, so I thought it could have something to do with that, so I changed back to XP SP2 but still got the same error. I've tried burning the discs from three different HDD's (all SATA2's) but still got the same error. About one of five discs get burned correctly and the backup works just fine on that disc, so I know there isn't anything wrong with the image I've got. I've tried both Verbatims and Aone/XB discs but both brands give me the very same error. Sometimes I get the errormessage after 64%, sometimes after 88%. It's always different, but still the same error. Just to clear things up: Right now, I'm using a Pioneer 112D (official firmware 1.22). This is the specifications of my computer if it helps: AMD Athlon 64 5600+ X2, 2GB DDR2 800MHz Kingston ValueRam, 2x160GB, 1x320GB, 1x500GB (all SATA2), Pioneer 112D with latest official firmware (1.22). I've lost 10 discs the latest 24h, so I'd prefer if I wouldn't waste too many more just to "try this and that" unless I really need to. I'd rather gather as much information and alternatives before re-trying to burn on my Verb's right now. I 07:55:09 Operation Started! I 07:55:09 Source File: G:\GAMES\NBASTREETHOMECOURT\dnl-nsh.dvd I 07:55:09 Source File Sectors: 3 697 696 (MODE1/2048) I 07:55:09 Source File Size: 7 572 881 408 bytes I 07:55:09 Source File Volume Identifier: XBOX360 I 07:55:09 Source File Implementation Identifier: Daikin U.S. Comtec Lab I 07:55:09 Source File File System(s): ISO9660; UDF (1.02) I 07:55:09 Destination Device: [0:0:0] PIONEER DVD-RW DVR-112D 1.22 (E:) (ATA) I 07:55:09 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D01-67) (Speeds: 2,4x; 4x; 6x; 8x) I 07:55:09 Destination Media Sectors: 4 173 824 I 07:55:09 Write Mode: DVD I 07:55:09 Write Type: DAO I 07:55:09 Write Speed: 8x I 07:55:09 Link Size: Auto I 07:55:09 Test Mode: No I 07:55:09 BURN-Proof: Enabled W 07:55:16 DeviceIoControl(FSCTL_LOCK_VOLUME) Failed! - Reason: Åtkomst nekad. W 07:55:16 DeviceIoControl(FSCTL_DISMOUNT_VOLUME) Failed! - Reason: Åtkomst nekad. I 07:55:16 User Specified L0 Data Zone Capacity: 1 913 760 I 07:55:44 Filling Buffer... (40 MB) I 07:55:45 Writing LeadIn... I 07:55:46 Writing Image... (LBA: 0 - 3697695) I 07:55:46 Writing Layer 0... (LBA: 0 - 1913759) I 08:03:03 Writing Layer 1... (LBA: 1913760 - 3697695) W 08:06:55 Failed to Write Sectors 2573856 - 2573887 - Write Error W 08:06:55 Retrying (1 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (2 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (3 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (4 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (5 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (6 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (7 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (8 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (9 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (10 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (11 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (12 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (13 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (14 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (15 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (16 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (17 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (18 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (19 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (20 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write E 08:20:00 Failed to Write Sectors 2573856 - 2573887 - Write Error I 08:20:00 Synchronising Cache... I 08:20:01 Closing Track... I 08:20:12 Finalising Disc... W 08:20:50 Potential 'WaitImmediateIO' Deferred Error - (1/2) - Session Fixation Error E 08:23:12 Finalise Disc Failed! - Reason: Session Fixation Error I 08:23:12 Finalising Disc (Last Attempt!)... E 08:23:45 Finalise Disc Failed! - Reason: Session Fixation Error E 08:23:45 Failed to Write Image! E 08:23:45 Operation Failed! - Duration: 00:28:36 Thanks alot! nu1mlock Edited August 31, 2007 by nu1mlock Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted August 31, 2007 Share Posted August 31, 2007 If you can't burn Verbs at 2.4x without getting the error, either the drive is still screwed or the media you've got is faulty. It shouldn't be *that* hard to get a working burn. Link to comment Share on other sites More sharing options...
dontasciime Posted August 31, 2007 Share Posted August 31, 2007 check the other software you have installed. Post the filter driver load order from tools menu Link to comment Share on other sites More sharing options...
nu1mlock Posted August 31, 2007 Author Share Posted August 31, 2007 If you can't burn Verbs at 2.4x without getting the error, either the drive is still screwed or the media you've got is faulty. It shouldn't be *that* hard to get a working burn. A firmware bug for both 111D and 112D makes it that 6-8x gives a much higher quality of the disc than burning at 2,4x. This is the second batch and second brand I've tried with the new Pioneer 112D. check the other software you have installed. Post the filter driver load order from tools menu I've tried burning just after installing either Windows Vista and Windows XP but this still gives me the error. Here's the filter driver load order: =============================================== Filter Driver Load Order - ImgBurn v2.3.2.0 =============================================== Upper Device Filter: redbook Upper Class Filter: [None Found] Device: CD/DVD-ROM Device Lower Class Filter: [None Found] Lower Device Filter: imapi Filter Name: redbook File Name: C:\WINDOWS\system32\DRIVERS\redbook.sys File Version: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) File Description: Drivrutin för Redbook-ljudfilter Product Name: Operativsystemet Microsoft® Windows® Product Version: 5.1.2600.2180 Company Name: Microsoft Corporation Copyright: © Microsoft Corporation. Med ensamrätt. Filter Name: imapi File Name: C:\WINDOWS\system32\DRIVERS\imapi.sys File Version: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) File Description: IMAPI Kernel Driver Product Name: Microsoft® Windows® Operating System Product Version: 5.1.2600.2180 Company Name: Microsoft Corporation Copyright: © Microsoft Corporation. All rights reserved. Thanks! nu1mlock Link to comment Share on other sites More sharing options...
dontasciime Posted September 1, 2007 Share Posted September 1, 2007 Try just sticking to 2.4x I have burnt over 100 verb DL+ at those speeds and each one scans at 96% or higher burnt using the 111D drive not opened my 112 yet as I cannot remember where I have put it. The other discs's you have are not worth bothering with I'm afraid. Link to comment Share on other sites More sharing options...
volvofl10 Posted September 1, 2007 Share Posted September 1, 2007 W 07:55:16 DeviceIoControl(FSCTL_LOCK_VOLUME) Failed! - Reason: Åtkomst nekad. translate the bold part for us please ? Link to comment Share on other sites More sharing options...
nu1mlock Posted September 1, 2007 Author Share Posted September 1, 2007 (edited) Try just sticking to 2.4x I have burnt over 100 verb DL+ at those speeds and each one scans at 96% or higher burnt using the 111D drive not opened my 112 yet as I cannot remember where I have put it. The other discs's you have are not worth bothering with I'm afraid. Yeah, I've burned a lot of Verbs at 2,4x too, but over 200 Verbatim +DL at 8x with only 2 of them not working (yes, I've counted), not counting those that woudln't burn the last day or two. I still get the same error when burning at 2.4x speed. W 07:55:16 DeviceIoControl(FSCTL_LOCK_VOLUME) Failed! - Reason: Åtkomst nekad. translate the bold part for us please ? Åtkomst nekad means "Access Denied". I belive that only means that ImgBurn can't lock the drive before burning. It doesn't happen all the time though. I get the other errors even without the Access Denied-error. Edited September 1, 2007 by nu1mlock Link to comment Share on other sites More sharing options...
cornholio7 Posted September 1, 2007 Share Posted September 1, 2007 check the faq about that http://forum.imgburn.com/index.php?s=&...dpost&p=975 Link to comment Share on other sites More sharing options...
nu1mlock Posted September 1, 2007 Author Share Posted September 1, 2007 check the faq about that http://forum.imgburn.com/index.php?s=&...dpost&p=975 Yeah, well I don't need a solution for that - I already know what it is. My problem is that I can't burn any DL discs. The "Access Denied-problem" doesn't happen all the time. nu1mlock Link to comment Share on other sites More sharing options...
chewy Posted September 1, 2007 Share Posted September 1, 2007 you've changed os's, changed drives, changed media have you checked the cable and/or the power supply? tested memory? Link to comment Share on other sites More sharing options...
nu1mlock Posted September 1, 2007 Author Share Posted September 1, 2007 you've changed os's, changed drives, changed media have you checked the cable and/or the power supply? tested memory? Yes, I've changed OS's, changed drives and changed media. I tested the memory last night with Memtest (both the original Memtest and then Memtest+) from a USB-stick. I let it run three loops but it couldn't find any errors. Yes, the cable is alright, I even changed it to another cable. The drive is set to Master and with no other IDE-drives on the same cable (I don't have any IDE's at all). The power supply works as it should with the correct voltage and such. nu1mlock Link to comment Share on other sites More sharing options...
chewy Posted September 1, 2007 Share Posted September 1, 2007 The power supply works as it should with the correct voltage and such. details please, I have seen more problems with power supplies and dvd burning that are hard to track down http://forums.extremeoverclocking.com/t137886.html best site I have ever found for this stuff Link to comment Share on other sites More sharing options...
nu1mlock Posted September 2, 2007 Author Share Posted September 2, 2007 I'm sorry, but I can't check the voltage with any tool, since I don't have one of those. Strangest thing happened yesterday. Well, since ImgBurn wouldn't burn my backups, I tried CloneCD. So far I have burned five working discs with CloneCD without any errors. I think it's strange that CloneCD do work when ImgBurn doesn't, don't you? nu1mlock Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted September 2, 2007 Share Posted September 2, 2007 See if changing the write type in the setting to incremental helps. Or change the I/O Interface to Elby. Link to comment Share on other sites More sharing options...
Recommended Posts