Author Topic: Beta 19 CTDs after about 1 minute. (Read 864 times)

Karnak · « **on:** March 29, 2004, 07:51:15 PM »

I am getting a CTD after about 1 minute in Beta 19. I only tested two aircraft, P-51D and Mosquito, but it behaved identically. This always occurs.

DXdiag data:

Machine name: KARNAK
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 1 (2600.xpsp2.030422-1633)
Language: English (Regional Setting: English)
System Manufacturer: NVIDIA Corporation.
System Model: nFORCE-MCP
BIOS: Award Modular BIOS v6.00PG
Processor: AMD Athlon(tm) XP 1800+, MMX, 3DNow, ~1.5GHz
Memory: 512MB RAM
Page File: 149MB used, 1100MB 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

Card name: NVIDIA GeForce4 Ti 4600
Manufacturer: NVIDIA
Chip type: GeForce4 Ti 4600
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0250&SUBSYS_2890107D&REV_A3
Display Memory: 128.0 MB
Current Mode: 1280 x 1024 (32 bit) (85Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0010.5664 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 3/3/2004 10:29:00, 4256896 bytes

Description: SB Live! Audio [C000]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0002&SUBSYS_80611102&REV_07
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.0252 (English)
Driver Attributes: Final Retail

Karnak · « **Reply #1 on:** March 29, 2004, 08:05:12 PM »

This did not occur while using the Spitfire Mk XIV.

EDIT:
Happened with the Spitfire Mk XIV. The first time I tested the Mk XIV it didn't happen.

JB73 · « **Reply #2 on:** March 29, 2004, 10:43:10 PM »

mine did first launch of AHII also. restarted the game (without restarting the PC and ran game for over an hour doing all sorts of odd stuff. not a problem after that.

i was in a 190D for the first flight using the "black" skin i DL'd from the skin site for that first sortie (thats the last sortie i did in AH beta 18). i switched it to the default skin on restart. dont know if that had an impact.

Karnak · « **Reply #3 on:** March 29, 2004, 10:52:44 PM »

I deleted my settings folder and this no longer occurs.

Hyrax81st · « **Reply #4 on:** March 30, 2004, 01:40:40 AM »

Karnak,

I attempted your fix and it worked for me too. I renamed settings folder to "saved".

Got back into AH2, re-selected video, etc... got up and no more CTD's...

Pei · « **Reply #5 on:** March 30, 2004, 02:47:29 AM »

I get this problem but deleting the settings folder doesn't fix it for me (tried it twice now):

AMD Xp2100, 1 Gig RAM
Win2K Sp2, GeF4 Ti4600 using 56.56 drivers
Dx9.0b

LJK_KämpferAs · « **Reply #6 on:** March 30, 2004, 03:59:50 AM »

worked for me

Pei · « **Reply #7 on:** March 30, 2004, 04:04:48 AM »

Quote

Originally posted by Pei
I get this problem but deleting the settings folder doesn't fix it for me (tried it twice now):

AMD Xp2100, 1 Gig RAM
Win2K Sp2, GeF4 Ti4600 using 56.56 drivers
Dx9.0b

I managed to fix the problem by returning to default settings for the graphics sliders.

If I then set the visible range to high (over ~2.75) the problem still sometimes occurs.

[EDIT - addition]

I can set the the other two sliders back to thier original positions (i.e my choices). It's only the bottom slider (range) that I have to drop back.

Zanth · « **Reply #8 on:** March 30, 2004, 10:28:37 AM »

I ran into this problem in AH1 once, and it was RAM that was causing me trouble -(and oddly was only showing up in AH). In the end a slight adjustment upwards of my RAM voltage squared me away and I never CTD'd again (except for that bug when you change arenas).

If you have tried everything else, here are a few ideas (be extreme careful handling RAM chips they are very sensitive to static electricity):

(1) check the specs for your RAM and see what they recommend (should be a range) and compare that to what you are running and adjusting voltage upward staying in that range.

(2) If you have multiple sticks of RAM, try removing all but one and see if you can recreate the trouble with each stick.

AKIron · « **Reply #9 on:** March 30, 2004, 12:42:06 PM »

Deleting the settings folder solved the ctd for me, thx for the tip.

Karnak · « **Reply #10 on:** March 30, 2004, 09:56:54 PM »

I think it is the range slider. If I set it higher than 2.75 miles or so I get the CTD after about a minute. With the range slider lower than that I do not get the CTDs.

Pei · « **Reply #11 on:** March 31, 2004, 06:44:21 PM »

Quote

Originally posted by Karnak
I think it is the range slider. If I set it higher than 2.75 miles or so I get the CTD after about a minute. With the range slider lower than that I do not get the CTDs.

Exactly what I was seeing.