User Details
- User Since
- Dec 12 2016, 4:09 PM (415 w, 5 d)
Dec 14 2016
Well 64bit Arma just hit dev Branch, time to pull out the big guns and see if my problem is solved, if so I vote 64 if not it's time to kick Arma to the curb and get medieval af..
Dec 13 2016
ahh shit now that vanilla arma isn't crashing i guess my ticket is moot... ?
I can get footage of the crash if needed
I've never had this issue with these mods before but I was using different hardware as I have recently upgraded, my best guess is arma doesn't like my ram, bios and titan or any combination of the latter drivers included. I was just hoping it was not exclusive to my particular setup.
This crash was not reproduced using multiplayer thus there is no mdmp file which would only be created if the crash was in mp, correct? the multiplayer crash is harder to reproduce or I have some how fixed that part of the issueas i am not crashing in wasteland now but the single player mission with rhs, ace 3 and alive is still crashing which you have all the data in those two files contained in the Crashlog zip file. I will upload the mission as well.
is there a way to force create that file via launcher or otherwise because thats all it gave me.
HMMMM, that file extension doesn't exist.
Dec 12 2016
https://drive.google.com/open?id=0BxofFjdBEQ1PaGV0UG84MVBTZjQ
Here is The DXDiag log if its useful.
Ive tried Clean installing windows 10, changing page file system allocated and custom ssd allocation. reinstalling mods, Arma 3. Ran Dwardens profiling branch, not overclocking changing the memory xmp profile to none and back, updated bios rubbed my belly and patted my head. ect... the one thing I have not done is what you are hopefully going to ask me to do that fixes the issue.