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
Older saves would work, but would CTD when fast traveling or after a couple minutes of play.
For me, it turns out that I didn't have enough vram due to the new SSD messing up windows' settings. I increased my paging file to 3 GB minimum and it seems to have solved my problems! No more crash and I can load my old save game.
Specs:
Win 10
Ryzen 5 3600
16 GB DDR-4 3200 (XMP profile)
GTX 1070
Samsung 980 PRO SSD
It always crashes from that one
"Starfield!agsSetDisplayMode"
line trying to write to an invalid address of "0000000000000000"
also one of the TID is running Starfield!Scaleform::System::HasMemoryLeaks"
which wouldn't be surprising as Autodesk Scaleform middleware was discontinued back in 2017. I can't find "HasMemoryLeaks" in Autodesk's docs either so maybe Bethesda added that seeing as Autodesk gave the final source code to certain customers.
I going to try to sus out what's going on focusing on
AMD GPU Services
and
Scaleform
seeing as my GPU is nVinda and CPU AMD I'll try some AMD chipset driver versions and disabling intergrated GPU functions.
If no luck there I'll see if I there is anything I can do the scaleform UI elements to see if that helps.
All shots in the dark for me though, I don't have enough experience to know what the issues is.
So you think it's a memory leak of some kind?
See what shows up for
FAILURE_BUCKET_ID:
and this area (example)
"
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff7190ae23c (Starfield!agsSetDisplayMode+0x000000000023855c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
PROCESS_NAME: Starfield.exe
WRITE_ADDRESS: 0000000000000000
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000000
"
That's a memory error problem.
Only starfield, no other stability issues with windows, other games or memtest.
Problems with the Ram are sometimes very difficult to find out. Ramtest is not very reliable.
and i think windows has its own memory diagnostic program now and its actually decent.
Same issue with either single stick or both sticks reversed.