StackAttack doesn't affect ramlib stack size.
And anyway, according to Thomas Richter, OS 3.9 don't suffer from ramlib stack issues.
quote from MMULib/Fixes/Fixes.readme
-----------------------------------------------------------------------------
RamLibFix
Fixes two bugs in the ramlib process. First of all, ramlib is too low on
stack which might cause certain problems. The mmu.library works around
this problem anyhow by swapping in its own stack, but this might be an
issue for other libraries as well. Second, ramlib uses SIGF_SINGLE as
message bit for its command message port, but the same bit has been used
for semaphore signalling. Hence, some race conditions could result if
semaphores are used in the library setup code. The bug has been reported
by Eddy Carroll (SnoopDos). Thanks, Eddy!
This program *ABSOLUTELY MUST* be copied into C:, and its name *MUST NOT
BE CHANGED*, due to the way it works.
This patch is longer required for Os 3.9.
-----------------------------------------------------------------------------
The problem looks more like some bogus library or device crashing at LIB_INIT. I'd say Warp3D, warp libs are famous for this behaviour (recursive ramlib calls). Make sure you have the latest libraries installed.
