Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: HighGTrn on August 11, 2008, 03:53:06 PM
-
Hi Skuzzy. Since the release of the latest patch, I've been plagued with a system lock up problem (not blaming the patch, just giving you a time reference of when it started). It only occurs when I'm playing this game. I've tried everything I can think of to include a complete, fresh install of the OS. I sent you my dxdiag about 3 weeks ago, I don't know if you had a chance to look at it. I sent it to the support email address. If you didn't get it, let me know and I'll send it again. Its too large to cut and paste in here.
So here is what happens:
I'm flying along and then all the sudden, the game locks up. Whatever view I happened to be in freezes and whatever vox/sound is playing keeps playing forever. There is no graceful way of recovering from these lock ups. The only think I can do is hit the power button. The only application running on this system other than the OS is this game.
I think it has something to do with my video driver (its updated to the latest driver) in combination with the latest patch (since all this started when I installed the new patch). I run an IMac 24 with 3Gigs RAM (boot camp) with a GForce 7300 card.
This afternoon was the final straw cause after spending a couple of hours reinstalling the OS, I locked up within 30 seconds of upping.
Help!!
Thanks,
HighGTrn@yahoo.com
-
I get these (generally when I dont reboot my system for a while). Narrowed it down to Terminal Services running, and polling - so killed that off (Dunno why, it just was). Also deleted my videocfg.8 file as well, which helped.
HTH,
Wurzel
-
If you use Yahoo as your email address, it can take up to a week to get a response and then it will be in your SPAM folder. Yahoo deliberately delays email delivery from us.
That said, if you send in something to support and do not get a reply within 24 hours, during the work week, then the email was either not received, or your email provider did not accept the response.
I do need a DXDIAG output to be able to provide some help.
Lockups like you are describing are typically related to resource issues in the computer. Those can be anything from not enough free RAM, to interrupts being shared, to heat.
-
Here is part of it.
------------------
System Information
------------------
Time of this report: 8/13/2008, 06:37:02
Machine name: GAMING-89B96FA2
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp.080413-2111)
Language: English (Regional Setting: English)
System Manufacturer: Apple Computer, Inc.
System Model: iMac6,1
BIOS: Default System BIOS
Processor: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz (2 CPUs)
Memory: 3056MB RAM
Page File: 165MB used, 4776MB 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.
Sound Tab 2: 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 7300 GT
Manufacturer: NVIDIA
Chip type: GeForce 7300 GT
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0395&SUBSYS_04020000&REV_A1
Display Memory: 128.0 MB
Current Mode: 1920 x 1200 (32 bit) (60Hz)
Monitor: Default Monitor
Monitor Max Res:
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.7519 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 5/16/2008 14:01:00, 6108928 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 5/16/2008 14:01:00, 6557408 bytes
Device Identifier: {D7B71E3E-40D5-11CF-EF7E-092400C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0395
SubSys ID: 0x04020000
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A
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: Logitech USB Headset
Default Sound Playback: Yes
Default Voice Playback: No
Hardware ID: USB\Vid_046d&Pid_0a0b&Rev_1013&MI_00
Manufacturer ID: 65535
Product ID: 65535
Type: WDM
Driver Name: usbaudio.sys
Driver Version: 5.01.2600.5512 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 4/13/2008 14:45:12, 60032 bytes
Other Files:
Driver Provider: Microsoft
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 100, 200000
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
Description: Realtek HD Audio output
Default Sound Playback: No
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0885&SUBSYS_106B1000&REV_1001
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RtkHDAud.sys
Driver Version: 5.10.0000.5469 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 10/8/2007 20:59:17, 4607488 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 8000, 192000
Static/Strm HW Mix Bufs: 33, 32
Static/Strm HW 3D Bufs: 33, 32
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: Yes, Yes
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
-
I assume you are running BOOTCAMP to run XP on it.
With the mobile Intel CPU you need to set the game to run in "Windows 98/ME" compatibility mode on the Apple due to the lack of dual high resolution clocks for the dual core CPU.
Right-click on the Aces High II startup ICON. Select "Properties". Select the "Compatibility" tab, and check the option to have the game run in compatibility mode, then select the "Windows 98/ME" option. This will force the game to run on one CPU.
-
Thanks Skuzzy, I'll try that. The other thing that seems to work well is deleting the video8.cfg file everytime I play. I'll let u know.,
-
Ok, did some experimenting with my watch and the game. I did like you said and enabled compatiblility with 98. The longest I was able to play today was about 15 minutes before the system locked up on me. Most times, it locks up within the first 5 minutes.
However, if I delete the video8.cfg file, I have no problems. I'm not a programmer but my reasoning tells me the problem stems from something in the last patch and the driver for my GeForce 7300 card. I've been playing with this system since Jan and had no problems with it until I installed the patch. Any other ideas Skuzzy? :pray
-
this sounds a like what I am dealing with...except I am not on a Mac. I tried to delete that video9 file...didnt work for me. I stay on game for about 1-5 minutes every time. Then it freezes up with last sound heard...or repeating last vox transmission. I can only reboot PC to get out of AH at that point.
-
I think I spoke too soon. Even with deleting the video file, I'm still getting disco'd.
This is getting really frustrating since I love to play this game. However, it doesn't make much sense paying for a subscription if I can't even play.
-
Wait a minute. Are you getting a disco? That is very different than a lockup.
-
Sorry, I meant lock up.
-
This sounds exactly like what happened to me, and my pc about 11 months ago, so long ago ive had to re sign up to the game and forums! Skuzzy tried to help me with it back then ( http://bbs.hitechcreations.com/smf/index.php/topic,234116.0.html ), and again more recently. I called in every computer whizz kid i know, learnt a lot about pcs and how the work, replaced damn near every part of the PC, in some cases several times.....
and in the end i spent 200squid on a new machine, new card, more ram etc, and it works fine. never did get to the bottom of it.
-
Hi Jing,
Unfortunately, I can't spend a whole lot more since the system I have is already a state of the art Mack daddy system that cost me mucho quids.
What's frustrating is that it worked fine once.
-
Ok, did some experimenting with my watch and the game. I did like you said and enabled compatiblility with 98. The longest I was able to play today was about 15 minutes before the system locked up on me. Most times, it locks up within the first 5 minutes.
However, if I delete the video8.cfg file, I have no problems. I'm not a programmer but my reasoning tells me the problem stems from something in the last patch and the driver for my GeForce 7300 card. I've been playing with this system since Jan and had no problems with it until I installed the patch. Any other ideas Skuzzy? :pray
just to clarify, the only change you did was the patch for the game, you did NOT update your video driver right?
-
i updated video drivers, SP3 and the game when I got back. I have since uninstalled game adn reinstalled, rolled back video drivers to previous known good driver that worked for me. no luck so far.
-
I did every possible combination. Again, remember that there is nothing else loaded on this system except for the OS (and all its baggage) and the game.
Since I've been suffering for several months with this, I've tried every possible combination that I can think of.
1. Uninstall, reinstall the game, driver, OS... etc....
2. Do it in different order reversing and going forward on driver versions.
3 Installing SP3 on old OS install, installed it on new OS install.
4. Enabling win 98 compatibility, disabling....
5. Deleting the video cfg file.
6. Playing with resolution an texture etc...
When the system locks up, I've been at the wide range of possible frames per second. I've also locked up with CNT still counting down and with CNT at zero. I've locked up in the middle of a dogfight, switching views like crazy. I've also locked up sitting in the tower or looking at the map. Heck, I've even locked up in a tank staring at a tree.
I thought for sure a fresh install of the OS woulda done it but it did no.
-
I have had problems with SP3 and have since not installed it on any of our computers. I have heard both good and bad about it.
Have you tried simply moving the "HTC" folder to another name and re-installing the game? Do not remove the folder, just rename it.
Also, do not install any custom sounds!!!!
-
Alright, I'll try this and see what happens. Thx Skuzzy.
-
had similar prob awhile ago - was reminded to set dx sound acceleration to down 3/4... what is yours set at - sometimes i had the vox looping and needed to hard boot out of the game
no problems since i did that
NwBie
-
Ok, hope I don't jinx myself but Nwbie's suggestion seemed to do the trick. Logged 2.5 hours of playing time without a single problem.
Thx guys!
-
Hi G,
Have a iMac myself. I used XP with SP 2 last time I played with no problems. When I partitioned, I didn't leave enough room for SP3 unintentionally. Don't think I've ever played with SP3 installed in the past either.
But it sound like you got it sorted out with the sound acceleration adjustment.
Good Luck,
hap
-
Also, do not install any custom sounds!!!!
slight hijack here, sorry. But i have heard that said a lot. I'm wondering why we shouldn't install custom sounds?
-
Many of the custom sound packs have a problems in the sound files that will cause the game to crash.
Also note, when using an onboard sound chip the custom sound files can cause massive stutters due to extensive resources requirements onboard sound chips simply lack. Not always, but they can do it and they do do it. Onboard sound chips are highly CPU dependent and require much more CPU than a good add in sound card does.
Now, there is no doubt someone out there thinks the onboard sound chips are fine and not causing them any troubles at all. All that means is they have attributed any troubles they do have to the sound chip or they have more than enough CPU due to having a very slow video card and the CPU is waiting on the video card. In which case they will only see stutters and pauses infrequently.
If you want the most from the game, then either avoid using onboad sound chips or avoid using custom high resolution sounds. In all cases, avoid using the existing sound packs as many have broken sound files which will cause the game to crash.
-
Many of the custom sound packs have a problems in the sound files that will cause the game to crash.
Also note, when using an onboard sound chip the custom sound files can cause massive stutters due to extensive resources requirements onboard sound chips simply lack. Not always, but they can do it and they do do it. Onboard sound chips are highly CPU dependent and require much more CPU than a good add in sound card does.
Now, there is no doubt someone out there thinks the onboard sound chips are fine and not causing them any troubles at all. All that means is they have attributed any troubles they do have to the sound chip or they have more than enough CPU due to having a very slow video card and the CPU is waiting on the video card. In which case they will only see stutters and pauses infrequently.
If you want the most from the game, then either avoid using onboad sound chips or avoid using custom high resolution sounds. In all cases, avoid using the existing sound packs as many have broken sound files which will cause the game to crash.
Skuzzy
I have been using a sound pack for awhile now - haven't noticed any issues - but have always blamed my cheap vid card for any stutters and such
How can i go about just reloading the standard sound files - ie: do i just delete the sounds folder and the game will auto reload the sounds when I log in
Or is there a download file i need to go with?
I dont really care whether the sounds are all that special - so I will try the suggestion about sticking with the standard game sounds..
NwBie
-
Skuzzy
I have been using a sound pack for awhile now - haven't noticed any issues - but have always blamed my cheap vid card for any stutters and such
How can i go about just reloading the standard sound files - ie: do i just delete the sounds folder and the game will auto reload the sounds when I log in
Or is there a download file i need to go with?
I dont really care whether the sounds are all that special - so I will try the suggestion about sticking with the standard game sounds..
NwBie
Just delete, move or rename the "sounds" folder.
-
I've been using Mitsu's sound pack with no problems. I recently grabbed Ranger's latest and really like it. I ended up removing it because every time I fired machine guns alone (like when my cannon was empty or the plane only had MG), I would instantly crash and the PC rebooted itself. I guess I'll wait until I build my new rig with a good sound card.
I renamed my Mitsu sounds folder before installing the new Ranger sounds, so it was a simple matter of renaming that folder back to "sounds" to get them back again.
-
Many of the custom sound packs have a problems in the sound files that will cause the game to crash.
Also note, when using an onboard sound chip the custom sound files can cause massive stutters due to extensive resources requirements onboard sound chips simply lack. Not always, but they can do it and they do do it. Onboard sound chips are highly CPU dependent and require much more CPU than a good add in sound card does.
Now, there is no doubt someone out there thinks the onboard sound chips are fine and not causing them any troubles at all. All that means is they have attributed any troubles they do have to the sound chip or they have more than enough CPU due to having a very slow video card and the CPU is waiting on the video card. In which case they will only see stutters and pauses infrequently.
If you want the most from the game, then either avoid using onboad sound chips or avoid using custom high resolution sounds. In all cases, avoid using the existing sound packs as many have broken sound files which will cause the game to crash.
i am using mitsu's sound pack with and onboard card. i dont really notice any lock ups or stutters due to sound being played. when i did have those problems i blamed it on the cheap vid card i had bought which burnt up and quit working after less than 9 months.
im playing on my onboard video and onboard sound now. i can still play fairly well but only in less poplulated arenas like MW DA and TA, frame rates range between 20 and 45. i can't touch a LW arena without crashing. seems more than 50 people on and i cant see nothing. its no big deal jus waiting for money to build my system which is gonna be a while from now as i just started colledge maybe i can use a little of that student loan money? lol
but one good thing came of it i found out that i really like the mid war arena its a different style of play, and besides all i really do is fighter and jabo runs. but to me a jabo run is pointless if no one is defending. so i mainly fly a spit 9/f6f combo and its really fun.
-
Many of the custom sound packs have a problems in the sound files that will cause the game to crash.
Also note, when using an onboard sound chip the custom sound files can cause massive stutters due to extensive resources requirements onboard sound chips simply lack. Not always, but they can do it and they do do it. Onboard sound chips are highly CPU dependent and require much more CPU than a good add in sound card does.
Now, there is no doubt someone out there thinks the onboard sound chips are fine and not causing them any troubles at all. All that means is they have attributed any troubles they do have to the sound chip or they have more than enough CPU due to having a very slow video card and the CPU is waiting on the video card. In which case they will only see stutters and pauses infrequently.
If you want the most from the game, then either avoid using onboad sound chips or avoid using custom high resolution sounds. In all cases, avoid using the existing sound packs as many have broken sound files which will cause the game to crash.
thanks for explainging that, sir. :salute
-
Gremlins are back with a vengence. Don't know if this helps Skuzzy but here is the corresponding App Event Log for a typical lock up:
Event Type: Information
Event Source: DrWatson
Event Category: None
Event ID: 4097
Date: 8/28/2008
Time: 8:14:01 AM
User: N/A
Computer: GAMING-89B96FA2
Description:
The application, C:\Program Files\HTC\Aces High II\aceshigh.exe, generated an application error The error occurred on 08/28/2008 @ 08:14:01.406 The exception generated was c0000005 at address 00000000 (<nosymbols>)
-
Doesn't help. Bogus information. Not unusual when a crash like that occurs.
-
Alright Skuzzy. Maybe I should call you and you can help me get you what you need to help me fix this then?
I'll call tomorrow.
-
I just wonder if SP3 is compatible with the Apple computers. Did you install SP3 or did it come with your XP installation?
I assume you have tried running the game in "Windows 98/ME" compatibility mode as well.
-
Hi Skuzzy,
I've tried it with and without SP3. Interesting thing though is that there was an update to Boot Camp drivers released in Apr. I just installed it.
Yes, I've tried running it in Windows 98/ME mode too.
I'll let you know if the updated drivers help.
-
Just to tap in. (using for time frame) After the last update, lockups started to occur at long intervals and slowly progressed to the point of about every other flight if I'm lucky. Started to beleive that I was overloading the main board by using video, sound and net resources off of it. Never had a prob before, but started removing some of these resources and added a better vid card, separate sound card, separate net card. After each one installed, it helped for about 4 flights then back to every other flight. Had reinstalled the game numerous times, OS numerous times and made sure of all updates for each item and chip. Last shot I have before beliving the MoBo is about ready to go, is changing the RAM as maybe one or the other bank is going bad and causing the lockup problem.
A few others that haven't posted here are having the sme problem as being described in this post. They could all be separate issues, I don't know..... but will keep watching and after the RAM gets here and installed, if that doesn't take care of it (have tried all posted items mentioned also), I'll send in to ya the data for a final look before I consider upgrading the MoBo.
-
The 7300 is a low end video card. I thought we had already covered that. Things like the "Maximum Texture Size" should be 256 and no advanced video card features should be enabled.
The latest NVidia drivers are also problmatic.