Author Topic: can't start AHBETA or AHBETA11  (Read 2445 times)

Offline flyndung

  • Copper Member
  • **
  • Posts: 119
can't start AHBETA or AHBETA11
« on: July 20, 2016, 09:13:38 AM »
attached DxDiag please advise.

I7-2600 3.4ghz
16 GB memory DDR3
2 x R9270s in Crossfire
2 x 500GB HDs in RAID0
AUDIO OUT: Optical out Audio to AMP 7.1 LPCM
« Last Edit: July 20, 2016, 09:23:22 AM by flyndung »

Offline Bizman

  • Plutonium Member
  • *******
  • Posts: 9606
Re: can't start AHBETA or AHBETA11
« Reply #1 on: July 20, 2016, 10:17:14 AM »
You were able to play it before, weren't you? And you were using the very same computer?

If so, my best guess is that somehow the game has got corrupted. A hickup during the download or something like that. Try reinstalling the entire Beta game over the existing one to save your settings. If that doesn't work, remove the Beta game from your computer and start from scratch.

Your computer is at the highest end of the entire community, so it's not because lack of power. Unless the culprit is your power supply...
Quote from: BaldEagl, applies to myself, too
I've got an older system by today's standards that still runs the game well by my standards.

Kotisivuni

Offline hitech

  • Administrator
  • Administrator
  • *****
  • Posts: 12398
      • http://www.hitechcreations.com
Re: can't start AHBETA or AHBETA11
« Reply #2 on: July 20, 2016, 10:37:57 AM »
Try renaming your settings folder. If that fixes you, zip up the renamed folder and email it to support@hitechcreations.com

HiTech

Offline flyndung

  • Copper Member
  • **
  • Posts: 119
Re: can't start AHBETA or AHBETA11
« Reply #3 on: July 20, 2016, 07:51:16 PM »
sorry for the long time to reply .. i was playing the beta and i uninstalled it about 2 weeks ago and never had a issue with installing AH before .. i redownloaded the new beta install and did a clean install from scratch. the only thing that changed was i switched to RAID0 and i upgraded my amp from 5.1 to 7.1... I play another game MechWarrior Online with no issues
« Last Edit: July 20, 2016, 10:11:43 PM by flyndung »

Offline flyndung

  • Copper Member
  • **
  • Posts: 119
Re: can't start AHBETA or AHBETA11
« Reply #4 on: July 20, 2016, 10:57:42 PM »
DOES THIS HELP? the other was too big to upload here




<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="ahbeta.exe" FILTER="CMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="ahbeta.exe" SIZE="3592168" CHECKSUM="0x3AD531B7" MODULE_TYPE="WIN32" PE_CHECKSUM="0x371357" LINKER_VERSION="0x0" LINK_DATE="07/15/2016 16:50:09" UPTO_LINK_DATE="07/15/2016 16:50:09" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="ahbeta11.exe" SIZE="3746792" CHECKSUM="0x79CE4808" MODULE_TYPE="WIN32" PE_CHECKSUM="0x399992" LINKER_VERSION="0x0" LINK_DATE="07/15/2016 16:46:15" UPTO_LINK_DATE="07/15/2016 16:46:15" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="ahclds.exe" SIZE="818664" CHECKSUM="0xDCAFD73D" MODULE_TYPE="WIN32" PE_CHECKSUM="0xD333A" LINKER_VERSION="0x0" LINK_DATE="07/15/2016 16:49:39" UPTO_LINK_DATE="07/15/2016 16:49:39" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="ahedit.exe" SIZE="2234344" CHECKSUM="0xA04E96E5" MODULE_TYPE="WIN32" PE_CHECKSUM="0x22DF9E" LINKER_VERSION="0x0" LINK_DATE="07/15/2016 16:49:24" UPTO_LINK_DATE="07/15/2016 16:49:24" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="ahedmiss.exe" SIZE="3165672" CHECKSUM="0xF515C6F9" MODULE_TYPE="WIN32" PE_CHECKSUM="0x307270" LINKER_VERSION="0x0" LINK_DATE="07/15/2016 16:49:49" UPTO_LINK_DATE="07/15/2016 16:49:49" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="ahfilm.exe" SIZE="2794984" CHECKSUM="0xB218367F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2B92E2" LINKER_VERSION="0x0" LINK_DATE="07/15/2016 16:49:40" UPTO_LINK_DATE="07/15/2016 16:49:40" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="ahgtuninstall.exe" SIZE="69524" CHECKSUM="0x8D20530F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x78458987" LINKER_VERSION="0x60000" LINK_DATE="12/27/2015 05:38:58" UPTO_LINK_DATE="12/27/2015 05:38:58" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="ahobedit.exe" SIZE="1786344" CHECKSUM="0x5352C427" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1C25D1" LINKER_VERSION="0x0" LINK_DATE="07/15/2016 16:49:10" UPTO_LINK_DATE="07/15/2016 16:49:10" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="ahskview.exe" SIZE="1338344" CHECKSUM="0x6B2F8A2F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1536CB" LINKER_VERSION="0x0" LINK_DATE="07/15/2016 16:48:58" UPTO_LINK_DATE="07/15/2016 16:48:58" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="ahupload.exe" SIZE="2050536" CHECKSUM="0x966D019B" MODULE_TYPE="WIN32" PE_CHECKSUM="0x202F2A" LINKER_VERSION="0x0" LINK_DATE="07/15/2016 16:49:05" UPTO_LINK_DATE="07/15/2016 16:49:05" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="D3DCompiler_47.dll" SIZE="3451392" CHECKSUM="0x59ACD28" BIN_FILE_VERSION="6.3.9600.16428" BIN_PRODUCT_VERSION="6.3.9600.16428" PRODUCT_VERSION="6.3.9600.16428" FILE_DESCRIPTION="Direct3D HLSL Compiler for Redistribution" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.3.9600.16428 (winblue_gdr.131013-1700)" ORIGINAL_FILENAME="d3dcompiler_47.dll" INTERNAL_NAME="d3dcompiler_47.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x357714" LINKER_VERSION="0x60003" UPTO_BIN_FILE_VERSION="6.3.9600.16428" UPTO_BIN_PRODUCT_VERSION="6.3.9600.16428" LINK_DATE="10/14/2013 05:37:13" UPTO_LINK_DATE="10/14/2013 05:37:13" EXPORT_NAME="D3DCOMPILER_47.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="D3DX9_43.dll" SIZE="1998168" CHECKSUM="0x6525781C" BIN_FILE_VERSION="9.29.952.3111" BIN_PRODUCT_VERSION="9.29.952.3111" PRODUCT_VERSION="9.29.952.3111" FILE_DESCRIPTION="Direct3D 9 Extensions" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® DirectX for Windows®" FILE_VERSION="9.29.952.3111" ORIGINAL_FILENAME="D3DX9D.dll" INTERNAL_NAME="D3DX9D.dll" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1994-2007" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1E926D" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="9.29.952.3111" UPTO_BIN_PRODUCT_VERSION="9.29.952.3111" LINK_DATE="05/22/2010 01:21:17" UPTO_LINK_DATE="05/22/2010 01:21:17" EXPORT_NAME="d3dx9_43.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="fmod.dll" SIZE="1466368" CHECKSUM="0x8B8F5730" BIN_FILE_VERSION="0.1.8.4" BIN_PRODUCT_VERSION="0.1.8.4" PRODUCT_VERSION="1.8.4" FILE_DESCRIPTION="FMOD Sound System" COMPANY_NAME="Firelight Technologies" PRODUCT_NAME="FMOD" FILE_VERSION="1.8.4 (build 76196)" ORIGINAL_FILENAME="fmod.dll" INTERNAL_NAME="FMOD Lowlevel API" LEGAL_COPYRIGHT="Copyright  Firelight Technologies 2004-2016" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="0.1.8.4" UPTO_BIN_PRODUCT_VERSION="0.1.8.4" LINK_DATE="05/25/2016 14:57:26" UPTO_LINK_DATE="05/25/2016 14:57:26" EXPORT_NAME="fmod.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="fmodstudio.dll" SIZE="1382400" CHECKSUM="0xF482CD83" BIN_FILE_VERSION="0.1.8.4" BIN_PRODUCT_VERSION="0.1.8.4" PRODUCT_VERSION="1.8.4" FILE_DESCRIPTION="FMOD Studio Runtime" COMPANY_NAME="Firelight Technologies" PRODUCT_NAME="FMOD" FILE_VERSION="1.8.4 (build 76196)" ORIGINAL_FILENAME="fmodstudio.dll" INTERNAL_NAME="FMOD Studio API" LEGAL_COPYRIGHT="Copyright  Firelight Technologies 2004-2016" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="0.1.8.4" UPTO_BIN_PRODUCT_VERSION="0.1.8.4" LINK_DATE="05/25/2016 14:59:27" UPTO_LINK_DATE="05/25/2016 14:59:27" EXPORT_NAME="fmodstudio.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="openvr_api.dll" SIZE="265024" CHECKSUM="0x7D2D27F1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x439E3" LINKER_VERSION="0x0" LINK_DATE="05/20/2016 22:09:54" UPTO_LINK_DATE="05/20/2016 22:09:54" EXPORT_NAME="openvr_api.dll" EXE_WRAPPER="0x0" />
</EXE>
<EXE NAME="ahbeta.exe" FILTER="CMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="ahbeta.exe" SIZE="3592168" CHECKSUM="0x3AD531B7" MODULE_TYPE="WIN32" PE_CHECKSUM="0x371357" LINKER_VERSION="0x0" LINK_DATE="07/15/2016 16:50:09" UPTO_LINK_DATE="07/15/2016 16:50:09" EXE_WRAPPER="0x0" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="CMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="1114112" CHECKSUM="0x1325986C" BIN_FILE_VERSION="6.1.7601.19018" BIN_PRODUCT_VERSION="6.1.7601.19018" PRODUCT_VERSION="6.1.7601.18015" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.1.7601.18015 (win7sp1_gdr.121129-1432)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x11C776" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="6.1.7601.19018" UPTO_BIN_PRODUCT_VERSION="6.1.7601.19018" LINK_DATE="09/29/2015 03:00:35" UPTO_LINK_DATE="09/29/2015 03:00:35" EXPORT_NAME="KERNEL32.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" />
</EXE>
</DATABASE>



<?xml version="1.0" encoding="UTF-16"?>

-<WERReportMetadata>


-<OSVersionInformation>

<WindowsNTVersion>6.1</WindowsNTVersion>

<Build>7601 Service Pack 1</Build>

<Product>(0x1): Windows 7 Ultimate</Product>

<Edition>Ultimate</Edition>

<BuildString>7601.19018.amd64fre.win7sp1_g dr.150928-1507</BuildString>

<Revision>1130</Revision>

<Flavor>Multiprocessor Free</Flavor>

<Architecture>X64</Architecture>

<LCID>1033</LCID>

</OSVersionInformation>


-<ProblemSignatures>

<EventType>APPCRASH</EventType>

<Parameter0>ahbeta.exe</Parameter0>

<Parameter1>0.0.0.0</Parameter1>

<Parameter2>57891441</Parameter2>

<Parameter3>ahbeta.exe</Parameter3>

<Parameter4>0.0.0.0</Parameter4>

<Parameter5>57891441</Parameter5>

<Parameter6>c0000005</Parameter6>

<Parameter7>001a606d</Parameter7>

</ProblemSignatures>


-<DynamicSignatures>

<Parameter1>6.1.7601.2.1.0.256.1</Parameter1>

<Parameter2>1033</Parameter2>

<Parameter22>0a9e</Parameter22>

<Parameter23>0a9e372d3b4ad19135b953a78882e 789</Parameter23>

<Parameter24>0a9e</Parameter24>

<Parameter25>0a9e372d3b4ad19135b953a78882e 789</Parameter25>

</DynamicSignatures>


-<SystemInformation>

<MID>35AC5053-A1C0-48DD-8EBB-75611AD768D4</MID>

<SystemManufacturer>Gigabyte Technology Co., Ltd.</SystemManufacturer>

<SystemProductName>P67A-UD4-B3</SystemProductName>

<BIOSVersion>F1</BIOSVersion>

</SystemInformation>

</WERReportMetadata>


Offline Chilli

  • Platinum Member
  • ******
  • Posts: 4278
Re: can't start AHBETA or AHBETA11
« Reply #5 on: July 21, 2016, 04:45:38 AM »
Ooops. Thought he needed help with attaching dxdiag until I looked at OP.
« Last Edit: July 21, 2016, 04:48:46 AM by Chilli »

Offline Skuzzy

  • Support Member
  • Administrator
  • *****
  • Posts: 31462
      • HiTech Creations Home Page
Re: can't start AHBETA or AHBETA11
« Reply #6 on: July 21, 2016, 06:20:57 AM »
I see one problem.  You are using the default Microsoft supplied audio driver instead of the native audio driver.  This has been known to cause crashes with applications using DirectSound.

That Microsoft driver was only intended to be used to get a computer up and running.  It is supposed to be replaced with the native driver for the sound device.

Install the native sound driver and see if that fixes it.
« Last Edit: July 21, 2016, 06:22:43 AM by Skuzzy »
Roy "Skuzzy" Neese
support@hitechcreations.com

Offline flyndung

  • Copper Member
  • **
  • Posts: 119
Re: can't start AHBETA or AHBETA11
« Reply #7 on: July 21, 2016, 06:49:55 AM »
I see one problem.  You are using the default Microsoft supplied audio driver instead of the native audio driver.  This has been known to cause crashes with applications using DirectSound.

That Microsoft driver was only intended to be used to get a computer up and running.  It is supposed to be replaced with the native driver for the sound device.

Install the native sound driver and see if that fixes it.

i am using the optical audio out not the onboard sound card. is that a problem?

Offline Bizman

  • Plutonium Member
  • *******
  • Posts: 9606
Re: can't start AHBETA or AHBETA11
« Reply #8 on: July 21, 2016, 08:09:06 AM »
i am using the optical audio out not the onboard sound card. is that a problem?

For what I understand the optical audio comes from the onboard card so that is the problem. Although the signal stays digital in the optical wire from your computer to your amp which converts it to an audible analog sound, some processing has to be made to it also in the computer. By that I mean things like locating sounds in a 3D landscape inside a game. Plain audio from a Youtube video, mp3 or a music CD are "as is" whereas three dimensional game audio changes every time you or the surrounding objects move.
Quote from: BaldEagl, applies to myself, too
I've got an older system by today's standards that still runs the game well by my standards.

Kotisivuni

Offline Skuzzy

  • Support Member
  • Administrator
  • *****
  • Posts: 31462
      • HiTech Creations Home Page
Re: can't start AHBETA or AHBETA11
« Reply #9 on: July 21, 2016, 11:04:22 AM »
i am using the optical audio out not the onboard sound card. is that a problem?

The optical out still needs a native driver.  It currently is using the default Microsoft supplied driver, which is woefully inadequate.
Roy "Skuzzy" Neese
support@hitechcreations.com

Offline flyndung

  • Copper Member
  • **
  • Posts: 119
Re: can't start AHBETA or AHBETA11
« Reply #10 on: July 24, 2016, 01:10:48 PM »
installed native Realtek Driver finally got it to work through My Optical out. still same issue.. soon as i launch either version i get the "has stopped working" box.

Offline Bizman

  • Plutonium Member
  • *******
  • Posts: 9606
Re: can't start AHBETA or AHBETA11
« Reply #11 on: July 24, 2016, 01:33:20 PM »
Hmm... How about the rest of your motherboard drivers? I'm not too good in reading dxdiag outputs, but since you hadn't installed the sound driver you might have skipped the others as well. If the generic Windows drivers work, you won't see any signs of the missing drivers in the Device Manager.

In case you haven't but can't find the Gigabyte CD, here's the link to the driver download page: http://www.gigabyte.com/products/product-page.aspx?pid=3759#dl
Quote from: BaldEagl, applies to myself, too
I've got an older system by today's standards that still runs the game well by my standards.

Kotisivuni

Offline flyndung

  • Copper Member
  • **
  • Posts: 119
Re: can't start AHBETA or AHBETA11
« Reply #12 on: July 24, 2016, 01:52:45 PM »
never had a issue til this new beta with a clean install. all my non-sound card drivers have stayed the same and worked with Aces high II and the Alpha before it went Beta. only reason i switched to the realtek sound drivers was to try and get this game to come up. when i first tried to install the drivers i got no sound outputing to my reciever and i have resolved that issue so i can keep the realtek sound drivers for now. the only other changes i made was moved my single HD to a Raid 0 (2 x 500GB)
« Last Edit: July 24, 2016, 01:56:03 PM by flyndung »

Offline Bizman

  • Plutonium Member
  • *******
  • Posts: 9606
Re: can't start AHBETA or AHBETA11
« Reply #13 on: July 24, 2016, 02:13:48 PM »
Even if you haven't installed the motherboard drivers you might have been able to act normally. That's what the generic drivers are for: To enable installing dedicated drivers in the familiar Windows way.

One explanation why you haven't had issues with AH2 is that it's more dependent on the processor. Microsoft's Intel drivers may work well enough for it to work. AH3 relays heavily on the video card and if you haven't installed the chipset drivers, the pci-e slot may not work properly when the load exceeds a boundary. The chipset also controls the built-in Realtek sound card and other onboard devices, so without specific drivers for it any issues are possible.
Quote from: BaldEagl, applies to myself, too
I've got an older system by today's standards that still runs the game well by my standards.

Kotisivuni

Offline flyndung

  • Copper Member
  • **
  • Posts: 119
Re: can't start AHBETA or AHBETA11
« Reply #14 on: July 24, 2016, 02:34:51 PM »
Even if you haven't installed the motherboard drivers you might have been able to act normally. That's what the generic drivers are for: To enable installing dedicated drivers in the familiar Windows way.

One explanation why you haven't had issues with AH2 is that it's more dependent on the processor. Microsoft's Intel drivers may work well enough for it to work. AH3 relays heavily on the video card and if you haven't installed the chipset drivers, the pci-e slot may not work properly when the load exceeds a boundary. The chipset also controls the built-in Realtek sound card and other onboard devices, so without specific drivers for it any issues are possible.


 wouldn't i had have the same issue when i installed the AH3 Alpha? and i was using the Microsoft drivers drivers then and everything seem to work just fine.