Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Krusty on June 14, 2009, 02:43:03 AM
-
TracerX has been having recurring system crashes in AH. He can't figure out on his end what it is. He thinks maybe it's video card related, says he's replaced his PSU recently, so I asked him to pull a DXDIAG.
No exact schedule on the crashes, but he can't get through half an FSO, usually under 30min/45min and he's gone. Often much sooner.
Here's the DXDIAG:
------------------
System Information
------------------
Time of this report: 6/4/2009, 19:41:03
Machine name: <<<>>>
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: System manufacturer
System Model: System Product Name
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+, MMX, 3DNow (2 CPUs), ~2.6GHz
Memory: 2046MB RAM
Page File: 135MB used, 3803MB 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
------------
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: WinFast PX8600 GT(NVIDIA)
Manufacturer: NVIDIA
Chip type: GeForce 8600 GT
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0402&SUBSYS_2A83107D&REV_A1
Display Memory: 512.0 MB
Current Mode: 1024 x 768 (32 bit) (75Hz)
Monitor: Dell P1110
Monitor Max Res: 1800,1440
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.6218 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 6/29/2007 00:43:00, 5690624 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 6/29/2007 00:43:00, 6807328 bytes
Device Identifier: {D7B71E3E-4742-11CF-876B-880A00C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0402
SubSys ID: 0x2A83107D
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: 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
{6CB69578-7617-4637-91E5-1C02DB810285}: 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
{6CB69578-7617-4637-91E5-1C02DB810285}: 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
{6CB69578-7617-4637-91E5-1C02DB810285}: 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 Audigy 2 Audio [CF00]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.0522 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 4/28/2004 20:01:00, 374000 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Standard
Cap Flags: 0x0
Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
Static/Strm HW 3D Bufs: 0, 0
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 Audigy 2 Audio [CF00]
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.0522 (English)
Driver Attributes: Final Retail
Date and Size: 4/28/2004 20:01:00, 374000 bytes
Cap Flags: 0x0
Format Flags: 0x0
-----------
DirectMusic
-----------
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: Enabled
Ports: SB Audigy 2 DirectMusic Synthesizer [CF00], Hardware (Kernel Mode), Output, DLS, Internal, Default Port
SB Audigy 2 Audio [CF00], Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy 2 Synth A [CF00] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy 2 Sw Synth [CF00] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy 2 Synth B [CF00] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
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: Saitek X52 Flight Control System
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x0255
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x1002, 0x4389
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 4/13/2008 11:45:37, 59520 bytes
| Driver: usbd.sys, 3/31/2003 05:00:00, 4736 bytes
----------------
Gameport Devices
----------------
------------
PS/2 Devices
------------
+ Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 4/13/2008 12:18:00, 52480 bytes
| Driver: kbdclass.sys, 4/13/2008 11:39:47, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 4/13/2008 17:13:20, 40840 bytes
| Driver: kbdclass.sys, 4/13/2008 11:39:47, 24576 bytes
|
+ Logitech USB Wheel Mouse
| Vendor/Product ID: 0x046D, 0xC00E
| Matching Device ID: hid\vid_046d&pid_c00e
| Service: mouhid
| Driver: mouclass.sys, 4/13/2008 11:39:47, 23040 bytes
| Driver: mouhid.sys, 3/31/2003 05:00:00, 12160 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 4/13/2008 17:13:20, 40840 bytes
| Driver: mouclass.sys, 4/13/2008 11:39:47, 23040 bytes
----------------------------
DirectPlay Service Providers
----------------------------
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.5512)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.5512)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.5512)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.5512)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.5512)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.5512)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.5512)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.5512)
DirectPlay Voice Wizard Tests: Full Duplex: Passed, Half Duplex: Passed, Mic: Passed
DirectPlay Test Result: Not run
Registry: OK
(cont)
-
-------------------
DirectPlay Adapters
-------------------
DirectPlay8 Serial Service Provider: COM1
DirectPlay8 TCP/IP Service Provider: Local Area Connection - IPv4 -
-----------------------
DirectPlay Voice Codecs
-----------------------
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s
-------------------------
DirectPlay Lobbyable Apps
-------------------------
------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 225.5 GB
Total Space: 238.5 GB
File System: NTFS
Model: ST3250310AS
Drive: D:
Model: TOSHIBA DVD-ROM SD-M1502
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.5512 (English), 4/13/2008 11:40:46, 62976 bytes
I also asked him to post the specs on the PSU but no joy on that yet.
-
I'd do a memory test.
-
What type of crashes is he having? System lock up, CTD, reboots? That info may help.
-
It's either reboots or system crashes. Takes him time to reboot to get back into FSO after it happens (not just logging back in).
-
Power supply, heat, corrupt data in the system folder, bad ram.... Any number of things could cause that.
-
Bad surge protectors can be the cause.
Viruses, drivers, even corrupt files in Aces High.
What does the error message say whenever is BSODs?
-
Hey guys, thanks for posting this Krusty. I almost started a thread many months ago, but my ambition was greater than my desire to gather all the data I wanted to present. So here is the short and dirty story.
I am getting lockups, not blue screens of death. The lockup is usually a frozen screen with the last one second of audio repeating endlessly, and I am unable to raise my task manager with cntrl-alt-del, so I just turn everything off. Sometimes I get dumped to the tower and I am able to still communicate, but my mouse is disabled so I have to restart, other times I can get the task manger open and can close the AH program that is not responding and then restart.
The History:
I did a complete new OS install when I got the new hardware (Mobo, CPU, Memory and HD). I actually installed the OS twice since I had a hiccup of some kind and wanted to start over. Installed drivers for Main Board, video and sound in that order, then began installing my programs. The first indication of any kind of problem was when I ran AH for the first time, and i got the spinning clipboard problem associated with the AMD duo core CPU which I have. I downloaded and installed the two drivers (I forget the details) to fix the problem, and tried again. This time AH seemed to run ok. I was able to fly a few times before I started to notice the lockups that I am experiencing now. I have seen no improvement in the conditions over the last 10 months or so, although I have thought I had fixed the problem several times because the problem is so intermittent. Sometimes I can fly the full FSO or a complete night of flying in the MA with no problems, and other times I have to reboot 3-4 times to make it through an evening. I know that if I run any other program (even if I close it) I will get a lockup of some kind for sure, so I always try to run AH after a clean boot. I don't run any other programs that exibit the same problems, but my other programs are basic office use programs from Microsoft and Intuit, and do not require sophisticated 3D video cards.
I have since replaced my Antec 350 watt power supply with a newer (cant remember brand) 500 watt power supply and added 2 case fans. It does not matter if I have the case open or closed, so I do not think it is a heat issue. I have tweaked the cpu voltage settings to override Auto and manually set the appropriate cpu and memory settings. I have reduced the video settings for textures in AH from 1024K to 256K and saw not noticable improvement.
I will get a detailed list of my hardware later.
Hope this helps.
-
You never mentioned this in your description. Are you running the game in Windows 98/ME Compatibility mode?
-
You never mentioned this in your description. Are you running the game in Windows 98/ME Compatibility mode?
No, not that I am aware of. Just normal Win XP SP3 I think now.
-
Try right clicking aceshigh.exe (In the C:\Program Files\HTC\Aces High II\ folder), going to properties, and enabling compatibility mode. As mentioned before, use Windows 98/ME compatibility mode.
-
I will give win98 compatibility mode a try, but I have never had to do that before. I was running AH in native XP operating environment with no problems at all before my hardware upgrade.
-
I've had this problem for a while too. I think it's as Skuzzy says, any number of things. I am also pretty sure it is sound related in my case. I have an old Soundblaster 5.1 card I originally bought just to have the game port. (That old). I don't even remember if I ever installed drivers for it or just let windows do its thing.
Anyway, froze up on me this weekend and instead of pulling the plug I walked away in disgust to get a drink. Lo and behold, when I came back it was unlocked and still flying.
Not that it will help any, but maybe wait and see what happens for a few minutes. Of course, the next two times I locked up I wasn't on autopilot and came back just in time to see myself hit the ground.
Dunno what the problem actually is but my top four guesses have always been heat, drivers, corrupted something or gremlins.
I even uninstalled the sound pack I was using, going back to the original sounds. I've since reinstalled all toghther. Still freezes every once and a while.
wrongway
-
I will give win98 compatibility mode a try, but I have never had to do that before. I was running AH in native XP operating environment with no problems at all before my hardware upgrade.
What type of CPU and Motherboard did you have before the hardware upgrade?
The AMD 2 core CPUs have had bugs which aren't entirely fixed by the core optimization patches released in the past. To get around the bugs you have to force Aces High to run on one core of your AMD processor. To do that you have to play in Win 98/ME compatibility mode.
-
The freezes sound about like what I had a month ago. It would randomly freeze and not start back up, had to restart PC.
I ended up re-installing the game 100% and the Dual Core Optimizer (http://support.amd.com/us/Pages/dynamicDetails.aspx?ListID=c5cd2c08-1432-4756-aafa-4d9dc646342f&ItemID=153) which stopped the freezing, but no idea what the real cause may be, just what helped here.
Aside from that one time, I have almost no troubles with AMD x2 in the game, just the dieing GPU is all. :)
-
Well, I tried the win98 compatibility mode last night, and the initial prognosis is good. 2-3 hours without any problems, well, except for providing myself as a target for a little green amphibian too many times. :D
-
Well, I hope it works for you. Let us know what you discover.
-
If win98 compatibility mode is only using one of the two cores, I would ultimately like to get to the bottom of the problem still. If I end up having no problems in win98 compatibility mode, would this point to the CPU as the culprit, or is it a software issue? I have reinstalled the CPU optimizer drivers once before because I thought there was a problem with them, but I did not see an improvement.
-
The AMD CPU optimizer does not correct all versions of the dual-core AMD problem the game happens to hit.
-
So, this is another example of a reason to buy Intel?
-
Either that or buy a newer AMD CPU which doesn't have the bug (Preferably one with 4 cores).