Please check if your issue has already been reported first!

When reporting a bug, please follow the template provided, otherwise the report will be declined. The information requested is vital to allow us to correctly reproduce and then fix what you are reporting.
We have temporarily disabled Firecrackers and the Flashbang Perk due to a bug which could cause the Killer's game to crash. These will be re-enabled in an upcoming patch when the issue is resolved.

PC - Libre Hardware Monitor occasionally gets flagged by anti-cheat software (Crash)

SoraKagami
SoraKagami Member Posts: 5
edited October 2023 in Bug Reporting

To Replicate:

  1. Start Libre Hardware Monitor (LHW, v0.90) https://github.com/LibreHardwareMonitor/LibreHardwareMonitor
  2. Boot the game
  3. Play as killer or survivor in a public match
  4. On average Libre Hardware Monitor will be flagged as a "cheat" by the anti-cheat and crash the game together with LHW once every approximately 3-12 hours of gameplay.

ADDITIONAL INFORMATION

  • Character played: any
  • Perks played: any (no specific perk which causes the conflict)
  • Map: (any)
  • Frequency of the issue: once every 3-12 hour

Suggested Fix

Please Add Libre Hardware Monitor (v0.90 and v0.91+) to the anti-cheat's exceptions list. Libre Hardware Monitor (and others like Open Hardware Monitor) use the WinRing0 library for accessing hardware stats (temperatures, fan speeds etc.) which some of us need to monitor while gaming (overclocked rigs that runs hot). My guess is that the kernel-level access required by hardware monitoring software/drives (LHW/WinRing0) is the primary cause of these false detections.

From the looks of things WinRing0 for certain applications have been appropriately whitelisted (Gigabyte's overclocking software etc.). They appear to have missed Libre Hardware Monitor and maybe Open Hardware Monitor too?

I am unsure which of these two logs is the "correct" log, so uploading both just in case based on the modified time/date.

Post edited by EQWashu on
1
1 votes

Declined · Last Updated

This looks like a technical issue. If you still require assistance, please ask other forum users in the Ask the Community sub section, as we do not offer technical support on this forum.

Comments

  • SoraKagami
    SoraKagami Member Posts: 5

    Just realised I recorded the round when the crash occurred. Here's a screenshot of the error itself:


This discussion has been closed.