The instruction at "0x7c911e58" referenced memory at "0x00000067". the memory could not be read. ?? Any help would be appreciated
Error
Moderators: fgagnon, nikos, Site Mods
-
fgagnon
- Site Admin

- Posts: 3737
- Joined: 2003 Sep 08, 19:56
- Location: Springfield
Are you using the latest version? [1.0.0.3]
There had been reports of crashing on exit in v1.0.0.0 & some in v1.0.0.1
But, other than that, & my not being clairvoyant, a little more information could be helpful ...
Like what had you been last doing with x2, what version, what OS, whether it always happens, or only if you had done something specific during the session, is this a new installation, etc.
There had been reports of crashing on exit in v1.0.0.0 & some in v1.0.0.1
But, other than that, & my not being clairvoyant, a little more information could be helpful ...
Like what had you been last doing with x2, what version, what OS, whether it always happens, or only if you had done something specific during the session, is this a new installation, etc.
-
MrKlean
- Member

- Posts: 29
- Joined: 2003 Oct 23, 21:27
Thanks for the reply ; ) It doesn't happen ALL the time. I'm using the latest lite version on a laptop with XP Home edition. I haven't found a rhyme or reason as of yet ; ) As far as I remember, I was just looking at directories, nothing earth shattering
Just thought you might have heard of it before and know what was happening. It never hurts to ask ; )
-
fgagnon
- Site Admin

- Posts: 3737
- Joined: 2003 Sep 08, 19:56
- Location: Springfield
Everybody hates intermittants (non-reprodicible "issues")
I take it that the problem occurs often enough to be an anoyance (on the order of a couple of times every dozen times you use x2.)
As this has not been reported for the most recent x2 version, I would encourage you to pay attention (keep a log in your head if not on paper) of the things you do with x2, and see if you can't establish a pattern.
Likewise, if there are other x2 users who are seeing occasional "crash on exit" behaviour, please describe what you can about the issue as you see it, and post it here on the board.
{For example, there was an issue which prevented x2 from closing properly (before v1.0.0.3) if the user had used the quick viewer to preview media files AND if the installed of WinMediaPlayer was a particular version. -- These sorts of dependencies are often hard to track down, and shared experience can be helpful.}
Thanks
I take it that the problem occurs often enough to be an anoyance (on the order of a couple of times every dozen times you use x2.)
As this has not been reported for the most recent x2 version, I would encourage you to pay attention (keep a log in your head if not on paper) of the things you do with x2, and see if you can't establish a pattern.
Likewise, if there are other x2 users who are seeing occasional "crash on exit" behaviour, please describe what you can about the issue as you see it, and post it here on the board.
{For example, there was an issue which prevented x2 from closing properly (before v1.0.0.3) if the user had used the quick viewer to preview media files AND if the installed of WinMediaPlayer was a particular version. -- These sorts of dependencies are often hard to track down, and shared experience can be helpful.}
Thanks
-
MrKlean
- Member

- Posts: 29
- Joined: 2003 Oct 23, 21:27
-
hpp3
- Member

- Posts: 51
- Joined: 2004 Jun 04, 15:36
Hey fgagnon, (or any other x2 acolytes) is that debug app that came with the x2 Betas still floating around? That might come in quite handy tracking down these last few "once in a dozen" bugs. I think it was called "dbmon" or some such. You would start it before opening x2 and it would keep a log of everything that came across as it was running.
Oh wait, (I just did a quick search) here it is:
http://www.ps.ic.ac.uk/~umeca74/dbmon.zip
although it doesn't work with 1.0.0.3...
Nevertheless, there it is.
Oh wait, (I just did a quick search) here it is:
http://www.ps.ic.ac.uk/~umeca74/dbmon.zip
although it doesn't work with 1.0.0.3...
Nevertheless, there it is.
-
fgagnon
- Site Admin

- Posts: 3737
- Joined: 2003 Sep 08, 19:56
- Location: Springfield
debug monitors only work for special software builds that are compiled to give a 'trace' output. (aka debug builds).
The released versions of x2 don't have that output.
However, nikos has been known to provide a special debug build to folks who are willing to work on specific problems. But they don't always help. Often as not, a simple awareness of "what you are doing when" can be more helpful.
The released versions of x2 don't have that output.
However, nikos has been known to provide a special debug build to folks who are willing to work on specific problems. But they don't always help. Often as not, a simple awareness of "what you are doing when" can be more helpful.
-
mario_a
- Member

- Posts: 20
- Joined: 2004 Oct 03, 18:08
Hi fgagnon,
Since x2 displays the same context menu that Windows Explorer does when a file or folder is right - clicked, it must load any shell extensions that have been installed. These shell extensions dlls remain resident in memory until x2 exits, which is when they are unloaded from memory. Now, if a shell extension dll attempts to executes some buggy code when it is unloaded, a crash will occur in the program (exe) which loaded the dll, in this case, "xplorer2.exe".
On my computer (Win XP, SP1) , disabling a shell extension called "IZArcCM.dll", which belongs to a freeware zip utility named IZArc, makes the problem go away.
If any one has IZArc installed (MrKlean?), the crash on exit can easily and reliably reproduced by following these steps:
1) Start x2.
2) Right click on any file or folder (This will load all shell extension dlls).
3) Exit x2.
A similar crash also occurred sometimes when Windows Explorer was shutting down (Windows Explorer also obviously needs to load all the shell extension dlls ). But since Explorer only shuts down when the computer is shutting down, it was difficult to catch the momentary error message that was displayed just before Windows shut down.
Its very likely that the crash MrKlean is reporting is also being caused by some rogue third - party shell extension that is installed (maybe even IZArc's !).
I've posted this problem to the IZArc forum (Link), but the author seems to be terribly busy right now, so it may be awhile before we hear from him.
Hope this helps.
I've been experiencing errors similar to what MrKlean reported (The instruction at "0xXXXXXXXX" referenced memory at "0xXXXXXXXX) when I exit xplorer2 Lite, and I think I've finally been able to identify and isolate the problem.fgagnon wrote: Likewise, if there are other x2 users who are seeing occasional "crash on exit" behaviour, please describe what you can about the issue as you see it, and post it here on the board.
Since x2 displays the same context menu that Windows Explorer does when a file or folder is right - clicked, it must load any shell extensions that have been installed. These shell extensions dlls remain resident in memory until x2 exits, which is when they are unloaded from memory. Now, if a shell extension dll attempts to executes some buggy code when it is unloaded, a crash will occur in the program (exe) which loaded the dll, in this case, "xplorer2.exe".
On my computer (Win XP, SP1) , disabling a shell extension called "IZArcCM.dll", which belongs to a freeware zip utility named IZArc, makes the problem go away.
If any one has IZArc installed (MrKlean?), the crash on exit can easily and reliably reproduced by following these steps:
1) Start x2.
2) Right click on any file or folder (This will load all shell extension dlls).
3) Exit x2.
A similar crash also occurred sometimes when Windows Explorer was shutting down (Windows Explorer also obviously needs to load all the shell extension dlls ). But since Explorer only shuts down when the computer is shutting down, it was difficult to catch the momentary error message that was displayed just before Windows shut down.
Its very likely that the crash MrKlean is reporting is also being caused by some rogue third - party shell extension that is installed (maybe even IZArc's !).
I've posted this problem to the IZArc forum (Link), but the author seems to be terribly busy right now, so it may be awhile before we hear from him.
Hope this helps.
Regards,
Mario
Mario
-
nikos
- Site Admin

- Posts: 16344
- Joined: 2002 Feb 07, 15:57
- Location: UK
-
MrKlean
- Member

- Posts: 29
- Joined: 2003 Oct 23, 21:27
-
fgagnon
- Site Admin

- Posts: 3737
- Joined: 2003 Sep 08, 19:56
- Location: Springfield
-
MrKlean
- Member

- Posts: 29
- Joined: 2003 Oct 23, 21:27
-
narayan
- Platinum Member

- Posts: 1430
- Joined: 2002 Jun 04, 07:01
-
MrKlean
- Member

- Posts: 29
- Joined: 2003 Oct 23, 21:27