Hello,
^Topic title
I had to uninstall Avast for now until it gets updated because after latest update I traced Avast as root cause for BEDaisy.sys error when launching GTA V as it was suggested in one of the forums I found. So I uninstalled Avast and game is lauching fine now. Please fix this in next Avast update.
To simulate you would have to launch GTA V from Steam and have Avast installed and running. Disabling Avast shields also didn’t solve error, only uninstalling helped.
PC Specs:
AMD FX-8370
Radeon RX580
Windows 10 Pro
Had the same issue. Only uinstall helped. Looks like Battleeye dont like avast too much. Can’t use avast anymore until fix.
1 Like
Have any of you tested the file for malware or reported to Avast as a false positive?
You could submit to test for malware here:
If clean, submit a false positive form to Avast using: Choose Your Sample Submission Type | Avast
Note: I am not an Avast Team member, just another user.
1 Like
Thanks for suggestion. I submitted false positive application without “Detection name” and “Alert Id” as Windows is crashing and Avast pop-up hasn’t appeared yet to see this info.
This file is dyanamically placed onto drive Program Files (x86) - Common Files - Battle Eye when game is launching so I suppose Avast doesn’t like something with that when system file suddenly appears or whatever.
Virus total gave me this result - VirusTotal
But interesting that when launching Red Dead Redemption 2 which also places this file into the same location on startup, Windows doesn’t crash with Avast being active.
But other games with same Battle Eye anticheat also crash after my initial searches.
Anyway strangest part still is, as I mentioned, that disabling shields doesn’t help (in that moment Avast shouldn’t scan anything for new threats) but only uninstalling helps.