Nothing burning at all

[OldSpice]

I've been in a constant battle with getting my laptop to burn images lately. I just did a fresh install of Windows Vista with SP1 hoping it'd help and it didn't. Just today I went out and bought a new DVD drive hoping it'd be the end all to my problems and it wasn't. My burns will usually get to about 8% then the buffers will drop to 0% and my burn will stop for about 10 minutes and will say my Hard drive has reached its threshold. It will start back up again when the buffers reach 100% but will only burn for about 10-15sec. I made sure that the drive is in DMA mode so that is not the issue. Also I tried deleting the UpperFilter/LowerFilter registry keys as I've read elsewhere which didn't help either. The only solution I have found is using an external DVD writer (USB), but would much rather prefer just being able to use my laptop's writer. Write speeds don't seem to have any effect on the problem either. Also, I would post a log but when I'm attempting to burn something my laptop refuses to do anything - meaning trying to do anything such as clicking the View>Log option takes about 20 minutes to open. I have no applications running, or resource heavy services/processes while attempting to burn. My laptop Specs are as follows:

 

Gateway P6831FX

Intel T5550 CPU @ 1.6

3GB Ram

Nvidia 8800m GTS 512

2x 200GB 7200RPM HDD in Raid0

Samsung S082H

 

It does this with all media, CD's, DVD's, DVD DL (Verbatim)

 

Thanks for any advice,

OldSpice

Edited October 27, 2008 by OldSpice

[mmalves]

Logs are saved automatically (look in Help menu -> ImgBurn Logs) so please post the log of the latest burn.

 

By the way, an external burner gives you better burn quality, especially on dual-layer media.

[LIGHTNING UK!]

Bring up task manager before you start burning.

 

Is the CPU% usage at 100% all the time during the burn? (which process is using it all up?)

 

If so, it still really seems as though DMA is the problem - regardless of you saying you've checked it or whatever.

 

Did you do your 'fresh install' and then put ImgBurn on BEFORE *anything* else and try it that way?

[OldSpice]

Bring up task manager before you start burning.

 

Is the CPU% usage at 100% all the time during the burn? (which process is using it all up?)

 

If so, it still really seems as though DMA is the problem - regardless of you saying you've checked it or whatever.

 

Did you do your 'fresh install' and then put ImgBurn on BEFORE *anything* else and try it that way?

 

 

No CPU usage is never above 10% while burning, only when the buffers raise again will the cpu usage spike. When I did a fresh install IMGBURN was one of the first things I installed and it burnt 2 things fine with no issues what-so-ever. After keeping the laptop shutdown for a few hours and booting back up to burn a few more discs it started giving me the issue again.

 

Log from latest burn:

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

; ImgBurn Version 2.4.2.0 - Log

; Monday, 27 October 2008, 18:36:40

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

;

;

I 18:36:28 ImgBurn Version 2.4.2.0 started!

I 18:36:28 Microsoft Windows Vista Ultimate Edition (6.0, Build 6001 : Service Pack 1)

I 18:36:28 Total Physical Memory: 3,143,360 KB - Available: 2,283,952 KB

I 18:36:28 Initialising SPTI...

I 18:36:28 Searching for SCSI / ATAPI devices...

I 18:36:28 Found 1 DVD

[volvofl10]

2 x 200gb hdd's ??

 

I'm wondering if your having overheating issues on 1 of the hdd's

I say that because i did with a 2 x hdd laptop, and like you i could burn to an external drive with no problem.

Poor chassis design of laptops cause overheat issues.

[LIGHTNING UK!]

Check event viewer too, it might show that there are errors on your hdd or something.

 

You can test if it's the hdd by burning a disc in discovery mode - where only memory is used because the data is made up on the fly.

[OldSpice]

Check event viewer too, it might show that there are errors on your hdd or something.

 

You can test if it's the hdd by burning a disc in discovery mode - where only memory is used because the data is made up on the fly.

 

Burning a disc in Discovery Mode worked 100% without any hitches. I my temperatures on the hdd's while burning seemed to be fine, screenshot below:

Edited October 28, 2008 by OldSpice

[LIGHTNING UK!]

How are your drives configured?

 

I'm sure a setup like that must be using SATA but on the off chance that there's some legacy PATA involved that could be where the problem is coming from.

 

PATA never did like 2 drives on the same channel being used at the same time. The use of the burner is probably preventing I/O to the hdds and hence your machine runs like a dog.

 

When you did that test burn in Discovery mode did you find that the machine stayed working just fine?

 

How about if you run hddtune on the hdds at the same time as burning. Do you notice any slowdowns in hdd read or DVD burn speed?

 

I assume you've got the latest intel matrix drivers installed (or whatever applies for your raid setup) ?

[volvofl10]

In RAID0 , isnt that like having 1 large drive instead of 2 smaller ones, where the data gets spread all over the place instead of going on just 1 of the drives ? causing an I/O error somewhere ( although not showing in IB log)

[LIGHTNING UK!]

Yeah a software read will be translated into 2 hardware reads so that the 'striped' data is read off both drives and then returned to the calling application as a normal chunk of data.

[OldSpice]

Yeah a software read will be translated into 2 hardware reads so that the 'striped' data is read off both drives and then returned to the calling application as a normal chunk of data.

 

Running HDDTune definately slowed my computer down entirely. My drives are set up in Raid0 both being SATA with a 100gb partition for my OS and the rest remaining for storage and my CD-Rom drive is just a normal slime drive for laptops.

[LIGHTNING UK!]

Ok, now see if you can verify a disc against an image on your hdd without the buffer being empty all the time.

 

It'll be interesting to see if the problem is just when you're burning to the drive or if it happens when you're reading from it too. The file on the hdd will be accessed in exactly the same way in both Write and Verify modes you see, so that bit is constant.

 

Did you check your intel matrix (raid) driver? I believe the latest version is 8.5 or something.