ImgBurn 1.1 erase problem

[rapscallion]

Hi All,

No problem with the previous version, however after upgrading to V 1.1.0.0
every time I try to quick erase a DVD +RW it causes the pc to reboot spontaneously.

My other programs, Nero/ Easy CD Creator work just fine. Anyone elese have this problem ? (btw DVD Decrypter by same author also works fine)
PC is Compaq P4 2.4, 512mb ram, Plextor 708a burner. Thanks

[CWR03]

It would have to be a hardware issue. If you're running XP, upon reboot you should have the option to send an error report which on completion will give you more information and some possible solutions.

[rapscallion]

OS is Win 2K, with latest service pak and updates. Again, no problem w/other programs or previous ver of IMGBURN

[LIGHTNING UK!]

So full erase is ok?

Does it crash before or after you click 'Yes' to the following message box?

---------------------------
ImgBurn
---------------------------
Erase Disc - Quick

All data on the disc will be erased!

Do you want to continue?
---------------------------
Yes No
---------------------------


EDIT:

Infact, I've just compared 1.0.0.0 to 1.1.0.0 and there is only 1 minor difference.

Also, the bit that changed is actually run in several different places. Just by putting a disc in the drive that bit of could would have been run, so I've no idea where this system crash (JUST when doing a quick DVD+RW erase) is coming from.

As CWR03 said though, applications don't crash XP or 2000, it's drivers/hardware that do. As ImgBurn doesn't have any drivers of its own, it must be something else in your PC.

Find the memory dump file (or minidump in c:\windows\minidumps) and email it to me - unless you want to use WinDbg on it yourself of course. That WinDbg program will allow you to analyse the dump file and see which driver crashed the system. It's a microsoft tool, just search Google for it.

EDIT AGAIN:

I 18:15:29 Operation Started!
I 18:15:29 Device: [2:1:0] BENQ DVD DD DW1640 BSOB (K:) (ATA)
I 18:15:29 Media Type: DVD+RW (Disc ID: RICOHJPN-W11-01) (Speeds: 2.4x, 4x)
I 18:15:29 Quick Erase: Yes
I 18:15:29 Erasing Disc...
I 18:15:34 Synchronising Cache...
I 18:15:34 Operation Successfully Completed! - Duration: 00:00:05

Works ok here ;)

I'll be honest though I dont do quick DVD+RW erases, it's pretty pointless! So in that sense it wouldn't have even been tested by me since I implemented it way back in DVD Decrypter! I had done loads of DVD+RW full erases though and I always knew that worked ok.

[rapscallion]

So full erase is ok?

Does it crash before or after you click 'Yes' to the following message box?

snipped---------------------------
.
Hi Lightning,

Crashes after I click "yes" and full erase is OK.

Tried Windbg and just see "rubbish" when I try to open the "dmp" file. Will email the file to you.

[LIGHTNING UK!]

Ok well WinDbg wasn't really very helpful (not to me anyway, I'm an amature!)

This is it's output:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_8

TSS: 00000000 -- (.tss 0)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

LAST_CONTROL_TRANSFER: from 00000000 to 80466d69

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nt!KiTrap08+0x3e


FOLLOWUP_IP:
nt!KiTrap08+3e
80466d69 ?? ???

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTrap08+3e

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 427b58bb

STACK_COMMAND: .tss 0 ; kb

FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+3e

BUCKET_ID: 0x7f_8_nt!KiTrap08+3e

Followup: MachineOwner
---------


It's only listing it as a kernel error, not some 3rd party driver.

If I was having this problem (and having read what I've now read), I'd first check my motherboard bios was up to date.
Then I'd test my computers memory with something like MemTest+
Then I'd check my motherboard chipset drivers / ide drivers were up to date.

If you do all those and it still fails, you've got me stumped! I can't reproduce it my end and haven't seen anyone else with a problem the same as / similar to your own.

[LIGHTNING UK!]

Oh, there's one more thing you can do for me (please!)...

Put a DVD+RW disc in the drive and copy + paste the info from the window on the right when in 'Write' mode within ImgBurn.

Thanks.

[rapscallion]

Hi Again Lightning,

BTW what did you use in Windbg to open the dump file ? The only thing I could open the file with was "open crash dump", under the file menu, and I didn't see anything like what you posted.

Below is info you requested :

PLEXTOR DVDR PX-708A 1.11 (ATA)
Current Profile: DVD+RW

Disc Information:
Status: Complete
Erasable: Yes
Formatted: Yes
Supported Write Speeds: 2.4x, 4x

Physical Format Information (ADIP):
Disc ID: MKM-A02-00
Book Type: DVD+RW
Part Version: 2
Disc Size: 120mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 2,491,711
Last Physical Sector in Layer 0: 0

Physical Format Information (Last Recorded):
Disc ID: MKM-A02-00
Book Type: DVD+RW
Part Version: 2
Disc Size: 120mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 2,491,711
Last Physical Sector in Layer 0: 0

Current Format Capacity:
Sectors: 2,295,104
Size: 4,700,372,992 bytes
Time: 510:03:29 (MM:SS:FF)

Maximum Format Capacity:
Sectors: 2,295,104
Size: 4,700,372,992 bytes
Time: 510:03:29 (MM:SS:FF)


Incidentaly, don't know if this matters, but I recently installed Sygate Personal Firewall. I'm going to try a disable and see if that makes a difference.
I don't remember if it was before or after I upgraded to v1.1

[LIGHTNING UK!]

See, that 'Current Format Capacity' and 'Maximum Format Capacity' is the ONLY thing that got changed in the function that does a quick erase on DVD+RW.

The difference between quick and full is that quick just writes zeros to the first few sectors. Full actually sends the 'format' command to the drive.

I don't see how writing to the disc can reboot your pc or it would do the same when you try to burn!

It's all very odd if you ask me!


As for WinDbg, yeah that's how I opened it.

You load the file via 'open crash dump' and then do what it says and type '!analyze -v' or something. You also need to have downloaded/installed all the symbol files into c:\windows\symbols

[rapscallion]

Thanks Lightning for all your responses....I'll just do the full erase from now on.

As far as WinDgb, I didn't have the symbol files installed. Thanks