Ah nothing works anymore!

[duragezic]

A while ago, Morpheus would always crash with this error. A reinstall didn't work, and neither did a format. Then it was resolved by deleting the contents of the /db/ folder. Then a few days ago Nandub started crashing giving me the same error (although I believe the memory address thing was a little different). Now ICQ does it. And now Gamespy Arcade did when I went to roll in with some Renegade demo. WTF??

This is a relatively new format, and the reason why I formatted last time is because ever f*cking program did the exact same thing and crashed with that memory error. WHY WHY? It hasn't been doing it forever since I got this computer, just the last few months I guess.

 

[HappyPuppy]

Yesterday I uninstalled Morpheus from a clients machine and cleaned out alll the registry entries it made and it suddenly started running well for a change.

 

[duragezic]

I tried that, searched through reg to clear out all entries, still no go.

And it kinda seems like since I upgraded my ram it started doing it (but not the day I put in my ram it did it, rather it NEVER did it with 256mb ram but it now does with 512mb, which doesn't really say its definitely the ram but...), I took out the new stick and kinda had my hopes up thinking it was defective ram or something but still that didn't fix it.

 

[duragezic]

bump

 

[MrTux]

If you are running XP like I am, Morpheus occasionally crashes because it's not built for XP. They are supposed to be coming out with an XP compatible version soon, but you know how that goes.

Anyway, I noticed you are overclocking the CPU. If you are upping the FSB, that increases other bus speeds on your mobo too, which can cause data to become corrupt. I'd recommend putting the proc back to it's stock speed then doing a reformat to see if you keep getting the same errors. Also, how big of power supply do you have?

 

[GiGoLo]

i did a search on deja newsgroups for you... there were several people having the same problem. they had the exact same error message and the only thing that differed was the memory address (and also some of them were using win2k instead of xp). neways, they all isolated the problem to either bad memory or a bad memory slot. i would suggest trying each of your sticks one at a time in each slot to try and narrow down the problem. or possible find a memory test program, but those aren't always 100% reliable.

another thing is what mrtux suggested... set ur system back to default settings (meaning not oced ) and see if that helps. i can tell you, i've had some f***ed up problems caused by overclocking. everything seems to work fine except one little thing, and it ends up being the ocing. can't hurt to try

good luck