Jump to content

Refererenced memory could not be read?? Terminate program???


Recommended Posts

Posted

Hi,

Just today lockon 1.1 has started giving me(again) memery problems. Sometimes it runs fine other times, (most times) when loading campaigns i get the following error message.

 

"The instruction at "0xbb666ac" feferenced memory at 0x00000000. The memory would not be read. Click ok to terminate program"

 

I have had this problem before, but the only way to fix it was to re-format twice. I really don't feel like wasting my night reformating. I have restored all default settings in bios with regards to memory and overclocking. Dito for the GPU. Memory tests run fine for several hours and no other programs complain. Im really at a loss with this one. Any help is apreciated.

cheers

Posted

I have had random problems like this, they come and go for me.

 

I am starting to think it is a virtual memory issue.

 

What I did was, turn off virtual memory. Boot into safe mode, then defrag. Then reboot normal, re-enable virtual memory, and then reboot of course.

 

I havent had an error in the week since I did it.

Posted

Might try shutting down NVSVC32.exe (task mgr - processes) for Nvidia, or ATISGAG and ATI2EVYY for the ATI guys. Also, shut down all firewalls and Antivirus stuff. Couldn't hurt.

Posted

Prophet is correct. This is do to timing discrepancies between page file (virtual memory) access times and how long lockon.exe waits for the requested data. It can also be caused by memory leaks where the program pointers get pushed beyond real address space. Its interesting to me that unmoddified (lockon tweaks) installations running missions created on unmoddified machines rarely experience this and similiar (MSCVRT.DLL) issues. Make sure your virtual memory is placed on a fast HDD (at least 7200rpm 8mb cache). Please note that the page file is not defraggable hence the procedure Prophet used above. :cool:

When all else fails, Eject then read the manual.

Oh, and a good wingman helps.

Posted
Prophet is correct. This is do to timing discrepancies between page file (virtual memory) access times and how long lockon.exe waits for the requested data. It can also be caused by memory leaks where the program pointers get pushed beyond real address space. Its interesting to me that unmoddified (lockon tweaks) installations running missions created on unmoddified machines rarely experience this and similiar (MSCVRT.DLL) issues. Make sure your virtual memory is placed on a fast HDD (at least 7200rpm 8mb cache). Please note that the page file is not defraggable hence the procedure Prophet used above. :cool:

 

My swapfile is on a second drive, in a partition of its own - I don`t need to

shut down my VM to defrag the drive #1 (where Lockon is installed), do I?

...also, I have a "minor" problem with disconnecting from some servers.

When I click on Exit button (to go back to HL) - everything freezes and I

have to close Lockon via Task Manager. There are exceptions: never happens

on VVS 504`s server (with 20 people playing ) At first I thought it was my

firewall... but then why only on some servers? Anybody has any ideas?

Posted

Crusty, Your swapfile maybe fragmented even though the OS does everything it can to prevent this place the file in contiguous space the data inside this space can be placed all over the place within. Removing it, defragging the drive it resides on and reinitializing it as prophet indicates ensure a clean contiguous space for new pagefile data.

 

Check for Lockon.exe.local in these threads and test that with your exit problem. If it works correctly then there is a DLL mismatch between your system and the mission creators systems you are joining.

When all else fails, Eject then read the manual.

Oh, and a good wingman helps.

Posted

If this bug crash during starting a mission (in campaign or not), than it is known issue and it will be fixed in 1.11

With Best Regards!

Daniel Tuseyev

Il-2: Battle of Stalingrad and Rise Of Flight projects manager

Posted

Yep thats when i get them, completely random. Played for hours tonight, loading heaps of missions and training tracks, then boom, memory error. Glad it a known error and is being adressed.

Thanks for the great support ED.

cheers

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...