Jump to content

Recommended Posts

Posted

Hey everyone i was trying to burn a game and it kept giving me this error that it could finalise disc because session fixation error writing lead out. I was wondering what the problem could be its done this months ago but not recently. Heres a log:

 

 

 

 

 

I 20:22:42 ImgBurn Version 2.5.5.0 started!

I 20:22:42 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)

I 20:22:42 Total Physical Memory: 3,010,536 KB - Available: 1,524,328 KB

I 20:22:42 Initialising SPTI...

I 20:22:42 Searching for SCSI / ATAPI devices...

I 20:22:42 -> Drive 1 - Info: TSSTcorp CDDVDW TS-L633C TF20 (D:) (ATAPI)

I 20:22:42 Found 1 DVD±RW!

I 20:24:15 Operation Started!

I 20:24:15 Source File: C:\Users\J ROC\Desktop\NHL_12_XBOX360-iCON\icon-nhl12-x360.dvd

I 20:24:15 Source File Sectors: 3,827,488 (MODE1/2048)

I 20:24:15 Source File Size: 7,838,695,424 bytes

I 20:24:15 Source File Volume Identifier: DVD_ROM

I 20:24:15 Source File Volume Set Identifier: d68a0000MS UDFBridge

I 20:24:15 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)

I 20:24:15 Source File Implementation Identifier: Microsoft CDIMAGE UDF

I 20:24:15 Source File File System(s): ISO9660, UDF (1.50)

I 20:24:15 Destination Device: [0:1:0] TSSTcorp CDDVDW TS-L633C TF20 (D:) (ATAPI)

I 20:24:15 Destination Media Type: DVD+R DL (Disc ID: MBIPG101-R10-65) (Speeds: 3x, 4x, 6x)

I 20:24:15 Destination Media Sectors: 4,173,824

I 20:24:15 Write Mode: DVD

I 20:24:15 Write Type: DAO

I 20:24:15 Write Speed: 2x

I 20:24:15 Link Size: Auto

I 20:24:15 Lock Volume: Yes

I 20:24:15 Test Mode: No

I 20:24:15 OPC: No

I 20:24:15 BURN-Proof: Enabled

W 20:24:15 Write Speed Miscompare! - Wanted: 2,770 KB/s (2x), Got: 4,155 KB/s (3x)

I 20:24:15 Book Type Setting: DVD-ROM

I 20:24:15 User Specified L0 Data Zone Capacity: 1,913,760

I 20:24:50 Set L0 Data Zone Capacity Succeeded!

I 20:24:51 Filling Buffer... (40 MB)

I 20:24:52 Writing LeadIn...

I 20:25:20 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487)

I 20:25:20 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487)

I 20:25:20 Writing Layer 0... (LBA: 0 - 1913759)

I 20:40:59 Writing Layer 1... (LBA: 1913760 - 3827487)

I 20:57:12 Synchronising Cache...

I 20:58:03 Closing Track...

I 20:58:53 Finalising Disc...

W 21:00:56 Potential 'WaitImmediateIO' Deferred Error - (99%, 0/3) - Session Fixation Error Writing Lead Out

W 21:00:56 Finalise Disc Failed! - Reason: Session Fixation Error Writing Lead Out

W 21:00:56 Retrying (1 of 3)...

W 21:01:56 Potential 'WaitImmediateIO' Deferred Error - (57%, 0/3) - Session Fixation Error Writing Lead In

W 21:01:56 Retry Failed - Reason: Session Fixation Error Writing Lead In

W 21:01:56 Retrying (2 of 3)...

W 21:02:50 Potential 'WaitImmediateIO' Deferred Error - (13%, 0/3) - Session Fixation Error Writing Lead In

W 21:02:50 Retry Failed - Reason: Session Fixation Error Writing Lead In

W 21:02:50 Retrying (3 of 3)...

W 21:03:47 Potential 'WaitImmediateIO' Deferred Error - (25%, 0/3) - Session Fixation Error Writing Lead In

W 21:03:47 Retry Failed - Reason: Session Fixation Error Writing Lead In

W 21:06:15 Retrying (4)...

W 21:07:46 Potential 'WaitImmediateIO' Deferred Error - (12%, 0/3) - Session Fixation Error Writing Lead In

W 21:07:46 Retry Failed - Reason: Session Fixation Error Writing Lead In

W 21:09:10 Retrying (5)...

W 21:11:44 Potential 'WaitImmediateIO' Deferred Error - (99%, 0/3) - Session Fixation Error Writing Lead Out

W 21:11:44 Retry Failed - Reason: Session Fixation Error Writing Lead Out

Posted

The only thing im going to try different is using vertabrim discs. Im guessing memorex dual layers are a hit and miss?? Hopefully using vertabrims arent.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.