roman2
-
Posts
5 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by roman2
-
-
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.
-
Thanks a lot!
I'll be more careful next time
-
That is, system's perfomance slows down and it's the reason of "waiting" or not? How to avoid that?
-
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
Burn Thread Runtime Exception,Error EinvalidOp
in ImgBurn Bugs
Posted
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.