New new issue since latest upgrade

[Muddy]

After the auto upgrade the game still runs no problem at all, however this error appears when I go to exit out. It does not happen every single time but about 90% .

There was a more extensive list of errors on one exit but that only happend one time.

The game seems to be running perfect so what are your suggestions to get rid of this.

 

Sorry about the screen shot lol I snapped it with the iPad .

 

 

Edited December 23, 2015 by Muddy17

[MK_RED13]

Same here.. every time.. hm.. nice update!

[6./ZG26_Gielow]

I had that too since summer patch.

[Muddy]

Ok well as long as it's not stopping game play, until next time..

I'm running on an Alienware laptop , it runs everything awesome ( Il2 COD excluded) don't have stats handy but are you guys running laptop as well, I have not seen anybody else mentioning this.

 

Too be sure, I am not complaining , however if we can steer clear of a patch that would ground people in the futer it would be best for them to acknowledge this issue.

[71st_AH_Mastiff]

been reported 

[310_cibule]

I had that too since summer patch.

So had I.

[Godfather_Actual]

I had this problem too since the last patch before this one. I did a work around by not using the launcher(i use it just to patch). I created a shortcut using the direct application .exe

[Asgar]

old bug.

[Czar66]

I had this once or twice while joining a server but the game ran normaly after a game restart.

[ScotsmanFlyingscotsman]

I also have a problem since last update, have a HOTAS WARTHOG, I re-mapped the throttle and it goes about 60% of it's travel, then as I continue to advance the throttle the engine retards.

So it goes 20-30-40-50- 60- 70- 20- 10- 0 if you see my drift. If I leave it at 70% it will suddenly drop to 49% or some other not helpful position

 

I have reinstalled the HOTAS software, it works in DCS World all versions, FSX and xplane. Also tested it on the Thrustmaster system and the travel is seen from 0 to 18,0000 whatsits, whatever it uses.

Have reversed the axes etc, but still got the same problem, Does not matter which aircraft it is, german or Soviet, the engine is showing. Any assistance appreciated

Using amd Athlon 64 bit, 3ghz processor , 2TB HDD , 11Gb Memory Win 10.

[APanchikov]

The access violation crash is also preceded with "Can't created Direct 3DDevice D3DERR_NOTAVAILABLE@" error. 

Check screen attached. 

The window also is blocking any operations with entirely OS until "OK" button is pressed.

 

So you really think this game worth its money?

[SilentOtto]

#7 Godfather_Actual -> Thanks mate

[71st_AH_Mastiff]

from what I have found out; anytime you install or add new skins you have to reboot your computer to get the memory of the game to accept the skins and not cause an error.

[XQ_Lothar29]

Equal error for me.. screenshot for my error

 

 

This error only in Multiplayer

 

 

This error in flight OffLine

 

Edited January 2, 2016 by E69_Lothar29

[Retnek]

I've never had that kind of crash to desktop with 1.105, it's new with 1.106. It happens every 2 or 3 hours flying, mainly during multiplayer flights, more often after > 30 min flight time. My *impression* is, it happens quite often directly after new server messages were displayed. Rebooting after the error helps to avoid it for a longer time, restarting the program without reboot might provoke the next CTD within 15 min.

 

Application popup: Windows - Application Error : The instruction at 0x008bfc91 referenced memory at 0x31d9aa4c. The memory could not be written.
 

Application popup: Il-2 Sturmovik: Windows - Application Error : The exception unknown software exception (0xc0000417) occurred in the application at location 0x7288ccd5.

 

Application popup: Windows - Application Error : The instruction at 0x008bfc91 referenced memory at 0x2f9ec6cc. The memory could not be written.
 

Application popup: Windows - Application Error : The instruction at 0x00b2ffc4 referenced memory at 0x00000000. The memory could not be read.
 

Application popup: Windows - Application Error : The instruction at 0x00b2ffc4 referenced memory at 0x00000000. The memory could not be read.
 

Application popup: Windows - Application Error : The instruction at 0x014c39e6 referenced memory at 0x0007cce4. The memory could not be written.

 

Application popup: Il-2 Sturmovik: Windows - Application Error : The exception unknown software exception (0xc0000417) occurred in the application at location 0x7249ccd5.

 

 

Add-on 03.01.16, 17:34:58 GMT+1 on the MP-Server "Operations Server Example Mission" - PC was running for a few min, I began the mission as the only player, choosen He-111-recon mission, CTD after 2 or 3 min of flight:

 

Application popup: Windows - Application Error : The instruction at 0x008bfc91 referenced memory at 0x3201b384. The memory could not be written.
 

Edited January 3, 2016 by Retnek

[F/JG300_Gruber]

Same here, I have quite a few occurence of these crashes on a regular basis since the 1.106

 

Good job collecting the different errors Retneck

[caryatid23]

I too am getting memory access errors on the client. Although mine is different than above; Buffer overrun style: 

[Retnek]

Same server, 5 min ago:

 

Application popup: Windows - Application Error : The instruction at 0x008bfc91 referenced memory at 0x31f3b384. The memory could not be written.

 

Most interesting is that address "0x008bfc91" is upcoming frequently and on different Client-PC. Anyhow, for multiplayer-events a rate of one CTD every 2 or 3 h is unacceptable, let's hope there is a solution with the next update.

Edited January 3, 2016 by Retnek

[Retnek]

I opened a ticket at the support, the bad news, the list below is part of the procedure: just a check the basic features and there seems to be no specific solution - we're fishing in murky waters. The god news: maybe this list might help someone:

 

##################################

Try the following steps:

-  to introduce the game to the exceptions list security features or to disable them.

- set the minimum settings the game, and then rise to an acceptable level

- disable "FullScreen" option

- disable the "GeForce Experience" (If you are using)

- if you have made changes in the settings of your video card drivers-please return them to the default state.

- you may need to reinstall driver for video card

- exit all unnecessary processes. . The normal number of processes for Win7/8 -32 -40 pieces. processes that work in parallel with the game can affect the speed of the CPU thread synchronization.

 take a look at this article:

http://support.microsoft.com/kb/929135/en-us

http://support.microsoft.com/kb/815069/en-us

- you may need to reinstall DirectX, Netframework 3.5 and Microsoft Visual C++ 2005 Redistributable from  \1C Game Studios\IL-2 Sturmovik Battle of Stalingrad\data\updater\3rd_party or website Microsoft

-there is a possibility that you have a corrupted game files. In this case, it makes sense to perform a full reinstall of the game

##############

 

I'm sure my system was fine anyhow, no need to check most of the stuff c.a. on a well cared PC. Anyhow, I went though it point for point, actual drivers. default settings etc, except the reinstall of the game. Result: no changes, FPS remained as good as it had been before and the first crash to desktop came within a few minutes after opening a multiplayer-session on a remote server. So next thing is to reinstall the game.

Edited January 15, 2016 by Retnek

[SOLIDKREATE]

Me too

 

 

 

[71st_AH_Mastiff]

I seem to not have any more crashes after the latest hotfix drivers from nvidia, 

 

https://forums.geforce.com/default/topic/910177/geforce-drivers/announcing-geforce-hotfix-driver-361-60/

[BSS_Sniper]

The crashes are becoming ridiculous and happening 50% of the time I go into multiplayer. It's the same as what's being talked about here and since the update.

[F/JG300_Gruber]

I seem to not have any more crashes after the latest hotfix drivers from nvidia, 

 

https://forums.geforce.com/default/topic/910177/geforce-drivers/announcing-geforce-hotfix-driver-361-60/

 

 

No luck for me: I updated to the 361-60 and I still crashed 4 times yesterday

[Hartigan]

I had same issues...but haven´t had any game memory crash after i downloaded game installer client and installed it. No need to uninstall game, just install it. Client will find your current game location. Nothing is lost ...all skins and input setups will remain but it will repair your registry cache. Crashes had something to do with Ccleaner i´ve use to clean my PC. 

 

Give it a try

Edited January 19, 2016 by Hartigan

[F/JG300_Gruber]

I may try that.

 

For the steam version do you think that verifying the cache integrity through steam might be enough ?

[Hartigan]

Hmm, i don´t know how to proceed with steam version. Maybe somebody else have found solution for that. Or you can just try fresh install. (backup skins and input folder

[BlackSix]

Hmm, i don´t know how to proceed with steam version. Maybe somebody else have found solution for that. Or you can just try fresh install. (backup skins and input folder

Verifying the cache integrity

https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335

or use our support

http://il2sturmovik.com/support/

or use Steam support

https://help.steampowered.com/

[Jade_Monkey]

The crashes are very frequent since the last update (1.107b). It's a bit ridiculous, and there are no crash dumps being generated despite having done the registry thing.

 

I got memory could not be written twice in a row.

[Quax]

Getting my first black screens in QMB after 1.107b. Crash is so fatal, that nothing works except reboot button.

[[7e]Forza42]

same here, i can't play more than 5 min ..... crash in menu, crash in mission, crash in briefing, crash everywhere.

Memory can not be read.