Imgburn hangs when reading disc - Please help!

[bubbalex]

I have been unable to get ImgBurn to create an image from a disc.  Every time I attempt it, ImgBurn hangs at "Reading Track 1 of X".  Here are the things I've already tried while troubleshooting:

 

1) Tried 2.5.7.0 and 2.5.8.0 versions of ImgBurn (no effect)

2) Tried both optical drives (both are LG GH24LS50's with YP02 firmware) (no effect)

3) Tried uninstalling and re-installing the optical drives and firmware (no effect)

4) Tried multiple different discs with different containers (.bin, .iso) (no effect)

5) Tried performing the same operation on my spare laptop (also running Win7 64 bit) (WORKS EVERY TIME!)

 

Not sure what is going on here since my cheap old laptop works beautifully with ImgBurn, while my newer desktop hangs every time no matter what.  Also, I've noticed that when I attempt to create an image, the drive never spins up, then eventually becomes disconnected, and I cannot close Imgburn or eject the disc.  I have to manually power off my computer and re-boot to close IMgBurn and recover the use of my disc drive.  Note at the end of this example log, it shows that it loses the disc drive.

 

Anyone have any ideas as to what is going on here?  Does ImgBurn just not get along with my disc drives?

 

Here's the log:

 

I 22:01:19 ImgBurn Version 2.5.8.0 started!
I 22:01:19 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)
I 22:01:19 Total Physical Memory: 16,753,416 KiB  -  Available: 14,273,436 KiB
I 22:01:19 Initialising SPTI...
I 22:01:19 Searching for SCSI / ATAPI devices...
I 22:01:19 -> Drive 1 - Info: HL-DT-ST DVDRAM GH24LS50 YP02-01 (E:) (SATA)
I 22:01:19 -> Drive 2 - Info: HL-DT-ST DVDRAM GH24LS50 YP02-01 (D:) (SATA)
I 22:01:19 Found 2 DVD±RW/RAMs!
I 22:01:51 Operation Started!
I 22:01:51 Source Device: [0:1:0] HL-DT-ST DVDRAM GH24LS50 YP02 (D:) (SATA)
I 22:01:51 Source Media Type: CD-ROM
I 22:01:51 Source Media Supported Read Speeds: 10x, 16x, 24x, 32x, 40x, 48x
I 22:01:51 Source Media Supported Write Speeds: 4x, 8x, 16x, 24x, 32x, 40x, 48x
I 22:01:51 Source Media Sectors: 319,405
I 22:01:51 Source Media Size: 654,141,440 bytes
I 22:01:51 Source Media Volume Identifier: Blue's Art Time
I 22:01:51 Source Media Volume Set Identifier: NOT_SET
I 22:01:51 Source Media Application Identifier: TOAST ISO 9660 BUILDER COPYRIGHT © 1997 ADAPTEC, INC. - HAVE A NICE DAY
I 22:01:51 Source Media File System(s): ISO9660, Joliet
I 22:01:51 Read Speed (Data/Audio): MAX / 48x
I 22:01:51 Destination File: H:\Blue's Art Time.iso
I 22:01:51 Destination Free Space: 996,934,582,272 Bytes (973,568,928.00 KiB) (950,750.91 MiB) (928.47 GiB)
I 22:01:51 Destination File System: NTFS
I 22:01:51 File Splitting: Auto
I 22:01:54 Read Speed - Effective: 48x
I 22:01:59 Reading Session 1 of 1... (1 Track, LBA: 0 - 319404)
I 22:01:59 Reading Track 1 of 1... (MODE1/2048, LBA: 0 - 319404)
W 22:15:20 Failed to Read Sectors 0 - 31 - Reason: The device is not connected.
W 22:15:20 Waiting for device to become ready...
W 22:15:26 Device Removal Detected!
W 22:15:26 The device list will be refreshed at the next available opportunity.
 

[LIGHTNING UK!]

Right click the drive selection box and pick 'Family Tree'. Close the prompt and then copy+paste everything from the Log window please.

 

Have you tried in Safe Mode at all? It could be a driver on your machine that's messing things up. There is no issue with the program and your drives, something else is stopping it from working correctly.

[bubbalex]

Problem solved!  Thanks Lightning UK! - To make a long story short, I found that my onboard 91XX Marvell SATA controller was the problem.  It's been working fine for everything else I do with my DVD drives, but apparently it doesn't get along with ImgBurn.

 

I reconfigured my drive setup in my case such that my optical drives are now plugged into my Intel SATA ports, and now everything is working normally.  (I had ruled out the Marvell controller as a possible cause earlier because I thought I had already tried using ImgBurn with my Intel ports, but apparently not).  Your suggestions helped me rule out ImgBurn/drive compatibility and driver issues, so thanks for guiding me in the right direction!