Esignal v10r3 Crashing several times a day

[RichardN]

In the last few weeks since upgrading to v10 I have experienced many crashes. Had 3 today. Started sending crash reports to esignal with the last crash. After the crash popup was this message:

The instruction at "0x5ad71531" referenced memory at "0x00000014". The memory could not be read. Click OK to terminate the program.

I was away from the computer for the better part of an hour and when I came back the crash popup was on the screen.

Sometimes when right clicking on a chart the drop down menu is missing the "Formulas" item and the Remove and Reload items. Unless I reboot my computer and restart esignal the crash will occur shortly thereafter.
Merely restarting Esignal will not fix the problem. I need to reboot to reestablish esignal.

I am running a Dell Inspiron 9400/E1705 with Windows XP and 2 gigs of RAM. I am using a Dell 24" external monitor. The Video Card is an NVIDIA GeForce Go 7900 GS with 256 mg RAM at 1920x1200.

I have seen other posts with similar problems posted so I don't think it"s just me. Thanks.

Richard

[zottl]

again and again. what and particularly when will eSignal do something against these failures? my impression is that eSignal is simply negating these problems. but why? it seems they want to loose customers.....

[RichardN]

Esignal crashed again yesterday 12/11 and again 12/12. Both times the was sitting idle. This did not happen in version 8.

Richard

[eSignal_AveryH]

Hello All,
Please PM me you username so that I can pull the crash reports to see if there is a pattern to the crashes you are receiving.

Thank you
AveryH

[eSignal_AveryH]

Thank you for sending the crash reports.

The crash reports are helpful to a point, they aren't something that tells us what the user was doing in the program or what exactly caused a crash. They point to an area of code that the application was in at the time of the crash. This can be helpful in looking into problems, but doesn't point to anything actual windows. It also doesn't guarantee that the true cause of the crash is in the area of code that the application was in at the time of the crash.

There are times when we get several reports a day and most of them are from various random areas in the code and are one time events. Our goal is to find groups of reports all coming from the same area of code which gives a clue that there's something to look into in that area. The best way to find and fix crashes is to gather as much information about what the user has and what they were doing when the crash occurred. You can help in this area by continuing to submit the report and in the comment area provided additional information about what you were doing or what the system was doing when the crash occurred.

Here’s what would help us pin point the problem you’re having:

• Does it only happen at start up?
• Are there any applications doing automatic updates (I.e. Norton Internet Securities, Windows Updates)
• Does it happen every time the application is launched?
• Which window were you in while the crash occurred?