Jump to content

Burn Thread Runtime Exception,Error EinvalidOp


GiORGiOLA

Recommended Posts

I download wii games from espalwii, I've just burned 10 games but sometimes, while I'm burning on ImgBurn compares this error :

BURN THREAD RUNTIME EXCEPTION, ERROR EINVALIDOP.

What does it means?

Until now I discarded 4 DVD!!! My God!!

I use Verbatim DVD-R , 4x speed, I have a Vaio laptop with Vista and PIONEER DVD-RW DVR-K17 1.00 (ATA) recording inside.

 

Help me!!!

Link to comment
Share on other sites

I download wii games from espalwii, I've just burned 10 games but sometimes, while I'm burning on ImgBurn compares this error :

BURN THREAD RUNTIME EXCEPTION, ERROR EINVALIDOP.

What does it means?

Until now I discarded 4 DVD!!! My God!!

I use Verbatim DVD-R , 4x speed, I have a Vaio laptop with Vista and PIONEER DVD-RW DVR-K17 1.00 (ATA) recording inside.

 

Help me!!!

 

 

Italian.

 

Do you know the problem?

Link to comment
Share on other sites

I have the same problem , it's the first time that i have this problem , i always used imgburn to burn iso files without problems .

 

can any one help :unsure:

Edited by bigie
Link to comment
Share on other sites

  • 3 weeks later...

Hello,

 

I got the same error for the first time...

ImgBurn.log was attached...

Other information (may be useful?):

 

TSSTcorp CDDVDW TS-L633L 0400 (ATAPI)

Current Profile: DVD+R DL

 

Disc Information:

Status: Incomplete

Erasable: No

Sessions: 1

Free Sectors: 2 720 352

Free Space: 5 571 280 896 bytes

Free Time: 604:33:27 (MM:SS:FF)

Supported Write Speeds: 3x; 4x; 6x

 

DVD

ImgBurn.log

Link to comment
Share on other sites

Don't be using the hard drive with the image file on it for anything else when you burn.

 

Any other access will force the drive to start random accessing and that's slow. Burning requires a nice steady stream of data and the buffer will only help out for so long.

Link to comment
Share on other sites

I've tried setting my locale to Russian and forcing buffer recovery to kick in (for about 2 minutes!) and I couldn't get it to crash.

 

If you can reproduce the error (when burning to a rewritable so you don't waste discs!), please let me know and maybe we can try to figure out the root cause of the problem.

Link to comment
Share on other sites

ooo, sorry... I forgot to add that process ImgBurn.exe hung and it utilized CPU about 50% after error occured.

I created the process dump and paid attention to stack of thread (exception handler):

0:000> !runaway
User Mode Time
 Thread       Time
  0:a44       0 days 1:10:52.696
  2:cdc       0 days 0:00:00.000
  1:1550      0 days 0:00:00.000
0:000> kb250
ChildEBP RetAddr  Args to Child              
0012f82c 779c8c24 76a9863e ffffffff 3aa471be ntdll!KiFastSystemCallRet
0012f830 76a9863e ffffffff 3aa471be 00000000 ntdll!ZwQueryVirtualMemory+0xc
0012f850 76a98667 ffffffff 3aa471be 0012f888 kernel32!VirtualQueryEx+0x1d
0012f868 76a76f0b 3aa471be 0012f888 0000001c kernel32!VirtualQuery+0x15
0012f8b4 76aef584 3aa471be 003206c8 e656722a kernel32!BasepFillUEFInfo+0x19
*** WARNING: Unable to verify checksum for ImgBurn.exe
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ImgBurn.exe - 
0012f940 0084a3aa 0012f958 00000000 00000000 kernel32!UnhandledExceptionFilter+0xd5
WARNING: Stack unwind information not available. Following frames may be wrong.
0012f960 779c9b99 0012fa4c 0012ff78 0012fa68 ImgBurn!Pngspeedbuttoninitialization$qqrv+0xe56ce
0012f984 779c9b6b 0012fa4c 0012ff78 0012fa68 ntdll!ExecuteHandler2+0x26
0012fa34 779c99f7 0012fa4c 0012fa68 0012fa4c ntdll!ExecuteHandler+0x24
0012fa34 00793abe 0012fa4c 0012fa68 0012fa4c ntdll!KiUserExceptionDispatcher+0xf
0012fd30 00787ecd 007e4360 01e975d0 0451a168 ImgBurn!Pngspeedbuttoninitialization$qqrv+0x2ede2
00000000 00000000 00000000 00000000 00000000 ImgBurn!Pngspeedbuttoninitialization$qqrv+0x231f1

The code below (into module ImgBurn.exe)

00793abe 8b08 mov ecx,dword ptr [eax]

generated access violation exception. Next, exception handler was executed and it didn't handle this type of exception, and exception was raised again and again in cycle.

Link to comment
Share on other sites

I've tried setting my locale to Russian and forcing buffer recovery to kick in (for about 2 minutes!) and I couldn't get it to crash.

hmmm... I enabled/disabled bluetooth and sent file through its during burning. I don't know what and how, but, may be, there were some resource contentions due to that.

Link to comment
Share on other sites

It's really just the first error that I need to look into (i.e. the one below), the access violations will be from the burn thread being killed.

 

E 15:50:35 BurnThread Runtime Exception! - Message: EInvalidOp

 

Reading and writing to the same drive several times whilst burning will cause buffer problems.

 

I made the error occur by burning a 2GB ISO file that was on a USB pen and copying that same ISO back to a hard drive at the same time.

USB pens are slow anyway so doing that just totally killed it!

 

If there's any way you can make the buffer problem happen again without too much messing around, let me know and I'll send you a special debug version of the program to try and narrow down the problem area.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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