Computer shuts off or reboots.

[Phaser11]

OK,
 I left the game a few months back untill I saved enough money to buy another computer. The one I had been using shut doen or rebooted when ever that was a lot of stuff going on (bombing, tank battles ect).

Now I have a new computer, This is a new computer, video card monitor, mouse, keyboard and joy stick. I re join aces high and the first battle I am in the this reboots just like last time. I really don't where to start here guys, Other flight sims work just fine, other games are no problem, only this one. Can someone please let me know what I need to load to fix this?

Thanks in advanced.

Phaser11

[The Fugitive]

Post the first third of your dxdiag here as well as what setting your using in the game ...texture size, bit mapping and so on.

It sounds like your pushing your computer too hard trying to run to much stuff.

[Tigger29]

Pushing a computer too hard (unless you're overclocking) shouldn't result in reboots/shutting down or any of that... yes a severe loss of performance but no not a shutdown.

First off, you have to look at any hardware that was reused from the old computer to the new.  Anything could be suspect.  If you are in fact not reusing ANYTHING, then there really can be only two options.

1> Defective computer... seems awfully coincidental, but anything is possible.  If it's a brand new computer, then you should obviously have a warranty.  If you bought a used one... well all bets are off

2> Poor power supply.  Yes, the computer's power supply could definitely be suspect, but what I'm talking about here is the electricity coming to your house.  If there is a lot of interference (such as sharing a circuit with say.. a microwave oven... HAM radio.. air conditioner, etc) this could definitely cause similar issues as well.  Try moving your power source to a different outlet (which utilizes a different circuit in the house)... likewise you can try purchasing a good UPS (uninterrupted power supply) which is kind of like a surge protector with a battery in it.  These can be good for 'cleaning up' and 'despiking' electrical input.

A computer is kind of like a car.  During light use it can tolerate a lot of less than ideal conditions... however under a heavy load is when any small problem can cause serious issues.  This is where 'borderline' conditions can turn into full-blown issues.  Take a car that is a gallon low on coolant/antifreeze.  On a 70 degree day... no issues whatsoever.. but try to drive it that way through a desert... and overheat city!

Unfortunately, without knowing more about your exact hardware/software and other factors, all we can do at this point is guess.

[Chalenge]

I hate to disagree with you Tigger but you missed one trait of the average computer buyer that often times goes overlooked. Many people buy big and powerful in the CPU and Graphics departments and then buy the cheapest PSU they can lay their hands on. In that case what ends up happening is the GPU seems to work just fine for most games but Aces High isnt most games and the load can go beyond the standard level. The minute the entire system places a high current demand upon the PSU it becomes overtasked and you get a reboot. This is a result of the PSUs protection system so that the system doesnt permanently fail. Eventually that event occurs anyway and it can take the CPU MB DIMMs and GPUs with it.

[ColTomb]

If you are using USB to connect to the intardnet..Don't. Use ethernet cable.
Your modem may be faulty. Call your ISP and have them run some checks on it.
Did you transfer/clone any programs,files,viruses,spyware to your new harddrive?
Turn off power management to your network adaptor and your USB devices.
Click start> R click my computer> L click properties> L click hardware>L click Device manager>
L click the x to expand network adapters> Double click your network adaptor> L click power management>
uncheck allow computer to turn off this device..Expand your USB devices while your there and turn off
their power management..You will see a power management tab on any device that you can control..
Is there any programs set to auto update ? Like one of the other post said,without more info,it's all a
guess...these are my guesses...

[Tigger29]

I hate to disagree with you Tigger but you missed one trait of the average computer buyer that often times goes overlooked. Many people buy big and powerful in the CPU and Graphics departments and then buy the cheapest PSU they can lay their hands on. In that case what ends up happening is the GPU seems to work just fine for most games but Aces High isnt most games and the load can go beyond the standard level. The minute the entire system places a high current demand upon the PSU it becomes overtasked and you get a reboot. This is a result of the PSUs protection system so that the system doesnt permanently fail. Eventually that event occurs anyway and it can take the CPU MB DIMMs and GPUs with it.

Yes Challenge, you are completely correct.. it is very possible he has more video than the computer's power supply can handle, but the way he worded things leads me to believe that he purchased a new, pre-built system due to the fact that he mentioned that he bought a new computer... not built a new one.  My ideas were based on that fact.

Regardless, this is exactly why I mentioned that it is impossible to really give anything truly helpful without more information about his hardware configuration...

[Chalenge]

You are right about the need for more information.

I have a squad mate that recently bought a prebuilt system (Dell). Not only was it not set up to make use of the SLI cards it came with but the PSU was not up to the job. It happens so what can you say? I think the system he had before that actually died because the PSU finally had enough (it was also an SLI system - a Dell - and the PSU was not rated for two cards).

[Phaser11]

------------------
System Information
------------------
Time of this report: 7/11/2010, 09:48:03
       Machine name:
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_rtm.040803-2158)
           Language: English (Regional Setting: English)
System Manufacturer: NVIDIA
       System Model: AWRDACPI
               BIOS: )Phoenix - Award WorkstationBIOS v6.00PG
          Processor: AMD Athlon(tm) 64 Processor 3700+,  MMX,  3DNow, ~2.2GHz
             Memory: 1024MB RAM
          Page File: 378MB used, 2083MB 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.
        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 FX 5200
     Manufacturer: NVIDIA
        Chip type: GeForce FX 5200
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0322&SUBSYS_194D270F&REV_A1
   Display Memory: 256.0 MB
     Current Mode: 1280 x 1024 (32 bit) (75Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0011.6921 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 12/5/2007 01:41:00, 5773568 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 12/5/2007 01:41:00, 7435392 bytes
Device Identifier: {D7B71E3E-4062-11CF-B65F-463900C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x0322
        SubSys ID: 0x194D270F
      Revision ID: 0x00A1
      Revision ID: 0x00A1
      Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D
 Deinterlace Caps: {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {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
                   {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {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 Live! 24-bit
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_1102&DEV_0007&SUBSYS_100A1102&REV_00
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: P17.sys
         Driver Version: 5.12.0001.0514 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 6/15/2007 11:47:26, 1127936 bytes
            Other Files:
        Driver Provider: CREATIVE
         HW Accel Level: Full
              Cap Flags: 0xF5F
    Min/Max Sample Rate: 4000, 96000
Static/Strm HW Mix Bufs: 64, 63
 Static/Strm HW 3D Bufs: 64, 63
              HW Memory: 0
       Voice Management: Yes
 EAX(tm) 2.0 Listen/Src: Yes, Yes
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
               Registry: OK
      Sound Test Result: Not run

            Description: Realtek AC97 Audio
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: PCI\VEN_10DE&DEV_0059&SUBSYS_F64A270F&REV_A2
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: ALCXWDM.SYS
         Driver Version: 5.10.0000.6300 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 9/24/2008 10:40:22, 4122368 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: 26, 25
 Static/Strm HW 3D Bufs: 26, 25
              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

---------------------
Sound Capture Devices
---------------------
            Description: SB Live! 24-bit
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: P17.sys
         Driver Version: 5.12.0001.0514 (English)
      Driver Attributes: Final Retail
          Date and Size: 6/15/2007 11:47:26, 1127936 bytes
              Cap Flags: 0x41
           Format Flags: 0xFFF

            Description: Realtek AC97 Audio
  Default Sound Capture: No
  Default Voice Capture: No
            Driver Name: ALCXWDM.SYS
         Driver Version: 5.10.0000.6300 (English)
      Driver Attributes: Final Retail
          Date and Size: 9/24/2008 10:40:22, 4122368 bytes
              Cap Flags: 0x41
           Format Flags: 0xFFF

-----------
DirectMusic
-----------
        DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
     DLS Version: 1.00.0016.0002
    Acceleration: n/a
           Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
                  Realtek AC97 Audio, Software (Kernel Mode), Output, DLS, Internal
                  SB Live! 24-bit, Software (Kernel Mode), Output, DLS, Internal
                  Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
                  Creative SoundFont Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
                  Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No 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 Controller
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x075C
        FF Driver: n/a

Poll w/ Interrupt: No
         Registry: OK

[TequilaChaser]

------------------
System Information
------------------
Time of this report: 7/11/2010, 09:48:03
       Machine name:
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_rtm.040803-2158)
           Language: English (Regional Setting: English)
System Manufacturer: NVIDIA
       System Model: AWRDACPI
               BIOS: )Phoenix - Award WorkstationBIOS v6.00PG
          Processor: AMD Athlon(tm) 64 Processor 3700+,  MMX,  3DNow, ~2.2GHz
             Memory: 1024MB RAM
          Page File: 378MB used, 2083MB available
        Windows Dir: C:\WINDOWS

OK,
 I left the game a few months back untill I saved enough money to buy another computer. The one I had been using shut doen or rebooted when ever that was a lot of stuff going on (bombing, tank battles ect).

Now I have a new computer, This is a new computer, video card monitor, mouse, keyboard and joy stick. I re join aces high and the first battle I am in the this reboots just like last time. I

is this a just a new computer to you, but is actually an older model PC? someone was selling?

all your drivers are 2 years old or older and you are running winXP SP2 still, and only have 1 gig of Ram and are using a quiet old Nvidia 5200 model video card..

or was this your old PC  DXDIAG report?

what is your PSU ( Power Supply ) ratings/type   and what settings are you trying to run the game at?

I was unaware Nvidia actually built PC's...... but your system manufacturer says that is who built it ????

you are running 1280 x 1024 screen res.. you might want to back that down to 1024 x 768 or lower, and try using either 256 or 128 textures  and turn off all advanced graphics that you might be able to turn on.....

and with that low of RAM and that video card, you might want to tweak your WinXP SP2 down to be running around 20 processes at idle..... with your pagefile info posted, you prob in the 28 to 35 processes range...... the less processes you have the more resources you will have available from that CPU for Aces high...

edit: also back off on our Direct X sound acceleration to either 1/2 or basic....... you have it set at FULL.. both FULL & maybe even 3/4 will be too much strain from the REALTEK  soundchip onboard for the CPU you have

still would like to know your PSU wattage....... but with that system a 250 watt would prob be ok...... you just can not push the graphic settings is all..

hope this helps..

[gyrene81]

TC, that's either a Geforce or Nforce motherboard. WinXP shows the chipset manufacturer. Processor is from 2005.

[TequilaChaser]

TC, that's either a Geforce or Nforce motherboard. WinXP shows the chipset manufacturer. Processor is from 2005.

thx.. early mornign ( or late wake up ) involuntary brain malfunctioning....... need..... more...... coffee.....  

btw. how did I do on y synopsis of his problem???

[gyrene81]

thx.. early mornign ( or late wake up ) involuntary brain malfunctioning....... need..... more...... coffee.....  

btw. how did I do on y synopsis of his problem???

LOL...man considering what you accomplished with that frankenstein system you put together from those used parts...I wouldn't argue with your recommendations.   

[Chalenge]

That video card was one of the worst for problems. Worse with the sound card you have (Live!) and the latest drivers for your chipset (I didnt actually check the driver numbers) you will never be able to avoid the random reboots due to a known conflict. Im surprised you are not getting complete system lockups actually no matter what the date of your drivers.

Also you are showing two audio chipsets (onboard and the Live! card) which will create conflicts.

[Phaser11]

OK TequilaChaser
I put the chages in I could (not changing any parts out) and it is now working fine!

You come to Detroit and the first 3 beers are on me! (even if it fails again, I has never worked this good!)

[TequilaChaser]

Also you are showing two audio chipsets (onboard and the Live! card) which will create conflicts.

yep I missed that..was going to comment on it when I read first part of your reply, but chalenge caught it & called it out.... Phaser make sure that both of these are not working at the same time or make sure that while checking proerties/drivers  that no conflicts are coming up... Chalenge  Good Eye.....


glad it is working good for you Phaser  ~S~