XYplorer Beta Club

Don't know if this is a bug or system problem, but it only happens when XYplorer is running. Sometimes it happens while I am using XYplorer and sometimes it happens while I am working in an another application with XYplorer just sitting idle in the background. Without warning I will get an error message as follows.

***************************************
XYplorer
The instruction at xxxxxxxx referenced at xxxxxxxxxx. The memory could not be "read".
Click OK to terminate or Click Cancel to Debug.
***************************************
Then XYplorer shuts down.
(xxxxxxxx = random memory addresses that are never the same)

I have run several different tests on my RAM memory and get no errors. I also scanned with a number of virus programs to make sure I'm not infected with anything.
I tried to attach the Dr. Watson error log and memory dump for anyone that has the expertise to understand what might be happening, but no matter what I try this board gives me an error message that ".log, or .txt" file attachments are not allowed.

Thanks for any help.
PS. I should also mention that this started happening while I was still using version 6, and is still happening with the current version.

I've had the same thing a few times recently! Though at moment, I'm not quite up to current on vers...

It seemed to mostly occur to me when i've had XY in background for a loooooong time and went to do a 'save all setting's' or close XY prior to putting laptop in stand-by...

I have been trying to debug this problem but the Dr Watson reports keep mentioning that certain symbols are missing. I went to the developers site and grabbed all the Windows symbol files they recommended but out of all those hundreds of symbols something is still missing.

David40 wrote:PS. I should also mention that this started happening while I was still using version 6, and is still happening with the current version.

This is a long time. And since I don't get this issue from other users I'm inclined to think it's something with your system.

Anyway, any conditions to narrow it down will be helpful.

I think it might be related to virtual memory.
I used to notice this sometimes if I was rendering or conforming and had several programs running. If I switched to XY there would be a delay while memory swapped, and then XY would either lock out with max CPU usage, or crash.

I should add than on 2010-04-14 the user told me via email the following:

Turns out this may have been a hardware problem. Even though the memory tested OK I remembered I had overclocked the CPU by 10% and set the chipset to Turbo. I went into the BIOS and dropped the overclocking to 5% and turned off the Turbo mode. I haven't had an XYplorer crash since. There must be something about the way XYplorer accesses memory that causes a memory read error at the higher speeds. So, everything seems to be working OK now.