Please help! SATA ROMS QUIT, two different systems?

_Str1keR · February 14, 2017, 2:35am

Hi Guys,

I’m new to the forums, and really in a pickle here… Please Help!

I have been using DVDFAB Platinum 3 for some time now, and never had a problem (with default settings)… until today, that is, after upgrading to version 3.1.5.0

The weirdest thing has happened that has me absolutely perplexed. While attempting to back-up “What the Bleep Do We Know & HOT FUZZ”, I noticed read/write speeds were extraordinarily fast. At 73% into the ‘burn’ (at 9.9x) of HOT FUZZ, the burner tray pops open, and I receive a burn failure msg.

Now here is were the weird part is… the burner is dead, like no power, and the tray will not retract. I remove the source DVD from the ROM drive, shut down DVDFAB, and reboot the system (WIN VISTA PREMIUM). On system restart, I notice neither opticle drives show activity. At this point I am thinking that my DVD burner just failed… no biggie. So I go to my second system (WIN XP with the same DVD ROM & DVD burner drives), quickly install DVDFAB, and again attempt to back-up HOT FUZZ.

Precisely the same thing happens, and now I realize there a REAL problem here. I then check system post and neither system is recognizing or detecting the optical drives… nothing in CMOS??? It’s like some NASTY code wacked my SATA channels, or the drives firmware??? Both systems are virus free and completely updated.

Both systems DVD ROMS will open & close, and lights blink, but the DVD burners appear completely dead, with trays doors open.

Could one of you brilliant minds PLEASE help, cause this O’l Fart D-@$$ doesn’t have a clue??? What caused this & how do I get my optical drives back?

Thank You!

The following is my primary (Vista) system config:

ASUS P5W DH Deluxe
Intel Core 2 Duo E6600 Conroe 2.4GHz 4M shared L2 Cache LGA 775 Processor
ATi Radeon X1950 XTX CrossFire, 2X 512 MB GDDR4 (Uber Edition)
CORSAIR XMS2 2GB (2 x 1GB) 240-Pin DDR2, 800 (PC2 6400)
Two (2) Seagate Barracuda ST3320620AS, 320GB, SATA 3.0Gb/s Hard Drives
ATi TV Wonder 650
Soundblaster Audigy 4
[B]* LITE-ON DVD SHD-16S1S (SATA)
LITE-ON DVDRW SH-16A7S (SATA)[/B]
Cooler Master CM Stacker 830 Evolution (7 - 120mm fans, CPU fan, 2 CrossFire fans, PS fan)
(LOL, Noisey!, but EVERYTHING runs VERY COOL!)
Thermaltake 750W Power Supply (ATi CrossFire Certified)

Log, DVDFAB_burn_VSO, session report to the time of failure:

7/31/2007 7:45:49 PM info ******************** Report session closed *********************
7/31/2007 6:45:08 PM info Media removed. Burning layer not ready to write
7/31/2007 6:45:06 PM info Finalization Time 00:01:22 - Total completion time 00:26:47
7/31/2007 6:43:43 PM info Write finished in 00:25:24 - Finalization start here. Avg. burn rate 4.35
7/31/2007 6:18:20 PM info Lead-in burning time (mS) 0
7/31/2007 6:18:18 PM info Write started 4085280 sectors to write
7/31/2007 6:18:18 PM info Layer change set to LBA 2085120 (3.98 Gb.)
7/31/2007 6:17:20 PM info Writing speed requested x4.0, effective x4.0
7/31/2007 6:17:20 PM info layer break set by filesystem builder at 2085120
7/31/2007 6:17:20 PM info Available write speed: 4x, 2.4x
7/31/2007 6:17:20 PM info Media ID: MKM-001-00
7/31/2007 6:17:20 PM info Media type: Dual Layer DVD+R
7/31/2007 6:17:20 PM info Ultra DMA mode 5 (ATA100)
7/31/2007 6:15:14 PM warning Layer Break is around 01:21:29, optimal value can’t be set within the possible range of [2042640…2086784].
7/31/2007 6:15:14 PM info Scanned files #48, folder #2 - total size 8365443072 b. (7.79 Gb.)
7/31/2007 6:15:14 PM info Inserted media type : DL DVD+R
7/31/2007 6:15:14 PM info Write started
7/31/2007 5:58:20 PM info New media inserted. Burning layer is ready to write
7/31/2007 5:51:46 PM info Media removed. Burning layer not ready to write
7/31/2007 5:51:44 PM info Finalization Time 00:00:25 - Total completion time 00:05:53
7/31/2007 5:51:18 PM info Write finished in 00:05:27 - Finalization start here. Avg. burn rate 10.50
7/31/2007 5:46:35 PM info Lead-in burning time (mS) 0
7/31/2007 5:45:50 PM info Write started 2119440 sectors to write
7/31/2007 5:45:50 PM info Writing speed requested x16.0, effective x16.0
7/31/2007 5:45:50 PM info Available write speed: 16x, 12x, 8x, 6x, 4x, 2.4x
7/31/2007 5:45:50 PM info Media ID: MBIPG101-R05-01
7/31/2007 5:45:50 PM info Media type: DVD+R
7/31/2007 5:45:49 PM info Ultra DMA mode 5 (ATA100)
7/31/2007 5:43:46 PM info Scanned files #24, folder #2 - total size 4339464192 b. (4.04 Gb.)
7/31/2007 5:43:46 PM info Inserted media type : DVD+R
7/31/2007 5:43:46 PM info Write started
7/31/2007 5:43:30 PM info New media inserted. Burning layer is ready to write
7/31/2007 5:42:42 PM info Media removed. Burning layer not ready to write
7/31/2007 5:42:32 PM error Write error at 1561616 (16) - Code 05 21 02 [Illegal request, Invalid address for Write]
7/31/2007 5:42:32 PM warning Reporting invalid address for write during recovery - trying to continue
7/31/2007 5:42:32 PM warning at sector 1561600 (16) - recover sequence started
7/31/2007 5:42:32 PM warning Write error - Code 03 0C 00 [Write error] - Info 0 - CSI 0
7/31/2007 5:42:32 PM info Try #0 - duration 2369861 Âµs
7/31/2007 5:38:44 PM info Lead-in burning time (mS) 0
7/31/2007 5:38:03 PM info Write started 2119440 sectors to write
7/31/2007 5:38:03 PM info Writing speed requested x16.0, effective x16.0
7/31/2007 5:38:03 PM info Available write speed: 16x, 12x, 8x, 6x, 4x, 2.4x
7/31/2007 5:38:03 PM info Media ID: MBIPG101-R05-01
7/31/2007 5:38:03 PM info Media type: DVD+R
7/31/2007 5:38:03 PM info Ultra DMA mode 5 (ATA100)
7/31/2007 5:35:59 PM info Scanned files #24, folder #2 - total size 4339464192 b. (4.04 Gb.)
7/31/2007 5:35:59 PM info Inserted media type : DVD+R
7/31/2007 5:35:59 PM info Write started
7/31/2007 5:29:29 PM info New media inserted. Burning layer is ready to write
7/31/2007 5:26:04 PM info Media removed. Burning layer not ready to write
7/31/2007 5:26:02 PM info Finalization Time 00:00:25 - Total completion time 00:05:57
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 045B1112 in module ‘vso_hwe.dll’. Read of address 0000000C]
7/31/2007 5:25:37 PM info Write finished in 00:05:31 - Finalization start here. Avg. burn rate 10.53
7/31/2007 5:25:37 PM error Exception encountered in read thread [Access violation at address 044E3163 in module ‘vso_hwe.dll’. Read of address 7FE3F008]
7/31/2007 5:20:50 PM info Lead-in burning time (mS) 0
7/31/2007 5:20:05 PM info Write started 2150336 sectors to write
7/31/2007 5:20:05 PM info Writing speed requested x16.0, effective x16.0
7/31/2007 5:20:05 PM info Available write speed: 16x, 12x, 8x, 6x, 4x, 2.4x
7/31/2007 5:20:05 PM info Media ID: MBIPG101-R05-01
7/31/2007 5:20:05 PM info Media type: DVD+R
7/31/2007 5:20:05 PM info Ultra DMA mode 5 (ATA100)
7/31/2007 5:18:02 PM info Scanned files #24, folder #2 - total size 4402759680 b. (4.1 Gb.)
7/31/2007 5:18:02 PM info Inserted media type : DVD+R
7/31/2007 5:18:02 PM info Write started
7/31/2007 5:17:40 PM info New media inserted. Burning layer is ready to write
7/31/2007 5:16:40 PM info Media removed. Burning layer not ready to write
7/31/2007 5:16:35 PM error Write error at 1578032 (16) - Code 05 21 02 [Illegal request, Invalid address for Write]
7/31/2007 5:16:35 PM warning Reporting invalid address for write during recovery - trying to continue
7/31/2007 5:16:35 PM warning at sector 1578016 (16) - recover sequence started
7/31/2007 5:16:35 PM warning Write error - Code 03 0C 00 [Write error] - Info 0 - CSI 0
7/31/2007 5:16:35 PM info Try #0 - duration 8944140 Âµs
7/31/2007 5:12:38 PM info Lead-in burning time (mS) 0
7/31/2007 5:11:52 PM info Write started 2150336 sectors to write
7/31/2007 5:11:52 PM info Writing speed requested x16.0, effective x16.0
7/31/2007 5:11:51 PM info Available write speed: 16x, 12x, 8x, 6x, 4x, 2.4x
7/31/2007 5:11:51 PM info Media ID: MBIPG101-R05-01
7/31/2007 5:11:51 PM info Media type: DVD+R
7/31/2007 5:11:51 PM info Ultra DMA mode 5 (ATA100)
7/31/2007 5:09:47 PM info Scanned files #24, folder #2 - total size 4402759680 b. (4.1 Gb.)
7/31/2007 5:09:47 PM info Inserted media type : DVD+R
7/31/2007 5:09:47 PM info Write started
7/31/2007 5:03:44 PM info New media inserted. Burning layer is ready to write
7/31/2007 5:03:44 PM info Compatible media types : DVD-R, DVD-RW Seq., DVD-RW RO, DVDRAM, DVD+R, DVD+RW, CD-R, CD-RW, DL DVD+R, DL DVD-R
7/31/2007 5:03:44 PM info New Drive selected : 2:1:0 - LITE-ON DVDRW SH-16A7S WS04 [E] (Ide)
7/31/2007 5:03:35 PM info New media inserted. Burning layer is ready to write
7/31/2007 5:02:07 PM info Current Drive selected : 2:1:0 - LITE-ON DVDRW SH-16A7S WS04 [E] (Ide)
7/31/2007 5:02:07 PM info Using SPTI interface
7/31/2007 5:02:07 PM info User default language : 1033 (0x0409h) - English (United States)
7/31/2007 5:02:07 PM info System default language : 1033 (0x0409h) - English (United States)
7/31/2007 5:02:07 PM info DLL Version 2.1.2.321
7/31/2007 5:02:07 PM info DLL C:\Program Files\DVDFab Platinum 3\vso_hwe.dll
7/31/2007 5:02:07 PM info Version 3, 1, 5, 0
7/31/2007 5:02:07 PM info ExeName : “C:\Program Files\DVDFab Platinum 3\DVDFabPlatinum.exe”
7/31/2007 5:02:07 PM info OS : Personal (Build 6000)
7/31/2007 5:02:07 PM info ******************** Report session started ********************

signals · February 15, 2017, 6:01am

Wow, nice system but bad problem! It sounds like the drive logic circuits are not being powered. If they are both powered from the same supply output I would suspect the power supply or a connector. If the supply was overloaded, it may have shut off the output on that leg. If you have not, try not only turning off but unplugging the supply from the AC for a minute or two, then power everything back up. Until this is sorted out, try reducing burn speeds–the log shows everything was burned at the max the media supported–try half that. If you have a digital voltmeter, see if the 5 & 12 VDC voltages are available on the drive connectors. And again if they are powered from the same supply output, try unplugging first one, then the other; a failure in one drive may be pulling the power bus low or causing the supply to shut it off due to overcurrent. Get inside and look around. You may find that the magic smoke has escaped from some components either in a peripheral or on the MB. /EDIT/ Not clear to me whether the drives on the XP system behaved the same way, i.e. drawers would not open close etc.

_Str1keR · February 15, 2017, 6:01am

Hi SigNals,

Thank you so much for the reply. I might have known it would have been a fellow southerner, to be the first to reply, LOL. I am just south of you in the Macon/Warner Robins area.

Yeah, agreed, “BAD PROBLEM”! BUT, what concerns me the most is ‘WHAT’ happened and why? Optical drive failure occured in [B]both[/B] systems, while executing exactly the same operations… DVDFAB Platinum 3 (after upgrade to 3.1.5.0). Again, I had zero problems with DVDFAB, until I upgraded to the latest release.

Previously, I have ran DVDFAB at default settings with no incident, but I will take your advise in reducing the burn speed. As far as power supply overload, do you think this would happen in two different systems? Wouldn’t my Thermaltake 750 have more than enough juice and stability, for the max output of any DVD burner? And, what software issue would induce this occurence? I BELIEVE YOU… LOL, just trying to grasp your theory.

[U]Common denominators[/U]:

*Both systems had the same failure while executing the same code, DVDFAB v 3.1.5.0

*Both systems failed while backing up the same source DVD, HOT FUZZ.

*Both systems are configured with the same make/model optical drives.
(LITE-ON DVD SHD-16S1S & LITE-ON DVDRW SH-16A7S)

*Both system’s optical drives are SATA, vice EIDE.

*Both systems are premium ASUS platforms, though different model motherboards.

I have my doubts that it is a hardware issue… again, this occurence is identical in two different systems, occuring during the same executions.

Replacing hardware to me is no big deal. I can change out the drives. BUT, what is the cause, and what is the ultimate resolution? I am inclined to believe that the hardware failure, is software induced. [B]My concern is once the hardware is back online, will I face this same issue again with DVDFAB[/B]. Again, it is as though some nasty code (like a virii), either induced from a protection scheme, or from within 3.1.5.0, has whacked my SATA channels or the drive’s firmware. Has anyone looked at the protections on HOT FUZZ, and 3.1.5.0’s ability to back it up? Or does 3.1.5.0 have issues with SATA?

At this point I think I need to say, I LOVE DVDFAB! And [B]FENGTAO[/B], I think your efforts have provided a great service to us all… you have done a marvelous job, and you are appreciated. I just feel at present, 3.1.5.0 has an issue that may need to be addressed.

I am still confused, burner trays extended, and an O’l Fart D-@$$…

HELP!

_Str1keR · February 15, 2017, 6:01am

SigNals,

LOL, Thanks-a-bunch!

Incidentally, I took your advice on the system shutdown and unpluging of the Pwr Supply. WORKED, like a champ. I have the SATA drives back now, but I am still really concerned with [B]WHAT[/B] caused this problem to begin with, ya know? I would hate to keep going thru this with 3.1.5.0. There is still an issue here… ???

I am going to again attempt ‘HOT FUZZ’, but this time the burn speed will be greatly reduced. I’ll keep you updated.

Thanks again Dude! You are the greatest!

signals · February 15, 2017, 6:01am

Hey man, that’s great news! I’m still not sure exactly what we are seeing and really hate problems that fix themselves. Not sure either that the particular version of DVDFab was the real culprit, but who knows. I still suspect some power related issue, but I may be way off base. Your supply is a hoss and has plenty of aggregate capacity, probably make a pretty good arc welder, but it may be the way the power is distributed among the outputs that is unbalanced. Look inside and make sure the magic smoke has not escaped from anything and see if the drive you use for burning is maybe on the same DC bus as the two SATA hard drives or some other power hog. If so, see if you can take its power from somewhere else, a different output that has less current demand. Or try the test burn with one of the HDDs powered down temporarily. Happy to be able to help out a fellow Southerner:iagree: but don’t sell our yankee cousins short–one of the best guys in the forum is so far north he’s practically Canadian (and he has seen the light and will be moving South in a year or so). Good luck and keep us updated as you spin everything back up.