Tried with the most recent update as of writing, but the problem still remains. While still lacking any symbols, the stack trace does show that the invalid memory access is triggered by a call to free() (shown below). I also re-downloaded and re-ran the analysis tool but that one still crashes as well, so I figure you guys didn't find the time yet to catch that file-not-found exception
.
I'll take a look at the BIOS settings soon-ish.
If someone could put a vanilla configuration folder up somewhere, I can put those files where the analysis tool expects them, and I can send the report to supportdos@larian.com
----------
> EoCApp.exe!017841a9() Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for EoCApp.exe]
EoCApp.exe!01783b87() Unknown
msvcr90.dll!_free () Unknown
kernel32.dll!_SetThreadAffinityMask@8 () Unknown
EoCApp.exe!01251a69() Unknown
KernelBase.dll!_GlobalFree@4 () Unknown
msvcr90.dll!__msize () Unknown
msvcr90.dll!__encoded_null () Unknown
msvcr90.dll!__unlock () Unknown
msvcr90.dll!__unlockexit () Unknown
msvcr90.dll!__onexit () Unknown
msvcr90.dll!___set_flsgetvalue () Unknown
msvcr90.dll!__getptd_noexit () Unknown
msvcr90.dll!__getptd () Unknown
msvcr90.dll!_LocaleUpdate::_LocaleUpdate(struct localeinfo_struct *) Unknown
msvcr90.dll!__ismbcalpha () Unknown
msvcr90.dll!__ismbblead () Unknown
00bc6d75() Unknown
kernel32.dll!@BaseThreadInitThunk@12 () Unknown
ntdll.dll!___RtlUserThreadStart@8 () Unknown
ntdll.dll!__RtlUserThreadStart@8 () Unknown
----------
