Jump to content

dkazaz

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by dkazaz

  1. So I tested a few discs including some that are definitely fine and the verification shows the same errors although at the end it says "successfully completed" and plays the happy tune. I guess its time to replace the drive. It seems you recommend the 2209 over the 209? It's about double the price on Amazon UK. Do you think its worth the difference?
  2. Hi and thank you for replying. My burner is the 209, which might be the OEM version of the 2209. I have had it for a couple of years so perhaps its on its way out The strange thing here is that verification seems to complete successfully but with these errors... I'll try to verify an old disc as you suggest and post back here...
  3. Hi all I'm having a strange problem. I'm burning bluray discs using a pioneer BDR-209 drive (Windows 10 x64). My burn's complete successfully but I get the following errors in the log: ====================== I 20:41:44 Verifying Session 1 of 1... (1 Track, LBA: 0 - 10481439) I 20:41:44 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 10481439) W 20:47:11 Failed to Read Sectors 4613216 - 4613247 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07) W 20:49:33 Failed to Read Sectors 7431456 - 7431487 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07) W 20:50:32 Failed to Read Sectors 8737888 - 8737919 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07) I 20:51:47 Exporting Graph Data... I 20:51:47 Graph Data File: C:\Users\Dimitri\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-209D_1.10_SUNDAY-13-MAY-2018_20-27_VERBAT-IMe-000_6x.ibg I 20:51:47 Export Successfully Completed! I 20:51:47 Operation Successfully Completed! - Duration: 00:10:03 I 20:51:47 Average Verify Rate: 34,822 KiB/s (7.9x) - Maximum Verify Rate: 49,268 KiB/s (11.2x) ======================= I'm using a 2-3 different types of media and not had this problem until a week ago. It's worrying because I don't know if I can trust the discs for archiving (I guess I can't). I tried running the verification twice and the same thing happens. Any idea what could cause it? Bad media, problem in the drive, something else? My thanks to anyone who can help!
  4. OK, I can live with it, though I suspect its some windows thing interferering with the i/o. Thanks a lot for all your replies!
  5. Hi, and thanks a lot for your reply! Here is the log from two recent burns - one on LS and one on DL media. Both were pretty good burns, but both exhibited the weird drops in device buffer (the imgburn buffer was steady) so it was something else getting in the way. No real complains about the burns, but without these dips the drive burns almost perfectly. I doubt a DMA problem as the device is currently on UDMA5. Any ideas? ; //****************************************\\; ImgBurn Version 2.4.4.0 - Log ; Sunday, 07 June 2009, 03:58:11 ; \\****************************************// ; ; I 02:42:33 ImgBurn Version 2.4.4.0 started! I 02:42:33 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7100) I 02:42:33 Total Physical Memory: 4,193,332 KB - Available: 2,794,040 KB W 02:42:33 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 02:42:33 Initialising ElbyCDIO... I 02:42:33 ELBYCDIO.DLL - Elaborate Bytes CDRTools - ElbyCDIO DLL - Version 6.0.9.0 I 02:42:33 Searching for SCSI / ATAPI devices... I 02:42:33 Found 2 DVD
  6. Hi all, When burning DVD+R DL disks, my device buffer keeps dropping to 10% every minute or so. I notice this coincides with a sudden drop in I/O activity. It is not related to any other use process running i.e. applications etc. I don't know about services or system processes. My system is an Intel Quad q9300 oc'd to 3GHz, 4GB RAM, Asus P45 motherboard, ATI HD3650 VGA card, WD Velociraptor as system drive and WD Caviar as data drive (imgburn reads data from this one). OW is Win7 RC x64. The rsult of this problem is burns which are OK, but much worse than before it started (I have not made any system changes to account for it). Any idea what could be causing it? Is there something I can do by playing with the buffer size or the I/O settings? Thanks a lot for any help!
×
×
  • Create New...

Important Information

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