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
Ram profiles being set as high they can go sometimes triggers it
also in game settings like GPU particles can trigger if they are set to highest setting
No clue what causes it tho.
If the test does flag up faulty memory areas then you'll have verified your suspicion.
All is not lost, you don't need to buy new memory. Just tell Windows to avoid using the bad memory areas. You can use the below command to do this as I have had to use it historically.
Example Faulty Memory Addresses
0x37488CF90
0x3A28E4D2C
CMD.exe Command Prompt (As Admin)
BCDEDIT /enum {badmemory}
BCDEDIT /set {badmemory} badmemorylist 0x37488C 0x3A28E4
BCDEDIT /set badmemoryaccess no
BCDEDIT /enum {badmemory}
Reboot
I didn't use the exact full memory addresses but instead a range (in the below command), and this meant Windows wouldn't be able to see around 120-140 Mb of the RAM, but it fixed application crashed and BSOD's I was having.
BCDEDIT /set {badmemory} badmemorylist 0x37488C 0x3A28E4
Everytime I build or buy a new system, before I get into installing drivers, software and games, I perform a full memory check to avoid this kind of pain half way down the line.