Error: EXCEPTION_ACCESS_VIOLATION

[InstantAli3n]

Callstack:

0: 005178DD
1: 005177DD
2: 0064FDFE
3: 00605A76
4: 005FFAB3
5: 004F1BB7
6: 004F0658
7: 004F0ED5
8: 00787DFA
9: 00787D45
10: 76E96359
11: 77407B74
12: 77407B44

https://cdn.discordapp.com/attachments/208106579944275968/728904979292749924/unknown.png

https://cdn.discordapp.com/attachments/208106579944275968/728914216404385892/Dump_1.2.26_7-2-2020-20200704-052534-6064-7368.dmp

Game crashes on selling item. Goes back to last move of last battle, can't get past it. :(

[InstantAli3n]

Ok second game that I can't sell anything without it crashing. On the third try the save file is corrupted and the game is lost.

[FuzzyJuzzy]

Check your antivirus settings and exempt the game's save folder in documents from AV scanning.

[InstantAli3n]

I'm not using any AV. There's nothing else running conflicting with the save file and I can exit the game and it saves as usual otherwise.
(Antivirus IS the virus.)

[FuzzyJuzzy]

If you're on Windows 10 then Windows Security is running. Go into exclusions under "virus & threat protection" and exclude the save folder. Worked for me

[InstantAli3n]

I have windows defender completely disabled. It's definitely not something from my system interfering, it's an actual game bug.

[FuzzyJuzzy]

you'll want to send your save file and deets to [e-mail]

[ShommyX]

Hey there! Have you managed to solve the problem?

[siuwjuh]

I am having a similar problem too. Can start the game, but this crash happens randomly during play. Tried solutions found online but nothing helps.

Anyone has a solution?

My "Callstack" is different though. 009F92A3, 00A512C2, etc.

Edit: Found a solution that works for me. Refer to this thread: https://steamcommunity.com/sharedfiles/filedetails/?id=1117915907
I used the "Alternative Access Violation Crash Fix" and it worked.

Edit: Problem came back after further playing. The above didn't work afterall, though, the problem seems to happen less regularly. Am now in contact with developer to try their solution.

[ShommyX]

Unfortunately I tried both of the solutions earlier and neither worked for me. I'm currently under the assumption it's something about the order of installed drivers, cause I added my GPU long after my initial pc setup (years later). I'm thinking that my GPU drivers are now in conflict with numerous tweaks I added over the years to my integrated Intel GPU

[Morphic]

Having a same problem. Just reinstalled the game after not playing it over a year.

Haven't done any GPU tweaks and recently did a clean install/update of latest Nvidia Drivers.

Seemingly happens randomly while playing after ~30 minutes of game time. My knee-jerk reaction is a Memory issue but I'm not really sure as other games don't have an issue.(played something like La-Mulana 2 for 2+ hours straight while streaming to Steam Link and didn't have an issue. Which leads me to believe this is a game specific issue and not a Hardware/OS issue.)

EDIT: Tried both "fixes" posted in this thread and neither worked. Ended up contacting Devs as well and submitted my Dxdiag and log.txt. Just waiting on a response. Hopefully will get one soon since from what little I've played, I really enjoy the game and would like to be able to actually play without crashes.

EDIT 2: So waiting around for a response from my email I decided to try solving it myself. I think I might have found a workaround to make the game playable. So far I am able to play 60+ minutes without a Callstack crash, whereas before I would crash every 30 minutes no matter what I did/was doing.

What I did:

1. Uninstall Into the Breach via Steam.
2. Navigate PC/Documents/My Games and Delete Into the Breach Folder.
3. Browse Steam/Steamapps/Common and ensure there is not an Into the Breach Folder.
4. Restart PC.
5. Reinstall Into the Breach.
6. Launch Into the Breach. (I deleted a secondary profile I had)
7. Do no alter any default fresh install settings. (game should be a small window)
8. Play game.

I haven't tried altering the graphic settings.(normally I play Fullscreen 1920x1080) I've managed to play ~2 hours so far without issue. I'll try playing Fullscreen later and see if I get a crash. Would be interesting if the game crashes in Fullscreen but not Windowed.

[ShommyX]

Thanks for the info! You might have something there. I'll come back with the results.

BTW do you own FTL by any chance as well? Cause that one also stopped working....

[Morphic]

Originally posted by ShommyX:

Thanks for the info! You might have something there. I'll come back with the results.

BTW do you own FTL by any chance as well? Cause that one also stopped working....

I do own FTL.(Played the crap out of it getting all ships lol)

It's been quite a while since I played it. Interesting that it is no longer working either... Guess I'll install it and see if I have issues with it.

EDIT: Installed and played FTL for ~70 minutes and seemingly didn't encounter an issue. I set the game to Fullscreen(not the native option since it ruined Alt-Tab for some reason).

At this point I have no idea what the issue is and how I seemingly "fixed it" by uninstalling, deleting a folder, reinstalling, playing windowed for a bit then playing fullscreen. Though I just read that people were having crazy issues with Steam Client/Servers yesterday and the day before... That's around the time I installed Into the Breach. Perhaps I had a botched install and something got corrupted? Literally only other thing I did was check Windows update and had to install a Defender Virus Definitions update. Which I doubt that would do anything for the game since I tried the Exclusion suggestion prior.

Looks like playing Fullscreen more than ~50 minutes on Into the Breach causes a Callstack error. Windowed so far seems fine since I can play 60+ minutes without a Callstack. Interesting that it crashes while Fullscreened but not Windowed.

IMO, must be a bug with the game unable to handle newer hardware/drivers or something. Especially since other games seemingly run fine. Let Factorio(CPU/Mem heavy) idle for ~80 minutes while I cooked dinner and nothing happened.(got a nice stockpile of resources tho!) Also played ARK(GPU/CPU heavy) for over an hour with a friend and no issues there...

[ShommyX]

Hey, thanks for trying it out:) Yeah I think this might be a driver-related problem also. I had a on-board GPU for a long time, and everything worked well. It's only when I installed a new GFX card these things started happening. ITB log says that game breaks after trying to 'draw-out' the game window.

I started checking out games one at a time and realized that lots of 2D games aren't working no more. Flinthook and Tower 57 are also dead....Maybe it's a pixel-art scaling issue... :/

BTW Still can't manage to make the ITB work:D

[Morphic]

Ah, that sucks.

Started getting a response from support. First thing they suggested was updating Drivers(which I was running latest) then try rolling back to a previous Driver. Still no dice, waiting on their next suggestion.

I'm unsure if it's entirely a pixel-art scaling issue as La-Mulana 2(pixel graphics) and Terraria work fine for me... but those could be the exception. Sucks when stuff like this happens and you basically need to wait around for a solution. :/

[InstantAli3n]

It's almost certainly a code issue introduced with the backend engine rewrite in April. They just don't want to acknowledge that possibility because it means digging through some code which is "more work than it's worth" so they're looking for a workaround.

Basically "Your configuration crashes, so change your configuration". Which is obviously not a solution when game engine stuff is involved.

I'd love to hear a dev response to that ^ (I can provide access to a machine where it crashes so they can capture the error easier).