Memory Error Issue

[nailgunner]

For about a week, I've been receiving the following error message when I shut down or restart. Application error in shutting down MagicJack. "The instruction at 0X...... referenced memory at 0X..... . The memory could not be read. Click OK to terminate." The referenced memory address changes with each error message. With the MagicJack unplugged or not running, there obviously is no error. I have tried un and re installing it several times with no luck. There have been numerous MagicJack issues of late, but it hasn't gone away and I seem to be the only one with this particular issue. The MJ forum has not been useful. I assume memory errors are not a good thing. Am I in danger of my device failing or is something worse about to happen. Thanks for any input.

 

[richc46]

Lets be sure it is not actually memory
Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[nailgunner]

Thanks for the suggestion. I ran two passes with no error messages. Man is that thing slow. I will run the full 7 pass test overnight, but it looks like the memory is good.

 

[richc46]

It may take the full 6 passes to show accurate results, some feel that 10 is even a better number. Do not rush, lets be sure that we can rule out ram problems before moving on.

 

[nailgunner]

Okie dokie. I'll set it up for the overnight passes and see how many it can do in 8-10 hours.

 

[nailgunner]

OK, I did an additional 8 passes, still with no errors.

 

[richc46]

The problem apparantly is on the part of MJ. If the initial question were I am getting this error message and what should I do, the answer would be do not use MJ.
You could look at the event viewer (type that in Search) and look at the errors that are present, but thats about all that I can think of.

 

[nailgunner]

The problem apparantly is on the part of MJ. If the initial question were I am getting this error message and what should I do, the answer would be do not use MJ.
You could look at the event viewer (type that in Search) and look at the errors that are present, but thats about all that I can think of.

I appreciate the input. I checked the event viewer and the errors all have the same exception code 0cx0000005. After searching, it appears to be a fairly common exception code. Now comes the feeling like a fool for 5 minutes questions. In general, if I continue to use MJ, am I only in danger of damaging the MJ device and/or MJ software? Or am I in danger of really screwing up the computer?

 

[richc46]

I think the worst that could happen to the computer is a BSOD, which is a pain, but can be corrected, since it will be a software rather than hardware problem.
Not familiar with MJ, I would assume that the software could become corrupted, to some extent.

 

[nailgunner]

Thanks again for the input. I will use the logic that I have used so much in my life and has gotten me in tons of trouble. My memory is checking out OK. It appears to be a MJ only problem. Only getting the error message when I shut down or reboot. If I unplug the MJ device before reboot, there is no error message. So I will roll the dice, unplug the device when I reboot and keep my fingers crossed. The device is $20 and $20 a year for the service. My year is almost up, so I will "invest" another $20 for a new device at that time. I really appreciated the help.

 

[Wishmaster]

I agree this would be a issue with MJ itself, and not the systems fault.

You do not have the PageFile disabled do you?


"The instruction at 0X...... referenced memory at 0X..... . The memory could not be read" Sounds It as if MJ is attempting to write and/or read from memory that is outside its allocated range for whatever reason generating the error.


You may want to try contacting customer support and have them send you a fresh copy of the MJupdate.
Uninstall the current version, and install the new one they give you.

 

[smarteyeball]

"The instruction at 0X...... referenced memory at 0X..... . The memory could not be read" Sounds It as if MJ is attempting to write and/or read from memory that is outside its allocated range for whatever reason generating the error.

+1

Bad programming.

 

[nailgunner]

I agree this would be a issue with MJ itself, and not the systems fault.

You do not have the PageFile disabled do you?


"The instruction at 0X...... referenced memory at 0X..... . The memory could not be read" Sounds It as if MJ is attempting to write and/or read from memory that is outside its allocated range for whatever reason generating the error.


You may want to try contacting customer support and have them send you a fresh copy of the MJupdate.
Uninstall the current version, and install the new one they give you.

Thanks for the input. I have windows managing the PageFile, so it is active. I have un and re installed the MJ a few times during this issue. The reinstall is done automatically when you plug the device in. As a side note, this is also how they put through updates, with no notice or option. The device does not even let you run an older version, as soon as you try, it forces the update through, so after the uninstalls, I have the latest update.

 

[nailgunner]

"The instruction at 0X...... referenced memory at 0X..... . The memory could not be read" Sounds It as if MJ is attempting to write and/or read from memory that is outside its allocated range for whatever reason generating the error.

+1

Bad programming.

In your opinion then, as long as I'm happy with how the device is working, that I should be safe running the device as is?

 

[Keiichi25]

There have been some varying reports with Magic Jack, so there is a possibility that MJ will have some weird quirks.

Just out of curiosity, are you dead set on MJ, or willing to use other kinds of VOIP services?

 

[nailgunner]

There have been some varying reports with Magic Jack, so there is a possibility that MJ will have some weird quirks.

Just out of curiosity, are you dead set on MJ, or willing to use other kinds of VOIP services?

Pretty dead set. There have been TOO many quirks with it lately, but nothing big. I'm getting good quality with my setup, and after the initial $20 for the device, you can't beat $20 a year for phone service. Unless of course I have to keep buying a new device. But after 10 months of use, I'm basically happy.

 

[smarteyeball]

Apart from the shutdown/reboot bug - If the majority of the time it's functioning fine, you should be good to go.

Prior to shutdown, have you tried killing the associated process in Taskmanager?

 

[nailgunner]

Apart from the shutdown/reboot bug - If the majority of the time it's functioning fine, you should be good to go.

Prior to shutdown, have you tried killing the associated process in Taskmanager?

Yea, I tried that with no success. If the device is unplugged, and I reboot, no error. But with just stopping the process the error is still there.

 

[nailgunner]

Apart from the shutdown/reboot bug - If the majority of the time it's functioning fine, you should be good to go.

Prior to shutdown, have you tried killing the associated process in Taskmanager?

Yea, I tried that with no success. If the device is unplugged, and I reboot, no error. But with just stopping the process the error is still there.

That didn't make sense, so I tried it "again" and stopped the process and rebooting did make the error go away. I have tried a whole bunch of stuff over the last few days, including stopping the process a few times, but I may not have rebooted right after, because that does have the same effect as unplugging the device.

 

[smarteyeball]

Have you tried their support? magicJack - Tech Chat Knowledgebase/FAQ

It sounds like that killing the process isn't sufficient enough to signal to 7 that device is 'done', so as far as 7 is concerned it's still 'active', hence the crash.

That didn't make sense, so I tried it "again" and stopped the process and rebooting did make the error go away. I have tried a whole bunch of stuff over the last few days, including stopping the process a few times, but I may not have rebooted right after, because that does have the same effect as unplugging the device.

If you kill the process and don't reboot/shutdown straight away, there's a fair chance that the process is re-starting.