Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: viking73 on November 07, 2009, 08:06:37 PM
-
The first is an error I get which crashes the game. The following error report was gathered by vista. Windows does not suggest a solution.:
Product
aceshigh.exe
Problem
Stopped working
Date
11/7/2009 12:09 AM
Status
Report Sent
Problem signature
Problem Event Name: APPCRASH
Application Name: aceshigh.exe
Application Version: 0.0.0.0
Application Timestamp: 4acccc4d
Fault Module Name: aceshigh.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4acccc4d
Exception Code: c0000005
Exception Offset: 001613f0
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834 160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834 160
Extra information about the problem
Bucket ID: 1503424389[/i]
Secondly I get a driver error that sometimes is fixed by vista and i can continue the game. The screen goes black or to the desktop and then back to the game. Sometimes it plain crashes me totally. The following is the vista problem report. Windows recommends updating my drivers but i've already have the newest.:
Product
Windows
Problem
Video hardware error
Date
11/7/2009 12:09 AM
Status
Solution Available
Description
A problem with your video hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Files that help describe the problem (some files may no longer be available)
WD-20091107-0009.dmp
sysdata.xml
Version.txt
Extra information about the problem
BCCode: 117
BCP1: FFFFFA80078CD4E0
BCP2: FFFFFA6002AEC220
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
Server information: abdf9f02-b3b0-4ffa-a9ef-9e184fe27fe8
Coolermaster HAF 950
MSI motherboard MS-7520
Intel Quad Core 920@2.67 Ghz,2668Mhz
6 GB memory
2- Nvidia GeForce GTX 285 SLI
driver version 8.16.11.9107
3- Acer x223w monitors 3840x800x59hz
-
Ubfortunatly I got the same message after the last patch, couldn't figure out why. I remembered something bout sli'd video cards( I had 2 nvidea 9800 gtx +) sli'd. I disconnected and removed thr slave video card and I have not had the problem since. Might be an option to try.
-
well i hope sli isn't the problem. if it is than Hitech needs to make an adjustment because more systems out there are dual cards, "sli'd".
Moderator (or whoever) needs to notify Hitech support or I can write them.
Plus you shouldn't have to take out the cards. Going into the properties and disabling SLI should be enough.
I made some changes in my graphics settings that I read here using NHawk's suggested settings. We'll see if that makes a difference.
-
If you have an nvidia chipset and you have SLI and you have a soundblaster audio card there is a very high likelihood you will see this very often. If that describes your system you would be very well off to upgrade to Windows 7. This is not a problem with Aces High but since AH is using the devices when they 'choke up' the operating system sees the program as being the problem. It can get much much worse the more background processes you have running. So far as I know the Intel chipsets do not have this issue.
-
We have no control over SLI'd video cards. The Aces High profile from NVidia contains settings which will create other problems. Such as running without vertical sync enabled.
That does bring up another point. Is it safe to assume you are using the Aces High profile supplied by NVidia?
-
well, that's what i recently changed. I went into nvidia's aces high profile and manually changed some things the same as NHawk and others supplied. (sorry don't have the link) It didn't crash the rest of the night last night. We'll see tonight how it does.
Windows 7? Hmmm, interesting.
Thanks all.
-
The problem is back again before and after the new patch. Stops working and driver error. Seems to happen when I switch views with the hat. But that could just be a coincidence. Happened so many times tonight that I had to quit. I updated to the newest drivers and it's still doing it. If it keeps up I may have to go back to 182.50 drivers. any ideas?