Author Topic: AH Shuts down my computer?!?!? (Read 437 times)

atlau · « **on:** April 02, 2006, 02:36:28 PM »

With the new 2.07 Patch II, AH2 will run a few minutes but will then cause my laptop to shutdown. This occasionally happened before, but now it occurs every time I run the game. I noticed my fan or harddrive makes a lot of noise prior so I wonder if its causing it to overheat? Ever seen this before?

Thanks
Anthony

Schatzi · « **Reply #1 on:** April 02, 2006, 06:28:17 PM »

Yes, sounds like an overheating problem to me. Maybe try and get some temp checking software? (Im a PC dolt myself, but i know such things exist....

)

Murdr · « **Reply #2 on:** April 02, 2006, 07:08:32 PM »

Same here. Since installing the new patch today, Ive had 3 spawntainous resets, 1 CTD, and 1 lockup. I had absolutely none of those three problems in recent memory before today.

atlau · « **Reply #3 on:** April 02, 2006, 09:52:09 PM »

Schatzi
So if it were overheating, is there anything one could to prevent this? I'm running a laptop so replacing the fan is probably not an option. And why would this only occur w/ AH running? Does this version need that much more power?
Thanks
Anthony

Clifra Jones · « **Reply #4 on:** April 03, 2006, 02:27:45 PM »

Well, if you fan isn't running you can check this fairly easily, no noise from the laptop and no air movement. If this is the case you have more problems that AH2.

Most likely it is a driver issue. AH2 tends to reveal driver issue better than most other software. Post your video and audio hardware and driver versions here or a dxDIag report.

Also, a lot of laptops borrow memory from the main system ram for video ram. Make sure you have enough RA< to run the game after your vid-card steals ram away.

Skuzzy · « **Reply #5 on:** April 03, 2006, 03:45:06 PM »

Yes, your computer will run hotter when playing nay high fidelity flight simulation. The enormous amount of floating point math tend to cause the CPU to run much hotter than other applications/games will.

x0847Marine · « **Reply #6 on:** April 03, 2006, 06:24:17 PM »

Quote

Originally posted by Clifra Jones
Well, if you fan isn't running you can check this fairly easily, no noise from the laptop and no air movement. If this is the case you have more problems that AH2.

Most likely it is a driver issue. AH2 tends to reveal driver issue better than most other software. Post your video and audio hardware and driver versions here or a dxDIag report.

Also, a lot of laptops borrow memory from the main system ram for video ram. Make sure you have enough RA< to run the game after your vid-card steals ram away.

Also witn some notebooks, widescreen is, uh, supported if you jump through hoops, edit something go through a few crashes and figure it out on your own.

My desktop is set to 1280x800, a typical WXGA 16:10... 128m 6600go / i915 chipset, 1024 RAM

After editing some text file to 1280x800, I start AH to check and it says im running at "640x480".. then starts the game at 1280x1024

1 out of 5 tries AH just crashes, or starts erasing the video8 file.

A quick review:
voodoo8 file set to 1280x800
AH tells me its going to start at 640x480
AH runs at 1280x1024.

If I edit the voodoo file to the resoultion is actually runs at, 1280x1024, it crashes and eats the video setting file.

Go figure that other games just figure it out... I wouldnt be so fast to blame hardware or drivers when the code / UI acts like this... Im not a programmer but would it be so hard to have the games UI tell me the truth and offer me options my hardware is made for? editing text files?, welcome to a few years ago.

Skuzzy · « **Reply #7 on:** April 03, 2006, 08:23:06 PM »

Just an addendum. There is nothing to jump through to support 16:9 aspect ratio screens. A simple edit of vide8.cfg is all that the game needs.

Any other issues are aside from that edit and have nothing to do with Aces High II. Plenty of people use 16:9 aspect ratios without any problems.

16:9 aspect computer screens are still a niche product, so there is no real reason to jump through hoops and code it at the moment as a method exists which allows the user to configure any custom resolution they like. As long as the hardware/drivers support the resolution, the game could care less.

I have no doubt you had problems, but I can say for certainty, Aces High II was not the issue. DirectX and/or video card drivers could be suspect, but all the game does is what it is told. It is up to the rest of the hardware and drivers to do the rest.
If the game was really the issue, then everyone who is running 16:9 (you keep saying 16:10, but 16:9 is the normal wide aspect ratio of HD monitors), would have similar problems. No one, to date, has had any issues with it, except you.

The video8.cfg file being removed is normal. It is what the game is designed to do when the hardware reports a failure to initialize the video display. This act allows the game to restart back at the video settings so the user can fix the problem.

I am only responding to this as you seem to want to propagate this information, and I want everyone to know it is not accurate in the manner you are expressing it.

And no one needs to figure out anything about this game on thier own. I answer emails and phone calls about it all day long. And many in the community are very knowledgable about is as well.

atlau · « **Reply #8 on:** April 03, 2006, 08:44:04 PM »

Thank you for the answers. The fan is definately running to its max when the game is playing... I can hear the difference. So is the new patch that much more demanding than the previous version that it would make the difference to my CPU, since this didnt really happen before. Would reducing the graphics help reduce the load on the CPU?

I attached part of the DXDIAG report. Not sure what it all means. I'm running a 3.0 Ghz P4 w/ 512 MB RAM and a 64MB ATI MOBILITY RADEON 9700. Oh yeah, and I attached a monitor to it, so the 16:9 shouldnt be an issue right?

Thank you
Anthony

------------------
System Information
------------------
Time of this report: 4/3/2006, 21:45:07
Machine name: LAPTOP
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Language: English (Regional Setting: English)
System Manufacturer: Acer
System Model: Aspire 1660
BIOS: PhoenixBIOS 4.0 Release 6.0
Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz (2 CPUs)
Memory: 510MB RAM
Page File: 286MB used, 963MB 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.
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: ATI MOBILITY RADEON 9700 Series
Manufacturer: ATI Technologies Inc.
Chip type: ATI MOBILITY RADEON 9700 AGP (0x4E50)
DAC type: Internal DAC(350MHz)
Device Key: Enum\PCI\VEN_1002&DEV_4E50&SUBSYS_00531025&REV_00
Display Memory: 64.0 MB
Current Mode: 1024 x 768 (32 bit) (60Hz)
Monitor: Default Monitor
Monitor Max Res:
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6422 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 2/10/2004 09:42:40, 388096 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: ati2mtag.sys
Mini VDD Date: 2/10/2004 09:42:18, 672256 bytes
Device Identifier: {D7B71EE2-0D10-11CF-836A-5920A1C2CB35}
Vendor ID: 0x1002
Device ID: 0x4E50
SubSys ID: 0x00531025
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_C ModeMPEG2_D

------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 21.4 GB
Total Space: 27.6 GB
File System: NTFS
Model: IC25N060ATMR04-0

Drive: D:
Free Space: 16.6 GB
Total Space: 27.7 GB
File System: NTFS
Model: IC25N060ATMR04-0

Drive: F:
Model: PIONEER DVD-RW DVR-K13RA
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (English), 8/4/2004 01:59:52, 49536 bytes

--------------
System Devices
--------------
Name: WLAN 802.11g mini-PCI Module
Device ID: PCI\VEN_14E4&DEV_4320&SUBSYS_1220185F&REV_03\4&356489C6&0&28A4
Driver: C:\WINDOWS\system32\DRIVERS\BCMWL5.SYS, 3.30.0015.0000 (English), 7/17/2003 16:40:06, 265728 bytes

Name: Realtek RTL8139/810x Family Fast Ethernet NIC
Device ID: PCI\VEN_10EC&DEV_8139&SUBSYS_00521025&REV_10\4&356489C6&0&50A4
Driver: n/a

Name: Texas Instruments PCI-1520 CardBus Controller
Device ID: PCI\VEN_104C&DEV_AC55&SUBSYS_00521025&REV_01\4&356489C6&0&21A4
Driver: C:\WINDOWS\system32\DRIVERS\pcmcia.sys, 5.01.2600.2180 (English), 8/4/2004 02:07:46, 119936 bytes

Name: Texas Instruments PCI-1520 CardBus Controller
Device ID: PCI\VEN_104C&DEV_AC55&SUBSYS_00521025&REV_01\4&356489C6&0&20A4
Driver: C:\WINDOWS\system32\DRIVERS\pcmcia.sys, 5.01.2600.2180 (English), 8/4/2004 02:07:46, 119936 bytes

Name: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
Device ID: PCI\VEN_104C&DEV_8023&SUBSYS_00521025&REV_00\4&356489C6&0&18A4
Driver: C:\WINDOWS\system32\DRIVERS\ohci1394.sys, 5.01.2600.2180 (English), 8/4/2004 02:10:08, 61056 bytes
Driver: C:\WINDOWS\system32\DRIVERS\1394bus.sys, 5.01.2600.2180 (English), 8/4/2004 02:10:06, 53248 bytes
Driver: C:\WINDOWS\system32\DRIVERS\nic1394.sys, 5.01.2600.2180 (English), 8/4/2004 01:58:29, 61824 bytes
Driver: C:\WINDOWS\system32\DRIVERS\arp1394.sys, 5.01.2600.2180 (English), 8/4/2004 01:58:29, 60800 bytes
Driver: C:\WINDOWS\system32\DRIVERS\enum1394.sys, 5.01.2600.0000 (English), 8/17/2001 09:46:40, 6400 bytes

Name: ATI RS300/RS300M Accelerated Graphics Port
Device ID: PCI\VEN_1002&DEV_5838&SUBSYS_00000000&REV_00\3&13C0B0C5&0&08
Driver: C:\WINDOWS\system32\DRIVERS\atisgkaf.SYS, 5.00.2195.1009 (English), 10/27/2003 03:59:00, 13842 bytes

Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1002&DEV_5833&SUBSYS_00000000&REV_02\3&13C0B0C5&0&00
Driver: n/a

Name: ATI MOBILITY RADEON 9700 Series
Device ID: PCI\VEN_1002&DEV_4E50&SUBSYS_00531025&REV_00\4&2686AC80&0&2808
Driver: C:\WINDOWS\system32\DRIVERS\ati2mtag.sys, 6.14.0010.6422 (English), 2/10/2004 09:42:18, 672256 bytes
Driver: C:\WINDOWS\system32\ati2dvag.dll, 6.14.0010.6422 (English), 2/10/2004 09:42:40, 388096 bytes
Driver: C:\WINDOWS\system32\Ati2mdxx.exe, 4.13.0001.0003 (English), 9/4/2001 04:24:26, 28672 bytes
Driver: C:\WINDOWS\system32\ati3d1ag.dll, 6.14.0010.4056 (English), 2/10/2004 09:34:14, 869376 bytes
Driver: C:\WINDOWS\system32\ati3d2ag.dll, 6.14.0010.4056 (English), 2/10/2004 09:36:50, 1056256 bytes
Driver: C:\WINDOWS\system32\ati3duag.dll, 6.14.0010.0220 (English), 2/10/2004 09:40:00, 1179808 bytes
Driver: C:\WINDOWS\system32\ativvaxx.dll, 6.14.0001.0004 (English), 2/10/2004 09:31:28, 592384 bytes
Driver: C:\WINDOWS\system32\ATIDDC.DLL, 6.14.0010.0005 (English), 2/10/2004 09:40:26, 81920 bytes
Driver: C:\WINDOWS\system32\atitvo32.dll, 6.14.0010.4100 (English), 2/10/2004 09:28:48, 17408 bytes
Driver: C:\WINDOWS\system32\ativcoxx.dll, 6.13.0010.0005 (English), 11/8/2001 23:01:04, 24064 bytes
Driver: C:\WINDOWS\system32\ati2evxx.exe, 6.14.0010.4096 (English), 2/10/2004 09:40:48, 397312 bytes
Driver: C:\WINDOWS\system32\ati2evxx.dll, 6.14.0010.4096 (English), 2/10/2004 09:40:52, 86016 bytes
Driver: C:\WINDOWS\system32\atipdlxx.dll, 6.14.0010.2487 (English), 2/10/2004 09:41:04, 114688 bytes
Driver: C:\WINDOWS\system32\Oemdspif.dll, 6.14.0001.0010 (English), 2/10/2004 09:41:00, 102400 bytes
Driver: C:\WINDOWS\system32\ati2edxx.dll, 6.14.0010.2493 (English), 2/10/2004 09:40:56, 30720 bytes
Driver: C:\WINDOWS\system32\atioglxx.dll, 6.14.0010.4145 (English), 2/10/2004 09:59:20, 6070272 bytes
Driver: C:\WINDOWS\system32\atiiiexx.dll, 6.14.0010.4000 (English), 2/10/2004 10:22:48, 290816 bytes

Skuzzy · « **Reply #9 on:** April 03, 2006, 08:59:49 PM »

Odd, no sound card listed in the DXDIAG output. I assume you edited it out of the file.

Here is the video settings you should be using with that system:

Maximum Texture size: 512 or 256, no higher
Preload textures to system RAM can be checked
DO NOT check preload into video RAM.
DO NOT check preload skins, unless you set the maximum texture size to 256 or less.

The two optimize options and hardware vertex processing should all be checked.

Now, does the laptop actually shutdown? Or is the game just dumping to the desktop? We really have no method to shutdown a computer. Have you tried looking into your power savings settings and disabling them?

Schatzi · « **Reply #10 on:** April 04, 2006, 04:03:53 AM »

Looks like you are in much better hands then mine now

.

Good luck.

Max · « **Reply #11 on:** April 04, 2006, 12:21:23 PM »

Skuzzy/Schatzi -

What is this CPU heat monitoring software you speak of? My e-machine laptop seemed to develop a hibernate-shutdown problem a few months ago. From what I gather it sounds like I may have a heatsink or fan problem. How can I check my cpu for overheating?

Thanks,
max

x0847Marine · « **Reply #12 on:** April 04, 2006, 01:58:39 PM »

Odd that Americas Army / HL are coded for us 'niche' buyers.

Its really not too much to ask that the UI offers me choices rather than having to research, edit and go through frustrating crashes.