Jump to content
Sign in to follow this  
Big10

EAccessViolation error when starting ImgBurn

Recommended Posts

Not sure if it's a bug or incompatibilty issue - but I get "EAccessViolation" error when starting ImgBurn. I have to try a few times before it actually starts.

Event viewer shows Event ID 1000: Faulting application imgburn.exe, version 1.0.0.0, faulting module imgburn.exe, version 1.0.0.0, fault address 0x000a78c7.

 

Any ideas?

Share this post


Link to post
Share on other sites

What exactly is on the screen when that happens?

 

Has the program actually loaded at all?

 

Has the splashscreen come up?

Share this post


Link to post
Share on other sites

It's not bad RAM - it's the only program on my PC that does that.

 

The program starts loading - the splashscreen with "Imgburn Loading...Please wait" and on top of it is the error window.

If I click OK on the error window, the Windows error window comes up :

Imgburn.exe has encountered a problem and needs to close.

When I click on the Close button another error window comes up:

Access violation at address FFFFFFFF Read of address FFFFFFFF.

Those keep coming up until I close Imgburn from the Task Manager.

post-127-1128541607_thumb.jpg

post-127-1128541640_thumb.jpg

post-127-1128541666_thumb.jpg

post-127-1128541688_thumb.jpg

Edited by Big10

Share this post


Link to post
Share on other sites

Hello again :)

 

Any chance I could mail you another version with some debugging info in it to help me?

 

If so, please email me at the address in the programs 'About' box.

Share this post


Link to post
Share on other sites
Hello again :)

 

Any chance I could mail you another version with some debugging info in it to help me?

 

If so, please email me at the address in the programs 'About' box.

 

Did you get my PM?

 

I found a workaround to start the program - haven't actually used it yet. I run the program in compatibilty mode of NT4 + SP5 . For some reason this works. I have a problem with Nero Infotool that get's stuck, and this was a solution I found on one of the boards. I thought it might work here as well - and it does.

Does this give you a clue?

Share this post


Link to post
Share on other sites

There are a couple of differences if you use NT4 and the SPTI I/O manager.

 

Shouldn't be anything major though, and leaving it without that compatibility setting certainly shouldn't crash things!

Share this post


Link to post
Share on other sites

There are a couple of differences if you use NT4 and the SPTI I/O manager.

 

Shouldn't be anything major though, and leaving it without that compatibility setting certainly shouldn't crash things!

 

Turn that thing off again and try to start the program whilst pressing down the F7 key. That'll disable all the I/O stuff and it may offer more clues!

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

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