Gets stuck when releasing buffer

[Singh400]

Long time user of ImgBurn here, from the beginning pretty much.

 

However, tried to burn a 3.15 GB bootable ISO yesterday and found ImgBurn got "stuck" when trying to release the Buffer.

 

OS: Vista x64 Ultimate with SP1

Optical Drive: Pioneer DVR-215BK

RAM: 4GB

CPU: Q9450 3.60Ghz

ImgBurn ver: Latest one available

 

My account is Adminstrator on the machine. And I have tried burning with User Account Control on and off.

 

Now the only thing that I have changed is that instead of using Verbatim DVDR+R, I'm using Verbatim DVD-R. Along with disabling built in Windows burning features - however this should not effect 3rd party burning tools such as ImgBurn.

 

Tried to burn the same image twice, first time round it got stuck at 40% when trying to release the buffer. Then after a hard reboot, I tried again and it got stuck at 97% when trying to release the buffer.

 

It appears the disc burns fine, because after a hard reboot I can read it fine. But when I try to verify it the same thing happens. ImgBurn just gets "stuck". And I have to hard reboot the computer.

 

Cheers for any help.

 

PS, When I say buffer, I do not mean Device Buffer.

 

Edit* I don't have the log file to hand. I will post it up as soon as I get home.

Edited January 8, 2009 by Singh400

[LIGHTNING UK!]

Does the status bar actually say it's deleting the buffer?

 

If not, what does it say?

[Singh400]

Can't remember off by heart, will check as soon as I get home from work. Cheers for the quick reply.

 

I have tried leaving it for 10 mins+ just to see if it resolves itself, it doesn't. The time just says "Time Remaining: Unknown"

[Singh400]

Ok so I am finally home (yay)

 

I think I've fixed it.

 

This is how:

1) Open ImgBurn settings

2) Reset ALL settings

3) Close ImgBurn

4) Uninstall ImgBurn

5) Restart

6) Install ImgBurn (download fresh copy)

7) Leave everything at default settings

8) Burrnn

 

I've just Burnt and Verified the same image I was trying to burn last night.

 

However, I suspect this was a problem with my computer and not ImgBurn - it has been playing up last few days.

 

I will now try to burn and verify again with my settings, instead of default settings.

[Singh400]

Must be something wrong with the settings I'm using. It's happened again. But this time it's gotten stuck during the burning process. Status is just "writing sectors" and the log file has no errors. Looks like I'm stuck with the default settings.

[LIGHTNING UK!]

The default settings are the best anyway, that's why they're the defaults!

 

That said, if your hardware was behaving itself properly, there's nothing you could change to actually stop it from working.

[Singh400]

Confirmed, it's my settings Just did another reset all settings (back to default settings) and it burnt flawlessly Oh welll, I'm stuck with default settings. Cheers for all the help

[LIGHTNING UK!]

What exactly were you changing?!

[Singh400]

Nothing major. The only biggie was changing the buffer from default to max which is 512 RAM. And seeing as I have 4GB of RAM that isn't an issue.

[Singh400]

Tried 3 different media types yesterday, all failed to burn with my settings. But fine with default settings.

 

Gut feeling says it's size of the buffer. Funny thing is that I've burnt an image before with my settings on this same PC with the same setup without a problem.

 

Is there anyway I can get ImgBurn to log/show everything that happens? Like an advanced log?

[LIGHTNING UK!]

Nope

[Singh400]

Any idea on how I can resolve this then? I've ruled out media, the drive. Must be either a Windows setting or ImgBurn quirk somewhere.

[LIGHTNING UK!]

Nope, sorry.

 

If the program doesn't throw up an error when it calls the VirtualAlloc API function to allocate the memory then as far as it knows, everything is fine.

 

If the machine then has problems with me trying to write to the allocated memory I'm afraid it's out of my hands.

 

Have a play around and try to work out the limit for what you can set it to. Personally I've never seen a need to go over the default value.

 

You could also try running memtest+ for a few hours / passes.

[Singh400]

The memory is fine. I've stress tested this rig for 24hrs+ when I OCed it a couple of months back. But I will do memtest+ again overnight tonight.

 

Think I'm going to re-enable Windows burning and see if that makes a difference.

[mmalves]

The most that can do is hold the drive so that ImgBurn can't lock it for exclusive access, but you're free to try

[Singh400]

I've never been beaten by a computer problem before and it won't start now thats for sure. I will find out whats happening. Even if I have to go through my 100 Verbatim Spindle.

[mmalves]

If you burn with Test Mode enabled does it also freeze?

[Singh400]

Ok errrr just reset default settings, and changed it back to my settings, and burnt with my settings. And it worked. Did it twice to make sure it wasn't a fluke. No idea wtf is going on. Media hasn't changed, nothing on my computer has changed. Think ImgBurn had a hangover

 

I 21:51:32 ImgBurn Version 2.4.2.0 started!

I 21:51:32 Microsoft Windows Vista Ultimate x64 Edition (6.0, Build 6001 : Service Pack 1)

I 21:51:32 Total Physical Memory: 4,192,380 KB - Available: 3,104,676 KB

I 21:51:32 Initialising SPTI...

I 21:51:32 Searching for SCSI / ATAPI devices...

I 21:51:52 Found 1 DVD