Another Memory Access Violation Thread

Bacchatus

Version: Experimental Build 39339

Circumstances: Game crashes when I'm a specific distance away from my stranded Seamoth, or perhaps when I'm in a specific portion of the map where the Seamoth is located. (Approx -443, -35, -636) System fans spin up and the game dumps me to an error.

Steps Taken

• Removed prop items found in the Aurora from my base. (I thought this resolved the crashing, but it just stalled it. Having these items in my base did cause problems.)
• Ran Windows memory diagnostics (Passed)
• Booted to Linux emergency recovery to run full memory scan. (Passed)
• Ran DXDIAG (No issues found.)
• Renamed Subnautica32.exe to Subnautica32.exe.bak
• Scanned for unsigned drivers. Found three, which are related to old VCDist installs.
• Disabled DEP
• Set Subnautica.exe to "Run as Administrator..."
• Forced Subnautica into DX9 mode.
• Ran Subnautica.exe in Sandbox mode (Comodo Internet Security)
• Performed a clean reinstall of VC Redist (x86 and x64)
• Lowered "Water Quality" to medium
• Lowered "Quality" to "Recommended"
• Lowered "Quality" to "Minimum"
• Disable DPI scaling on high DPI settings
• Bumped the quality settings back up and enabled VSYNC
• Increased page file size to 1GB.
• Used debug command to spawn a new Seamoth in a different area of the map. Was able to board this one fine. When I got close to the original, the game crashed.
• Used entreset to reload game assets. This removed the floating props outside of my base, but still crashed when I approached the unstable Seamoth.
• PATCH WAS PUSHED OUT AFTER I DID THIS.
• Game still crashed on approaching the Seamoth.
• Tried to sneak up on the Seamoth really slowly and drowned.
• Tried to sneak up on the Seamoth a little less slowly and the game crashed.
• Gave up and just spawned in another Seamoth.

System Hardware Summary (Full Speccy output available on request)

Summary
Operating System
Windows 10 Home 64-bit
CPU
Intel Core i7 6700 @ 3.40GHz 42 °C
Skylake 14nm Technology
RAM
16.0GB Dual-Channel Unknown @ 1064MHz (15-15-15-36)
Motherboard
ASUSTeK COMPUTER INC. G20CB (LGA1151) 115 °C
Graphics
DELL S2409W (1920x1080@60Hz)
4095MB NVIDIA GeForce GTX 970 (ASUStek Computer Inc) 35 °C
Storage
1863GB TOSHIBA DT01ACA200 (SATA) 44 °C
Optical Drives
Slimtype DVD A DA8A6SH
Audio
Realtek High Definition Audio
Operating System
Windows 10 Home 64-bit
Computer type: Desktop
Windows Security Center
User Account Control (UAC) Enabled
Notify level 2 - Default
Windows Update
AutoUpdate Not configured
Windows Defender
Windows Defender Enabled
Firewall
Firewall Enabled
Display Name COMODO Firewall
Antivirus
COMODO Antivirus
Antivirus Enabled
Virus Signature Database Up to date
Windows Defender
Antivirus Disabled
Virus Signature Database Up to date
.NET Frameworks installed
v4.6 Full
v4.6 Client
v3.5 SP1
v3.0 SP2
v2.0 SP2
Internet Explorer
Version 11.321.14393.0
PowerShell
Version 5.1.14393.0
Java
Java Runtime Environment
Path C:\Program Files (x86)\Java\jre1.8.0_101\bin\java.exe
Version 8.0
Update 101
Build 13

Update: The Drama Continues

Tried to spawn a new Seamoth beside my base. The video locked, but the sounds continued in the background. Eventually, Windows killed the game process.

Bacchatus

I think if there were a way to just destroy that Seamoth, it'd be fine. Not fine, but at least that part would be resolved.

Racer1

If savegames weren't so huge, I'd suggest posting it online so others could try doing this.

Bacchatus

Racer1 wrote: »

If savegames weren't so huge, I'd suggest posting it online so others could try doing this.

That had crossed my mind as well.

I spent a little time denigrating the Seamoth's maternal lineage, just for good measure. But I still couldn't shame it into letting me close. That thing is thick-skinned.

Bah dum psh.

I suppose I'm going to have to drop out of experimental. I really only turned it on for the hydrocloric acid, but that's not even available. While I do enjoy the game, I'm bored with having to start over on new bases.