Jump to content

"Waiting for hard disk activity to reach threshold level"


hunginator

Recommended Posts

Hey guys,

 

I just bought a new burner hoping that it would solve my problem but it did not!

 

My problem right now is that whenever I burn a DVD, the buffers will die and my computer will slow down like crazy when I open a program. I am pretty 100% sure that there is nothing wrong with my hardware in my computer especially not my HDD's. Also, I am using Windows Vista Ultimate 32-bit. However, the burns do finish successfully. It usually takes like 18 minutes to burn a full DVD now which is ridiculous!!!

 

Here's my log that I saved from a previous burn:

 




I 21:32:10 ImgBurn Version 2.3.0.0 started!
I 21:32:10 Microsoft Windows Vista Ultimate Edition (6.0, Build 6000)
I 21:32:10 Total Physical Memory: 1,046,720 KB - Available: 542,732 KB
I 21:32:10 Initialising SPTI...
I 21:32:10 Searching for SCSI / ATAPI devices...
I 21:32:10 Found 1 DVD-ROM and 1 DVD?RW!
I 21:32:31 Operation Started!
I 21:32:31 Source File: E:\Especial Kelly Karaoke DVD\KELLY_MTVX20.ISO
I 21:32:31 Source File Sectors: 2,201,760 (MODE1/2048)
I 21:32:31 Source File Size: 4,509,204,480 bytes
I 21:32:31 Source File Volume Identifier: KELLY_MTVX20
I 21:32:31 Source File Application Identifier: NERO BURNING ROM
I 21:32:31 Source File Implementation Identifier: Nero
I 21:32:31 Source File File System(s): ISO9660, UDF (1.02)
I 21:32:31 Destination Device: [1:0:0] PIONEER DVD-RW DVR-112D 1.09 (H:) (ATA)
I 21:32:31 Destination Media Type: DVD-R (Disc ID: TYG02) (Speeds: 4x, 6x, 8x, 12x)
I 21:32:31 Destination Media Sectors: 2,297,888
I 21:32:31 Write Mode: DVD
I 21:32:31 Write Type: DAO
I 21:32:31 Write Speed: MAX
I 21:32:31 Link Size: Auto
I 21:32:31 Test Mode: No
I 21:32:31 BURN-Proof: Enabled
I 21:32:32 Filling Buffer... (20 MB)
I 21:32:32 Writing LeadIn...
I 21:33:01 Writing Image... (LBA: 0 - 2201759)
W 21:34:20 Waiting for buffers to recover...
W 21:34:24 Waiting for hard disk activity to reach threshold level...
I 21:34:49 Writing Image...
W 21:35:30 Waiting for buffers to recover...
W 21:35:36 Waiting for hard disk activity to reach threshold level...
I 21:36:10 Writing Image...
W 21:36:34 Waiting for buffers to recover...
W 21:36:42 Waiting for hard disk activity to reach threshold level...
I 21:37:27 Writing Image...
W 21:37:43 Waiting for buffers to recover...
W 21:37:45 Waiting for hard disk activity to reach threshold level...
I 21:37:47 Writing Image...
W 21:38:07 Waiting for buffers to recover...
W 21:38:10 Waiting for hard disk activity to reach threshold level...
I 21:38:18 Writing Image...
W 21:38:28 Waiting for buffers to recover...
W 21:38:35 Waiting for hard disk activity to reach threshold level...
I 21:40:30 Writing Image...
W 21:41:24 Waiting for buffers to recover...
W 21:41:29 Waiting for hard disk activity to reach threshold level...
I 21:41:34 Writing Image...
W 21:42:14 Waiting for buffers to recover...
W 21:42:20 Waiting for hard disk activity to reach threshold level...
I 21:42:55 Writing Image...
W 21:43:34 Waiting for buffers to recover...
W 21:43:36 Waiting for hard disk activity to reach threshold level...
I 21:43:41 Writing Image...
W 21:43:53 Waiting for buffers to recover...
W 21:43:56 Waiting for hard disk activity to reach threshold level...
I 21:44:01 Writing Image...
W 21:44:11 Waiting for buffers to recover...
W 21:44:19 Waiting for hard disk activity to reach threshold level...
I 21:44:28 Writing Image...
W 21:45:25 Waiting for buffers to recover...
W 21:45:34 Waiting for hard disk activity to reach threshold level...
I 21:45:38 Writing Image...
W 21:45:47 Waiting for buffers to recover...
W 21:45:50 Waiting for hard disk activity to reach threshold level...
I 21:45:54 Writing Image...
W 21:46:03 Waiting for buffers to recover...
W 21:46:09 Waiting for hard disk activity to reach threshold level...
I 21:46:25 Writing Image...
W 21:46:39 Waiting for buffers to recover...
W 21:46:46 Waiting for hard disk activity to reach threshold level...
I 21:46:55 Writing Image...
I 21:47:14 Synchronising Cache...
I 21:47:27 Image MD5: 448811071d9024864cc5f3addab1a384
I 21:47:28 Operation Successfully Completed! - Duration: 00:14:56
I 21:47:28 Average Write Rate: 5,168 KB/s (3.7x) - Maximum Write Rate: 17,407 KB/s (12.6x)


 

Any help would be greatly appreciated!

 

Thanks!

Link to comment
Share on other sites

Is it the device buffer or the application buffer or both that empty regularly ?

 

 

If its the device buffer there must be some issue with sending data to the drive then and that is not of ImgBurn's making.

 

Check your filter drivers using the free tool from http://www.bustrace.com and you can remove any crap filters you find.

 

You can put it's info in the clipboard and paste it on here if you like, then the boss or others with more knowledge can help point out the bad ones (if there are any).

Link to comment
Share on other sites

Try upping the buffer to 40MB.

 

It would seem your machine just wont sustain a constant flow of data from the hdd to the program's internal buffer.

 

As you have a new machine, I doubt this is the case, but are your drives sharing the same cable?

 

Whilst you're here, I'll just mention the ImgBurn 2.3.1.0 update, and firmware 1.15 for your Pioneer :)

 

Remember to check for updates or you'll get left behind!

Link to comment
Share on other sites

Both buffers empty out regularly after like a minute of burning. I will try that bustrace program when I get home :)

 

@LIGHTNING UK!: How do I increase the buffer to 40MB? Also, my HDD's aren't sharing the same cable because my HDD's are SATA disks.

 

Also, i've never tried upgrading firmware on drives before... is there a step-by-step guide I can look at to do it?

Link to comment
Share on other sites

You don't need to use the bustrace program now, I added a similar feature into ImgBurn under the Tools menu.

 

 

To change the buffer, click Tools -> Settings and switch to the I/O tab. On there you'll find a 'Buffer Size' slider bar thingy.

 

As for the firmware update, it's just like any other program. You download the firmware file and run it. It'll detect the drive and just ask you to confirm you want to update it - to which you simply press the 'Yes' button (or type the 'Y' key).

 

You can download the update for the 112D from here:

 

http://wwwbsc.pioneer.co.jp/cgi-bin/www1/d...12D_FW115EU.EXE

 

(Just click 'Agree' at the bottom of the page)

Link to comment
Share on other sites

Ok, I just tried what you told me to do lightning uk.

 

I increased my I/O buffer size to 40mb from 20mb. And then I also updated my DVR112 to the latest firmware (1.15). However, the same problem exists. Both buffers empty like crazy and then it slows my computer down like crazy!

 

If it might help with the problem solving, I am using Windows VISTA Ultimate 32-Bit...

Link to comment
Share on other sites

Ok, I just tried what you told me to do lightning uk.

 

I increased my I/O buffer size to 40mb from 20mb. And then I also updated my DVR112 to the latest firmware (1.15). However, the same problem exists. Both buffers empty like crazy and then it slows my computer down like crazy!

 

If it might help with the problem solving, I am using Windows VISTA Ultimate 32-Bit...

 

I am also having the same prob.. Haven't tried other media but these are "Maxell DVD-R" "6x 8x 12x 16x" (supposedly).

My drive should be capable of 8x? I get the hard drive problem 1-5 times. (It throttles back like it is suppose too, but I don't understand why it would have to do this?) (SATA Drive 60MB+ Rsec) (No other running programs.. I looked with Process Explorer during one burn). My buffer was 40MB this time.. same problem but it only throttled back once(!) Oh ya, once it throttles the speed back shouldn't it try and go back up to 8x again? (It always stays at 6x - with this media at least...) This is what bothers me the most.. or is it suppose to do this. Well overall I am very happy with your software. Thanks ahead of time!

 

BTW I just remembered. Maybe it is the media, as I recall I haven't really tried to burn at 8x until recently. I never noticed this problem (and my buffer use to be 20mb, too!) So dunno....?

 

 

I 12:23:58 ImgBurn Version 2.3.0.0 started!
I 12:23:58 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)
I 12:23:58 Total Physical Memory: 1,047,276 KB  -  Available: 546,548 KB
I 12:23:58 Initialising Patin-Couffin...
I 12:23:58 Patin-Couffin - VSO Software - Version 1.37.0.0 - Internal Revision 37
I 12:23:58 Searching for SCSI / ATAPI devices...
I 12:23:59 Found 1 DVD-ROM and 2 DVD?RWs!
I 12:34:02 Operation Started!
I 12:34:02 Source File: X:\Archives Extraction\Black.iso
I 12:34:02 Source File Sectors: 2,257,719 (MODE1/2048)
I 12:34:02 Source File Size: 4,623,808,512 bytes
I 12:34:02 Source File File System(s): ISO9660
I 12:34:02 Destination Device: [0:0:0] LITE-ON DVDRW SHW-160P6S PS0B (K:) (ATA)
I 12:34:02 Destination Media Type: DVD-R (Disc ID: MXL RG04) (Speeds: 6x, 8x, 12x, 16x)
I 12:34:02 Destination Media Sectors: 2,298,496
I 12:34:02 Write Mode: DVD
I 12:34:02 Write Type: DAO
I 12:34:02 Write Speed: 8x
I 12:34:02 Link Size: Auto
I 12:34:02 Test Mode: No
I 12:34:02 BURN-Proof: Enabled
I 12:34:03 Filling Buffer... (40 MB)
I 12:34:04 Writing LeadIn...
I 12:35:05 Writing Image... (LBA: 0 - 2257718)
W 12:36:27 Waiting for buffers to recover...
W 12:36:43 Waiting for hard disk activity to reach threshold level...
I 12:36:44 Writing Image...
I 12:44:27 Synchronising Cache...
I 12:44:45 Image MD5: 0047192665ab6fed00f5ea77945bb632
I 12:44:45 Exporting Graph Data...
I 12:44:45 Graph Data File: F:\Program Files\CD-DVD Stuff\ImgBurn\2007-04-11_LITE-ON_DVDRW_SHW-160P6S_PS0B_12-34_PM_MXL_RG04_8x.ibg
I 12:44:45 Export Successfully Completed!
I 12:44:45 Operation Successfully Completed! - Duration: 00:10:42
I 12:44:45 Average Write Rate: 8,048 KB/s (5.8x) - Maximum Write Rate: 11,316 KB/s (8.2x)
I 12:44:45 Cycling Tray before Verify...
W 12:44:53 Waiting for device to become ready...
I 12:45:05 Device Ready!
I 12:45:06 Operation Started!
I 12:45:06 Source Device: [0:0:0] LITE-ON DVDRW SHW-160P6S PS0B (K:) (ATA)
I 12:45:06 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: MXL RG04) (Speeds: 6x, 8x, 12x, 16x)
I 12:45:06 Image File: X:\Archives Extraction\Black.iso
I 12:45:06 Image File Sectors: 2,257,719 (MODE1/2048)
I 12:45:06 Image File Size: 4,623,808,512 bytes
I 12:45:06 Image File File System(s): ISO9660
I 12:45:06 Read Speed: MAX
I 12:45:06 Verifying Sectors... (LBA: 0 - 2257718)
I 12:50:28 Device MD5: 0047192665ab6fed00f5ea77945bb632
I 12:50:28 Image MD5: 0047192665ab6fed00f5ea77945bb632
I 12:50:32 Exporting Graph Data...
I 12:50:32 Graph Data File: F:\Program Files\CD-DVD Stuff\ImgBurn\2007-04-11_LITE-ON_DVDRW_SHW-160P6S_PS0B_12-34_PM_MXL_RG04_8x.ibg
I 12:50:32 Export Successfully Completed!
I 12:50:32 Operation Successfully Completed! - Duration: 00:05:22
I 12:50:32 Average Verify Rate: 14,023 KB/s (10.1x) - Maximum Verify Rate: 22,072 KB/s (15.9x)

Edited by bonecrusher
Link to comment
Share on other sites

I have no control over the speed the drive returns to using, it'll return to whatever speed it wants to.

 

If you watch the main buffer buring a burn, does it keep moving?

 

It should be rock steady at 100% the whole time - hdd transfer speeds and access times far exceed those of your burner.

Link to comment
Share on other sites

have you tried with another I/O interface ?

 

Funny that you say that. I just switched it a minute ago to SPTI and all is well (burned at 8.2x most of the way)!

 

@LIGHTNING UK!:

Ya, I figured, actually during the write I mentioned above(in *this msg* ^ not the one that slowed down to 6x), at first the image buffer fluctuated quite a bit (all above 80% though) then after 1/2 way through the burn it 'stabilized' at 99%+. SO there you go. Hopefully this is working right now. I am happy..

 

-

Thanks for the quick reply (to both of you)!

Edited by bonecrusher
Link to comment
Share on other sites

With all that memory why not try a buffer of 256MB?

Also, have task manager open before burning and, while the buffers are getting empty, check if any process is using an abnormal amount of CPU time.

By the way, how fragmented is your HD? I believe you can check it with Windows' Defrag.

Link to comment
Share on other sites

You really shouldn't need a buffer that big. Even at only 20mb, I never see mine fall below the maximum!

 

It could well be due to fragmentation, but then it could also be something with vista indexing your files or something.

 

Basically, if the program can't read the data fast enough to burn, *something* else must be using the drive too. It just doesn't make much sense otherwise.

 

There are various performance counters your could look at in perfmon but I don't know if you've seen that tool before / would be comfortable looking at it.

Link to comment
Share on other sites

Just click start -> run and then type in 'perfmon' (without quotes).

 

You should be able to get a nice graph of hdd activity before / during the burn etc.

 

It should be on almost nothing when not doing anything and increase a little when burning.

 

When you notice the buffer dropping off, it's probably busy and the hdd graph should show that.

Link to comment
Share on other sites

Ok, I tried that and my disk is usually at around 10MB/sec when the burning speed is set at 12x, is this good? Also, my cpu usage is roughly in between 10-40% so it seems fine on the CPU side...

 

Also, on the graph, there's the green plots and also the blue line. What does the blue line represent?

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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