memoury could not be read

[85_Hawker]

trying to log in via steam getting this all the time ( the instruction at 0x0000000006ABB16BB referenced memoury at 0x000000000CDCDBD. The memoury could not be read. click on ok to terminate the program. ) please help. I am running

 

windows 10 home processor intel® core i3-4150 cpu@ 3.50ghz 3.50 ghz 8.00 gb installd ram 64-bit operating system x64-baced processor and a NIVIDIA GeForce GT 740 with itergrated RAMDAC total avalibel memory 5089 mb Dedicated memoury 1024mb shared system memoury 4065mb

[DickDong]

Getting very similar error when I shut down IL-2.  I5, Geoforce 740 with 4gb, 8gb RAM.  Attached error screenshot.  This only happens when I hit EXIT GAME in main menu.  Just completely uninstalled game and reinstalled a clean copy and no joy, the error still pops.

[85_Hawker]

found the problem, it was my joy stick driver and razor hand pad conflicting in windows 10, I disconnected the razor now I have no problems

[Djosha]

I have exactly the same problem. Exactly, except number of  instruction  is Ox63b11a3b. One month already  to solve the problem , and nothing. As to the help from socalled "support", it is quite insulting no-help. They are sending me constantly to the same page of Q&A, and that is it. I am very angry, especially that prior to update (which feautured tank), game worked flawlessly.  Please, help me if you can. I tried your method, took out everything except mouse+ board + sound s., +joystick,  again nothing. Should I take out joystick how I will play?

[Djosha]

Well, you were right it is joystick driver (Black Widow Speedlink). After updating, problem solved. But after 1 month of trying!  Thank you, if not for you, I would still roaming about cfg or whatever.

[Jade_Monkey]

I got a similar error now, it happens mostly when trying to get into Wings of Liberty server (once it finishes loading), and now it happened in QMB in the middle of a flight.

 

I have the latest Win 10 drivers for Saitek X55 HOTAS.

 

I started getting this error since the last patch.

Edited January 9, 2016 by Jade_Monkey

[Djosha]

You know, it may be stupid, but try to connect your joystick on different USBs. I had it connected in the back of computer; changed to USB in front..Voila!...Now, I don´t know if updated driver did it, or change of USB ? Anyway, it is not difficult to try.

[CCG_bexhausted]

Hello !

I had  the same error but i apologize i forgot to take a screen with the error message.

Also i took the two files xxx.gui.log because i didn't know the one you need.

https://www.dropbox.com/s/d8rpc33mghg503v/Error%20memory.7z?dl=0