Page MenuHomeFeedback Tracker

Arma 3 APPCRASH in kernelbase.dll after changing monitor
Closed, ResolvedPublic

Description

Hi,

1st of all, my arma3 worked fine up to few hours ago.
The only thing which changed is my monitor: i went from a fullhd 120hz monitor to a 1366x768 60hz one.

I tried to start arma3 and it crashes. On the same pc, it does not happen with neither arma2, neither dayz standalone, neither a lot of other games.

I also tried to edit the cfg, changing manually the resolution and the refresh rate, with no result.

Here are a copy paste of the details of the crash:

Firma problema:
Nome evento problema: APPCRASH
Nome applicazione: arma3.exe
Versione applicazione: 1.38.128.937
Timestamp applicazione: 54bd4194
Nome modulo con errori: KERNELBASE.dll
Versione modulo con errori: 6.1.7601.18409
Timestamp modulo con errori: 53159a86
Codice eccezione: 406d1388
Offset eccezione: 0000c42d
Versione SO: 6.1.7601.2.1.0.256.1
ID impostazioni locali: 1040
Informazioni aggiuntive 1: 375d
Ulteriori informazioni 2: 375d7f8896349689eeae94fb5d0c01e8
Ulteriori informazioni 3: c687
Ulteriori informazioni 4: c687b36a9619159b30abca10db7daa1b

Trying various things, i found out that deleting the arma3 folder inside appdata solved the problem. And it was working fine for few hours, i was even closing and reopening a3 few times.

Then, for the first time in few years, electricity power at home went down, for like a pair of seconds, while i was playing a3. Since when i opened back the PC, A3 is doing again the same error, and every other game, dayz and a2 included, is working instead fine.

This is the new error:

Firma problema:
Nome evento problema: APPCRASH
Nome applicazione: arma3.exe
Versione applicazione: 1.38.128.937
Timestamp applicazione: 54bd4194
Nome modulo con errori: KERNELBASE.dll
Versione modulo con errori: 6.1.7601.18409
Timestamp modulo con errori: 53159a86
Codice eccezione: 406d1388
Offset eccezione: 0000c42d
Versione SO: 6.1.7601.2.1.0.256.1
ID impostazioni locali: 1040
Informazioni aggiuntive 1: 375d
Ulteriori informazioni 2: 375d7f8896349689eeae94fb5d0c01e8
Ulteriori informazioni 3: c687
Ulteriori informazioni 4: c687b36a9619159b30abca10db7daa1b

Unluckily this time the appdata a3 folder doesnt have any involvement in the crash, i deleted it again and it didnt fix it.
This does make even less sense then before!

Details

Legacy ID
1373397903
Severity
None
Resolution
No Bug
Reproducibility
Always
Category
Game Crash
Steps To Reproduce

I have no idea, it just happens all the time i open arma3 now

Event Timeline

SpaceMarineITA edited Additional Information. (Show Details)
SpaceMarineITA set Category to Game Crash.
SpaceMarineITA set Reproducibility to Always.
SpaceMarineITA set Severity to None.
SpaceMarineITA set Resolution to No Bug.
SpaceMarineITA set Legacy ID to 1373397903.May 7 2016, 8:11 PM
Bohemia added a subscriber: Bohemia.May 7 2016, 8:11 PM

Did you installed drivers to new monitor? Also chcek you profile data folder (My documents/Arma 3/arma3.cfg and search lines about resolution and refresh rate. Be sure your monitor support them, if game will still grash delete all settings in folers inlcuding arma3.cfg and arma3 other profiles (also my documents) arma3profile files.

Also TRY TO RUN GAME WITHOUT ANY MOD!

Eventualy try this one:
http://forums.steampowered.com/forums/showthread.php?t=2908144

  1. i didn't install any driver
  2. i managed to find another monitor which is exactly the same as the 1st one, the problem is still here, so i guess it was a coincidence, it's not monitor related
  3. i am not running any mod at the moment, the crash is still here.
  4. the lines inside my CFG, like i have wrote in the initial post, have been corrected both times accordingly to the specs of the monitor used.

I even tried removing the cfg file completely, arma3 doesnt reach a state in which it creates a new one, it crashes well before it.

  1. why did u link me this tread on the steam forums? It's a different game and i never used "games for windows live" in my life.

Arma3 doesnt use GFWL and i didn't install it in the last 12 hours.
Yesterday night it was working perfectly fine.

I have heard people in forums complaining about a recent A3 update. Maybe is update related. Cant say if my a3 updated tonight btw, i was sleeping, and left the pc running with steam open

More infos for you:

http://forums.bistudio.com/showthread.php?188220-Arma-3-APPCRASH-in-kernelbase-dll-after-changing-monitor

an user in this thread gave me a password for the 1.36 steam version beta subscription.

I just installed it and it works.

So it's a problem with the last patch

StJimmy added a subscriber: StJimmy.May 7 2016, 8:11 PM

Any chance you've been using this tweak?
http://forums.bistudio.com/showthread.php?177454-a-simple-registry-tweak-for-increased-performance

The monitor changing might have been just coincidence because your problem sounds very much the same as with that tweak. It isn't working anymore and is causing Arma 3 to crash instantly especially fresh started computer but computer that has run for some time Arma 3 might work without problems.

Arma 3 working on 1.36 really makes me think it's that tweak that's causing the problem.

Yes, it might be, im not sure it's running right now but i remember this page, i have seen it before, and i tend to tweak a lot my pc

At the moment im switching back from 1.36 to stable branch.

Ill try to start arma without touching whichever tweak is actually running, and then if it crashes again, ill try that .reg for disabling it and see what happens

Arma 3 might run well until you restart your computer if you've that tweak on.

Switching back to 1.38 seem to have made it working, but it might be the same thing that happened when i actually installed the update and it was working, but just for a while.

If the crash happens again i'll update this request and let you know.

Btw im also fowarding this solution in the forum

Jimmy, u are right, im trying this right now, will update soon

Yes, it crashed, i run the reg for uninstalling it, and apparently it's not crashing any more.
I guess that was the problem.

If it happens again ill report updates

StJimmy removed a subscriber: StJimmy.May 31 2016, 6:21 PM