Topic awaiting preservation: Application error (Page 1 of 1)

These errors started about a month ago have become progressively more abundant lately. At first these errors appeared when closing Internet Explorer and now have started showing themselves at the opening of almost every program on my computer. Winamp, Outlook Express, Trillian, ect. It then prompts me either to click "Ok" or "Cancel" and both immediately close the program or application. Running Windows XP.

Example:

quote:

---

Instruction at "XXXXXXXXX" referenced Memory at "0x000000000". The memory could not be "read".

---

[This message has been edited by Kriek (edited 02-26-2003).]

Kriek: Not the kind of hassle you want for your birthday

___________________
Emps

FAQs: Emperor

Wow, I haven't seen those types of errors since Windows 98.

Okay, first of all, if you could write down the exact addresses of the instruction and the memory that might help. If the program did reference memory location 0x000000000 then that is a problem because that is a reserved address.

Now, I saw this exact problem a lot with Windows 98 and it was either one of 2 things. Either your software is corrupt somewhere (i.e. faulty dll files, corrupt executables) or you have bad RAM.

Try swapping out your RAM chips one by one. If that clears up the error, than you just need to buy new ram.

If the error still isn't cleared up, try to download the IE install files from microsoft's website on another computer. Than, you can run the install on your computer, and you should have an option to repair your IE installation. If this doesn't work, try a new installation.

That's how Windows XP displays memory errors.

Usually it's just a bug in a program. In your case it sounds like it may be more serious.

I meant that the type of error was common with Windows 98. Specifically, when opening IE you'd get the error and clicking on it would cause IE to close. It also would come on randomly when using IE. The usual cause back then was, like I said, either the program was referencing memory incorrectly or the memory modules themselves were corrupted.

I reinstalled a few of the main programs and received the same type errors.

The most recent error occurred upon opening Trillian.

quote:

---

trillian.exe - Application Error

The instruction at "0x00f6fb00" referenced memory at "0x0103c000". The memory could not be "read"

Click on OK to terminate the program
Click on CANCEL to debug the program

---

Immediately following that I attempted to reopen the program again and got this error.

quote:

---

trillian.exe - Application Error

The instruction at "0x00f6fb00" referenced memory at "0x00c3c000". The memory could not be "read"

Click on OK to terminate the program
Click on CANCEL to debug the program

---

Different errors for the same program.

quote:

---

trillian.exe - Application Error

The instruction at "0x1001daae" referenced memory at "0x00000000". The memory could not be "read"

Click on OK to terminate the program
Click on CANCEL to debug the program

---

[This message has been edited by Kriek (edited 02-26-2003).]

This '... bla bla bla could not be read" error I have received some times in WinXP. As far as I remember, it only happened in a certain program that I uninstalled and installed an older version just for the sake of avoiding receiving the error, and it worked. Once I received the same error but ending with "... cannot be write", instead of "... read", but it was only once and I don't remember what I was doing. I believe it's a problem of the a program, but not of WinXP, but, since you're receiving too many of this same error, some more serious stuff should be going on in your system, as stated already. Have no idea how to solve it.

Now that's interesting - since I booted my computer today Trillian keeps displaying the exact same messages every time I try to start it. I've never had anything crash like this on XP before, so what's that? A conspiracy? Hmmmmm.......

I can't believe anyone out there is actually using XP, after this thread.

Oh well...hope you get the problem fixed.


WebShaman

WS - but where are the alternatives? WinXP/2000 are the first Windowses that are running really stable on my system (apart from these odd errors if they're actually Windows' fault ), and since I tend to play recent games from time to time 2000 isn't really an option. What I need to do, though, is getting more into Linux (esp. Wine) - but that only makes sense if I can get it to work with the scanner, digicam and cd recorder... bah.

Kriek - strangely, I have also been getting the same errors when launching Trillian, starting yesterday. I've just given up and started using AIM again. I haven't bothered to try reinstalling it.

I just downloaded and reinstalled v0.74 but that didn't change anything for me, either

WS - despite all the fuss, I don't have better option than WinXP for my situation. It does everything I want, it's stable, it has a lot of compatibility, it's very easy to find the softwares I need (strict and latu sensu), etc. etc. I would never change my OS because of a single article. An article express the opinion of one or some persons. I am concerned with what the article tells but not to the point of changing OS, not even close to it. I believe that when things turn out to be really worrisome, then Linux will be much more of an alternative then it is today, and then I'll make the move.

kuckus: If you scroll through that article until you see "Solve security problems: Don't let Microsoft connect." They have a good solution. I have an old computer that I am going to do this with actually. I was just going to use it as a "firewall" so to speak. Now I think I am going to go this route with it as well.

Later,

C:\


~Binary is best~

Trillian Patch D solved the problem for me

quote:

---

These patches include several changes to the AIM and ICQ engines within Trillian:

1. Fixes the AIM connectivity crash that started on 02/11/2003.
2. Adds ICQ2Go support.
3. Fixes the issues with AOL 8.0 and Trillian.
4. Update: If you downloaded 0.74 Patch C and are experiencing connection difficulties, please download the newest 0.74 Patch D below.

---

http://www.ceruleanstudios.com/trillian-v0.74-patch-d.exe

Aha, yes, patch 1.0C made it work again. Thanks kuckus =)

[This message has been edited by Slime (edited 02-26-2003).]

Wow, that solved the Trillian errors and in turn I haven't had any problems with my other programs.

However I have suspected bad RAM for quite sometime now. Hopefully I can fix that soon.

Glad to see the patches worked out for you guys.

As a side note, I have gotten almost every single game I own to work with Windows 2000 without a problem. The only one that won't work is XCOM, but all the others, old ones and several recent ones, work fine. And I highly recommend Windows 2000 over Windows XP.