Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: 33Vortex on March 05, 2005, 11:02:23 PM
-
Anyone else having this problem? It has happened to me three times the last few days that XP decides, for no obvious reason, to terminate the program. The game is running fine, no lag, no problems whatsoever and then a sys msg pop up and say aceshigh.exe needs to be terminated because of some problem. It really sux... Anyone know what may be causing this and how to fix it?
-
I get that on the rare occasion with XP Home and SP2 also. I always just assumed that these sorts of things were just "features" of Windows in general lol.
Zaphod
-
Does it give you an error message of any kind?
-
No, all it says is that "aceshigh.exe has encountered a problem and needs to be terminated". This is seriously pissing me off! No reason given and it's always been running just fine before. Just more M$ bull****!
-
easy way to look that up is go to Control Panel->Admin Tools->
->Event Viewer->click on Aplications/select date of error and you may have a better idea as to what is causing that error
-
Can you think of any changes you have made recently (before it started I mean)? Even things that might seem to be totally unrelated. But especially updates to drivers, that sort of thing?
-
Wild guess idea... can you try and check if you have the "XD" bit enabeld and disable it?
This would only apply if you have a pretty new processor that has XD and that it is enabeld in Windows, i think you have to enable it manually... maybe you did that?
I think it should list in the event log why it was shut down.
-
Where do I find the event log and how do I activate that whatever it was you said, XD?
The only error message I get is "aceshigh.exe has run into a problem and needs to close. Sorry for the inconvenience. bla bla" I mean, it would be ok if it happened maybe once every few days, but when it happens repeatedly when in a fight it really sucks.
-
The message you got was a generic message telling you that
SOMETHING has gone wrong. If you haven't been messing around with any bois or windows settings or havent opened your case removing hardware, Id be inclined to believe that some file in Aces High got corrupt. Could also maybe be that your got spyware/virus hogging memory to the point AH2 cant run
-
In correctly installed, out of date, or problematic video drivers will also cause this.
Sound card drivers too.
Send me the output from DXDIAG and I will be happy to check it out.
-
It could be the sound card driver, since I couldn't find the original disc for the audigy card when I reinstalled. Tried downloading from creative.com but it just doesn't seem right, some software is missing.
Removing the custom sounds (Waffle's sound pack, whatever the latest version is) fixed the problem, and since 3 days AH is running fine.
I'll send you a dxdiag though skuzzy, thanks!
-
Got it and found the problem. You have mail!
-
Making the recommended changes and then I'll reinstall the custom sound pack. Will post here if this fixes the issue.
Thanks again skuzzy!
-
Seems like that was the problem, played a couple hours last night, wafflesounds installed and no disco yet.
-
Correction... still having problems.
-
Chased a buff formation out of 209 today, just minutes ago. Got to 15k then discoed. Started up AH again and upped from a base SW of 209, buffs were now at 25k, I intercepted at 30k. Made one pass, didn't get a good angle and came around for a second pass. Just as I was about to press the trigger the screen goes blank and I get that frickin error message AGAIN. !#¤%""!#¤% :mad:
-
What kind of video card do you have and what version of the drivers are you using?
-
AMD Athlon XP 3000+
2.10 GHz, 1024 MB RAM
NVIDIA GF FX 5700 256 DDR
Current driver: 61.77_win2kxp_english.exe (as recommended by skuzzy)
Previous driver: 71.84_win2kxp_english.exe
-
i have same problem but not that often. happend several times while filming, then all of a sudden my film veiwer went poof
-
You have already made all the alterations I would have suggested, and if Skuzzy has already been over it with you I doubt I can improve on his advice. The only possibility I can suggest is that you are experiencing the infamous "loop error". I remember reading it's more prevalent with 256MB video cards. If you have access to another video card, try it and see if you still get the same problems with no other changes. Of course if you dont have access to another card, I dont know what to suggest. Nobody that I know of has nailed down a specific cause for the problem, other than it is related somehow to possibly faulty video cards or driver issues with certain card architechtures.
-
Alright, I believe I've found the source of the problem. The RAM installed, 2 sticks of PC3200 512 MB, were of different make. After removing one the system has been stable, and it seems to be stable using either of the two. So... I'm getting another stick of RAM now.