Troubleshooting Help:

 

What is your parts list?

CPU: AMD Ryzen 9 7950x

Cooler: Corsair H115i RGB PRO XT

Motherboard: ASRock X670E Taichi

RAM: G.Skill Trident Z5 DDR5-6000 SL C32 DC - 64GB

GPU: XFX SPEEDSTER MERC 310 Radeon RX 7900 XTX

NVMe: Samsung 980 PRO 1 TB

NVMe: WD_BLACK SN750 1TB

NVMe: Corsair MP400 1TB

SSD: SanDisk Ultra 3D 2 TB

SSD: Samsung SATA 870 QVO 4TB

SSD: Samsung SATA 860 QVO 1TB

SSD: Samsung SATA 860 QVO 1TB

HDD: Seagate Barracuda 2TB

PSU: be quiet! Straight Power 11 Platinum 1200W

Case: Corsair 7000D AIRFLOW

OS: Arch Linux

 

Describe your problem. List any error messages and symptoms. Be descriptive.

My PC shuts down shortly after the Unreal Engine logo when starting Hell Let Loose. I already found out that this doesn’t happen when using a fresh install of the game. It only happens after the second time of starting it. I didn’t change any settings between the first and the second launch of the game.

 

journalctl doesn’t show any logs related to my issue.

 

The PC just turns off like someone had pulled it’s power plug. After that, it won’t turn on for some time. Unplugging the power cord for ~2 minutes gets it to turn back on again. Unplugging for ~1 minute doesn’t fix the issue.

 

Every other game is fine, running CPU and GPU at 100% for extended periods of time is fine. This only happens with Hell Let Loose and only after the second time of launching the game.

 

My motherboard has two buttons for power and reset, normally those are lit when the PC is turned off. When I trigger my issue, those LED’s aren’t lit.

 

My temperatures are totally fine, there isn’t much dust built up inside the PC. The whole system is a little over a year old.

 

List anything you’ve done in attempt to diagnose or fix the problem.

System is up to date, including BIOS, Kernel and all packages. I stress tested CPU and GPU separately and at the same time, my issue didn’t appear.

 

Alright, that’s all the details I have until now. Does anyone know what could be the cause for this? Thank you very much in advance.

 

EDIT: Thank you everyone, I’ve decided to replace my PSU. I’ve generally been quite unsatisfied with be quiet! (their fans also kinda suck). I Will report back if that fixes my issue.

 

EDIT 2: Replacing my PSU fixed my issue. Never buying from be quiet! again.

  • elgordio@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    11 months ago

    You could try reducing your power load by temporarily disconnecting any drives you don’t need to run the game, and if your ram is 4 sticks then going to 2.

    If the game then works you’d know it was a power issue.

    • naught@sh.itjust.works
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      11 months ago

      That is not going to reduce power significantly right? If anything, underclockimg cpu and gpu is far easier to do (in software!) with a more definite solution. If you remove ram, perhaps it was a faulty stick instead of power consumption etc. Drives hardly take any power anyway

    • statue7559@lemmy.sdf.orgOP
      link
      fedilink
      arrow-up
      2
      arrow-down
      2
      ·
      edit-2
      11 months ago

      Running games with 100% GPU load for hours doesn’t trigger my issue. Reencoding a video with all CPU cores while running a game doesn’t trigger it either. It’s just Hell Let Loose that causes it to turn off and only after the second launch of the game since reinstalling it. When using a fresh install and playing for hours I don’t encounter any issues. Restarting the game once after that triggers my issue.

      • elgordio@kbin.social
        link
        fedilink
        arrow-up
        2
        ·
        11 months ago

        Maybe the first time it’s run it’s compiling shaders for a while, might explain why it’s different behavior the second time? If the game has a shader cache and you can find it, delete the cache after the first run and see if it still does it on the next run.

        Your system is clearly capable of running 100% but maybe He’ll Let Loose is triggering some spike that the PSU thinks is a potential fault and trips?