EAC Enabled will not allow my game to launch - V1.1

warmer

warmer

Well-known member
I started having this issue months ago and forgot about until I tried to join a server that required EAC enabled.

With EAC turned on I constantly get a launcher failure. This is with 1.1 and latest experiemental.

Both Fresh installs, and after verifying integrity. Does anyone know why this happens?

I used to use EAC all the time and turned it off for a mod a year or so ago, and it will never work now. I've deleted my 7days folder in my steam game slave location and my user/app data folders.

I can't understand why I can't launch this with zero mods and a brand new install with zero mods. I have tried every configuration I can think of with the launcher. All render options. Graphics jobs enabled and disabled. Native input module off. Exclusive full screen on and off. NOTHING WORKS?! EAC is the only thing keeping the game from launching and I have never used cheats on any game in my life. 
image.png

 
Last edited by a moderator:
I'm guessing it's this section of the log that is failing with all the memory allocation errors. 

[ALLOC_DEFAULT] Dual Thread Allocator
  Peak main deferred allocation count 44102
    [ALLOC_BUCKET]
      Large Block size 4.0 MB
      Used Block count 1
      Peak Allocated bytes 4.0 MB
      Failed Allocations. Bucket layout:
        16B: 1 Subsections = 1024 buckets. Failed count: 421428
        32B: 13 Subsections = 6656 buckets. Failed count: 115713
        48B: 49 Subsections = 16725 buckets. Failed count: 66669
        64B: 31 Subsections = 7936 buckets. Failed count: 59200
        80B: 149 Subsections = 30515 buckets. Failed count: 52644
        96B: 9 Subsections = 1536 buckets. Failed count: 34815
        112B: 2 Subsections = 292 buckets. Failed count: 8596
        128B: 2 Subsections = 256 buckets. Failed count: 20799
    [ALLOC_DEFAULT_MAIN]
      Peak usage frame count: [16.0 MB-32.0 MB]: 1713 frames, [32.0 MB-64.0 MB]: 6647 frames, [64.0 MB-128.0 MB]: 1 frames
      Requested Block Size 16.0 MB
      Peak Block count 5
      Peak Allocated memory 64.7 MB
      Peak Large allocation bytes 30.2 MB
    [ALLOC_DEFAULT_THREAD]
      Peak usage frame count: [8.0 MB-16.0 MB]: 61 frames, [16.0 MB-32.0 MB]: 6529 frames, [32.0 MB-64.0 MB]: 32 frames, [64.0 MB-128.0 MB]: 6 frames, [128.0 MB-256.0 MB]: 1733 frames
      Requested Block Size 16.0 MB
      Peak Block count 17
      Peak Allocated memory 230.1 MB
      Peak Large allocation bytes 135.7 MB
[ALLOC_TEMP_JOB_1_FRAME]
  Initial Block Size 2.0 MB
  Used Block Count 0
  Overflow Count (too large) 0
  Overflow Count (full) 0
[ALLOC_TEMP_JOB_2_FRAMES]
  Initial Block Size 2.0 MB
  Used Block Count 0
  Overflow Count (too large) 0
  Overflow Count (full) 0
[ALLOC_TEMP_JOB_4_FRAMES (JobTemp)]
  Initial Block Size 2.0 MB
  Used Block Count 1
  Overflow Count (too large) 1
  Overflow Count (full) 0
[ALLOC_TEMP_JOB_ASYNC (Background)]
  Initial Block Size 1.0 MB
  Used Block Count 1
  Overflow Count (too large) 0
  Overflow Count (full) 0
[ALLOC_GFX] Dual Thread Allocator
  Peak main deferred allocation count 4
    [ALLOC_BUCKET]
      Large Block size 4.0 MB
      Used Block count 1
      Peak Allocated bytes 4.0 MB
      Failed Allocations. Bucket layout:
        16B: 1 Subsections = 1024 buckets. Failed count: 421428
        32B: 13 Subsections = 6656 buckets. Failed count: 115713
        48B: 49 Subsections = 16725 buckets. Failed count: 66669
        64B: 31 Subsections = 7936 buckets. Failed count: 59200
        80B: 149 Subsections = 30515 buckets. Failed count: 52644
        96B: 9 Subsections = 1536 buckets. Failed count: 34815
        112B: 2 Subsections = 292 buckets. Failed count: 8596
        128B: 2 Subsections = 256 buckets. Failed count: 20799
    [ALLOC_GFX_MAIN]
      Peak usage frame count: [32.0 KB-64.0 KB]: 1 frames, [64.0 KB-128.0 KB]: 1713 frames, [256.0 KB-0.5 MB]: 89 frames, [0.5 MB-1.0 MB]: 358 frames, [1.0 MB-2.0 MB]: 6194 frames, [2.0 MB-4.0 MB]: 3 frames, [4.0 MB-8.0 MB]: 3 frames
      Requested Block Size 16.0 MB
      Peak Block count 1
      Peak Allocated memory 4.2 MB
      Peak Large allocation bytes 0 B
    [ALLOC_GFX_THREAD]
      Peak usage frame count: [0-1.0 KB]: 1 frames, [128.0 KB-256.0 KB]: 629 frames, [256.0 KB-0.5 MB]: 1083 frames, [1.0 MB-2.0 MB]: 2 frames, [4.0 MB-8.0 MB]: 62 frames, [8.0 MB-16.0 MB]: 6584 frames
      Requested Block Size 16.0 MB
      Peak Block count 1
      Peak Allocated memory 15.1 MB
      Peak Large allocation bytes 0 B
[ALLOC_CACHEOBJECTS] Dual Thread Allocator
  Peak main deferred allocation count 1611
    [ALLOC_BUCKET]
      Large Block size 4.0 MB
      Used Block count 1
      Peak Allocated bytes 4.0 MB
      Failed Allocations. Bucket layout:
        16B: 1 Subsections = 1024 buckets. Failed count: 421428
        32B: 13 Subsections = 6656 buckets. Failed count: 115713
        48B: 49 Subsections = 16725 buckets. Failed count: 66669
        64B: 31 Subsections = 7936 buckets. Failed count: 59200
        80B: 149 Subsections = 30515 buckets. Failed count: 52644
        96B: 9 Subsections = 1536 buckets. Failed count: 34815
        112B: 2 Subsections = 292 buckets. Failed count: 8596
        128B: 2 Subsections = 256 buckets. Failed count: 20799
    [ALLOC_CACHEOBJECTS_MAIN]
      Peak usage frame count: [32.0 MB-64.0 MB]: 8318 frames, [64.0 MB-128.0 MB]: 43 frames
      Requested Block Size 4.0 MB
      Peak Block count 24
      Peak Allocated memory 120.5 MB
      Peak Large allocation bytes 36.1 MB
    [ALLOC_CACHEOBJECTS_THREAD]
      Peak usage frame count: [128.0 KB-256.0 KB]: 1 frames, [16.0 MB-32.0 MB]: 1710 frames, [64.0 MB-128.0 MB]: 6 frames, [128.0 MB-256.0 MB]: 6644 frames
      Requested Block Size 4.0 MB
      Peak Block count 34
      Peak Allocated memory 164.0 MB
      Peak Large allocation bytes 50.2 MB
[ALLOC_TYPETREE] Dual Thread Allocator
  Peak main deferred allocation count 1
    [ALLOC_BUCKET]
      Large Block size 4.0 MB
      Used Block count 1
      Peak Allocated bytes 4.0 MB
      Failed Allocations. Bucket layout:
        16B: 1 Subsections = 1024 buckets. Failed count: 421428
        32B: 13 Subsections = 6656 buckets. Failed count: 115713
        48B: 49 Subsections = 16725 buckets. Failed count: 66669
        64B: 31 Subsections = 7936 buckets. Failed count: 59200
        80B: 149 Subsections = 30515 buckets. Failed count: 52644
        96B: 9 Subsections = 1536 buckets. Failed count: 34815
        112B: 2 Subsections = 292 buckets. Failed count: 8596
        128B: 2 Subsections = 256 buckets. Failed count: 20799
    [ALLOC_TYPETREE_MAIN]
      Peak usage frame count: [4.0 KB-8.0 KB]: 1703 frames, [8.0 KB-16.0 KB]: 6658 frames
      Requested Block Size 2.0 MB
      Peak Block count 1
      Peak Allocated memory 11.9 KB
      Peak Large allocation bytes 0 B
    [ALLOC_TYPETREE_THREAD]
      Peak usage frame count: [0-1.0 KB]: 1 frames, [2.0 KB-4.0 KB]: 1702 frames, [256.0 KB-0.5 MB]: 6 frames, [2.0 MB-4.0 MB]: 6652 frames
      Requested Block Size 2.0 MB
      Peak Block count 2
      Peak Allocated memory 3.1 MB
      Peak Large allocation bytes 0 B


---- the end of the log

 
warmer said:
https://pastebin.com/n34impWJ
link to the full file
Click to expand...
I am not sure that is the correct logs, as the startup arguments show -noeac (so EAC is disabled), can you double check that the date/time that the file was created matches the time you tried to start it without EAC?

From your previous screenshot, it looks like we need the launcher.log instead of output_log_client. It should be in the same folder location. It looks like since there's only 1 file you will need to try starting with EAC then post the log, because if you play with EAC disabled later it will overwrite that file

 
Last edited by a moderator:
Ya you are correct, that is the output log. The launcher log has very little info. I was trying to find line 740 in it, but it doesn't always create the output log. This time it didn't. Brand new install.  Completely wiped the user directories and my steamlibrary directories. Verified integrity. The ONLY thing I haven't done is go hunting for registry entries to see if that is screwing it up. This is a fairly new install of Windows, only 2 years old, so those registry entries can't be older than that.

This is the entire thing right here. I just tried now and it fail with EAC enabled. like I said I am 100% sure that it's enabled, but the output log says it's not, that is what is so confusing. What is line 740? That is the failure I suppose
 

2024-11-17 09:34:53

Orig CWD:          E:\SteamLibrary\steamapps\common\7 Days To Die
argv[0]:           E:\SteamLibrary\steamapps\common\7 Days To Die\7dLauncher.exe
App.ExeName:       E:\SteamLibrary\steamapps\common\7 Days To Die\7dLauncher.exe
GetModuleFileName: E:\SteamLibrary\steamapps\common\7 Days To Die\7dLauncher.exe

AppData: C:\Users\Jesse\AppData\Roaming

Launcher invocation: E:\SteamLibrary\steamapps\common\7 Days To Die\7dLauncher.exe
    -from-steam

From Steam: TRUE
From BPM: FALSE
On SteamDeck: FALSE

Executing: E:\SteamLibrary\steamapps\common\7 Days To Die\7DaysToDie_EAC.exe
    -force-d3d11
    -nogs
    -logfile
    C:\Users\Jesse\AppData\Roaming\7DaysToDie\logs\output_log_client__2024-11-17__09-34-53.txt

Error launching the game: EProcess: Failed to execute  : 740

 
Last edited by a moderator:
Try running steam as an admin and see what happens.  I had that fault on a different game and it ended up being an issue with my steam launch.  Not sure if this is the same solution

 
warmer said:
HOLY SH!T that was IT!
Click to expand...


Something in the background either updated and messed up settings or something tried to update and it was not a good update.

It could either have been Steam or Windows.  I believed I ended up deleting steam, running several checks in Windows Updates, and then reinstalled Steam once I got it to run properly in admin role.

 
BFT2020 said:
Something in the background either updated and messed up settings or something tried to update and it was not a good update
Click to expand...
It's a head scratcher for sure. Because I have several other games I play that use EAC and they don't require admin priv to launch. 7d2d is the only game that does. It makes sense it would be related to an update since it previously worked without admin priv. I want to say A21 didn't require admin priv, but 1.0 did. I took off EAC about a 9-10months ago for a mod. That would have been a few months before 1.0

 
You must log in or register to reply here.
Back
Top