Yes an error panel, I had to use Task Manager to gain access to my desktop.
Pretty normal faulting info for Aces High. No WATCHDOG mini dump to debug on my end. And then only in the past with NVIDIA cards and their drivers. 0xc0000005 could be video, RAM, sound, USB controllers even my CPU getting old. I have a 750W PS and excellent cooling. The PC passes health checks other wise. Or resource exaustion related to a peice of hardware.
Pretty normal situation. A very loud high population area, then the CTD after moving away. From what I can determin by talking to my squad this is an expected occurence with all of them from time to time. Some worse than others for number of times in a month or even in a session. This dosen't happen as much since I moved to an ATI card. Once or twice a month opposed to 3 times a week with NVIDIA. But, this has been an expected occurence on every PC and 2 OS that I've played this game with since 2002. Frankly my current PC with Win7 and an ATI 6770 has CTD the least of all of my PC running Aces High since 2002.
I'm not sure what good it would do to setup a video memory logger for my game sessions to see if there is any kind of pattern in this. With the Miles sound and Win7 should we be setting our source to Windows (Primary Sound Driver) and (Microsoft Sound Mapper) rather than the specific hardware function? Are there any simple sound resource loggers out there? I could run sound and video memory loggin each session for awhile to see what it looks like when I CTD like this. I've got the HD space for the logs. Catch-22 though with the added background activity.....
Hitech ever consider sending out an executable that will trigger a full memory dump off a CTD? I'll volunteer to run it as a guinie pig. Not sure you want to look through a 4-8G debug file, though you can search on known tags, or Hitech could create debug symbols for the game unless they are already there. Can't be as bad as crashing an 8-way SQL server on a tagged event line for a full memory dump to catch a DB2 gateway driver causing processor (7) to peg at 100 performing Gbyte file transfers during live business production. Seems the DB2 gateway driver hadn't been updated in in the last year by the Sr. DB Engineer. You might say that was some mondo resource exaustion when it hung the file transfer needing a reboot a couple of times a week. MS pointed fingers at IBM and vice versa while HP pointed fingers at both of them after testing the hardware.
Techs ultimatly get all the fingers pointed at them and very littel thanks.
Thank you Skuzzy.......
-----------------------------------------------------------------
Faulting application name: aceshigh.exe, version: 0.0.0.0, time stamp: 0x4f5f6c43
Faulting module name: aceshigh.exe, version: 0.0.0.0, time stamp: 0x4f5f6c43
Exception code: 0xc0000005
Fault offset: 0x000112b8
Faulting process id: 0x670
Faulting application start time: 0x01cd0d49f0872e5e
Faulting application path: C:\Hitech Creations\Aces High\aceshigh.exe
Faulting module path: C:\Hitech Creations\Aces High\aceshigh.exe
Report Id: ef54232f-7943-11e1-893c-002215f3e00f