Ok, I have some good news and bad news regarding the ongoing research
into the stop error, AKA Blue Screen of Death, created when exiting
Mysteries of the Ancients.
The good news is a couple of you have sent me a copy of your minidump
files which has allowed me to extract the stop error code the BSOD
displayed shortly before Windows goes down for the count. as expected
the stop error code relates to a memory access violation of some kind.
The bad news is that particular error code, stop error 0x10000050,
usually indicates faulty memory. I'm not saying that your memory is
actually faulty only that Windows XP thinks your memory is faulty for
some reason. Unless of course you are over 70 and memory is the first
thing to go. Just kidding.
Seriously though, apparently when the program exits forsome reason
Windows can't access a block of memory for some reason, signals a page
fault, blue screens, and reboots. Why this doesn't happen on every
single Windows computer out there is beyond me, but thats what I've
found out so far.
Now, that I have some idea of what is causing the crash I can go
through and hopefully discover what isn't getting uninitialized before
exiting. There is apparently something hanging on to a block of memory
when the program closes and Windows gets a bit tempermental about it,
and wants it back. In short the BSOD is like Windows throwing a temper
"Its mine. That is my memory, and you can't have it. Give it back.
Give it back. Mommie, make him give it back. Fine, I'll just shut down
And who says computers don't have personalities?
Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org.
You can make changes or update your subscription via the web, at
All messages are archived and can be searched and read at
If you have any questions or concerns regarding the management of the list,
please send E-mail to gamers-ow...@audyssey.org.