Game crashing during loading with really weird, consistent symptoms

So my game has crashed while loading a few times now, if I persevere, it works, but it takes about 3 tries re-loading it until it succeeds, then another 3 after it disconnects me for "being inactive" (On a side note, isn't there a way you could make it so someone isn't auto-disconnected from being inactive if their client didn't load in the first place?)

It's a little bit of hit or miss when it crashes, about one in 4 times, but when it does, it has some really weird symptoms, which are always consistent. (A note real quick, I tried repairing, it didn't work).

It always takes exactly three times to work properly:

• The first time it says I've been disconnected from the server during the loading screen, only once everyone has reached 100% and the game was about to start.
• Then it shows me the client again, but instead of the reconnect screen, it shows me the normal screen. I must then attempt to start another game, when it will inform me that I'm in a game, and tells me to re-open the client. (If I don't do this, and just re-open the client, it gives me the regular screen, and until I go through this process, it won't work).
• After I close and open the client again, it shows me the reconnect button, and when I press that it loads. However, at some time during this loading, it crashes and (here's the weird part), proceeds to not bugsplat, and empty all of the log files it was creating. Now let me clarify on this a bit, I was confused by this when I opened the logs to post it and found an empty file, so I decided to look through the previous logs for anything abnormal. The previous logs looked fine though, so I proceeded to run a custom until I reproduced the issue, and watched the log file as it updated during it. What I found is that as soon as the issue first starts, the logs stop recording (all of them...), then once I get to the part where it crashes, it deletes everything. And I mean everything. I opened it in a hexcode editor, it had nothing at all... It does however give me a stack trace as per apple's standard system of doing that ("You should send this issue to apple!" Thanks apple.... but I don't think you can do a thing about it....), and that can be found here: http://pastebin.com/pt4XTrtK
• After it does that crash, I can re-open the client and it will work fine. Well.... fine except for the fact that upon loading, I get disconnected from "being inactive", and have to repeat the process again. Interestingly, if it happens once, and I disconnect in the middle of the game, it will keep happening until I start a new game, implying to me it's a problem loading an asset into the computer's memory. I can tell you that there is no consistent champion, or map it happens with (by myself with ashe on the howling abyss is just as likely to proc the issue as a full team on SR with no ashe on either team).

I'm afraid that's all I can think of that might be helpful in reproducing the issue. It's not consistent when it happens, I had started playing normals again cause I had over twenty games in a row on customs then it hit again, before being about every other game, then every 3 games, then every game, before once ever six games, it's not consistent, so I can't tell when it's fixed...

Hopefully you can figure out my weirdly specific bug... To be honest, the only thing I can imagine that would do this is a virus or a partially corrupted OS, as I can't even thing of an easy way to tie your client, and game logging systems programmatically. It would make much, much more sense to program them separately, especially since the game and the client are essentially completely different applications. And yet them both being cleared suggests that this issue is somehow spanning both applications. I did a deep search with anti-virus software and came up with nothing though, and I don't know why someone would make a virus do such an oddly specific set of things. So that leaves the OS or part of the RAM being corrupted (which I should have noticed elsewhere) or something really funky going on with the game.

Regardless, if you have anything you want me to test, just speak up! Also, thanks for maintaining this game to whoever ends up reading this! I can't imagine it's easy to work with such an intricately networked game. I myself hate networked programming, too many unintentional issues caused by corrupted packets looking fine....