Fresh Install with Windows 10 and TIR Issue

[6./ZG26_Emil]

I have a new install of Windows 10

 

My IL2 was on another drive so I left it as is, I installed the new TIR software and when I ran the game I had a windows error pop up. I uninstalled IL2 and reinstalled and have the same issue except this time I can get in the game but when I leave I get this error.

 

Any help would be appreciated!!

[6./ZG26_Emil]

uninstalled TIR software and gone back to 5.3 and it seems ok....so far

[6./ZG26_Emil]

and it's back....has no one else had this? It's more stable now but is happening random instead of when I shut the game down

[Bando]

Nope. No problems here.

Does not help, I know.

[6./ZG26_Emil]

I think it's more to do with TIR and not IL2. Is there any way to decipher these messages or are they just totally useless?

[216th_Jordan]

But you just have this message when you leave?

Seems I've got it too, but most of the time I exit with alt+F4 and don't get the message, anyways: exit procedure was always bugged in some way or another so if your game works fine don't wrestle with it!

 

Jordan

 

PS: Overread one of your posts: Yes got those CTDs sometimes too and you're not the only one, although it seems that this is more of a common problem than a Windows 10 one..

Edited February 21, 2016 by 71st_AH_Jordan

[6./ZG26_Emil]

Hi Jordan so you get this message as well?

 

I also got another one 3d or d3 something.

 

Originally that message was happening when I hit Exit but then today it happened while I was in game, when I clicked OK to terminate it blew away BOS so I guess it's pointing to BOS being the problem. It sounds like a memory issue.

[216th_Lucas_From_Hell]

Not sure how this could help you since the situations are entirely different, but it might at least point to the root of the problem:

 

I'm running severely under minimum specs, including RAM. Since I had to bring my PC back to factory-fresh settings recently (meaning Vista 32-bit madness), BoS was working terribly and I was getting that memory error all the time - understandably, of course. The solution I found was this, which allowed user-launched applications to tool with 3GB out of the underwhelming 4GB the OS can play with. I have only gotten one or two of these errors ever since - one during the SP part 1 of the early Stalingrad campaign, and another during last Friday's Bomber Flight.

 

Of course, this doesn't apply at all to your OS and your RAM at all, but elaborating further the first of those crashes after the CMD fix happened because I didn't close a lot of stuff running on the background (Firefox with 25 tabs from an extensive search, Skype, HP-supplied bloatware and so on), clogging my short supply of RAM. The second time I was running TeamSpeak and BoS only, but that day everyone CTD'd like flies.

 

I don't know how much you have running in the background by default, but I suppose it doesn't hurt to open the W10 Task Manager and zap any process that you won't be needing while playing the game and see if that has a positive impact (kind of a safe-mode gameplay, if you must).

 

Hope it at least points you in the right direction, if anything. There's also the new crash report method introduced in the last update, have you had a look at that?