drviruz Posted April 8, 2010 Share Posted April 8, 2010 Hey guys, first time poster but long time user. This error has only started occuring since I installed the new version. Now its all fine until the end of the burn where the deferred error gives me 3 options: Cancel, Try again or Continue. Try again just repeats the error over and over. Continue causes a Coaster. Weirdly, Cancel causes ImgBurn to do one last attempt which works and the disc comes out perfect. I have AnyDVD (which is disabled) and Daemon Tools' STPD driver installed. I've looked around the forum for other errors that match the dialogue but the solutions given don't work. My Liteon drive's firmware is the most modern I can find on the Liteon site. The disks are MKM-003-00 Verbs (which you say can burn fine at 8x). All and all I'm out of options and Have no idea why this suddenly happens with the update. Cheers, DrV Log: I 13:42:44 ImgBurn Version 2.5.1.0 started! I 13:42:44 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 13:42:44 Total Physical Memory: 4,193,464 KB - Available: 2,212,704 KB W 13:42:44 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! W 13:42:44 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 13:42:44 Initialising SPTI... I 13:42:44 Searching for SCSI / ATAPI devices... I 13:42:45 -> Drive 1 - Info: LITE-ON DVDRW LH-20A1S 9L09 (F:) (SATA) I 13:42:45 -> Drive 2 - Info: EXGTE IB8DEFWL 1.03 (H:) (SCSI) I 13:42:45 -> Drive 3 - Info: EXGTE IB8DEFWL 1.03 (I:) (SCSI) I 13:42:45 Found 1 DVD±RW/RAM and 2 BD-ROM/HD DVD-ROMs! I 13:52:46 Operation Started! I 13:52:46 Source File: D:\sp-ua2.dvd I 13:52:46 Source File Sectors: 3,827,488 (MODE1/2048) I 13:52:46 Source File Size: 7,838,695,424 bytes I 13:52:46 Source File Volume Identifier: DVD_ROM I 13:52:46 Source File Volume Set Identifier: 356fc000MS UDFBridge I 13:52:46 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM) I 13:52:46 Source File Implementation Identifier: Microsoft CDIMAGE UDF I 13:52:46 Source File File System(s): ISO9660, UDF (1.50) I 13:52:46 Destination Device: [6:0:0] LITE-ON DVDRW LH-20A1S 9L09 (F:) (SATA) I 13:52:46 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) (Speeds: 2.4x, 4x, 6x, 8x) I 13:52:46 Destination Media Sectors: 4,173,824 I 13:52:46 Write Mode: DVD I 13:52:46 Write Type: DAO I 13:52:46 Write Speed: 4x I 13:52:46 Link Size: Auto I 13:52:46 Lock Volume: Yes I 13:52:46 Test Mode: No I 13:52:46 OPC: No I 13:52:46 BURN-Proof: Enabled I 13:52:46 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x) I 13:52:46 Book Type Setting: DVD-ROM I 13:52:46 Advanced Settings - Force HT: No, Online HT: Yes, OverSpeed: No, SmartBurn: Yes I 13:52:46 Optimal L0 Data Zone Capacity: 1,913,760 I 13:52:46 Optimal L0 Data Zone Method: Copied From Original Disc I 13:54:00 Set L0 Data Zone Capacity Succeeded! I 13:54:00 Filling Buffer... (40 MB) I 13:54:00 Writing LeadIn... I 13:54:04 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487) I 13:54:04 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487) I 13:54:04 Writing Layer 0... (LBA: 0 - 1913759) I 14:05:52 Writing Layer 1... (LBA: 1913760 - 3827487) I 14:17:43 Synchronising Cache... I 14:17:51 Closing Track... I 14:17:59 Finalising Disc... W 14:29:08 Potential 'WaitImmediateIO' Deferred Error - (0%, 0/3) - Session Fixation Error Writing Lead In W 14:29:08 Finalise Disc Failed! - Reason: Session Fixation Error Writing Lead In W 14:29:08 Retrying (1 of 3)... W 14:29:47 Potential 'WaitImmediateIO' Deferred Error - (0%, 0/3) - Session Fixation Error Writing Lead In W 14:29:47 Retry Failed - Reason: Session Fixation Error Writing Lead In W 14:29:47 Retrying (2 of 3)... W 14:46:55 Potential 'WaitImmediateIO' Deferred Error - (0%, 0/3) - Session Fixation Error Writing Lead In W 14:46:55 Retry Failed - Reason: Session Fixation Error Writing Lead In W 14:46:55 Retrying (3 of 3)... W 14:48:08 Potential 'WaitImmediateIO' Deferred Error - (0%, 0/3) - Session Fixation Error Writing Lead In W 14:48:08 Retry Failed - Reason: Session Fixation Error Writing Lead In W 16:20:23 Retrying (4)... W 16:21:29 Potential 'WaitImmediateIO' Deferred Error - (0%, 0/3) - Session Fixation Error Writing Lead In W 16:21:30 Retry Failed - Reason: Session Fixation Error Writing Lead In W 16:21:32 Retrying (5)... W 16:23:53 Potential 'WaitImmediateIO' Deferred Error - (0%, 0/3) - Session Fixation Error Writing Lead In W 16:23:53 Retry Failed - Reason: Session Fixation Error Writing Lead In E 16:23:57 Finalise Disc Failed! - Reason: Session Fixation Error Writing Lead In I 16:23:57 Finalising Disc (Last Attempt!)... I 16:24:40 Exporting Graph Data... I 16:24:40 Graph Data File: C:\LITE-ON_DVDRW_LH-20A1S_9L09_08-APRIL-2010_13-52_MKM-003-00_4x.ibg I 16:24:40 Export Successfully Completed! I 16:24:40 Operation Successfully Completed! - Duration: 02:31:53 I 16:24:40 Average Write Rate: 5,398 KB/s (3.9x) - Maximum Write Rate: 5,631 KB/s (4.1x) Link to comment Share on other sites More sharing options...
mmalves Posted April 8, 2010 Share Posted April 8, 2010 Try burning at 6x or 8x. Also try a lens cleaning disc on your burner. Link to comment Share on other sites More sharing options...
drviruz Posted April 8, 2010 Author Share Posted April 8, 2010 Try burning at 6x or 8x. Also try a lens cleaning disc on your burner. That one was burned at 4x, I've tried 6x and 2x. It's just odd that the error is fixed by pressing cancel at the end. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted April 8, 2010 Share Posted April 8, 2010 Pressing cancel only issues the exact same command again but it does so without setting the 'immediate' bit in the command descriptor - so rather than sending the command and 'polling' the drive to see when it's done (hence the 'WaitImmediateIO' bit in the log), you send the command and it only returns control to the program when it's totally finished (successful or not). One working and the other not is totally down the drive (and its firmware), I have no control over how well it performs (or doesn't). Link to comment Share on other sites More sharing options...
drviruz Posted April 8, 2010 Author Share Posted April 8, 2010 Pressing cancel only issues the exact same command again but it does so without setting the 'immediate' bit in the command descriptor - so rather than sending the command and 'polling' the drive to see when it's done (hence the 'WaitImmediateIO' bit in the log), you send the command and it only returns control to the program when it's totally finished (successful or not). One working and the other not is totally down the drive (and its firmware), I have no control over how well it performs (or doesn't). Ah ok; just a bit odd it only happens in the new version. I'll try swapping the SATA port or checking the chipset drivers. It could be coincidental it happened during the new version and possibly the hardware/motherboard change I recently did. Cheers for the help though! Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted April 8, 2010 Share Posted April 8, 2010 The code didn't change between versions, it was fine in 2.5.0.0 so there was no reason to change it. Link to comment Share on other sites More sharing options...
drviruz Posted April 8, 2010 Author Share Posted April 8, 2010 The code didn't change between versions, it was fine in 2.5.0.0 so there was no reason to change it. Ah perfect, so that means it's something I've changed! Thanks, least I can rule out the software and look elsewhere. Don't suppose you have any idea what could cause this? Cheers again! Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted April 8, 2010 Share Posted April 8, 2010 Well in theory, it's nothing to do with anything you've done. Your drive/firmware is in complete control of the burn (and burn quality) on your chosen media. If you're running into problems then the issue lies somewhere between those three (drive/firmware/media). You know... maybe the drive needs a clean, maybe the laser/lens isn't quite what it used to be (get worse with age/usage), maybe the discs aren't quite what the firmware is expecting for MKM-003-00 (they can vary depending on where in the world they're sourced from). Link to comment Share on other sites More sharing options...
drviruz Posted April 9, 2010 Author Share Posted April 9, 2010 Update: Apperantly this motherboard used AHCI mode for IDE/SATA by default. Turning AHCI off (back to normal IDE mode) seemed to fix this error. I only noticed this as I was going to reflash my liteon drive and noticed the flash tool didn't detect it. Link to comment Share on other sites More sharing options...
Recommended Posts