Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: Jasta on August 15, 2004, 02:44:24 PM

Title: CTDs return
Post by: Jasta on August 15, 2004, 02:44:24 PM
As soon as I DLed patch 8, I noticed the return of CTDs...

I had flown a full frame of BoB during patch 7 with no problems, and all month in the MA no problem.

Patch 8 and IM CTD all the time, and I had to drop out of Frame 3 of BoB because of a CTD. I do notice it usually happens around areas with alot of action.. But sometimes it happens in a deserted tower.

System Information
------------------
Time of this report: 8/15/2004, 14:41:13
       Machine name: NINJA-MACHINE
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 1 (2600.xpsp2.030422-1633)
           Language: English (Regional Setting: English)
System Manufacturer: VIA Technologies, Inc.
       System Model: VT8366-8233
               BIOS: Award Modular BIOS v6.00PG
          Processor: AMD Athlon(tm) XP 2000+,  MMX,  3DNow, ~1.7GHz
             Memory: 512MB RAM
          Page File: 118MB used, 1132MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0b (4.09.0000.0902)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.0001.0902 32bit Unicode


IRQ Conflicts: Video Card, Audio Card, USB Hub sharing same IRQ...


I garuntee nothing has changed since patch 7.
Patch 8 DEFINATELY has something to do with it.
Title: CTDs return
Post by: Blooz on August 15, 2004, 06:39:40 PM
Delete the contents of the cache folder in AH2 directory.

It's kind of a pain because you'll get the long pre load bar as it replaces all the graphics but it might help you out.

I had to do this right after the patch to get things running right.

Hope it works for you too.
Title: CTDs return
Post by: Jasta on August 16, 2004, 06:57:44 PM
bump...
suggestion didnt work.
Title: CTDs return
Post by: Skuzzy on August 16, 2004, 08:56:20 PM
Your video card and audio card are sharing the same IRQ.  That is going to cause instability.

Beyond that, email me a copy of the DXDIAG output and be sure to run the Display and Sound diagnostics before dumping the DXDAIG data to a file.
Title: CTDs return
Post by: Jasta on August 16, 2004, 10:19:42 PM
Skuzzy, I have done that before... But the only thing I need to know is how to change my IRQs for these cards!

Ive messed around with slot settings, but if these three devices are all on IRQ 11 (Audio, Video, USB), and all three cant be moved, what am I supposed to do?

My audio is Onboard, Video is AGP, and USB is onboard of course.
I messed with my NIC, but in some situations, the NIC just conflicts with something else. I need help with how to change this.

DXDIAG sent...
Title: CTDs return
Post by: spiffykraits on August 17, 2004, 04:32:48 AM
Quote
Originally posted by Jasta
Skuzzy, I have done that before... But the only thing I need to know is how to change my IRQs for these cards!

Ive messed around with slot settings, but if these three devices are all on IRQ 11 (Audio, Video, USB), and all three cant be moved, what am I supposed to do?

My audio is Onboard, Video is AGP, and USB is onboard of course.
I messed with my NIC, but in some situations, the NIC just conflicts with something else. I need help with how to change this.

DXDIAG sent...


I had the same problem -random CTDs. Reducing the DirextX sound aceleration helped (on-board sound chip) but still got them.
Fitted a Sound card and disabled on-board sound in BIOS, problem went away.  The new AH2 doesn't seem to like on-board sound at all, so advise geting a new sound card instead on the onboard sound chip.
Title: CTDs return
Post by: Skuzzy on August 17, 2004, 07:29:17 AM
Jasta, try this, it might work.  Typically, motherboards have the first PCI slot and the AGP bus on the same physical IRQ.

1)  Remove the video card driver.
2)  Reboot the system into the BIOS setup.  Do not let Windows boot, or start at number 1 again.
3)  Find the place in the BIOS setup to force an IRQ to be assigned to PCI slot #1.
4)  Set that IRQ to 10, which should be available.
5)  Save and reboot.
6)  Install the video drivers.

Check to see if that does the trick.

Oh, new Hyperion drivers were released yesterday.  Might want to grab them too.