Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Phil on November 17, 2008, 08:43:35 AM
-
Posted this thread few weeks ago.
Freezing up after 45min of game play.
Many recommended "dusting off" the tower... It sounded like "overheat" problem.
Boy what a cloud of dust that was ! :aok
Unfortunately it still crashes/freezes. When it happens, the screen goes black.
I do the ALT-CNTL-DELETE and still don't get any responce.
I have to log off by manually turning the puter off...
The tower have temp gauges(3) and all are fine !
I don't think its a connection problem because I play the game "offline" or
simply watch AH recorded films and suddenly my screen goes black/dark !
Not a puter wiz but here is my hardware....
AMD Athlon 64 X 2 dual Core 3.2MHz
Western Digital 250GB Sata 16MB(X2)
Asus M2N-E AM2 PCIE MB
Atrix case
Echo Star 680-watt 24pin dual fan
Corsair ( 2 X 1GIG DDR2-667) Kit
Asus GeForce 7950 HDTV 512MB
Sound Blaster Audigy X-FI Platinum
View Sonic VX922 19in LCD
Software: Windows XP
Flying hardware: CH all around ! Stick/throttle and pedals
TrackIRII
Skuzzy can you help me out ?
Phil / OPP7755
-
Phil:
post a dxdiag for Roy,see mossie thread for directions if ya dont know how.
also check task manager,see how many programs are running,I suspect your having a conflict with one of the background programs,like antivirus or such.
-
G'day Sir !
I run FSAUTOSTART everytime I play.
It drops to the low 30's...
Never had any problems with this !
I've read and printed the procedures to run Xdiag etc...
My question is: When it jams/freezes, my computer needs to be restarted/rebooted manually. When I do that, will the right info still be in the XDIAG report ????
Phil
-
Do any other programs cause your computer to lock up like this, or only AH?
ack-ack
-
At this time, AH is the only game played on my puter !
:frown:
Phil / OPP7755
-
I wonder if the power supply is strating to go bad.
Go into the system BIOS and check the power output levels for the various rails. What you are looking for are swings in the voltage levels. At idle they should be almost perfectly stable. Also check to see if any of the rails are too low.
-
may be a stupid question, but, do you have an automatic shutdown setting after 45 minutes of non use?
look in your energy saver settings, see if there is a shutdown sequence.
Worth a look.
-
This is a bit of a long shot, but look really really closely at your screen the next time this happens, and see if you can see any outlines of what was there before it crashed.
Something like this happened to me a while ago, then I worked out that it was actually just the backlight in the screen failing (it would stay on for a second or two after toggling the display on/off).
<S>
Yossarian
-
I have the same problem only my pc still works afterword. i just cant pull the game back up without restarting. tried cleaning, brand new power supply, everything is working fine on my pc, and i close all other programs running. what could it be?
-
Did the problem start when you got the new PSU?
-
No, this is the only PSU that ive used in this pc for a month had no other problem with it on anyother games, including those that mine can barely run. so it is not my power supply
-
Without a DXDIAG output it is most difficult to know where to start. Most of the time (keyword: MOST), lockups are resource related, but not always.
Custom sound packs are a huge problem with onboard sound chips, for example. Using texture sizes too large or settings that compound resource usage.
Vista plus NVidia drivers can also be problematic.
There are a host of things that can cause computers to lockup. Thereis no gaurantee one cure will fix all ills.
-
Skuzzy !!!
As you suggested in BIOS mode, you want me to check for some kind of meters...
What kind of numbers should I expect to see when I check the PSU rails ?
What is low numbers when puter is at idle speed ? What numbers are abnormal ?
Will the XDIAG report be good to you when I need to reboot the puter before being able to do the XDIAG procedures ?
Trying to understand, please be patient with me ... :(
Working night shift at this time.
Will be trying your advice this weekend and will keep you posted.
And to add, my puter freezes when watching AH recorded films. Not even playing
online !!!!!
PSU is fairly new(2yrs). What size should be in there ?
Tks
Phil
-
All the rail numbers are critical. Rather than give a guess, go ahead and post them, and be sure to note how far they drift. You should watch them for a minute or so.
The DXDIAG can be run anytime.
-
I think this is the stuff yall need if not let me know what else
System Information
------------------
Time of this report: 11/20/2008, 19:49:57
Machine name: TRISTAN
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.080814-1236)
Language: English (Regional Setting: English)
System Manufacturer: Dell Computer Corporation
System Model: Precision 330
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A09
Processor: Intel(R) Pentium(R) 4 CPU 1700MHz
Memory: 1024MB RAM
Page File: 520MB used, 1171MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode
Display Devices
---------------
Card name: NVIDIA GeForce FX 5200
Manufacturer: NVIDIA
Chip type: GeForce FX 5200
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0322&SUBSYS_31031458&REV_A1
Display Memory: 128.0 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Monitor: Default Monitor
Monitor Max Res:
Driver Name: nv4_disp.dll
Driver Version: 6.14.0010.7189 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 4/1/2005 15:16:00, 3980288 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 4/1/2005 15:16:00, 3454656 bytes
Device Identifier: {D7B71E3E-4062-11CF-FD6B-091100C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0322
SubSys ID: 0x31031458
Revision ID: 0x00A1
Revision ID: 0x00A1
-
Here is the readout of my dxdiag: Looked into bios and can't find anywhere where i can see different voltage for anything. Anything more specific would help me find out the info u guys need. thks
System Information
------------------
Time of this report: 11/20/2008, 21:13:42
Machine name: SECRET
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.080814-1233)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+, MMX, 3DNow (2 CPUs), ~2.2GHz
Memory: 2046MB RAM
Page File: 314MB used, 3625MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: NVIDIA GeForce 7950 GT
Manufacturer: NVIDIA
Chip type: GeForce 7950 GT
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0295&SUBSYS_82251043&REV_A1
Display Memory: 512.0 MB
Current Mode: 1024 x 768 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0010.9147 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 8/11/2006 08:42:52, 4496128 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 8/11/2006 08:42:42, 3958496 bytes
Device Identifier: {D7B71E3E-41D5-11CF-4850-2FA200C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0295
SubSys ID: 0x82251043
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A
Deinterlace Caps: {212DC724-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{212DC724-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{212DC724-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{212DC724-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
-------------
Sound Devices
-------------
Description: SB X-Fi Audio [A400]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0005&SUBSYS_00211102&REV_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.1144 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 10/29/2005 06:16:23, 439680 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Standard
Cap Flags: 0xF5F
Min/Max Sample Rate: 1, 192000
Static/Strm HW Mix Bufs: 128, 128
Static/Strm HW 3D Bufs: 128, 128
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
---------------------
Sound Capture Devices
---------------------
Description: SB X-Fi Audio [A400]
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.1144 (English)
Driver Attributes: Final Retail
Date and Size: 10/29/2005 06:16:23, 439680 bytes
Cap Flags: 0x41
Format Flags: 0xFFF
-----------
DirectMusic
-----------
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: Enabled
Ports: SB X-Fi DMusic Synth [A400], Hardware (Kernel Mode), Output, DLS, Internal, Default Port
SB X-Fi Audio [A400], Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB X-Fi Synth A [A400] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB X-Fi Synth B [A400] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB X-Fi MIDI Port [A400] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, External
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB X-Fi MIDI Port [A400] [Emulated], Hardware (Not Kernel Mode), Input, No DLS, External
Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal
Registry: OK
Test Result: Not run
-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: CH PRO THROTTLE USB
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x068E, 0x00F1
FF Driver: n/a
Device Name: CH PRO PEDALS USB
Attached: 1
Controller ID: 0x1
Vendor/Product ID: 0x068E, 0x00F2
FF Driver: n/a
Device Name: CH FIGHTERSTICK USB
Attached: 1
Controller ID: 0x2
Vendor/Product ID: 0x068E, 0x00F3
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
-
I think this is the stuff yall need if not let me know what else
<snip>
In the games "Video Settings", make sure the "Maximum Texture Size" is no higher than 256.
Also, you would be better served by using the 61.77 version of the NVidia drivers as those were the last drivers that were optimized for the 5000 series video cards.
You also will not ever want to load any custom sounds. Your system is going to be taxed with just the normal sounds.
-
Phil, you need to update your NVidia driver as the 9x.xx drivers were pretty buggy. And you also need to update the X-Fi audio drivers as they also had some issues early on.
You should also go ahead and set the game to run in "Windows 98/ME" compatibility mode.
-
Jaygongin:
I have an FX 5200 an I have to use bare minimum of prossesses running(17 with dialup going and using winXP, but I don't use it for anything else), AH's default video settings, clean it our every 3 months(smoker) and run the fans up with SpeedFan (get from downloads dot com). This vid card has no fan of it's own and suffers heat related illnesses without preventive care.
-
Phil, you need to update your NVidia driver as the 9x.xx drivers were pretty buggy. And you also need to update the X-Fi audio drivers as they also had some issues early on.
You should also go ahead and set the game to run in "Windows 98/ME" compatibility mode.
Thanks Skuzzy!!!!!
Where do I find in the game to run in "Windows 98/ME" mode ????
Phil / OPP7755
-
Right-click on the "Aces High II" startup ICON, select "Properties" from the pop-up menu, then select the "Compatibility" tab, check the option to run the application in compatibility mode, then select "Windows 98/Windows ME" mode from the drop down list.
-
I have been having this problem ever since the last couple of patches. I have no idea what causes it other than to suspect a memory leak in AH or windows ,resource conflicts, or the load balancing algorithm AH uses to limit the players in any arena. I have noticed lately when I get "booted"(EG game locks up) that when I have restarted my system the load balance has gone down and there are far more in an arena than the maximun allowed. I have turned off all the services I am comfortable in turning off given my level of expertise and followed the early advice of this forum, still no joy. I get on average one system hang per hour. When I use taskmanager to quit AH and then restart the gamewithout rebooting, the clipboard is spinning and I have to reboot. Maby this is a display driver-AH conflict. I am running an nvidia board and all my drivers are up to date. Also, if I change arenas and quit to go back to the arena clipboard, the clipboard is spinning. I suspect this is also a conflict with AH and the displaydriver or how AH manages graphics in the game. Just guessing, wonder what would happen if AH set up a system and tested it?
Slopoke
-
The 'spinning clipboard' issue is due to a bug in the AMD dual-core CPU's, we happen to hit. It does not happen with the Intel desktop dual-core CPU's
It can also happen with dual-core Intel laptop CPU's, but this is more to do with the power management than a bug, where one core gets shut down causing a clock out of sync issue.
There are work-arounds, but it depends on the operating system.
-
Just got locked up again, seems thresholds for arenas changed at the same time
and had spinning clipboard as well
-
I saved a dump file in the task manager, can you use it?
-
Dumps are useless as they will be coming from a device driver.
A DXDIAG output would be more helpful.
-
Updated drivers did the trick Skuzzy !!!
Thanks a million Sir !
Owe you a cold CANADIAN beer Sir !
:salute
Phil / OPP7755
-
mine is fixed. turned out to be a video driver problem.