Latest Build of ACE causes a ilegal Instruction error

[enderrrrrrrrrr]

ACE3 Version: 3.1.0
(indicate if stable or dev, if dev indicate the commit the version is based on)

Mods:

• @cba_a3
• @ace3

Placed ACE3 Modules:
irrelevant

Description:
Trying to enter a game causes a crash with the following error

The exception Illegal Instruction
An Attempt was made to execute an ilegal instrcution.
(oxc0000001d) occurred in the application at location 0x0f023282.

On termination i get

Exit code:0xc0000001d / -1083841895
reason: unkown

Where did the issue occur?
Both

RPT log file:
http://pastebin.com/g1ipaPcg

[thojkooi]

From the rtp:

Distribution: 0
Version 1.46.131175
Fault time: 2015/06/15 06:34:48
Fault address:  0F023282 01:00012282 C:\Users\Carson\AppData\Local\Temp\Rar$DRa0.632\@ace\ace_advanced_ballistics.dll
file:     Arsenal
world:    VR
Prev. code bytes: 00 00 00 8B F8 03 CE 2B FA 8B C7 83 E0 1F 2B F8
Fault code bytes: C5 F4 57 C9 03 F9 EB 0F C5 F5 74 01 C5 FD D7 C0

[thojkooi]

The fix for this should be branched off release.

I will be able to take a look at this later today as well.

@enderrrrrrrrrr Do you get this every time? How do we reproduce this?

[thojkooi]

@enderrrrrrrrrr you seem to be using the mods from some temp location.
C:\Users\Carson\AppData\Local\Temp\Rar$DRa0.632\

Could you try to load it from for example the A3 root directory instead?

[whiztler]

Been testing 3.1.0 with my missions. Could not reproduce the issue
ACE 3.1.0. + CBA_A3 latest, Altis, Stratis, Takistan, VR

[enderrrrrrrrrr]

@enderrrrrrrrrr Do you get this every time? How do we reproduce this?

@Glowbal Yes Every time. I'm not sure how you reproduce it as it started happening at the latest release whenever i attempted to enter any type of game. I get about halfway through the load screen and the crash happens.

@enderrrrrrrrrr you seem to be using the mods from some temp location.
C:\Users\Carson\AppData\Local\Temp\Rar$DRa0.632\

@Glowbal I had originally loaded it from my A3 directory but i wanted to make a fresh crash without any of my own mods impacting the crash report so i made a temp directory with just ace and CBA3. It happens just the same if i have it in the a3 directory.

Been testing 3.1.0 with my missions. Could not reproduce the issue
ACE 3.1.0. + CBA_A3 latest, Altis, Stratis, Takistan, VR

@whiztler when i googled the illegal exception error it brought up something to do with the ballistics file and that it only happened on a certain percentage of machines. It may be possible that it is a similar issue for this and then only a certain number of machines are effected.

[nicolasbadano]

We think we know what's causing this. The dll will be recompiled tonight.

[enderrrrrrrrrr]

@esteldunedain Okay thanks

I made a video of the issue in case that helps: http://www.twitch.tv/enderrrrrrrrrr/b/669339632

[nicolasbadano]

@enderrrrrrrrrr, we think your processor is from the faulty batch that doesn't support avx instructions. We usually compile extensions in a way they don't use those, but yesterday the ab extension was compiled wrong for some reason.

[enderrrrrrrrrr]

@esteldunedain I have a i7-4770k if i have a faulty cpu i would like to see if i can get the manufacturer to replace it. What is the issue that i would list in my complaint to them? Thanks for your help.

[nicolasbadano]

I'm really not an expert, but it may be related to this :#1042

[enderrrrrrrrrr]

@esteldunedain thanks!

[thojkooi]

#1640

[nicolasbadano]

@enderrrrrrrrrr, please try replacing the dll by this one:

https://github.com/acemod/ACE3/blob/fix-ab-extension/ace_advanced_ballistics.dll

and report back.

[enderrrrrrrrrr]

@esteldunedain

No love, same error.

Edit: On closer inspection error code is a different location 0x52043282

exit code is 0xc000001d / -1073741795

[enderrrrrrrrrr]

Pastebin for new .dll crash: http://pastebin.com/cVCVfGZn

[enderrrrrrrrrr]

@esteldunedain So the new version of that .DLL that they updated to Seems to have fixed the problem. Will continue testing to make sure.

[nicolasbadano]

Great to hear!

[enderrrrrrrrrr]

As far as i can tell the latest .DLL fix seems to have resolved the issue. Thanks for your help guys. I'll let one of you guys close it in case theres anything you want to add to the issue.