Ide??

Hello everyone.

It's Kelly here and you have all been really helpful with my problems in the past, that I figured you may like to help me with this one.

Firstly, what is an ide?

And secondly, msn seems to have committed suicide on my computer. What I mean is everytime we try to sign in, along comes a blue screen with the words, 'A fatal exception OE has occured at module whatever (it changes) in (a few letters and a bunch of numbers.)

Any help would be appreciated.

An IDE is an Intergrated Development Enviroment.

for example:
http://www.kdevelop.org
http://www.borland.com/products/index.html
http://msdn.microsoft.com/vstudio/

kellybelly182_1,

You could try reinstalling MSN (choose last version for your OS) from http://messenger.msn.com/

Good luck.

Hey again!!

Firstly, thankyou the_jinx for your help. Now I know what an ide is.

Secondly, I think this problem goes further than msn. How do I know? Well, I typed in the exception number thing in a search engine and found other people with the same problem as me. Everything went straight over my head though.

When I try to log in to msn I get this message.

A fatal exception OE has occured at 0028:C0004A64 in VXD VMM(01) + 00003A64. The current application will be terminated.

Who wants to help me???

Seriously though, any help would be really appreciated.

Luv ya's.

Does this screen only appear when you try to sign in?Has this screen appeared in other programs as well?This sounds like a memory module which is failing.If you have more than one module try removing one, untill you get the culprit.

hope this helps--
vanman:)

Hi,

At the risk of sounding really, really stupid, how do I know what my memory modules are or how many I have?

And it's only msn that the screen has appeared in. It's annoying as all hell though.

Thanks

Jinx: It is also quite possible that IDE stands for Integrated Drive Electronics..... Which is highly likely the type of drive Kellybelly is using.

Kellybelly: What contect are you seeing the IDE in?

You're right Tiger Shark.

Kelly i had the same problem on WinXP without finding any solution except of the following one:
1) I have installed WinXP FE and I have overclocked my PC and as vanman said it has been a confusion with RAM's frequencies. I tried overclocked the RAM too, without any good. But since i installed WinXP pro SP1 i have no problem. Only my on-board sound card didn't work properly since i de-overclock the whole PC system.

kelly: try reinstalling the newest version of the software and all the recent windows updates and stuff, it might be something really simple. or as vanman said it might be..
memory modules - wot he means is the ram cards plugged into your motherboard, open up the box and look for a couple of small cards about 10-15cm x 4cm slotted directly into to the main board in a neat little row. take one out and turn the power on, if u get the same error, replace it and try the next one. if there's only one in there u wont be able to do this. _be VERY carefull_ with this sh*t if u haven't much experience, you can zap the life out of these things if u don't take precautions against static.

Ya, to add to halfdoghalfman's comment. I was taking RAM out of my comp. to take it to CompUSA and so I thought if i put it in a pastic bad then it would be fine. I got there, bought an identical RAM card and sure enough when I got back, the one in the bad was fried. It's pathetic how easily those things get damaged. Oh well, life isn't always fair...

To avoid ESD (damage from static electricity) always make sure you 'unload' yourself before touching pc parts. So before you start working on a box, touch the metal case / chassis. You can leave the power cord plugged therefor it stays earthed. If you are free of static electricity, unplug the power cord and work on the box.

A VXD file is a virtual device driver (most typically associated with video drivers, though not exclusive to them), and VMM stands for something like Virtual Memory Management.
Your cure, if you take what I said, is simply to uninstall and reinstall your MSN.
True, that the memory references an actual memory allocation address, however, a problem of this nature is usually solved with a reinstallation of software. USUALLY being the keyword. Try uninstalling and reinstalling MSN before you go poking around inside your machine, especially if you have never been in there before.
To give you a better understanding of the VMM and VXDs, go to Microsoft's site, and do a search for VMM and VXD.
Good luck!!

KellyBelly my dear.......

Before you get carried away with diving headfirst into removing memorty modules that you profess not to know what they even look like, (that is not meant as a criticism at all), you should first reinstall the offending app. I have rarely, no.... extremely rarely, ever seen a system that always gives a memory error at exactly the same place in the same program and only that program be anything to do with the memory hardware itself.

When you get these kinds of errors it is because the program is attempting to access an area of memory that has been set aside and is protected for the operating systems use. The program is in error trying to access that area of memory and this is usually due to the program being damaged and having a wrong destination address or offset call as a result. So your program wombles along quite happily until it needs to execute the damaged code. At that point let's say the call was an offset, (jump to the code at address X and execute that code), of 1000 characters. That jump would put it at memory address, (yes, it's an address just like your house has one....<s>), 2000 let's say. That's all fine - the address at 2000 and above are set aside for the programs to use and everything runs along fine. Then one day the program gets damaged and the spot that got damaged is that place that determines how much that offset is and it gets changed to 500. Now when you program hits the offset it jumps to 1500...... Oooooops..... Bummer, the memory addresses from 1000 to 1999 have been set aside for the system itself and are protected by the system. Your program makes the call to the address and the system shows you the error message you are seeing.... It is simply telling you that it has prevented a program, (in your case MSN), from accessing an area of memory it is not allowed to access.

Hey everyone,

Wow, I didn't think I'd get this many replies! The context I'm seeing ide in is when I turn my computer on and the black screen comes on and it shows me the memory and stuff. If you get what I'm saying. It isn't important, but I'd never noticed before and I just thought I'd ask what it is.

I deleted and reinstalled msn, and now my computer just freezes when I try to sign in. So I don't know if my problem has progressed at all.

But it also freezes when I'm not trying to log into msn sometimes and I get the dreaded blue screen and a message saying that there's an invalid page fault in module mshtml.dll at 0137:70c343b4.

In short, I seriously need a better computer. Maybe when I grow up.

Anyway, thankyou all for your help so far.

Love Kelly

Who wants to know how dumb I feel?

So, even though I already deleted and reinstalled msn, I figured I'd try it all again because going inside to my memory thingos and unscrewing and static electricity and stuff all sounded a bit daunting. I reinstalled it, it worked and my problem went away. I think. Well, it's not here at the moment.

Why do you think it was there in the first place?

Anyway, I'm gonna say a huge thankyou to each and every single person who tried to help me.

THANKYOU!!

You guys have made me feel really welcome. I just hope that one day I'll know enough to help someone like me the way you have.

Bye!

Hey

Just thought 'd let you know that my last post somehow got two made into one.

Don't ask me.

Bye!

KellyBelly: As an old friend and mentor once said to me more years ago than I care to remember....... "Sometimes this stuff is just voodoo"......... :D

Glad you seem to be fixed.