Cannot stop imgburn without corrupting my Win 7 installation

[XEyedBear]

Today is my first use of this software. The results are not encouraging. After the first attempt the software remained displaying the status "synchronising cache..." for about 4 hours after creating a 3.7 GB data ROM. During this time the drive light was continually flashing. Attempts to close the log window or the other application window warned me that I would be aborting the program and, by implication, the burn would be aborted. In fact no attempts of mine to close either window were accepted. In the end I had to use the task manager to kill the application. Windows would not boot thereafter - I had to use a restore disk.

 

As I write this, my second attempt to use the software appears to following exactly the same course. If my windows installation is corrupted again I will be seriously not amused.

 

What is going wrong here?

 

My system:

Win 7 Home Premium running from SSD with 8GB RAM

LiteOn DVD - R Dual Layer

 

Copy and paste of log:

 

I 21:46:46 ImgBurn Version 2.5.8.0 started!

I 21:46:47 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)

I 21:46:47 Total Physical Memory: 8,379,132 KiB  -  Available: 4,884,940 KiB

W 21:46:47 Drive I:\ (FAT32) does not support single files > 4 GiB in size.

I 21:46:47 Initialising SPTI...

I 21:46:47 Searching for SCSI / ATAPI devices...

I 21:46:47 -> Drive 1 - Info: ATAPI iHAS322   8 3L11 (F:) (RAID)

I 21:46:47 Found 1 DVD±RW/RAM!

W 21:55:48 GUI Font has been changed to 'Segoe UI' !

I 22:09:26 Operation Started!

I 22:09:26 Building Image Tree...

I 22:09:26 Checking Directory Depth...

E 22:09:40 Directory depth exceeds ISO9660 limit of 8 levels!

E 22:09:40 Name: '\Tbird Archive\010111\ug134lxr.default\Mail\pop.ntlworld.com\Friends.sbd\Xpqu.sbd\ChinaQuest.sbd\'

E 22:09:40 Number of directory levels in path: 9

E 22:09:40 Most directory levels in any path: 9

E 22:09:40 Operation Failed! - Duration: 00:00:14

I 22:09:54 Operation Started!

I 22:09:54 Building Image Tree...

I 22:09:54 Checking Directory Depth...

I 22:09:54 Calculating Totals...

I 22:09:55 Preparing Image...

I 22:09:56 Checking Path Length...

I 22:09:56 Contents: 3,409 Files, 397 Folders

I 22:09:56 Content Type: Data

I 22:09:56 Data Type: MODE1/2048

I 22:09:56 File System(s): ISO9660, UDF (1.02)

I 22:09:56 Volume Label: [Not Configured]

I 22:09:56 Size: 4,323,099,483 bytes

I 22:09:56 Sectors: 2,112,499

I 22:09:56 Image Size: 4,336,418,816 bytes

I 22:09:56 Image Sectors: 2,117,392

I 22:09:56 Operation Successfully Completed! - Duration: 00:00:02

I 22:11:34 Operation Started!

I 22:11:34 Building Image Tree...

I 22:12:16 Checking Directory Depth...

I 22:12:16 Calculating Totals...

I 22:12:16 Preparing Image...

I 22:12:18 Checking Path Length...

I 22:12:18 Contents: 3,409 Files, 397 Folders

I 22:12:18 Content Type: Data

I 22:12:18 Data Type: MODE1/2048

I 22:12:18 File System(s): ISO9660, UDF (1.02)

I 22:12:18 Volume Label: Tbird Archive

I 22:12:18 Size: 4,323,099,483 bytes

I 22:12:18 Sectors: 2,112,499

I 22:12:18 Image Size: 4,336,418,816 bytes

I 22:12:18 Image Sectors: 2,117,392

I 22:12:42 Operation Successfully Completed! - Duration: 00:01:08

I 22:12:42 Operation Started!

I 22:12:42 Source File: -==/\/[bUILD IMAGE]\/\==-

I 22:12:42 Source File Sectors: 2,117,392 (MODE1/2048)

I 22:12:42 Source File Size: 4,336,418,816 bytes

I 22:12:42 Source File Volume Identifier: Tbird Archive

I 22:12:42 Source File Volume Set Identifier: 4588B16100204F0E

I 22:12:42 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER!

I 22:12:42 Source File Implementation Identifier: ImgBurn

I 22:12:42 Source File File System(s): ISO9660, UDF (1.02)

I 22:12:42 Destination Device: [2:0:0] ATAPI iHAS322   8 3L11 (F:) (RAID)

I 22:12:42 Destination Media Type: DVD+R (Disc ID: YUDEN000-T02-00)

I 22:12:42 Destination Media Supported Write Speeds: 4x, 6x, 8x

I 22:12:42 Destination Media Sectors: 2,295,104

I 22:12:42 Write Mode: DVD

I 22:12:42 Write Type: DAO

I 22:12:42 Write Speed: MAX

I 22:12:42 DVD+R Reserve Track: No

I 22:12:42 Link Size: Auto

I 22:12:42 Lock Volume: Yes

I 22:12:42 Test Mode: No

I 22:12:42 OPC: No

I 22:12:42 BURN-Proof: Enabled

I 22:12:42 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)

I 22:12:42 Book Type Setting: DVD-ROM

I 22:12:42 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes

I 22:12:43 Filling Buffer... (80 MiB)

I 22:12:47 Writing LeadIn...

I 22:13:04 Writing Session 1 of 1... (1 Track, LBA: 0 - 2117391)

I 22:13:04 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2117391)

I 22:20:40 Synchronising Cache...

I 22:29:29 Abort Request Acknowledged

 

[LIGHTNING UK!]

I can assure you that using task manager to end task on ImgBurn isn't going to corrupt your OS.

 

The sync cache command is processed by the drive and ImgBurn simply waits for it to say it has finished. If yours isn't finishing, either your drive got stuck processing it (doesn't like the discs etc) or your drivers are messing with the response.

 

If the drive is stuck, you'd have to totally power the machine off so it can reset properly. Take the disc out as it powers back up.

 

If it's the drivers, update them. What controller have you attached the drive to?

Right click the drive selection drop down box and pick family tree. Close the prompt that comes up and then copy + paste everything from the log window please.

[XEyedBear]

<clip>

 

The sync cache command is processed by the drive and ImgBurn simply waits for it to say it has finished. If yours isn't finishing, either your drive got stuck processing it (doesn't like the discs etc) or your drivers are messing with the response.

 

<clip>

 

If it's the drivers, update them. What controller have you attached the drive to?

Right click the drive selection drop down box and pick family tree. Close the prompt that comes up and then copy + paste everything from the log window please.

Thanks for this informative reply: from what you say it's obvious that I have to examine my DVD drive. It's a SATA drive, directly attached to the southbridge on the mobo (ASUS M4A785TD-M EVO), with drivers which I assume are automatically installed from the Win7 retail install CD (right ?) Device Manager shows no errors.

 

I do not understand the expression "drive selection drop down box and pick family tree" - right clicking on the drive listed in Windows Explorer does not present  an item titled 'family tree'. Please clarify this.

[LIGHTNING UK!]

It's an option within ImgBurn.

 

Load the program, switch to Write mode and then right click on the drive selection drop down in the 'Destination' box.

 

Regarding your SATA controller, I recommend ensuring your bios is up to date and that you're running the latest drives for the controller from AMD's website.

[XEyedBear]

It would seem I have no optimally configured the SATA drives on my system - for which I plead that the documentation supplied in the mobo manual and driver disk is inexcusably confusing (I'm going to seek enlightenment on techsupportforum). A result of the corruption of my system the other day prompted me to learn how to make an easily installable system image - using  a Knoppix-based RunTimeLiveCD (and DriveIMageXML). I discovered that the bootable CD I made from the ISO would not boot. Having looked at the boot sequence setting in my BIOS I found 2 entries for the ATAPI drive - one preceded with the word 'RAID'. For obvious reasons I had not set this option as the highest boot priority.

 

Now having changed that BIOS Boot sequence choice and selected the drive labelled 'RAID: Atapi....' as the first drive,  my RunTimeLive CD boots immediately - and I suspect that the 'Synchronising cache...' information msg in your app will be posted for just a short period of time. I'll try that soon, but before then I will revert to the 'wrong' Atapi drive selection, and get the info. you previously requested. Back shortly.

[XEyedBear]

 

I have now taken screen shots of the output of the family tree as requested.

 

The first image (capture0.jpg) reflects the BIOS configuration of having the first bootable device as "ATAPI CD-ROM".

 

For image capture1.jpg, the first bootable device is "RAID: ATAPI iHAS322 8"

 

The outputs are identical. However with the first bootable device set to "RAID: ATAPI iHAS322 8", the imgburn app completes as expected and verifies the written data without problem.

 

I do not understand why there are two ATAPI device definitiosn in BIOS or why they should have such a dramatic effect on imgbrn.