Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: Chitownflyer on December 15, 2004, 01:02:06 PM

Title: New Motherboard/Crash and burn in AH
Post by: Chitownflyer on December 15, 2004, 01:02:06 PM
I have just purchased a new mother board/450w power supply/memory and Ah crashes to bootup, or locks up froze solid.

I have the following setup
Asus A7V8X-X mother board
with a AMD xp2200+ "Thoroughbred" CPU chip;1 gig of  ddr memory;
Nivida G-force MX440  Video card
with 64 meg ram on it.

I have W2000 pro OS, with all the updates and patchs installed.

I have the APG aperture size set for 128 on mboard.  and this is set for 1800hz clock. speed

AH is crashing, locking and unplayable right now.  

Now this setup is work fine for every thing else including viso/office publisher paintshop pro etc..

help!

Mark
Title: New Motherboard/Crash and burn in AH
Post by: StarOfAfrica2 on December 15, 2004, 03:49:27 PM
Your best bet is to post your DxDiagnostic report, or email it to Skuzzy.  There are lots of things that could cause a ctd, especially with a new setup.  Could be drivers, could be an overheating problem, could be processes running in the background that are taking up processor time...................

Run the DxDiagnostic program.  Run all the tests, especially in the video and sound categories.  Assuming you pass all those with no error messages, check your processes running and make sure you dont have too many, and that nothing is tying up your processor.  Check to make sure you dont have any IRQ conflicts or shared IRQ's on major components.

The DxDiagnostic report will show if you have any out of date drivers.
Title: New Motherboard/Crash and burn in AH
Post by: Chitownflyer on December 16, 2004, 02:16:44 AM
------------------
System Information
------------------
Time of this report: 12/16/2004, 02:05:59
       Machine name: ROSEBUD
   Operating System: Windows 2000 Professional (5.0, Build 2195) Service Pack 4
           Language: English (Regional Setting: English)
System Manufacturer: n/a
       System Model: n/a
               BIOS: Default System BIOS
          Processor: AMD Athlon(TM) XP 2200+, ~1.8GHz
             Memory: 1024MB RAM
          Page File: 117MB used, 2392MB available
        Windows Dir: C:\WINNT
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.0001.0904 32bit Unicode

------------
DxDiag Notes
------------
  DirectX Files Tab: No problems found.
      Display Tab 1: No problems found. DirectDraw test results: All tests were successful. Direct3D 7 test results: All tests were successful. Direct3D 8 test results: All tests were successful. Direct3D 9 test results: All tests were successful.
        Sound Tab 1: DirectSound test results: All tests were successful.
          Music Tab: DirectMusic test results: All tests were successful.
          Input Tab: No problems found.
        Network Tab: No problems found. DirectPlay test results: All tests were successful.

--------------------
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 GeForce4 MX 440
     Manufacturer: NVIDIA
        Chip type: GeForce4 MX 440
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0171&SUBSYS_00000000&REV_A3
   Display Memory: 64.0 MB
     Current Mode: 1024 x 768 (32 bit) (75Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0010.5216 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 10/6/2003 15:16:00, 4246528 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 10/6/2003 15:16:00, 1550043 bytes
Device Identifier: {D7B71E3E-4231-11CF-D077-0A2002C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x0171
        SubSys ID: 0x00000000
      Revision ID: 0x00A3
      Revision ID: 0x00A3
      Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D
 Deinterlace Caps: {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,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)=(YUY2,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {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: All tests were successful.
 D3D7 Test Result: All tests were successful.
 D3D8 Test Result: All tests were successful.
 D3D9 Test Result: All tests were successful.

-------------
Sound Devices
-------------
            Description: SB Live! Audio [FFE0]
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_1102&DEV_0002&SUBSYS_80651102&REV_0A
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: ctaud2k.sys
         Driver Version: 5.12.0001.0252 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 7/18/2002 20:47:52, 837548 bytes
            Other Files:
        Driver Provider: Creative
         HW Accel Level: Full
              Cap Flags: 0xF5F
    Min/Max Sample Rate: 4000, 191999
Static/Strm HW Mix Bufs: 32, 31
 Static/Strm HW 3D Bufs: 32, 31
              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: All tests were successful.

---------------------
Sound Capture Devices
---------------------
            Description: SB Live! Audio [FFE0]
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: ctaud2k.sys
         Driver Version: 5.12.0001.0252 (English)
      Driver Attributes: Final Retail
          Date and Size: 7/18/2002 20:47:52, 837548 bytes
              Cap Flags: 0x40
           Format Flags: 0xFFF

-----------
DirectMusic
-----------
        DLS Path: C:\WINNT\SYSTEM32\drivers\GM.DLS
     DLS Version: 1.00.0016.0002
    Acceleration: Enabled
           Ports: SB Live! DirectMusic Synthesizer [FFE0], Hardware (Kernel Mode), Output, DLS, Internal, Default Port
                  SB Live! Audio [FFE0], Software (Kernel Mode), Output, DLS, Internal
                  Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
                  SB Live! Sw Synth [FFE0] [Emulated], Hardware (Not Kernel M
Title: New Motherboard/Crash and burn in AH
Post by: Chitownflyer on December 16, 2004, 02:35:51 AM
Application exception occurred:
        App:  (pid=748)
        When: 12/16/2004 @ 02:13:15.517
        Exception number: c0000005 (access violation)

*----> System Information <----*
        Computer Name: ROSEBUD
        User Name: GAME
        Number of Processors: 1
        Processor Type: x86 Family 6 Model 10 Stepping 0
        Windows 2000 Version: 5.0
        Current Build: 2195
        Service Pack: 4
        Current Type: Uniprocessor Free
        Registered Organization: home
        Registered Owner: joe

*----> Task List <----*
   0 Idle.exe
   8 System.exe
 144 SMSS.exe
 168 CSRSS.exe
 188 WINLOGON.exe
 216 SERVICES.exe
 228 LSASS.exe
 408 svchost.exe
 436 spoolsv.exe
 516 svchost.exe
 540 mdm.exe
 572 nvsvc32.exe
 620 regsvc.exe
 644 mstask.exe
 700 WinMgmt.exe
 716 svchost.exe
1044 explorer.exe
 832 CTHELPER.exe
1096 rundll32.exe
 748 firefox.exe
1032 notepad.exe
 288 DRWTSN32.exe
   0 _Total.exe

(00400000 - 00A66000)
(77F80000 - 77FFD000)
(60070000 - 600C4000)
(60130000 - 60156000)
(7C2D0000 - 7C332000)
(7C570000 - 7C623000)
(77D30000 - 77DA1000)
(75050000 - 75058000)
(75030000 - 75044000)
(78000000 - 78045000)
(75020000 - 75028000)
(602D0000 - 60330000)
(60200000 - 60207000)
(60210000 - 60216000)
(782F0000 - 78535000)
(77F40000 - 77F7B000)
(77E10000 - 77E75000)
(63180000 - 631E9000)
(71710000 - 71794000)
(77A50000 - 77B3F000)
(60230000 - 6024A000)
(60160000 - 601B5000)
(60250000 - 602AA000)
(602B0000 - 602CB000)
(60330000 - 60344000)
(76B30000 - 76B6E000)
(779B0000 - 77A4B000)
(77820000 - 77827000)
(759B0000 - 759B6000)
(77800000 - 7781E000)
(76620000 - 76630000)
(775A0000 - 77630000)
(77840000 - 7787E000)
(770C0000 - 770E3000)
(74FD0000 - 74FEE000)
(75010000 - 75017000)
(01A30000 - 01A5B000)
(60000000 - 60045000)
(01CB0000 - 01CBD000)
(6B2C0000 - 6B2C5000)
(782C0000 - 782CC000)
(77980000 - 779A4000)
(77340000 - 77353000)
(77520000 - 77525000)
(77320000 - 77337000)
(75150000 - 7515F000)
(75170000 - 751BF000)
(7C340000 - 7C34F000)
(77BF0000 - 77C01000)
(77950000 - 7797A000)
(751C0000 - 751C6000)
(773B0000 - 773DF000)
(77380000 - 773A3000)
(77830000 - 7783E000)
(77880000 - 7790E000)
(7C0F0000 - 7C151000)
(774E0000 - 77513000)
(774C0000 - 774D1000)
(77530000 - 77552000)
(77360000 - 77379000)
(777E0000 - 777E8000)
(777F0000 - 777F5000)
(601C0000 - 601F2000)

State Dump for Thread Id 0x124

eax=02f52c8c ebx=6030d3ee ecx=00010101 edx=00000000 esi=00000000 edi=0155ecc8
eip=77e117e8 esp=0012f9e0 ebp=0012fa28 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00200202


function: WaitMessage
        77e117dd b836120000       mov     eax,0x1236
        77e117e2 8d542404         lea     edx,[esp+0x4]          ss:00ba98c7=????????
        77e117e6 cd2e             int     2e
        77e117e8 c3               ret

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
0012FA28 0078B7FA 01701058 004026FC 0155EC48 00000000 user32!WaitMessage
0012FF04 00401012 01534054 0155EC48 008A7FBC 0040102E !nsPrintSettings::GetPrintBGColors
0012FFC0 7C59893D 00000000 00000000 7FFDF000 00000000 !
0012FFF0 00000000 008A2C40 00000000 000000C8 00000100 kernel32!ProcessIdToSessionId

*----> Raw Stack Dump <----*
0012f9e0  4e 2e 51 00 00 00 00 80 - ee d3 30 60 00 00 00 00  N.Q.......0`....
0012f9f0  b0 00 0d 00 13 01 00 00 - 00 00 00 00 80 a0 2f 60  ............../`
0012fa00  8e 36 f5 02 4d 00 00 00 - 00 00 00 00 f0 ff 30 60  .6..M.........0`
0012fa10  74 8e a0 00 00 00 00 00 - 1c fa 12 00 00 00 00 00  t...............
0012fa20  01 00 00 00 00 00 00 00 - 04 ff 12 00 fa b7 78 00  ..............x.
0012fa30  58 10 70 01 fc 26 40 00 - 48 ec 55 01 00 00 00 00  X.p..&@.H.U.....
0012fa40  08 07 04 78 00 00 00 00 - 32 30 30 34 31 31 30 37  ...x....20041107
0012fa50  31 31 00 00 20 be d9 77 - 00 be d9 77 c1 89 d4 77  11.. ..w...w...w
0012fa60  01 00 00 00 00 be d9 77 - a8 fc 12 00 00 00 00 00  .......w........
0012fa70  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
0012fa80  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
0012fa90  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
0012faa0  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
0012fab0  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
0012fac0  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
0012fad0  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
0012fae0  00 00 00 00 a5 03 a2 a5 - 2f b4 89 5b 17 23 7f 24  ......../..[.#.$
0012faf0  49 80 7a ea 00 0a 00 00 - 00 00 00 00 80 00 00 00  I.z.............
0012fb00  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
0012fb10  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................

State Dump for Thread Id 0x3f0

eax=00000000 ebx=80020000 ecx=00000000 edx=00000000 esi=00145200 edi=00000100
eip=77f83310 esp=0132fe28 ebp=0132ff74 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000206


function: ZwReplyWaitReceivePortEx
        77f83305 b8ac000000       mov     eax,0xac
        77f8330a 8d542404         lea     edx,[esp+0x4]          ss:01da9d0f=d9819800
        77f8330e cd2e             int     2e
        77f83310 c21400           ret     0x14

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
0132FF74 77D37B4C 77D35924 00145200 77D33E01 00130000 ntdll!ZwReplyWaitReceivePortEx
0132FFA8 77D358D6 00144988 0132FFEC 7C57B388 00145360 rpcrt4!NdrCorrelationInitialize
0132FFB4 7C57B388 00145360 77D33E01 00130000 00145360 rpcrt4!RpcBindingFree
0132FFEC 00000000 00000000 00000000 00000000 00000000 kernel32!lstrcmpiW

State Dump for Thread Id 0x130

eax=9cd80000 ebx=0152febc ecx=0152ffa4 edx=00000000 esi=77f82865 edi=000001ac
eip=77f82870 esp=0152fea0 ebp=0152fec4 iopl=0         nv up ei ng nz ac po cy
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000297


function: NtWaitForSingleObject
        77f82865 b8ea000000       mov     eax,0xea
        77f8286a 8d542404         lea     edx,[esp+0x4]          ss:01fa9d87=00000000
        77f8286e cd2e             int     2e
        77f82870 c20c00           ret     0xc

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
0152FEC4 7C57B3DB 000001AC 0000EA60 00000000 60147E6C ntdll!NtWaitForSingleObject
0000EA60 00000000 00000000 00000000 00000000 00000000 kernel32!WaitForSingleObject

*----> Raw Stack Dump <----*
0152fea0  e4 9f 59 7c ac 01 00 00 - 00 00 00 00 bc fe 52 01  ..Y|..........R.
0152feb0  a4 9d 23 00 88 9e 23 00 - b4 9c 23 00 00 ba 3c dc  ..#...#...#...<.
0152fec0  ff ff ff ff 60 ea 00 00 - db b3 57 7c ac 01 00 00  ....`.....W|....
0152fed0  60 ea 00 00 00 00 00 00 - 6c 7e 14 60 ac 01 00 00  `.......l~.`....
0152fee0  60 ea 00 00 98 9c 23 00 - 88 9e 23 00 50 ff 52 01  `.....#...#.P.R.
0152fef0  98 9c 23 00 0c 42 14 60 - a4 9d 23 00 b4 9c 23 00  ..#..B.`..#...#.
0152ff00  98 34 33 00 c0 45 14 60 - 98 34 33 00 53 43 14 60  .43..E.`.43.SC.`
0152ff10  88 9e 23 00 30 9d 23 00 - 98 9c 23 00 98 34 33 00  ..#.0.#...#..43.
0152ff20  70 9c 23 00 30 d0 2f 60 - 30 9d 23 00 98 34 33 00  p.#.0./`0.#..43.
0152ff30  34 9f 23 00 d4 9d 23 00 - 68 a0 23 00 a8 35 31 60  4.#...#.h.#..51`
0152ff40  b0 98 32 60 0a 00 00 00 - 01 00 00 00 01 00 00 00  ..2`............
0152ff50  b4 ff 52 01 5c 75 2f 60 - 00 00 00 00 88 9e 23 00  ..R.\u/`......#.
0152ff60  21 4c 14 60 c8 9d 23 00 - 60 44 23 00 60 44 23 00  !L.`..#.`D#.`D#.
0152ff70  28 25 f8 77 68 a0 23 00 - 4b 6d 14 60 88 9e 23 00  (%.wh.#.Km.`..#.
0152ff80  bc 85 00 78 88 9e 23 00 - 28 25 f8 77 ff ff ff ff  ...x..#.(%.w....
0152ff90  68 a0 23 00 be e7 42 80 - 20 d0 cc f7 88 ff 52 01  h.#...B. .....R.
0152ffa0  ff ff ff ff dc ff 52 01 - 6a bd 00 78 20 2f 03 78  ......R.j..x /.x
0152ffb0  00 00 00 00 ec ff 52 01 - 88 b3 57 7c 68 a0 23 00  ......R...W|h.#.
0152ffc0  28 25 f8 77 ff ff ff ff - 68 a0 23 00 00 b0 fd 7f  (%.w....h.#.....
0152ffd0  00 00 00 00 c0 ff 52 01 - 00 00 00 00 ff ff ff ff  ......R.........

State Dump for Thread Id 0x2e8

eax=015986a8 ebx=ffffffff ecx=01598108 edx=00000000 esi=7fffffff edi=00000102
eip=77f82870 esp=01a2cd38 ebp=01a2cd70 iopl=0         nv up ei ng nz ac po cy
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000297


function: NtWaitForSingleObject
        77f82865 b8ea000000       mov     eax,0xea
        77f8286a 8d542404         lea     edx,[esp+0x4]          ss:024a6c1f=????????
        77f8286e cd2e             int     2e
        77f82870 c20c00           ret     0xc

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
01A2CD70 74FD3C59 00000204 000001B8 00000000 00000004 ntdll!NtWaitForSingleObject
01A2CE5C 750312F5 00000000 01A2DF1C 00000000 00000000 msafd!WSPSetSockOpt
01A2CEC0 60149979 00000000 01A2DF1C 00000000 00000000 ws2_32!select
00000000 00000000 00000000
Title: New Motherboard/Crash and burn in AH
Post by: Roscoroo on December 16, 2004, 03:44:58 AM
set the agp at 64mb apeture (in the bios)

check asus for updated mainboard drivers



(" Driver Version: 6.14.0010.5216 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 10/6/2003 ")

Im not shure but this video driver may be conflicting also .  (wasnt it the 52.xx series nvidia's that had alot of problems ??)

thats the 3 things i see that could be the problem .
Title: New Motherboard/Crash and burn in AH
Post by: Schutt on December 16, 2004, 04:02:52 AM
Notch sound accel back to 3/4 instead of full.

Run prime95 to check if you have memory issues, but i doubt it

Check if your graphic card / cpu gets to hot... open case and blow in with an external fan onto gk and cpu.

See if the cpu fan runs and is more or less dustfree.

Be carefull when you open the case... discharge yourself, dont leave screws and tools inside usw.
Title: New Motherboard/Crash and burn in AH
Post by: Chitownflyer on December 16, 2004, 04:15:38 AM
well, the chips are warm, not hot to touch est... 85deg f

I will set apg to 64 and will run prime95 to see if it's memory issue...

I have a feeling that the program is leaking memery becuase i can run and it runs good for about 2 to 5 min but will crash to desktop...

I'm not a programer but I do have expreiance as a A+ tech...

I will check nvida for drivers to see if there are certified as well as the latest non-certified drivers...

I wonder if lot of others are having problems too??

Mark
Title: New Motherboard/Crash and burn in AH
Post by: TheDudeDVant on December 16, 2004, 10:38:07 AM
Quote
I have the APG aperture size set for 128 on mboard. and this is set for 1800hz clock. speed


I dont understand this.. Do you have your Vid card clocked?
Title: New Motherboard/Crash and burn in AH
Post by: Chitownflyer on December 16, 2004, 11:46:40 AM
I video card is not overclocked ... but at this time I think that the video card, which is a genaric gforce mx440 apg 4x is not very happy in a A7V8X-X Asus mother board.

Now, I have long experiance with Asus, I have owned and installed, for others, hundreds of asus boards, so the board is of a good quality.  I have done a memory burn in test last night and the memory passed with out one fault.
the installation of W2000 pro is flawless and working fast and with out fault , the only thing wrong is the AH is crashing to desktop after a few minutes of play... I personally think AH has a memory leak with the Gforce/Auss card combnation.  So,
I am going to try replacing the Video card with  The following....

Asus Radeon 9250 Vdieo Card
Powered by ATI®’s Radeon™ 9250 Visual Processing Unit(VPU), the only graphics processor supporting DirectX 8.1 programmable shaders in its class...

I would assume that the mother board and card would be compatable.  Now..if AH doesn't work with this combo, then MAYBE AH IS not capable running on whole classes of common hardware out there such as  AMDxp Thunderbred/asus/RADEON ATI... if thats really the case, then I  would be very disapointed...

Chitown flyer aka Mark K

(A+ N+ MCP, MCSE) tech with 15 years experiance with WINTEL hardware software as well as a SELS pilot.
Title: New Motherboard/Crash and burn in AH
Post by: Roscoroo on December 16, 2004, 12:43:11 PM
the slowest pc i had ah2 running on was a 800 mhz tbird with a generic gf2 -mx400 64mb ... it was ok for offline and h2h but in the ma the fps was in the gutter .

my old gamer 1.3ghz morgan (with 256 L-2 cache ) and the siluro gf 2 mx 400 64mb (a tweeked card) ran 15-50 fps but took a single digit dive in the heavy traffic area's .  I added a powercolour ati 9550 256 mb card to this machine and it now runs at 30-80 fps and is very playable .

now isnt the 9250 an 64mb dx8 card ???
Is this card really much improvement over a gf4 64mb card ??


 
And yes ah2 is picky on soft/hardware enviroments ... some machines take right to it.. and others take tons of different drivers ect ...http://forums.overclockers.co.uk/showthread.php?threadid=17333848 (http://forums.overclockers.co.uk/showthread.php?threadid=17333848)
Title: New Motherboard/Crash and burn in AH
Post by: Chitownflyer on December 16, 2004, 12:53:59 PM
Its a 128 MB card... I figure I should see some impovement...
Title: New Motherboard/Crash and burn in AH
Post by: Skuzzy on December 16, 2004, 12:55:25 PM
Chitown, a memory leak is not the issue.  

What is the CPU temperature at crash time?  How much power supply do you have?

When you run Aces High, you can be pretty well sure the temperatures of the CPU are going to go up by about 20F.  Power consumption is much higher as well.

I see you have a VIA based motherboard.  You are aware the SB Cards usually have issues with VIA chipset motherboards?

As a general comment.  Aces High can be very strenous on hardware.  Flight simulators, in general, are going to push hardware more than other types of games due to the enormous amount of floating point math involved with flight modeling.
Title: New Motherboard/Crash and burn in AH
Post by: Estes on December 16, 2004, 01:02:15 PM
I have the same motherboard with a Radeon 9800 Pro, 1 gig of ram. Athlon XP 2700 480 watt PS and SB Audigy 2 ZS Platinum.

I don't have any of those problems. So, could be heat. Bad vid card, or possibly driver issue.
Title: New Motherboard/Crash and burn in AH
Post by: Chitownflyer on December 16, 2004, 01:41:13 PM
Thanks for reply....

AS far as the CPU is conserned, the Temp is running about 95 to 100 deg when
the game is running.  I have a very large copper based heat sink with compond between the the sink and the chip face.

The power suppy is a 450 watt  unit.

Now, SB card may be faulting so I will remove it and use the onboard motherboard sound output.

I will try that.. see if that works..


Mark
Title: New Motherboard/Crash and burn in AH
Post by: Chitownflyer on December 17, 2004, 09:50:23 AM
I removed the SB and enabled the mother board based sound as it was suggested.

I concure with the incompatablity of the VIA KT400 chip set to SB card.

Now with that, I tried AH again and it failed with in 5 min's of running.

Again, I have Auss temp probe running and it's showing the CPU chip to be 90deg F at the time of crashing to the desktop.

My next action will be to purchase of one Asus Radeon 9250 Vdieo Card.  This card should be compatable with the Asus mother board and the VIA KT400 Chip set.

I would assume that this will clear the problem...

Any rate, I wonder why AH is so fussy.

Mark Kmiecik
Title: New Motherboard/Crash and burn in AH
Post by: Chitownflyer on December 17, 2004, 04:40:50 PM
it appears the purchase of the
asus ATI 9250 vid card corrected the
problem..