thollian Posted October 29, 2006 Posted October 29, 2006 (edited) What does this mean? how can I fix this? DMA is enabled, and haven't made any changes to the system... When burning a DVD+R, I am getting this... ; //****************************************\\ ; ImgBurn Version 2.1.0.0 - Log ; Saturday, 28 October 2006, 20:44:39 ; \\****************************************// ; ; I 20:32:56 ImgBurn Version 2.1.0.0 started! I 20:32:56 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 20:32:56 Initialising SPTI... I 20:32:56 Searching for SCSI / ATAPI devices... I 20:32:57 Found 1 DVD-ROM and 1 DVD?RW! I 20:33:29 Operation Started! I 20:33:29 Source File: D:\TOS_S3D3B.ISO I 20:33:29 Source File Sectors: 1,971,723 (MODE1/2048) I 20:33:29 Source File Size: 4,038,088,704 bytes I 20:33:29 Source File Volume Identifier: x I 20:33:29 Source File Implementation Identifier: x I 20:33:29 Source File File System(s): ISO9660, UDF (1.02) I 20:33:29 Destination Device: [0:0:0] _NEC DVD_RW ND-3550A 1.06 (E:) (ATA) I 20:33:29 Destination Media Type: DVD+R (Disc ID: SONY-D21-00) (Speeds: 4x, 6x, 8x, 12x, 16x) I 20:33:29 Destination Media Sectors: 2,295,104 I 20:33:29 Write Mode: DVD I 20:33:29 Write Type: DAO I 20:33:29 Write Speed: 4x I 20:33:29 Link Size: Auto I 20:33:29 Test Mode: No I 20:33:29 BURN-Proof: Enabled I 20:33:29 Filling Buffer... I 20:33:30 Writing LeadIn... I 20:33:56 Writing Image... W 20:36:04 Waiting for buffers to recover... W 20:36:18 Waiting for hard disk activity to reach threshold level... I 20:36:22 Writing Image... W 20:36:33 Waiting for buffers to recover... W 20:36:47 Waiting for hard disk activity to reach threshold level... I 20:36:51 Writing Image... W 20:37:04 Waiting for buffers to recover... W 20:37:14 Waiting for hard disk activity to reach threshold level... I 20:37:16 Writing Image... W 20:37:44 Waiting for buffers to recover... W 20:37:54 Waiting for hard disk activity to reach threshold level... I 20:37:56 Writing Image... W 20:38:07 Waiting for buffers to recover... W 20:38:20 Waiting for hard disk activity to reach threshold level... I 20:38:22 Writing Image... W 20:38:33 Waiting for buffers to recover... W 20:38:47 Waiting for hard disk activity to reach threshold level... I 20:38:49 Writing Image... W 20:39:08 Waiting for buffers to recover... W 20:39:17 Waiting for hard disk activity to reach threshold level... I 20:39:18 Writing Image... W 20:39:32 Waiting for buffers to recover... W 20:39:43 Waiting for hard disk activity to reach threshold level... I 20:39:47 Writing Image... W 20:40:00 Waiting for buffers to recover... W 20:40:09 Waiting for hard disk activity to reach threshold level... I 20:40:13 Writing Image... W 20:40:27 Waiting for buffers to recover... W 20:40:40 Waiting for hard disk activity to reach threshold level... I 20:40:43 Writing Image... W 20:40:54 Waiting for buffers to recover... W 20:41:05 Waiting for hard disk activity to reach threshold level... I 20:41:09 Writing Image... W 20:41:21 Waiting for buffers to recover... W 20:41:30 Waiting for hard disk activity to reach threshold level... I 20:41:34 Writing Image... W 20:41:47 Waiting for buffers to recover... W 20:41:57 Waiting for hard disk activity to reach threshold level... I 20:42:01 Writing Image... W 20:42:13 Waiting for buffers to recover... W 20:42:24 Waiting for hard disk activity to reach threshold level... I 20:42:32 Writing Image... W 20:42:46 Waiting for buffers to recover... W 20:42:57 Waiting for hard disk activity to reach threshold level... I 20:43:00 Writing Image... W 20:43:13 Waiting for buffers to recover... W 20:43:24 Waiting for hard disk activity to reach threshold level... I 20:43:25 Writing Image... I 20:43:57 Abort Request Acknowledged I 20:43:58 Synchronising Cache... I 20:43:59 Closing Track... I 20:44:11 Finalising Disc... E 20:44:27 Failed to Write Image! E 20:44:27 Operation Aborted! - Duration: 00:10:57 I 20:44:27 Average Write Rate: 2,780 KB/s (2.0x) - Maximum Write Rate: 5,750 KB/s (4.2x) I 20:44:39 Close Request Acknowledged I 20:44:39 Closing Down... I 20:44:39 Shutting down SPTI... I 20:44:39 ImgBurn closed! Edited October 29, 2006 by thollian
polopony Posted October 29, 2006 Posted October 29, 2006 theres a number of things you can do and rather than make a list go to the SEARCH function at the top of the page and type threshold level and do some reading ,bad media, old hardware ,multitasking,theres a number of things that cause that error
thollian Posted October 29, 2006 Author Posted October 29, 2006 theres a number of things you can do and rather than make a list go to the SEARCH function at the top of the page and type threshold level and do some reading ,bad media, old hardware ,multitasking,theres a number of things that cause that error well I am using SONY media, which is not bad...I have burned over 50 of them and have had no problems...no multitasking, I am not doing anything on the computer, and everything is close except imgburn. And the computer is little over a year old, and dvd burner is less then 3 months old...anything other suggestions?
blutach Posted October 29, 2006 Posted October 29, 2006 Did you actually search? LUK! has answered this question in detail a number of times. Regards
LIGHTNING UK! Posted October 29, 2006 Posted October 29, 2006 The whole threshold level thing isn't really the problem here. You need to find out why your internal program buffer and device buffer is falling right down low so that it triggers the buffer recovery - which is where the threshold level comes into play. What's happening on your PC that's so stressful it can't read from the HDD and burn at 4x?! Or did you change the buffer size to 1MB or something? Do you have any free RAM or are you always working in the swapfile virtual memory?
polopony Posted October 29, 2006 Posted October 29, 2006 Did you actually search? LUK! has answered this question in detail a number of times. Regards couldn't have as for the Sony discs very mixed reviews
thollian Posted October 29, 2006 Author Posted October 29, 2006 (edited) The whole threshold level thing isn't really the problem here. You need to find out why your internal program buffer and device buffer is falling right down low so that it triggers the buffer recovery - which is where the threshold level comes into play. What's happening on your PC that's so stressful it can't read from the HDD and burn at 4x?! Or did you change the buffer size to 1MB or something? Do you have any free RAM or are you always working in the swapfile virtual memory? What's happening on your PC that's so stressful it can't read from the HDD and burn at 4x?! Or did you change the buffer size to 1MB or something? I am not sure, when I burn, I don't do anything else while burning....my HD light on the PC is usually solid whenever burning something.... Do you have any free RAM or are you always working in the swapfile virtual memory? I got over 700mb free when burning... Edited October 29, 2006 by thollian
thollian Posted October 29, 2006 Author Posted October 29, 2006 (edited) Did you actually search? LUK! has answered this question in detail a number of times. Regards yes I did search, and only thing they say is because of bad media, I have used Sony, RiData, Verbatim, and same thing. It has never done this before, until the last few days it just started... Edited October 29, 2006 by thollian
LIGHTNING UK! Posted October 29, 2006 Posted October 29, 2006 and yet your buffers are all over the place? It's ok for the device buffer to drop down now and then, most drives do that when they perform wopc stuff. The one just marked 'Buffer' however should NOT drop off below maximum. Yours must be or the buffer recovery thing would never kick in. Do you have DVDInfoPro downloaded / installed? ImgBurn produces these little 'IBG' files which you can open/display in DVDInfoPro. It shows buffer usage, cpu usage, write speed, verify speed etc all on pretty graphs. If you could show us one of those from you burning it might help. If you don't auto export imgburn graph data the easiest way to show it in dvdinfopro is to click the little disc + information speech bubble just below the 'destination' box on the front screen. Or you can click 'File' -> 'Display Graph Data using DVDInfoPro'.
thollian Posted October 29, 2006 Author Posted October 29, 2006 (edited) file removed. Edited October 29, 2006 by thollian
LIGHTNING UK! Posted October 29, 2006 Posted October 29, 2006 Ok so it's easy to see some glitches in that file around the 1.3 GB mark but it's not exactly all over the place the entire time - which is what I was kinda expecting. I think this issue is just something you're going to have to fix yourself via some problem solving and a lot of trial and error. Something is happening that's preventing the program from reading enough data from the hdd to sustain a pretty measly 4x write speed. You just need to find out what that is Maybe take a look in perfmon.msc and see what your typical 'average disk queue length' is. You should be able to just watch the graph! At the moment mine is on 0.002.
thollian Posted October 29, 2006 Author Posted October 29, 2006 (edited) Ok so it's easy to see some glitches in that file around the 1.3 GB mark but it's not exactly all over the place the entire time - which is what I was kinda expecting. I think this issue is just something you're going to have to fix yourself via some problem solving and a lot of trial and error. Something is happening that's preventing the program from reading enough data from the hdd to sustain a pretty measly 4x write speed. You just need to find out what that is Maybe take a look in perfmon.msc and see what your typical 'average disk queue length' is. You should be able to just watch the graph! At the moment mine is on 0.002. thanks for your help, do you think the files themselves are messed up? or the files are fine, and something is just interfering with the burn? the average is at 1.216 at the current moment of this posting.. Edited October 29, 2006 by thollian
LIGHTNING UK! Posted October 29, 2006 Posted October 29, 2006 1.216?! Surely the average value can't be that high? Even when I use XP's search for files thing mine only goes as high as 1. If yours is at 1.216 all the time then that could explain things. Search google for 'Average Disk Queue Length' and see what Microsoft has to say about it. You might find some pointers on how to troubleshoot it. Maybe running chkdsk and defrag would be a good start.
thollian Posted October 29, 2006 Author Posted October 29, 2006 doesn't look to be all the time, only under high load...0.002 right now...
thollian Posted October 29, 2006 Author Posted October 29, 2006 well looks as though it was the Intel Matrix storage driver; I installed the latest version (6.1) and have burned 2 dvd's with no problems... thanks for everyones help
LIGHTNING UK! Posted October 29, 2006 Posted October 29, 2006 Naughty thing, glad you sorted it I just checked mine, I'm running 6.1 already! phew!
Recommended Posts