[ INFO ] Slowdown / crash problems on 4GB RAM systems

Ask here if you experience technical problems with X Rebirth.

Moderator: Moderators for English X Forum

donzi
Posts: 1258
Joined: Mon, 12. Feb 07, 14:29
x4

[ INFO ] Slowdown / crash problems on 4GB RAM systems

Post by donzi »

CONCLUSION
Removed a bunch of useless dxdiag info.. the bottom line is that the game requires "Available OS Memory: 4096MB RAM" -- 4095 won't do.

This technically is stated. And if this is your problem then you too can feel like a noob like me. ;-)

My system uses a small amount of ram to suppliment the descrete ram the video adapter has. This is enough to cause all the problems as I'd mentioned below.

So, if you have a similar system you may be able to disable using main ram by your integrated video adapter via your UEFI or BIOS interface.

If you have an apple then, well... I am sending some marines to see if they can break into the UEFI on my iMac..

Otherwise you'll find the cure for the problems below by adding a second 4GiB module to the Mac.

FWIW: I have been playing with the help of a utility called CleamMem for a couple days and it has helped for my particular configuration (4G RAM total w/ a small amount of that being used for integrated video). Eventually the game will still begin to show signs of slowdown but I've played some 6-8 hours with CleanMem being triggered every 15 mins. Without this, if I was doing a lot of station roaming (playing smalltalk) I'd have probably needed to restart the game 1-3 times an hour to keep things working smooth.

link: http://www.pcwintech.com/cleanmem





Hello,
since the latest release I've been observing predicatable degredation of the ability to play the game. Below you'll find the SOP info and so forth.

- playing version 3.50.0.0 campaign in english
- no bonus content, workshop, etc -- vanilla game as was installed by free weekend
- steam overlay enabled
- steam cloud disabled for game
- was some 3 hours into a playing session
- had not used steam overlay or its features
- had not alt-tabbed from game
- game settings 1280x720, all other settings off or low except radar = high

additional notes, resources and tests below..

A bit of additional info maybe in my original posts here

game decay - ongoing iMac issue

Consistently reproducable degredation of playability (temporaily relieved by game exit and restart, wash rise repeat) appears to be by docking and roaming.

Space travel may eventually decay also, but usually it remains better than station roaming, which will decay to the point where it's not possible to properly naviagte or play the smalltalk game.

I am thinking that somehow the game is breaching the shared ram that the video adapter is allocated on the 4GiB RAM machine. On the other where there is 8GiB RAM and also a similar video with dedicated and shared memory, it seems memory management is being handled differently, correctly? I don't rightly know but the process of elimination seems to indicate a problem or difference in how the 4GiB system is being used vs the 8GiB system by the 64-bit game.

I could buy a 4GiB module for the imac but I hate to put any money into this POS beyond what apple got from me.

tests - second machine and 32-bit xrebirth
I have spent 2-3 hours testing a couple variations

A) the x64 xrebirth on a macbook pro with 8GiB ram, pretty much similar configuration to iMac although the MBP has slightly older ATI drivers fwiw.
- same game version, no DLC
- resolution 1920x1200
- varied quality from ultra to medium
- multiple checks during play process pvt bytes always hovering ~2.5GiB
- continuous docking and station roaming among other things using one of the existing game saves.
- never witnesses playability decay with need to restart the game
- MBP dxdiag 64-bit below..

B) original machine as dxdiag below using the xrebirth v2.51 32-bit
- fresh game
- same settings as used on iMac with 64-bit game
- continuous station docking and station roaming since start, some 20-30?
- periodic process check showed ~3.2GiB pvt bytes
- game never decayed to unplayability and station roaming and ship cockpit entry exit remains mostly smooth with full detail and animation

crash - random iMac issue
X rebirth froze while I was roaming around a station. This was the first lockup I've seen like this in some 30 hours since the free weekend and my subsequent purchase.

- used windows key to get taskbar as alt-tab was acting poorly
- rmb on taskbar to get windows task manager
- stopped unresponding xrebirth application
- process xrebirth.exe run by my user (admin) account would not terminate
- executed process hacker to examine other factors
- xrebirth process showing 3.75GiB + private memory depending on tool
+ note that I have seen pvt bytes as high as ~4.5GiB but never froze. above figure is specific to this catastrophic failure case..
- created windows task manager dump file for xrebirth.exe process
- exit steam or overlay process unresponsive
- terminated steam.exe process and tree
- created dump with process hacker
- tried more way to kill pid for rebirth.exe w/o success
- logged user out and watched normal processes ending
- logged user back in
- xrebirth.exe process still running (!) as my user with slightly less mem use
- shutdown windows
- machine would not respond to soft power switch to restart system, fwiw
- un-plugged AC power and re-plugged after a couple secs
- power switch turned on system as expected, logged in etc
- rebirth.exe process no longer running as expected. :-)

dumps - from crash above
I've two dumps from the wierd crash outlined above. If you'd like them to examine I can make them available. Presently each dump is compressed to ~900M .RAR file. One from preocess hacker and one from ms task manager.

I dug through the event logs and found nothing pertinent to the crash.

Although I am not going to rule out a problem somehow with the iMac, I have no reason to suspect it being at fault. I regulalry play a huge array of games old and new on this and frankly this is the first time in a long while that I've seen any problems running something from my library of games.

With any luck, the info here or the dumps will lead to killing an elusive bug that has yet to be isolated within the product.

Thanks!


dxdiag 64-bit output - 4GiB iMac

Code: Select all

------------------
System Information
------------------
Time of this report: 3/16/2015, 07:19:13
       Machine name: APLPOS1
   Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.150113-1808)
           Language: English (Regional Setting: English)
System Manufacturer: Apple Inc.
       System Model: iMac12,1
               BIOS: Default System BIOS
          Processor: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz (4 CPUs), ~2.5GHz
             Memory: 4096MB RAM
Available OS Memory: 4072MB RAM
          Page File: 960MB used, 7205MB available

..snip

---------------
Display Devices
---------------
          Card name: AMD Radeon HD 6750M
       Manufacturer: Advanced Micro Devices, Inc.
          Chip type: AMD Radeon Graphics Processor (0x6741)
           DAC type: Internal DAC(400MHz)
         Device Key: Enum\PCI\VEN_1002&DEV_6741&SUBSYS_6741106B&REV_00
     Display Memory: 2281 MB
   Dedicated Memory: 501 MB
      Shared Memory: 1780 MB

..snip
dxdiag 64-bit output - 8GiB MBP

Code: Select all

------------------
System Information
------------------
Time of this report: 3/16/2015, 19:10:08
       Machine name: APLPOS2
   Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.150113-1808)
           Language: English (Regional Setting: English)
System Manufacturer: Apple Inc.
       System Model: MacBookPro8,3
               BIOS: Default System BIOS
          Processor: Intel(R) Core(TM) i7-2860QM CPU @ 2.50GHz (8 CPUs), ~2.5GHz
             Memory: 8192MB RAM
Available OS Memory: 8102MB RAM

..snip

---------------
Display Devices
---------------
          Card name: AMD Radeon HD 6770M
       Manufacturer: ATI Technologies Inc.
          Chip type: ATI display adapter (0x6740)
           DAC type: Internal DAC(400MHz)
         Device Key: Enum\PCI\VEN_1002&DEV_6740&SUBSYS_00F9106B&REV_00
     Display Memory: 707 MB
   Dedicated Memory: 1008 MB
      Shared Memory: 3795 MB

..snip
Last edited by donzi on Sun, 22. Mar 15, 14:25, edited 4 times in total.
CBJ
EGOSOFT
EGOSOFT
Posts: 54300
Joined: Tue, 29. Apr 03, 00:56
x4

Post by CBJ »

The game cannot "breach" the memory allocations defined by Windows. If you are using a shared-memory graphics card on a system with only 4GB, the absolute minimum memory requirement for the game, then of course it's going to struggle. This will be more noticeable over time during a given play session because the game caches data in memory to avoid constantly loading it from disk. Testing against the 32-bit version doesn't really contribute much; it uses a little less memory to start with but has an absolute hard limit of 4GB (minus the graphics card memory) after which it will simply crash rather than slowing down.
donzi
Posts: 1258
Joined: Mon, 12. Feb 07, 14:29
x4

Post by donzi »

Hi CBJ,

rats! thank you for setting me straight. Here I thought the little marine buggers were boarding my shared ram space and causing havok.

Time to try and send my own marines into the uefi and see what I can do.

Seems my previous message hit a limit too. Didn't notice that in the preview.. gonna trim out the dxdiags since they're long and moot now.

Return to “X Rebirth - Technical Support”