Jump to content

Always burning error with sata Optiarc AD-7241S


Recommended Posts

Hi,

I've got a problem with cdburnerxp (4.2.7.1849) every times I try to burn a disc at 80/90% of the process it returns this error

An error occurred while burning the disc...

(devNoSeekComplete) Could not write to Disc (LBA: 1639040 Length: 32). No Seek Complete. -0x030200

I can't burn any dvd, it always return's this error.

My system:

Windows 7 64 bit

Matrix sata storage driver updated

DVD burner Optiarc AD-7241S Sata

It seems that it burns always at the maximum speed also. :-(

The native windows 7 burning process works fine.

Any suggestions ?

Thanks in advance

Link to post
Share on other sites
Guest Gertfried Zobel

Hi,

seems i am with you.

Windows7 64 Bit.

Intel DP45SG

LG GH22NS30 DVD, Firmware 2.0

An error occurred while burning the disc...

(devNoSeekComplete) Could not write to Disc (LBA: 1639040 Length: 32). No Seek Complete. -0x030200

This happens only on burning DVD Dual Layer +R,

DVDs at 4.7GB work 100% fine.

CD BurnerXP is latest.

Link to post
Share on other sites
  • 2 months later...

I'm having the same problem.

Drive: Optiarc DVD RW AD-7240S

Media: TDK 16x DVD-R single layer

OS: Win 7 64-bit

Happened with my previous version of CDBXP, upgraded to the latest one (4.3.0.2015), still happening.

I get the error when I reach about 71% of the burn when recording at 16x speed. Also tried 8x, same problem.

Link to post
Share on other sites
  • 2 weeks later...
Guest Jaco

I have the same problem in win 7 64 bit - newest xpBurner - disks are Kodak dvd-r - it's a new dvd-writer - I thought it was the disks - exchanged it at shop for a new stack (new stack same problem - could be because same batch??) - also - there is no problems writing to tdk dvd-r disks I have from another stack

Link to post
Share on other sites

Same problem here (Windows 7 32 bit, newest version of CDBurnerXP, most recent firmware). After installation of this drive (2 weeks ago) I managed to write about 10 dvd+r discs (Philips 16x speed), after that every disc failed with the same error. Also tried Sony and Imation discs, but this had the same result.

I was thinking of uninstalling the drive and sending it back to the shop, but before doing so I tried Nero Burning Rom and that worked without any problems. I have not had any errors with Nero yet, and I have written about 20 dvd+r discs now. So it looks like the problem lies with CDBurnerXP. It's a shame, because I prefer using freeware, and up to now, CDBurnerXP never let me down.

Link to post
Share on other sites
  • 2 weeks later...

same problem by me too.

although i've got WinXP (32bit), with the latest CDBurnerXP (4.3.2.2140).

burning stops at 70-80% with error.

no problem with Roxio 8 or Ashampoo 9.

it's a shame for CDBurnerXP.

Link to post
Share on other sites
  • 2 months later...
  • 2 months later...
  • 1 month later...

After burning about 1-3 DVDs CDburnerXP fails to burn every DVD until the next reboot, producing an error at 0%-1% completion. Burning with Nero BurnLite 10 works (after CDburnerXP started to produce errors, without reboot or something).

Had similar problems with Nero 7, it said something about invalid SATA commands.

My system:

Windows 7 x64

Asus M3N-HDMI board (nvidia), AMD CPU

Sony Optiarc AD-7240S SATA

Media: Verbatim 16x DVD-R

CDburnerXP version 4.3.7.2356

I really like CDburnerXP, especially since it is not loaded to the top with adware like BurnLite, but loosing about one third of my DVDs makes it unuseable to me.

Link to post
Share on other sites

Even if I don't respond since I cannot currently offer a solution, please continue posting your problems so that I can gather impressions about the problem.

Link to post
Share on other sites
Guest jldg

I have the same error with windows 7 64b

the burning was ok during some month after March 2010

then error burning ( 3/4 ?)

lba 2012960 devseekerror no seek ....;

and no error with nero lite!

motherboard ga-ex58-ud5 intel core i7 920 ssd intel x25m

cdxp burner 4.3.0.1948

it's very sad that no solution appears since one year...

thank you for help

Link to post
Share on other sites
Guest jldg

follow my previous message from yesterday

after upgrade of cdburnerxp to the 4.3.7.2423 , new behaviour

after 3 min windows bar show 6% , time counter are running,

led burner go and stay off

20 min later windows bar show 6% , time couter running <1min

30 min error message (dev NTSPTI could not write to disk LBA 133760)

unable to close the program, even with taskmanager (windows 7 64b), reboot!!

same video compilation burning OK with imgburn....

what to do? , how to investigate ??

Link to post
Share on other sites
  • 1 year later...
Guest Jay

I am having the same issue, (devnoseekcomplete) Could not write to Disc (LBA: 1734048 Length: 32) No Seek Complete. - 0x030200

Link to post
Share on other sites
  • 1 month later...
Guest Ashmotif200

I am having the same issue, (devnoseekcomplete) Could not write to Disc (LBA: 1734048 Length: 32) No Seek Complete. - 0x030200 when burning DVDs

but when i try again with different speed it works...

when it did not work on 16x i changed to 12x and it worked.

and now i am currently burning on 8x... hope it works :P

Link to post
Share on other sites
  • 6 months later...

I'm having the same problem too.

I'm using a Sony AD-7240S sata drive, and am running Windows 7 Pro 64-bit.

Always fails around 80%, but the LBA address is slightly different each time.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.