APPCrahs with BoBII 2.14 Multiskin/ Win 7 64-bit

[brianjgregory]

All,
After several months lay-off due to persistent back problems, I have come back to BoBII/ Win 7 (also still tinkering with BoBII under Windows 8 64-bit on a separately booting drive). Having clean reinstalled BoBII under Win7 64-bit per Buddye's guide (registry & BoB directory cleaned, drive defragged etc before installation; then install & upgrade to 2.12 + 2.11 multiskin, then JSGME addition of 2.14 mods etc) I am getting a CTD after about 2 mins from going into 3D for takoff every time. The APPCRASH details are below. Anyone able to help me resolve them, please?

One other comment that may help: Win 7 doesn't seem to want to hold onto the DEP exception for BoB2 English text. Even when I try to enforce it via an elevated command prompt "bcdedit.exe /set nx AlwaysOff", set the BoBII exception then reverse the process. I just a get "The boot configuration data store cannot be opened. The requested system device cannot be found". Could this be because I am running a triple boot system with each OS on a separate drive: Windows 8.1, Windows 7, Linux Mint 15 managed by GRUB" under Linux Mint?

Problem signature:
Problem Event Name: APPCRASH
Application Name: bob.exe
Application Version: 2.1.2.0
Application Timestamp: 50d4f336
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 53ff8b90
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Thanks in anticipation of any advice
Rgds.& Thanks, Brian Gregory

[brianjgregory]

Forgot to add hardware etc details to my previous posting below:

BoBII is installed on an 80Gb Fujitsu MHZ2080A4 G2 HDD running Windows 7 64-bit
Main system drive running Windows 8.1 on a 1Tb Samsung 840Evo SSD
Third system drive running Linux Mint 15 on a 60Gb Crucial M4-CT064M4SSD2 SSD

Motherboard: Asus Sabertooth 990FX R2.0
CPU: Watercooled AMD FX-8350 running at 4.4GHz
RAM: 32Gb (4 x 8Gb) Corsair DDR3 (1866MHz max rated; running at 1600MHz)
GPU: 2 x Radeon R9 290X 8Gb Vapor-X in Crossfire mode
Monitor: Asus ROG PG278Q (natural resolution 2560 x 1440 @ 120Hz since not nVidia GPUs)

Rgds., Brian Gregory.

[PV]

I did a quick websearch for "stackhash", and I
find it is a part of the DEP process. It seems the
DEP is objecting to something in BoB2. I don't
recall ever having so set such an exception in the
first place - BoB2 has always just installed and run.

...I presume you have set the usual items in the
run icon - disable desktop composition, run as
administrator?

[brianjgregory]

Thanks for the suggestion, PV. Am indeed running BoB2 as administrator in compatibility mode (XP SP3); with Desktop composition disabled. Suspected it was a DEP issue; just don't know how to resolve it & have to reset the DEP exception for BoB2 every time I boot into Win7. Rgds., BJG.

[two27]

I've never had to used XP compatibility mode in Win 7 for BobII. Disable desktop composition and Run as Administrator are all you should need for those settings.

Here are Buddye's the instructions for setting up the game.
http://a2asimulations.com/forum/viewtop ... 17&t=33747

[brianjgregory]

Thanks two27. I'll try running in Win7 mode with admin rights & with desktop composition disabled and see what happens. Rgds., BJG

[PV]

BoB2 runs natively in Win7. We never suggest to run it otherwise,
as it most surely breaks when you do so.

[brianjgregory]

Running BoBII in Win 7 native mode has solved the CTD on entering 3D issue in Win 7. Will, see if it helps under Win 8.1 separately and report back later. Thanks for everyone's help on this. Sadly, out of the frying pan, into the fire......Now that I can run the game I have hit a new snag: I am using a Corsair K95 RGB mechanical keyboard & BoBII does not seem to be recognising all the keystrokes: the "F1-F9" keys (but weirdly not "F10"!) and most of the numericals (whether main or right-hand ones controlled by the NumLock key) all seem to have gone AWOL. Can't for example use radio commands as "R" is recognised but not the subsequent numeric inputs. Anyone else hit this snag with the K95 RGB? Should I post this as a separate issue or leave it in this thread?

Thanks in anticipation of any advice.

Rgds., Brian Gregory.

[PV]

Running BoBII in Win 7 native mode has solved the CTD on entering 3D issue in Win 7. Will, see if it helps under Win 8.1 separately and report back later.

Having noted the extensive thrashing done by several W8.1 users here,
I can confidently say it has no effect. Running natively is the default
setting for anyone trying a BoB2 install.

[two27]

My best recommendation about the keyboard is to post your question on SimHQ. They have more traffic through their boards.