Jump to content

Duplex Secure's SPTD driver can have a detrimental effect on drive performance.


Dymblos

Recommended Posts

When I start the Imgburn, that message appears

 

Then I download the "SPTDinst-V183-x64", run the program and unistall

 

Now the message is no longer displayed, the version I had installed was version 1.81

 

My question, I need to install version 1.83? (the most recent)

Edited by Dymblos
Link to comment
Share on other sites

If you use something that makes use of the SPTD driver (and can't function without it), yeah you'll have to install SPTD again.

 

Of course then the message will come back. If you don't have any problems with slow read/verify operations, you have nothing to worry about - just ignore the warning.

Link to comment
Share on other sites

lol

 

nero , burn dvd = sucess

clonedvd, burn dvd = sucess

imageburn burn dvd = fail (more than 10 dvd to the trash)

 

never use this program again...

 

error_zps2669a59b.png

 

sometimes 2%.. others 4%

 

burner is not the problem

 

this is 100% imgburn problem

Edited by Dymblos
Link to comment
Share on other sites

DAEMON Tools uses the SPTD driver, as does Alcohol 120% etc.

 

Whilst I don't expect you to understand, the program can only peform as well as your system lets it.

 

If it submits a command to the drive and an error is returned, that's out of my hands. The program just reports the error.

 

If you've got CloneDVD installed, try switching to the ElbyCDIO interface on the I/O tab within the settings. It may be able to bypass whatever's causing Windows to report that error.

 

I'd help you try and get to the bottom of the issue but I can't and won't do that if you think you know best and have already made your mind up.

Link to comment
Share on other sites

i already unistall clonedvd, nero, deamon tools, all . because a friend told me i must use imgburn to burn xbox games.. but after 10 dvd to trash, no more >_>

before, with clonedvd and nero, no problems

 

 

also, this are the default options in imgburn??

 

1_zpsc563246e.png

 

2_zpsdc8d64e4.png

 

3_zps63d0cc8c.png

 

4_zps53c7c4f2.png

 

5_zps0f8b92ba.png

 

6_zps0e0884cd.png

Edited by Dymblos
Link to comment
Share on other sites

What would actually help here is to see a log file - as per the pink box up the top.

 

If you've just installed ImgBurn, it's going to be running with the default settings. If in doubt, just his the 'Restore Defaults' button - that's what it's there for.

 

You don't have to waste discs to test things out. You can use rewritables or DVD-R media (with 'Test Mode' enabled) until we figure out what's causing your machine to error out.

Link to comment
Share on other sites

No, I need to see the stuff I asked for - i.e. the log from your failed burn.

 

There are things I want to know / check before I give you any advice on what to do next.

 

I'd also like to see the 'Family Tree' info.

 

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

Link to comment
Share on other sites

No, you can access old logs via the 'Help' menu in the program.

 

What I'd start by doing is updating your chipset drivers and put the v10.8 Intel Rapid Storage Tech. driver on (to replace that 9.2 version you're currently running). That's what I have on mine.

 

Intel Chipset Software - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21594

 

Intel Rapid Storage Tech - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2101&DwnldID=20768

You want the 'STOR_allOS_10.8.0.1003.exe' one.

 

Check your motherboard BIOS is up to date too as they sometimes update the option ROMs.

Link to comment
Share on other sites

Log:

 

 

; //****************************************\\

; ImgBurn Version 2.5.7.0 - Log

; miércoles, 24 octubre 2012, 14:50:21

; \\****************************************//

;

;

I 14:43:59 ImgBurn Version 2.5.7.0 started!

I 14:43:59 Microsoft Windows 7 Enterprise x64 Edition (6.1, Build 7601 : Service Pack 1)

I 14:43:59 Total Physical Memory: 8,364,676 KB - Available: 7,066,088 KB

I 14:43:59 Initialising SPTI...

I 14:43:59 Searching for SCSI / ATAPI devices...

I 14:43:59 -> Drive 1 - Info: PIONEER DVD-RW DVR-218L 1.03 (E:) (SATA)

I 14:43:59 Found 1 DVD±RW/RAM!

I 14:44:51 Operation Started!

I 14:44:51 Source File: C:\Users\Dymblos\Downloads\BlaBlal\BlaBla\BlaBla.iso

I 14:44:51 Source File Sectors: 1,874,176 (MODE1/2048)

I 14:44:51 Source File Size: 3,838,312,448 bytes

I 14:44:51 Source File Volume Identifier: BlaBla_BlaBla

I 14:44:51 Source File Volume Set Identifier: 4146024B001C98E4

I 14:44:51 Source File Application Identifier: IMGBURN V2.5.7.0 - THE ULTIMATE IMAGE BURNER!

I 14:44:51 Source File Implementation Identifier: ImgBurn

I 14:44:51 Source File File System(s): ISO9660, UDF (1.02)

I 14:44:51 Destination Device: [4:0:0] PIONEER DVD-RW DVR-218L 1.03 (E:) (SATA)

I 14:44:51 Destination Media Type: DVD-R (Disc ID: GSC003)

I 14:44:51 Destination Media Supported Write Speeds: 4x, 6x, 8x

I 14:44:51 Destination Media Sectors: 2,297,888

I 14:44:51 Write Mode: DVD

I 14:44:51 Write Type: DAO

I 14:44:51 Write Speed: 4x

I 14:44:51 Link Size: Auto

I 14:44:51 Lock Volume: Yes

I 14:44:51 Test Mode: No

I 14:44:51 OPC: No

I 14:44:51 BURN-Proof: Enabled

I 14:44:52 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x)

I 14:44:52 Advanced Settings - Optimal Writing Speed: No

I 14:44:54 Filling Buffer... (80 MB)

I 14:44:54 Writing LeadIn...

I 14:45:20 Writing Session 1 of 1... (1 Track, LBA: 0 - 1874175)

I 14:45:20 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1874175)

W 14:45:45 Failed to Write Sectors 66752 - 66783 - Reason: The request could not be performed because of an I/O device error.

W 14:45:45 Retrying (1 of 20)...

W 14:46:26 Retry Failed - Reason: Write Error

W 14:46:26 Retrying (2 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (3 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (4 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (5 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (6 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (7 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (8 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (9 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (10 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (11 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (12 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (13 of 20)...

W 14:46:26 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:26 Retrying (14 of 20)...

W 14:46:27 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:27 Retrying (15 of 20)...

W 14:46:27 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:27 Retrying (16 of 20)...

W 14:46:27 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:27 Retrying (17 of 20)...

W 14:46:27 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:27 Retrying (18 of 20)...

W 14:46:27 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:27 Retrying (19 of 20)...

W 14:46:27 Retry Failed - Reason: Logical Block Address out of Range

W 14:46:27 Retrying (20 of 20)...

W 14:46:27 Retry Failed - Reason: Logical Block Address out of Range

E 14:49:21 Failed to Write Sectors 66752 - 66783 - Reason: The request could not be performed because of an I/O device error.

I 14:49:21 Synchronising Cache...

E 14:50:18 Failed to Write Image!

I 14:50:18 Exporting Graph Data...

I 14:50:18 Graph Data File: C:\Users\Dymblos\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_DVD-RW_DVR-218L_1.03_MIÉRCOLES-24-DE-OCTUBRE-DE-2012_02-44_p.m._GSC003_4x.ibg

I 14:50:18 Export Successfully Completed!

E 14:50:18 Operation Failed! - Duration: 00:05:27

I 14:50:18 Average Write Rate: 556 KB/s (0.4x) - Maximum Write Rate: 5,634 KB/s (4.1x)

I 14:50:21 Close Request Acknowledged

I 14:50:21 Closing Down...

I 14:50:21 Shutting down SPTI...

I 14:50:21 ImgBurn closed!

Link to comment
Share on other sites

Ok so from that log I can see your drive did actually report a 'Write Error' after that initial 'The request could not be performed because of an I/O device error.' one from Windows.

 

In an ideal world, you wouldn't have ever seen that initial error and you'd have just got the real error from the drive to start with. That's where drivers (and filter drivers) etc come into play and mess things up.

 

If your drive can't write to the 'GSC003' media at 4x without erroring out, give the other supported write speeds a shot. There are a few other things you can try too, but I'll get to them in another post.

 

Do you have any decent quality discs from Verbatim / Taiyo Yuden? I've purchased a lot of random cheap ones in my time but I don't recall ever ending up with any using the 'GSC003' MID / dye.

 

The fact 'Test Mode' works means that when the drive is instructed not to actually write to the media, everything else works fine. So it's just when the laser is active and it's actually trying to write to the disc. The commands sent by ImgBurn are identical (besides the 1 flag in a structure to enable 'Test Mode'). It can therefore only ever be the drive/firmware/media combo that's at fault here - even if you believe otherwise.

Link to comment
Share on other sites

ImgBurn isn't failing, your drive is failing.

 

I really can't stress that enough. All software does is send data to the drive. The drive has complete control of the burn. I couldn't make the drive fail with a 'Write Error' if I tried.

 

Show me some other logs where it's failed and let's see what error messages you got.

Link to comment
Share on other sites

All things being equal (something you'll never know as you probably can't snoop on I/O), all 3 would behave identically.

 

As I said in post #13, there are a few other things to try (things that other programs may do by default).

 

If your drive can't write to the 'GSC003' media at 4x without erroring out, give the other supported write speeds a shot. There are a few other things you can try too, but I'll get to them in another post.

 

It's swings and roundabouts with these things. Sometimes other programs constantly fail for people and ImgBurn will work. Other times, ImgBurn won't work and others will. Unfortunately, you can't have it both ways.

 

 

1. Try the other write speeds. Drives perform better / worse at different speeds. Slower doesn't always equal better.

2. Try with 'Perform OPC Before Write' enabled in the settings. If the strategy in the firmware isn't tailored perfectly for your discs (and with cheapo ones sold under loads of different brand names, that's quite possible), it may help your drive adjust how it burns the disc.

3. Try with the 'Write Type' set to 'Incremental' instead of 'DAO/SAO'.

 

Don't forget about what I said in Post 11 regarding the drivers. You should never have got that initial ''The request could not be performed because of an I/O device error.' error from Windows.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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