Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
A memory location is returning an access violation, which usually happens on a memory leak (an overflow buffer exception perhaps?). Hmmm... how to ensure that a leak is blocked? I know that my Intel 5960x has overflow buffer protection built into it, but i'm sure it's configurable in the BIOS. Let me switch it off and see where I get to.
Hmm, I see. It's a bummer really, what a great concept of a game.
I've switched off No Execute Bit - buffer overflow protection temporarily to see if the CPU isn't terminating the application due to the access violation. I've also installed an older DX version (or reinstalled, it doesn't tell you if you have it already). Let's see how we get on. Running NMS now.
This is what I did:
- In BIOS, disable No Execute Bit. Which disabled the buffer overflow protection.
- Overclock CPU to 4.0Ghz and Ram to 3.0Ghz.
- Reinstall Visual C++ 2012 for Visual Studio
- Reinstall Visual C++ 2013 for Visual Studio
- Install https://www.microsoft.com/en-gb/download/details.aspx?id=8109 - which is the older version of DirectX.
- Set NMS.exe processor priority from AboveNormal to High.
I will play again and report back.