Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: Ardy123 on January 10, 2011, 04:03:57 PM

Title: Random crashes possible associated with vox
Post by: Ardy123 on January 10, 2011, 04:03:57 PM
I enjoy playing the game a lot, but sadly about twice a night, the game crashes to desktop. It seems to be associated with a lot of vox traffic, but I'm not sure. I could get call stack from  visual studio if thats helpful... (I'd have to install VS again).


Title: Re: Random crashes possible associated with vox
Post by: Ardy123 on January 10, 2011, 04:06:48 PM
dx dag info
dxdiag output is below
------------------
System Information
------------------
Time of this report: 10/5/2010, 22:43:58
       Machine name: EARTH
   Operating System: Windows Vista™ Ultimate (6.0, Build 6002) Service Pack 2 (6002.vistasp2_gdr.100608-0458)
           Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
       System Model: System Product Name
               BIOS: BIOS Date: 07/20/09 20:48:23 Ver: 08.00.14
          Processor: Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz (2 CPUs), ~3.2GHz
             Memory: 4094MB RAM
          Page File: 1495MB used, 6888MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
     DxDiag Version: 7.00.6002.18107 32bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
        Card name: NVIDIA GeForce GTX 275
     Manufacturer: NVIDIA
        Chip type: GeForce GTX 275
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_05E6&SUBSYS_0E0619F1&REV_A1
   Display Memory: 2668 MB
 Dedicated Memory: 877 MB
    Shared Memory: 1791 MB
     Current Mode: 1920 x 1200 (32 bit) (60Hz)
          Monitor: Generic PnP Monitor
      Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
   Driver Version: 8.17.0012.5896 (English)
      DDI Version: 10
   BGRA Supported: Yes
Driver Attributes: Final Retail
 Driver Date/Size: 7/10/2010 05:38:00, 12471400 bytes
      WHQL Logo'd: n/a
  WHQL Date Stamp: n/a
Device Identifier: {D7B71E3E-46A6-11CF-496D-0A2E1FC2C535}
        Vendor ID: 0x10DE
        Device ID: 0x05E6
        SubSys ID: 0x0E0619F1
      Revision ID: 0x00A1
      Revision ID: 0x00A1
      Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
     DDraw Status: Enabled
       D3D Status: Enabled
       AGP Status: Enabled

-------------
Sound Devices
-------------
            Description: Speakers (Creative SB X-Fi)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_1102&DEV_000B&SUBSYS_00431102&REV_04
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1348 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 7/7/2010 22:16:24, 697816 bytes
            Other Files:
        Driver Provider: Creative
         HW Accel Level: Basic
              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

            Description: SPDIF Out (Creative SB X-Fi)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: PCI\VEN_1102&DEV_000B&SUBSYS_00431102&REV_04
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1348 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 7/7/2010 22:16:24, 697816 bytes
            Other Files:
        Driver Provider: Creative
         HW Accel Level: Basic
              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
Title: Re: Random crashes possible associated with vox
Post by: guncrasher on January 11, 2011, 02:19:42 PM
I am having the same problem, so far this tour 9 of 40 flights in buffs have been discos.  all i get is somebody talking on vox and boom, it crashes.

semp
Title: Re: Random crashes possible associated with vox
Post by: Chalenge on January 11, 2011, 04:36:57 PM
Right off Vista + Nvidia GPU + Sound Blaster X-Fi = formula for instability. I was in denial about it too but once I got away from Vista it became obvious. Vista was supposed to be the ultimate multimedia experience with DRM but something went horribly wrong. I would bet that if you upgrade to W7 or downgrade to XP (either one) you would be instantly happy. Personally I think Windows 7 (32 bit) is the best OS I have ever seen but sadly my XP experience was with a very unstable system and now even though I have it I never use it.

I also think that if you decide to utilize SB X-Fi of any flavor you should expect some small amount of crashes and other problems. SB just isnt that great.
Title: Re: Random crashes possible associated with vox
Post by: Ardy123 on January 11, 2011, 05:12:36 PM
I haven't had issues with other games, which often are more resource intensive than AH.
Title: Re: Random crashes possible associated with vox
Post by: Chalenge on January 12, 2011, 06:44:16 AM
Thats interesting because I have hundreds of other games and none of them are as resource intensive as Aces High.
Title: Re: Random crashes possible associated with vox
Post by: katanaso on January 12, 2011, 08:11:44 AM
I get crashes from Vox too, but it's almost always after alt-tabbing back into the game.  It's random, but the first Vox can lock up the system to where I have to close the program, disable the device driver, enable the device driver, and then re-launch AH.

This is with Windows 7 64bit, Asus Xonar D1, E8400, Ati 5850.

mir
Title: Re: Random crashes possible associated with vox
Post by: TinmanX on January 13, 2011, 04:43:53 PM
Vox is crashing my game also. Have uninstalled and re-installed a fresh download, taken out all custom sound files and I'm still getting crashes.

------------------
System Information
------------------
Time of this report: 1/13/2011, 14:40:48
       Machine name: JERRY
   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621)
           Language: English (Regional Setting: English)
System Manufacturer: Acer
       System Model: Aspire G7750
               BIOS: BIOS Date: 03/31/10 12:33:25 Ver: 08.00.15
          Processor: Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz (8 CPUs), ~2.8GHz
             Memory: 12288MB RAM
Available OS Memory: 12278MB RAM
          Page File: 2132MB used, 22423MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7600.16385 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
          Card name: NVIDIA GeForce GTX 470
       Manufacturer: NVIDIA
          Chip type: GeForce GTX 470
           DAC type: Integrated RAMDAC
         Device Key: Enum\PCI\VEN_10DE&DEV_06CD&SUBSYS_079F10DE&REV_A3
     Display Memory: 4064 MB
   Dedicated Memory: 1248 MB
      Shared Memory: 2815 MB
       Current Mode: 1920 x 1080 (32 bit) (60Hz)
       Monitor Name: Generic PnP Monitor
      Monitor Model: VE246
         Monitor Id: ACI24F9
        Native Mode: 1920 x 1080(p) (60.000Hz)
        Output Type: DVI
        Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.17.0012.6099 (English)
     Driver Version: 8.17.12.6099
        DDI Version: 10.1
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 10/16/2010 10:55:00, 12788840 bytes
        WHQL Logo'd: n/a
    WHQL Date Stamp: n/a
  Device Identifier: {D7B71E3E-458D-11CF-BD64-93271DC2C535}
          Vendor ID: 0x10DE
          Device ID: 0x06CD
          SubSys ID: 0x079F10DE
        Revision ID: 0x00A3
 Driver Strong Name: oem30.inf:NVIDIA_SetA_Devices.NTamd64.6 .1:Section004:8.17.12.6099:pci\ven_10de&dev_06cd
     Rank Of Driver: 00E62001
        Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
   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
                    D3D9 Overlay: Supported
            DXVA-HD: Supported
       DDraw Status: Enabled
         D3D Status: Enabled
         AGP Status: Enabled

-------------
Sound Devices
-------------
            Description: Headset (USB PnP Sound Device          )
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: USB\VID_0D8C&PID_013C&REV_0100&MI_00
        Manufacturer ID: 65535
             Product ID: 65535
                   Type: WDM
            Driver Name: USBAUDIO.sys
         Driver Version: 6.01.7600.16385 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 7/13/2009 16:06:32, 109568 bytes
            Other Files:
        Driver Provider: Microsoft
         HW Accel Level: Basic
              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

            Description: Speakers (Realtek High Definition Audio)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10250326&REV_1002
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RTKVHD64.sys
         Driver Version: 6.00.0001.5969 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 10/27/2009 19:40:58, 2018080 bytes
            Other Files:
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Basic
              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

            Description: Realtek Digital Output (Realtek High Definition Audio)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10250326&REV_1002
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RTKVHD64.sys
         Driver Version: 6.00.0001.5969 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 10/27/2009 19:40:58, 2018080 bytes
            Other Files:
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Basic
              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
Title: Re: Random crashes possible associated with vox
Post by: bustr on January 13, 2011, 04:56:42 PM
Ardy you have a tech job. Borrow an OEM 32bit copy from one of your tech guys. Or buy one. Just load up a dual boot or new installation of win7 and get off vista. I have your vid card and sound card on Win7 64bit and no sound related discos. Interesting point is I used to get apparent VOX lockups and TDR resets once in a while. With 2.22 and its patch I've not had a single TDR or VOX lockup.

More often with the VOX lockup(looping sound) it would really be a video TDR freezing the system and then win7 would recover from it and resume the game up to 30 seconds later. On rare occasions the TDR which seemed like a VOX lockup would freeze my system requiring a reboot or return to the desktop and killing the game. Some of the more severe lockups would cause a aceshigh.exe error and a mini bug report. Debugging those always showed a video TDR event not a sound driver issue.

The two most intensive resource events in the game client are video rendering and sound. Most of my TDR used to happen while firing 5inch and 8inch batteries while looking into the sun during intensive sea battels. In the last year or so some of them were during furballs with everyone screaming on VOX. Win7 has handeled these better than XP by freezing my system for up to 30sec and then resuming my game most of the time. XP would just lockup or crash. But, with the last version release so far I've not experienced a TDR event.

I wonder how many of everyones VOX lockups may be because of the conversion of old maps to the new format.
Title: Re: Random crashes possible associated with vox
Post by: TequilaChaser on January 13, 2011, 05:08:48 PM
Vox is crashing my game also. Have uninstalled and re-installed a fresh download, taken out all custom sound files and I'm still getting crashes.

------------------
System Information
------------------
Time of this report: 1/13/2011, 14:40:48
       Machine name: JERRY
   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621)
           Language: English (Regional Setting: English)
System Manufacturer: Acer
       System Model: Aspire G7750
               BIOS: BIOS Date: 03/31/10 12:33:25 Ver: 08.00.15
          Processor: Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz (8 CPUs), ~2.8GHz
             Memory: 12288MB RAM
Available OS Memory: 12278MB RAM
         Page File: 2132MB used, 22423MB available  <----- 2132 pagefile used shows you got probably near 75 to 85 processes running, a clean system Win 7 64 bit is around 35 to 45
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
-------------
Sound Devices
-------------
            Description: Headset (USB PnP Sound Device)   <---- USB headset/mic takes alot more power consumption / draw
Default Sound Playback: Yes
 Default Voice Playback: Yes
         
 Hardware ID: USB\VID_0D8C&PID_013C&REV_0100&MI_00
        Manufacturer ID: 65535
             Product ID: 65535
                   Type: WDM
            Driver Name: USBAUDIO.sys
         Driver Version: 6.01.7600.16385 (English)
  

- one or more of the processes in the background running during AH game play is probably causing your problem of crashing

- USB audio devices also put a larger strain on the whole PC system

just a quick look at the PC I am on shows 42 processes running with pagefile used of 1026mb  on win 7 Ult. 64 bit

hope this helps
Title: Re: Random crashes possible associated with vox
Post by: TinmanX on January 13, 2011, 06:20:59 PM
That is how my system looks out of game. As soon as I launch AH I'm running 43 processes including Aces High;
(http://sphotos.ak.fbcdn.net/hphotos-ak-snc6/hs001.snc6/165111_496926939797_827524797_5853741_671737_n.jpg)



I don't have a USB headset, I have a 3.5mm.

Title: Re: Random crashes possible associated with vox
Post by: TequilaChaser on January 13, 2011, 06:49:21 PM
That is how my system looks out of game. As soon as I launch AH I'm running 43 processes including Aces High;
(http://sphotos.ak.fbcdn.net/hphotos-ak-snc6/hs001.snc6/165111_496926939797_827524797_5853741_671737_n.jpg)



I don't have a USB headset, I have a 3.5mm.



http://sphotos.ak.fbcdn.net/hphotos-ak-snc6/hs001.snc6/165111_496926939797_827524797_5853741_671737_n.jpg

picture was not showing up on my end with the img tags used

so your processes drop to under 40 then, so are you using some type of tweaker program for this to happen???

could you click on "show processes from all users" and take another snap shot to show all 42 processes???

edit: picture showing now correctly

your headset plugged into the keyboard maynot be USB, but it looks as if your keyboard is USB and there for launches the USBAudio driver since that is what it shows as default sound in and default sound out.......... unless I am mis-reading the DXDIAG
Title: Re: Random crashes possible associated with vox
Post by: Ardy123 on January 15, 2011, 07:31:15 PM
Ardy you have a tech job. Borrow an OEM 32bit copy from one of your tech guys. Or buy one. Just load up a dual boot or new installation of win7 and get off vista. I have your vid card and sound card on Win7 64bit and no sound related discos. Interesting point is I used to get apparent VOX lockups and TDR resets once in a while. With 2.22 and its patch I've not had a single TDR or VOX lockup.

More often with the VOX lockup(looping sound) it would really be a video TDR freezing the system and then win7 would recover from it and resume the game up to 30 seconds later. On rare occasions the TDR which seemed like a VOX lockup would freeze my system requiring a reboot or return to the desktop and killing the game. Some of the more severe lockups would cause a aceshigh.exe error and a mini bug report. Debugging those always showed a video TDR event not a sound driver issue.

The two most intensive resource events in the game client are video rendering and sound. Most of my TDR used to happen while firing 5inch and 8inch batteries while looking into the sun during intensive sea battels. In the last year or so some of them were during furballs with everyone screaming on VOX. Win7 has handeled these better than XP by freezing my system for up to 30sec and then resuming my game most of the time. XP would just lockup or crash. But, with the last version release so far I've not experienced a TDR event.

I wonder how many of everyones VOX lockups may be because of the conversion of old maps to the new format.

I can't get  a copy of win xp32 but I might get a copy of win7 x64. Its just a hassle, because it overwrites the boot sector and messes up GRUB2, which is used already so that I can duel boot into windows and Linux.
Title: Re: Random crashes possible associated with vox
Post by: bustr on January 20, 2011, 05:23:30 PM
I'll burn some incense for you to the Unix gods and make offerings of heated personal remarks to BillyG boy for starting this mess in the first place...... :salute
Title: Re: Random crashes possible associated with vox
Post by: Ardy123 on January 20, 2011, 06:50:42 PM
I noticed that since my squad has moved to ventrillo, the crashes have happened much less.
Title: Re: Random crashes possible associated with vox
Post by: guncrasher on January 21, 2011, 12:40:49 AM
I removed my xtreme gamer sound card completely with drivers and havent had a disco since then.  using mobo/usb headset no problems in two days.  and yeah ventrillo rocks  :banana: :banana: :banana: :banana:

semp
Title: Re: Random crashes possible associated with vox
Post by: bustr on January 21, 2011, 01:51:34 AM
Few years back I had to use a USB headset for the same problems but I had an earlier SB card in that system. Turns out the eairlier card was going bad so I replaced it with an X-fi card. That was with an earlier motherboard with a single core 3Ghz CPU. This issue with lockups during VOX has been a constant with the game as long as I've been playing over three different PC, 6 video cards and 3 different sound cards since 2002.

Some versions of the game or patches of versions have been solid. Some made pull my hair out or replace/upgrade the vido or sound card. Or just build a bigger badder computer all together. If Skuzzy describes his current game PC in an off hand remark and he's describing a completely new machine from just a few months ago and it's about time for a new game version. I know its time to get a bigger stick to beat the game with at my end........
Title: Re: Random crashes possible associated with vox
Post by: Ardy123 on February 03, 2011, 02:51:31 PM
Could TDRs be happening due to inadequate cooling?

I purchased some larger case fans...

Any tools to stress the gfx card?
Title: Re: Random crashes possible associated with vox
Post by: Chalenge on February 03, 2011, 04:56:28 PM
After one month of flying Windows 7 32 bit the number of crashes of AH were 0. After two days of flying Windows 7 64 bit the number of crashes of AH so are 4. I dont believe vox is related at all but I do think networking is. It is possible it is tied to system latency. What I believe I am seeing is AH attempting to execute along some line and the system blocking the process because of a busy resource. In order to really find the source of the problem I suspect it is going to take a monitoring program of some sort which is beyond me. I have removed individual devices and drivers all the way down to the MB (still ongoing) as possible and I still have not discovered the source of the problem.
Title: Re: Random crashes possible associated with vox
Post by: bustr on February 04, 2011, 08:47:08 PM
Read this:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;969028

When it happens use the hot keys and generate your own memory dump. You will then get a Blue Screen with the following message.

*** STOP: 0x000000E2 (0x00000000,0x00000000,0x00000000,0x00000000)
The end-user manually generated the crashdump.

When it is finished, see if Skuzzy might be interested in reading it. Or debug it with Windbg your self.

The article mentions some applets also if you can get to the desktop.