Original Post — Direct link
when i que ranked, unranked or casual (online games) i at different times get kicked, either in que or mid game with the messaage (connection failiure, the attempt to connect the server failed) and other times i get another fail code wit h the same things happening, i get kicked message: ( removed from match, u have bin kicked out by battle eye, reason corrupted memory)
this happend 2 days ago, all other games work


so therefore i have tried to fix it by:
deleting and reeinstalling battle eye as admin.
Different ram bricks
reeinstalled siege on default way and with revo unninstaller
booted my hole pc again on windows
edited properties on (be service x64) i edited it to run as windows 7 as i saw that to be the best on internet
set max fps to 200 in game files
set UseProxyAutoDiscovery=0 to UseProxyAutoDiscovery=1
validated game files through steam on r6



i have had so many problems on r6 the last year...
over 3 years ago - Ubi-Orion - Direct link
Originally Posted by BluDog.SET
when i que ranked, unranked or casual (online games) i at different times get kicked, either in que or mid game with the messaage (connection failiure, the attempt to connect the server failed) and other times i get another fail code wit h the same things happening, i get kicked message: ( removed from match, u have bin kicked out by battle eye, reason corrupted memory)
this happend 2 days ago, all other games work


so therefore i have tried to fix it by:
deleting and reeinstalling battle eye as admin.
Different ram bricks
reeinstalled siege on default way and with revo unninstaller
booted my hole pc again on windows
edited properties on (be service x64) i edited it to run as windows 7 as i saw that to be the best on internet
set max fps to 200 in game files
set UseProxyAutoDiscovery=0 to UseProxyAutoDiscovery=1
validated game files through steam on r6



i have had so many problems on r6 the last year...
Hey there.

Do you have MSI SDK and MSI Dragon Center installed? We are aware of reports that a recent update to those has caused a great deal more instances of this particular error. Please try uninstalling those and then see if the issue persists. We're also aware that if this isn't the case that updating Windows to the latest version has also helped.

If after both of these you're still experiencing this issue please let us know. Thanks!