# Terminal Crash on Using Venting Shriek

**URL:** <https://forums.fatsharkgames.com/t/terminal-crash-on-using-venting-shriek/97407>\
**Category:** Technical Support\
**Tags:** acknowledged\
**Created:** [July 23, 2024, 8:21pm UTC](https://forums.fatsharkgames.com/t/terminal-crash-on-using-venting-shriek/97407 "2024-07-23T20:21:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cerebrophage](https://dub1.discourse-cdn.com/flex013/user_avatar/forums.fatsharkgames.com/cerebrophage/32/92210_2.png) [@Cerebrophage](https://forums.fatsharkgames.com/u/Cerebrophage)\
**Post date:** [July 23, 2024, 8:21pm UTC](https://forums.fatsharkgames.com/t/terminal-crash-on-using-venting-shriek/97407/1 "2024-07-23T20:21:35Z")

</div>

### Issue Type (Required):

Crash - During Play

### Issue Description (Required):

Using Venting SHriek on 50+ Hordes. Each time the shriek was used, we crashed to desktop. I was advised to check for [LUA] [ERROR], didn’t find any, so I thought this passed the litmus test for you guys to check out… This has only happened twice and it happened 100% of the time the conditions were identical.

### [PC] Do You Use Mods? (Optional):

Yes, and I’ve tried disabling them

### Reproduction Rate (Required):

Constant (100%)

### Player ID (Optional):

> **[Steam Community :: Cerebrophage](https://steamcommunity.com/id/youtubecerebrophage/)**

### [PC] Upload Console Log & darktide\_launcher.log (Optional):

[console-2024-07-23-03.14.11-137f4e10-bec1-4e49-bb97-6c42542052e2.log](https://forums.fatsharkgames.com/uploads/short-url/eWl4vHQaYs07LH3DCFCPlRmSxty.log) (1.98 MB)

---

<div class="post-metadata">

**Author:** ![FatsharkJulia](https://dub1.discourse-cdn.com/flex013/user_avatar/forums.fatsharkgames.com/fatsharkjulia/32/11653_2.png) [@FatsharkJulia](https://forums.fatsharkgames.com/u/FatsharkJulia)\
**Post date:** [July 24, 2024, 8:32am UTC](https://forums.fatsharkgames.com/t/terminal-crash-on-using-venting-shriek/97407/2 "2024-07-24T08:32:15Z")

</div>

Hm, the log is cut short unfortunately, which can happen if the client ends too abruptly. If you happen to encounter this crash a third time, please do share the associated log with us and we’ll have another look. I’ll share this with the QA department in the meantime.