Freezing Problem (modded game)

I decided to check out the E4X mod. The game runs fine for a while but then it starts freezing for about ten seconds at a time, with about half a second of unfrozen function then freezes again. While frozen only the cursor works but I can queue up a game pause so the moment it unfreezes it pauses. While paused I can interact with the game again, click buttons, move the map etc.

I looked in the task manager and cpu usage sits at 8.33%. Totally static. I assume the game still only utilizes 1 core (correct me if im wrong) and the cpu activity shows up on core 8. Picture here http://i.imgur.com/C0uZblh.jpg?1. As you can see the activity graph is spiking up and down well above and below 8% (if im reading it right) and there is a large amount of activity on core 7 for some reason even all the other processes are listed as being on core 0 or core 1.

 

System 
Intel Core i7-3930k @ 3.20GHz 
16GBs Corsair Vengeance DDR3 SDRAM 1600 
Nvidia GTX 980 4GB(new drivers are out, havent installed them yet.)
Windows 7 64bit up to date. 
DirectX 11 up to date 
WD Black 7200 RPM 1TB 
ASUS Rampage IV Extreme LGA 2011

 

 

6,972 views 4 replies
Reply #1 Top

That activity on Core 7 is definitely strange. While your PC is honestly better than mine, if you like you can send me the save and your mod order, and I can at least figure out if it's the game or something specific to your computer.

Reply #2 Top

Game uses 2 cores I think, one for sound/music and one for everything else....in essence, one core...that might be why you see stuff on two cores instead of just one....

Reply #3 Top

First, it's an i7, it's hyper-threaded, two virtual cores.  That's one core in your shot, not two.  The game is loading everything on the #4 core.  This is part of your performance problem, perhaps.  Sins is one of those games where hyper-threading is capable of reducing performance.

 

Unfortunately, the symptoms you describe are that of a pegged CPU, 100% utilization of a core, not 60-70%.

 

Assuming you have no such issues with the vanilla game, I'd suggest looking into the health of your install.  E4X isn't particularly resource intensive, it shouldn't run that much worse than vanilla does.  A broken file could be causing all kinds of performance hell though, data corruption could result in your symptoms.

 

If you do have similar issues, just less extreme, it could be a rather diverse array of issues, from a buggered directx install to a corrupted drive.  It's also possible you have a contributing factor resulting in your hardware inadequacy, such as an anti-virus going haywire over the game files, or an encrypted file environment.

 

Tried running in window mode?

Reply #4 Top

I'm having exactly the same problem as OP.

I'm also running E4X with E4X reworked AI and no Superweapons and some graphical mods. I've had two games where everything's smooth as daisies untill around the 2:20 hour mark it starts to freezing in rapid succession. First for a second, after that a few seconds, then longer and longer until it just hangs. When the freezes occur I can move the cursor just fine, and if I'm quick enough I can pause the game through the menu and the freezes stop until I resume the game again.

Looking at my Task Manager, the CPU hovers around 30%:

CPU
Intel Core i5 3570K @ 3.40GHz
RAM
12,0GB Dual-Channel DDR3 @ 799MHz (9-9-9-24)
Graphics
2047MB NVIDIA GeForce GTX 680

Quitting and reloading the saves with the issue has no effect. If the save happened just as the freezes were starting it picks up from there, becoming worse until it hangs or reload/quit again.

So far I've tried:

  • Disabling graphical mods
  • Lowering the graphical effects to minimum
  • Changing to windowed mode
  • Making sure I've put the mods in the correct order - First the enhanced AI and no Superweapons, then the E4X main mod, and finally Bailknights and gurkoz graphical mods below that.
  • Disabling the Stellar phenomenon DLC
  • Enable the Large Adress Aware Patch.

All with no effect.

Next up I'm going to redownload E4X and the minimods and try again.