Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I did and found out how.
https://en.wikipedia.org/wiki/NProtect_GameGuard
Yes; PUBG is on that list as well. And is the usual cause of this piece of crap finding its way onto your system.
As far as anti-cheat goes, it's extremely invasive. It apparently runs continuously and monitors all keyboard strokes. Which would mean it's blatant spyware.
Next to that it also indiscriminately decides to kill any process it deems suspect; or block any legit DirectX or Win32 API call it does not fancy. These can of course cause all kinds of weird compatibility problems with software other than the game it is meant to protect.
It's also a shoddy piece of work. It's tied to causing kernel memory corruptions that trigger BSODs. No doubt this is due to the same unsafe programming practices that also cause it to fail to pass the memory integrity conditions. Some versions of GameGuard also have an unpatched privilege escalation bug which allows malicious actors to gain administrator - possibly even system - level access on your machine.
If your system can handle it; I would always recommend running with memory integrity switched on. A driver which is incompatible with it is with nigh certainty written to execute dynamically built or received code. In case of anti-cheat solutions that usually means code prepared outside of the kernel by lower privilege processes, being passed to the kernel driver for execution. And that's basically: a remote code execution and privilege escalation vulnerability waiting to happen.
If a game requires such a driver to work; refund it. It is not a safe product.