Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Dawger on January 19, 2011, 09:33:50 AM
-
Aces High locks up since the last AH update and it seems the only solution is to change the OS.
Anyone got any ideas other than that?
-
Im testing it right now.
Windows 7 64 bit fresh install with just Windows updates (for Windows) and drivers for system devices loaded. No custom sound files installed at all.
Same for Windows 7 32 bit on the same system. This will take time because I plan on giving each install a week to see if any lockups happen.
-
A DXDIAG would be helpful, as there are cases where the installed sound card drivers were not native and this will cause problems.
The 64 bit version of Windows 7 still suffers from some driver related problems than do not occur in the 32 bit version.
-
One thing I noticed during the install of Windows was that the CH Control Manager program was the first to crash Windows with a BSOD during install. On both versions (32 and 64) the CHCM needed to be installed twice in order to complete properly. Prior to this I had only experienced crashes on the 64 bit system but up to this point both 32 bit and 64 bit are behaving.
-
Did you try disabling UAC, before installing it, and see if that impacted the installation?
-
That was the very first thing I did after getting Windows installed.
-
I'm running AH on Win 7 64 bit and haven't had any lock ups. I'm also using TikTok's sound pack and X52 controller and CH pedals.
If needed I could also post a DXDIAG for comparison. :salute
-
I am running windows7 ultimate 64 bit for aprox 1 year now and I haven't had any problems yet. So if you want I can post my dx when I get home.
-
Did you try disabling UAC, before installing it, and see if that impacted the installation?
Computer Neanderthal question---What is the advantage of disabling the UAC?
-
There is a lot of overhead involved with UAC. It does a lot of funky things to the data locations in the filesystem as well.
PLEASE NOTE: You only want to disable UAC after a fresh installation of Windows 7/Vista. To do so after the computer has been running for a while can cause many, many of your applications to lose thier settings and configurations and data.
It is not really lost, but misplaced,...sort of.
-
One thing I noticed during the install of Windows was that the CH Control Manager program was the first to crash Windows with a BSOD during install. On both versions (32 and 64) the CHCM needed to be installed twice in order to complete properly. Prior to this I had only experienced crashes on the 64 bit system but up to this point both 32 bit and 64 bit are behaving.
About the CH control manager...it seems it can't coexist with the saitek software that comes with the X65. Gave me huge stutters ingame. I use Win7 64bits also :airplane:
-
Over the course of the first week with W7 32bit I didnt experience a single crash of the program except when I (basically) made it crash by locking Windows (Ctrl-Alt-Del and "Lock this computer"). This is without any custom sounds or gunsights and for the most part using the system only for Aces High during that time. Instead of copying settings from my older version of AH I just went with everything new or default. I am also using the high res texture pack and I have downloaded all skins. Starting Monday I will do the same with W7 64 bit.
-
First flight on W7 64 bit resulted in the program crashing. Hows that for a revealing test? :rolleyes:
-
We know there is a problem in Windows 7 64 bit, as the crashes we observe are all located in the Windows kernel. This would normally indicate some type of driver problem. It is not limited to that, but it is normally the first thing to look at.
-
In my mind the primary suspect would be Sound Blaster X-Fi but to be absolutely fair I would have to test it with several devices removed. I have an APC UPS system which I cannot bring myself to run without but I could try it without the Phonic Firefly or TrackIR and so on (and of course the Sound Blaster). Im not sure what the point would be because I am sold on using 32 bit.
-
Chalenge,
what are your reasons for running your test of Aces High on Windows 7 64 bit OS ? are you just experimenting? or did you run nto an issue with AH on windows 7 64 bit before?
Skuzzy, Sir, the win7 64 bit problem causing AH to act up that HTC has acknowledged which you reported crashes in the windows Kernel.... are these viewed as being sporadic across all the different PC platforms or is it more detailed as to certian components being used in conjunction with one another?
I have not yet ran in to any issues with my main PC system which uses Windows 7 64 bit Ult. / SB X-Fi pro series / AMD athlon II 6400+ x2 3.2ghz dualcore / 4 gigs Corsair XMS2 DDR2 / etc etc etc other components and CH's CM v4.1 ( or 4.0?? )
(edit: I have been using Win 7 64 bit Ult. since around Jan/Feb of 2009 and using AH on it without any significant issues )
NOTE: I can get access to 5 totally different systems that have Windows 7 64 bit as the operating system and could install AH on them for test purposes if it would help ( well install AH on 4 of them, mine already has AH on it )
-
Thank you for the effort you are going through. <S>
-
Using win7 64 bit here, dxdiag details below (had very few issues as yet - the odd crash once in a blue moon - heat my end, as it was in summer and a bit warm)
------------------
System Information
------------------
Time of this report: 1/24/2011, 17:28:35
Machine name: GPWNOW
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621)
Language: English (Regional Setting: English)
System Manufacturer: Si
System Model: SYX-P6T-SE
BIOS: BIOS Date: 03/08/10 11:34:30 Ver: 08.00.15
Processor: Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz (8 CPUs), ~2.8GHz
Memory: 10240MB RAM
Available OS Memory: 10232MB RAM
Page File: 2291MB used, 18168MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 64bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Display Tab 2: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Sound Tab 3: No problems found.
Sound Tab 4: No problems found.
Input Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: ATI Radeon HD 5700 Series
Manufacturer: ATI Technologies Inc.
Chip type: ATI display adapter (0x68B8)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_68B8&SUBSYS_1482174B&REV_00
Display Memory: 716 MB
Dedicated Memory: 2009 MB
Shared Memory: 2803 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: HP w2338h Wide LCD Monitor
Monitor Model: HP w2338h
Monitor Id: HWP281C
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.17.0010.1052 (English)
Driver Version: 8.791.0.0
DDI Version: 10.1
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 10/27/2010 02:54:24, 645120 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71EE2-2BF8-11CF-E770-8834BEC2C535}
Vendor ID: 0x1002
Device ID: 0x68B8
SubSys ID: 0x1482174B
Revision ID: 0x0000
Driver Strong Name: oem22.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Evergreen:8.791.0.0:pci\ven_1002&dev_68b8
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{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
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
Only thing wrong with my system is it has 12gb ram installed, but only reports 10gb - memtest's show all 12gb available tho - and cant find anything in bios to pick up the extra 2gb (no biggie)
Wurzel
-
-------------
Sound Devices
-------------
Description: Realtek HD Audio 2nd output (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_104383C0&REV_1001
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.6167 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 7/28/2010 17:26:00, 2445672 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Description: Realtek Digital Output (Realtek High Definition Audio)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_104383C0&REV_1001
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.6167 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 7/28/2010 17:26:00, 2445672 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
-
Description: Digital Output(RCA+Optical) (Realtek High Definition Audio)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_104383C0&REV_1001
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.6167 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 7/28/2010 17:26:00, 2445672 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Description: Speakers (Realtek High Definition Audio)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_104383C0&REV_1001
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.6167 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 7/28/2010 17:26:00, 2445672 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
I also use track ir, CH stick, saitek peds and throttle.
Posted for comparison purposes
Wurzel
-
Tequila the reason I am doing it is I got Windows 7 64 bit completely stable except for AH and film viewer... or so I thought. I really was considering that AH had another issue with clouds or something because of the frequency of crashes at 17.3k (four times) but then it happened from the tower one day and I decided I was going to trace it down.
I will figure out what is causing it on my system eventually but from what Skuzzy is saying it could happen to anyone.
I can force 32 bit to crash by locking Windows while playing AH but who does that? Its really the only thing I have done that will crash it. I was using Windows Live Movie Maker and building a video with AH up and did several alt-tabs and played streaming radio without an issue. Doing the same thing on 64 bit I get crashes at different times so what Skuzzy is saying makes sense.
I will continue this as I have time.
-
In my mind the primary suspect would be Sound Blaster X-Fi but to be absolutely fair I would have to test it with several devices removed. I have an APC UPS system which I cannot bring myself to run without but I could try it without the Phonic Firefly or TrackIR and so on (and of course the Sound Blaster). Im not sure what the point would be because I am sold on using 32 bit.
Are you running in "Test mode"? Every driver you use is Microsoft certified?
-
No... Yes and it doesnt seem to matter because the OS is crashing while playing AH. Now if it turns out to be a MB driver then nothing will make a difference.
-
We know there is a problem in Windows 7 64 bit, as the crashes we observe are all located in the Windows kernel. This would normally indicate some type of driver problem. It is not limited to that, but it is normally the first thing to look at.
Skuzzy would you mind elaborating on this, I mean, I have quite a large library of games on my machine, many which are more taxing on my system than aces High and those games hardly cause any stability issues with my machine, in fact I can't remember the last time I had a lock up or a crash outside of playing AH2.
I have attempted to upgrade as much as I can in terms of drivers and firmware etc, and whilst that seemed to help in reducing the problem, the game still locks up far to frequently for my liking. The end result has been that I've unsubscribed for now until a "fix" is available, installing a different operating system on my machine is not an option for me.
Many Thanks.
C
-
Aces High locks up since the last AH update and it seems the only solution is to change the OS.
I'm having the same problems... Win7 64 bit.
I thought this problem was fixed a few months ago?
-
I am running windows 7 64 bit on a cheaper laptop. Only issue I have had playing Aces High 2 is the sound.. I am always losing my sound and I have to switch from mono, to stereo, to blahbedy blah over and over. It happens like once or twice an hour. It's probably my cheap laptop and not the new windows.
:salute
-
Skuzzy would you mind elaborating on this, I mean, I have quite a large library of games on my machine, many which are more taxing on my system than aces High and those games hardly cause any stability issues with my machine...
I understand why you might think thats true but I am afraid you are mistaken. People look at the graphics of AH and the frame rates and they think well this other game I play has better this or that and the frame rates are lower so its really hitting my system hard.
Aces High is more load.
-
I understand why you might think thats true but I am afraid you are mistaken. People look at the graphics of AH and the frame rates and they think well this other game I play has better this or that and the frame rates are lower so its really hitting my system hard.
Aces High is more load.
Its not automatically more load than every game on the market. Come on man.
Anyways, I would somewhat like to install Windows 7, but the only case I can make for doing that is if I install the 64 bit version, for the 32 bit version I may as well stick to XP (which is what I've done). And if AH is likely to randomly crash with Win7-64, then I really have very little reason to install Win7-64. It would be nice to see this solved though.
-
Its not automatically more load than every game on the market. Come on man.<snip>
I cannot say, with absolute certainty, our game loads a computer more than any other game on the market, but I can say Aces High does place an equally high load on all components of a computer system.
Generally speaking, games that place a high load on a graphics card, normally cause a lighter load to be placed on other components.
-
The reason that you want to move to Windows 7 is security. No... Windows 7 is not automatically more secure than XP. As XP grows longer in the tooth and the programs that it runs are not as well maintained as the newer versions for W7 the XP environment becomes more susceptible to viruses and other targeted attacks. Thats a fact that loyalty to the OS will not overcome.
You cannot imagine how frustrating it is to try and track down this W7 64 problem.
-
You cannot imagine how frustrating it is to try and track down this W7 64 problem.
I understand, but I would never of signed up for this upcoming scenario knowing it was still around, I thought it was gone.
Nothing is worse than flying with the bombers all the way to Berlin in the scenario and have AH crash. It could literally mean a 3 hour waste of time...
-
Is AH officially supporting Win7 64bits or not?
-
Is AH officially supporting Win7 64bits or not?
good question nuke!
-
It is not up to the application to support an OS, per se. We cannot fix bugs in an OS. It is difficult, to impossible, to work around an undocumented OS bug, when you do not have access to the source code of the OS.
All we can do it program to what the operating system provides. After that, it is up to the OS/drivers to do what they are documented to do.
NOTE: OS bug could be drivers as well, which is not Microsoft's responsibility.
Why does this bug exist on the 64 bit version of Windows 7, and not the 32 bit says the problem could be in the core OS, or in a driver. The inconsistency of the problem points more to drivers, than to the core OS. That is just a logical assumption, with no real basis in fact.
-
If it helps any, I've been running AH problem free for over a year (win7 64 bit).
Then I started experiencing lock ups. Happened three times in two weeks. Nothing I could reproduce obviously, and once it happened while simply sitting in the tower. I walked away to get a beverage and came back with the "AH HAS EXPERIENCED A PROBLEM" message or whatever.
Then about a week and half ago, Windows update wanted to update my on-board sound drivers. It caught me off guard because I thought it had already just updated them and was surprised to see another update available so quickly.. then it hit me that the crashes began after updating the drivers the first time, so I went ahead and let it install the other new update.
It hasn't crashed since then. I'm not sure if it's just coincidence or whether it's going to happen still or not. I should also note that I don't even use my on-board sound with AH. Yes, the driver is enabled (I used it for my other basic windows sounds, surfing, music, etc) but I plug in my Turtle Beach USB headphones which use their own sound drivers, and I have everything set to go through that from within Aces High.
*I should note that I can set the radio up for the headphones and the sounds through the speakers and while it's kind of cool, I prefer to just run it all through the headphones.
I think maybe I'll reinstall the sound drivers from the motherboard's website and see what happens...
-
Tigger29,
is your onboard sound Realtek ?
they have came out with new driver updates pretty frequently in the last several months....... not sure why , Ihave not bothered to read up on it any..
just one website I frequent that shows a lot of PC/OS/videocard/soundcard/internet/security information which sometimes shows up 2 to 3 months earlier before I see people like Cnet or PCworld or the regular internet PC/Web News/information sites post it....
seems bout every week or 2 to 3 weeks lately their have been postings of "New REALTEK Audio Driver Update" threads posted....
might have something to do with why some people are having problems while others are not, regarding windows 7.... who knows
-
yep the exact chipset you are sporting would be useful, also if you could fetch the different driver versions you used that'd be great! My own experience with inboard sound cards is that it caused micro freezes in the game, even if I was using a different output device. I deactivated it in the BIOS and put a sound blaster 2 ZS instead and it fixed the freezes. I use Win7 64bits also.
-
Tigger29, is your onboard sound Realtek ?
Actually yes it is, however the drivers Windows was installing said "High Definition Audio Device" but there were two instances installed, and then there was a third audio device for my Turtle Beach 5.1 USB Headset, "Audio Advantage SRM Device."
In my bios, I disabled the on-board audio. Upon reboot, now I still had one instance of "High Definition Audio Device". That ended up being the HDMI audio drivers for the video card. I could have SWORE that I disabled that, but now that I think of it I think I'm thinking of when I disabled it for a squadmate's system I was building. Anyway I have that disabled in the Device Manager (I can't find any other way to disable it). I downloaded the Realtek drivers from my motherboard's website (ASRock G43Twins-FullHD) and the Audio Drivers from Turtle Beach's website. I then fully uninstalled the Turtle Beach software AND the realtek software, as well as right clicking on them from the Device Manager and "uninstalling" as well as checking the box to remove all drivers as well.
I then proceeded to install the Realtek drivers from my download, and after testing that rebooted and installed the Turtle Beach software. After another reboot I have everything back up and running, and now show the following three entries in my Device Manager:
-Audio Advantage SRM Device (This is for the Turtle Beach headphones)
-High Definition Audio Device - DISABLED (This is the HDMI audio for the video I don't use anyway)
-Realtek High Definition Audio (This is the onboard audio and set as the DEFAULT audio device in the sound properties)
I went into Aces High OFFLINE mode and played with the sound settings and got everything back to normal. I've noticed that the sound properties for AH get kind of goofy whenever a change is made. Simply selecting the proper device for the headphones and for the speakers is not enough. I've found that you have to click ACCEPT and then back out and back in to the menu and switch all four devices to "SPEAKER", click accept again and then switch them all back to "HEADSET" once again regardless to how it was set before. It's kind of like it forgets what to do with what and when you make a change (even if you are changing it BACK to where it was to begin with) then it updates and then everything is good. It's just a small bug that hopefully will get fixed eventually.
It's kind of fun to set up the sounds for the speakers and the vox for the headset, but to me that kind of defeats the purpose of having a surround sound headset... especially one that covers your ears and blocks the sound from the speakers... so I run it all through the headset.
Anyway, I'll keep you guys posted if I experience another crash. I honestly don't know for sure if this is the issue or not, but it feels good to have the actual "realtek" drivers installed now, instead of generic microsoft drivers... I just have to remember not to let it update them.
-
There are too many topics regarding the "Aceshigh stopped working.exe" in combination with W7 x64, so I picked one, and this is it ;)
Anyway, I have 2 different systems which have the same issue. They both have completely different hardware components, nvidia and ati cards, soundblaster and onboard cards, etc etc.
Since a few days I updated to Windows 7 Service Pack 1, it's just released, and I suggest to update to this SP anyway. Coming with that I noticed a patch in the 'Optional' section of Windows update. It is described in this article:
"An application that uses Direct2D or Direct3D may crash in Windows 7 or in Windows Server 2008 R2"
http://support.microsoft.com/kb/2488113
Since I'm running with that update, I had no crash so far, but I only have played for about 3 to 4 hours. So I'm not in the position to raise the flag yet, but could all of you guys suffering with this issue please check this optional update in your "Windows Update" and give it a try, so that we can have some feedback if this solves something... I'll report back when I'm able to build some more flying hours.. Thanks!
~S~
-
Does Aces High host Internet Explorer components? :huh
-
I will note that it's been almost three weeks now since I straightened out my audio drivers, and I haven't suffered one single crash.
(Of course now that I said that it will probably crash next time I log on! :lol )
I haven't made the SP1 just just yet... I'll need to update my backup image and all that before I make that leap of faith.
-
Does Aces High host Internet Explorer components? :huh
It could be that a lot is hosting these components. IE is known to be deeply integrated within the OS, so who knows...
-
Does Aces High host Internet Explorer components? :huh
No.
-
I will note that it's been almost three weeks now since I straightened out my audio drivers, and I haven't suffered one single crash.
(Of course now that I said that it will probably crash next time I log on! :lol )
I haven't made the SP1 jump just yet... I'll need to update my backup image and all that before I make that leap of faith.
:ahand HAHA it locked up once last night. Was in a panzer. Thought it was all cleared out. Stopped completely on grass about 1 mile from base. Ended flight. Got "ditched" message and BAM lockup!
That's OK though... I'll try SP1 and see what happens.
-
Get the optional ones too Tigger, hope it will help for you.. ~S~
-
Get the optional ones too Tigger, hope it will help for you.. ~S~
Yeah I just finished all the updates... I can't really tell any difference. I think I'll fly some today and see what happens.
That's kind of the problem with working from home. Some days it's just hard to get motivated! ROFL
-
For those with latest NVIDIA drivers try setting the maximum pre-rendered frames to 0. I was having one or two crashes a night plus stuttering in sound and pauses with Joystick. Now seems OK. I have win7 x 64
-
There may be no connection but...
I had been experiencing at least one crash to desktop per day, until the B29 patch. I had not had a crash to desktop until today's patch (the first one).
May not be related, but thought I would put it out there.
-
There may be no connection but...
I had been experiencing at least one crash to desktop per day, until the B29 patch. I had not had a crash to desktop until today's patch (the first one).
May not be related, but thought I would put it out there.
A bunch of windows updates came out at that same exact time too.. might be because of that.
-
After patch, I thought crash when logging was fixed. I logged out yesterday, "ah exe stopped working", video went to 1024x768 from 1680x1050.
Could not get desktop resolution to change.
In game, I got a "Disabling Advanced graphics" message. Everything moved real slow.
And I was told I was warping.
Rebooted, all normal. Weird, this has only happened in last week.
It started before update or patch.
Any thoughts? Heat?
I also noticed instead of picking up my LG monitor, it's saying "Generic PnP Monitor".
<S> Oz
-
I thought it was fixed too. Just got the crash in a 163. Only crash this month. Was chasing altobuffs over the strat and pulled the e6b up to check my fuel. The screen froze in the middle of the clipboard popping up. :bhead I think something similar happened last tour.
-
As of the more recent updates, the first time I run the game, the moment I select an arena, it crashes, after every boot. After the initial crash, it works alright though... maybe a initialization issue with a particular device?
-
As of the more recent updates, the first time I run the game, the moment I select an arena, it crashes, after every boot. After the initial crash, it works alright though... maybe a initialization issue with a particular device?
More that likely a device in an unknown state and when DirectX tries to init it, it fails, causing the game to crash. Or another piece of software is interferring with a device DirectX is trying ito init.
Run DXDIAG and check all the devices, then look for any software that might be using any of those devices.
-
After patch, I thought crash when logging was fixed. I logged out yesterday, "ah exe stopped working", video went to 1024x768 from 1680x1050.
Could not get desktop resolution to change.
In game, I got a "Disabling Advanced graphics" message. Everything moved real slow.
And I was told I was warping.
Rebooted, all normal. Weird, this has only happened in last week.
It started before update or patch.
Any thoughts? Heat?
I also noticed instead of picking up my LG monitor, it's saying "Generic PnP Monitor".
<S> Oz
I had that happen to me and my graphics driver had become corrupted. Reinstalling a new driver fixed things.