GFAC and Easy Anti cheat causes Blue screen of death

[Victoria97 53]

@MageLO
Ok so am I the only one with this sudden problem or there are other people experiencing this annoying thing as well?
After researching almost entire day, re installing APB entirely, re installing GFAC and clicking repairs like crazy the issue persist.
Each time I try to start APB it gives me Blue screen of death (BSOD) with the error messages

Stop code: PAGE_FAULT_IN_NONPAGED_AREA

What failed: GFAC_Sys_x64.sys

 

I did next steps:

1) I ran commands in cmd sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth

2)I ran mdsched.exe

3) I white listed both GFAC and EAC in my anti virus and firewall
4) I disabled Deep Behavior Inspection temporarily
5) I re installed EAC

My event log confirmed next:
“LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard. PackageName: negoexts.”

and also mentions “Virtualization Based Security for Credential Guard auto enablement status.”

These refer to Windows’ security subsystem (LSA — Local Security Authority) and VBS (Virtualization-Based Security).

Now, I know that Easy Anti-Cheat (EAC) operates very close to kernel level, the same privileged layer that Credential Guard and VBS use.
So when LSA / Credential Guard report signature or compatibility issues, it often means EAC tried to hook into protected memory, which Windows 11’s security system blocked or crashed instead of allowing.

That fits perfectly with my BugCheck 0x50 PAGE_FAULT_IN_NONPAGED_AREA.

 

Am I on the good track? 
My question is also why is Easy Anti-Cheat still coming with APB install package? If we all agreed to use GFAC? 
Are there any players here experiencing this same error?

 

[Westford 196]

1 hour ago, Victoria97 said:

@MageLO
Ok so am I the only one with this sudden problem or there are other people experiencing this annoying thing as well?
After researching almost entire day, re installing APB entirely, re installing GFAC and clicking repairs like crazy the issue persist.
Each time I try to start APB it gives me Blue screen of death (BSOD) with the error messages

Stop code: PAGE_FAULT_IN_NONPAGED_AREA

What failed: GFAC_Sys_x64.sys

 

I did next steps:

1) I ran commands in cmd sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth

2)I ran mdsched.exe

3) I white listed both GFAC and EAC in my anti virus and firewall
4) I disabled Deep Behavior Inspection temporarily
5) I re installed EAC

My event log confirmed next:
“LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard. PackageName: negoexts.”

and also mentions “Virtualization Based Security for Credential Guard auto enablement status.”

These refer to Windows’ security subsystem (LSA — Local Security Authority) and VBS (Virtualization-Based Security).

Now, I know that Easy Anti-Cheat (EAC) operates very close to kernel level, the same privileged layer that Credential Guard and VBS use.
So when LSA / Credential Guard report signature or compatibility issues, it often means EAC tried to hook into protected memory, which Windows 11’s security system blocked or crashed instead of allowing.

That fits perfectly with my BugCheck 0x50 PAGE_FAULT_IN_NONPAGED_AREA.

 

Am I on the good track? 
My question is also why is Easy Anti-Cheat still coming with APB install package? If we all agreed to use GFAC? 
Are there any players here experiencing this same error?

 

You are not the only one.

 

I too spent a few days troubleshooting, reinstalling, ran Memory Checker, sfcannow, disabled anti-virus,  only to be greeted with the 

BSOD - 

Stop code: PAGE_FAULT_IN_NONPAGED_AREA

What failed: GFAC_Sys_x64.sys

 

Many people on LO Discord commented on this same issue.

It appears to be a discrepancy with GFAC file versioning that has/is being deployed.

 

11 hours ago, Westford said:

I wanted to share my latest email I submitted to LO support for my support ticket I opened

on Sept 26 concerning the GFAC error's, and the inability to launch the game.

 

 

__________________________________________________________________________________________________________________________________

Some interesting information to share.

 

I was discussing this GFAC issue with another APB player on 

Little Orbit's Discord, and they mention that I need to get a working copy of the following 

two files;

 

GFAC.dll - 997.68k

GFAC_Sys_x64.sys - 2.11MB

 

I looked at the file size of those two files in my C:\Program Files\GFAC, 

and there are as follows;

 

GFAC.dll - 999k

GFAC_Sys_x64.sys - 2.11MB

I re-downloaded the GFAC.dll from the "manifest.json" URL you sent me.

https://gfac.gamersfirst.com/updates/0.5.1.28/GFAC.dll

 

And the file size again for GFAC.dll was 999k.

 

So the person on the Discord channel has a different version of the GFAC.dll, 

than I do, and his game is working.

__________________________________________________________________________________________________________________________________

 

 

So it appears that for that individual on Discord that is not having a problem launching the game, 

he has a different version of the GFAC.dll than I have.

 

The full manifest to manually download the files that LO support provided for me is here.

 

https://gfac.gamersfirst.com/stable/manifest.json

 

 

I understand the dev team is working on this, and is having a difficult time chasing this down.

I hope they have made some progress, and will be releasing a patch release for GFAC soon.

 

 

 

LO has been pretty quite so far concerning this issue, the last official word was posted last Thursday by MageLO.

 

Some comments from Discord is there is a noticeable drop in population since the GFAC 1.0 release.

 

Is this because a fair portion of players are experiencing the same issue with GFAC (BSOD)  and cannot start the game, 

as apposed to the initial thought that only a "handful of players" are having this issue ?

 

Or...

 

Is the GFAC 1.0 release that effective, and many players that did not support fair gameplay gave up their cheating ways

and just left the game ?

 

For me, and I am sure quite a few others, have not been able to launch the game for over 2 weeks.

I have exhausted all troubleshooting methods that I have available to me, and will wait patiently for LO to provide a fix.

 

 

[Yapopal 208]

You are not alone in your problem. You're just the only ones who are looking for a solution with such tenacity.
The administration should roll back the client version to stable and then resolve the issue. 
I am surprised by the loyalty of the community to this company of fans of poles and bicycle wheels.

[Victoria97 53]

10 hours ago, Westford said:

I was discussing this GFAC issue with another APB player on 

Little Orbit's Discord, and they mention that I need to get a working copy of the following 

two files;

 

GFAC.dll - 997.68k

GFAC_Sys_x64.sys - 2.11MB

 

I looked at the file size of those two files in my C:\Program Files\GFAC, 

and there are as follows;

 

GFAC.dll - 999k

GFAC_Sys_x64.sys - 2.11MB

Did you perhaps come into possession of those different sizes of these 2 files? If you did, please upload it on some free uploading site and send me the link to download them.

 

10 hours ago, Westford said:

Is this because a fair portion of players are experiencing the same issue with GFAC (BSOD)  and cannot start the game, 

as apposed to the initial thought that only a "handful of players" are having this issue ?

 

Or...

 

Is the GFAC 1.0 release that effective, and many players that did not support fair gameplay gave up their cheating ways

and just left the game ?

I think its sooner the first than the latter. Because hackers who systematically cheat and hack in APB entire decade didn't care for Battle-eye, nor EAC, and they surely wont care for GFAC. Its usually premium hacks they pay on monthly basis which are hard to detect.

If the sudden pop drop is after releasing GFAC 1.0 then logical conclusion is that this was the anomaly that keeps players away from APB. Like me and you.

The good news in this bad news is that I am not only one with this error. I was afraid that I am special like always in APB regarding every single error there possibly can be. I had it. It always attacks exactly my laptop lol. I have had issues from day one with GFAC but then they deployed fix and it worked flawlessly all until this monday when after longer time being offline I returned to APB and experienced first error after lobby when I tried to login with my char. At that point I got message that GFAC is not working and restarting APB will fix the problem. "Shockingly" as expected it didn't.
I restarted like 30 times to no avail.
Then I started to play and troubleshoot it deeply, adding anti-virus white list to GFAC, to APB...even went editing some group policies. 
After 200 steps I did (half of which I already forgot what I changed) I started to get BSOD with exactly .sys file. 
No app aka executable file should EVER be able to bring down my entire OS to complete restart of the system.
Meaning GFAC is putting its nose into the kernel memory sections where its not suppose to even be at. Windows knows it and therefore we have this problem. 
Most important thing to me was that @MageLO and support team is aware of this issue so that they can start working on it asap. Or like you said simply re-roll back to previous version which obviously worked for everyone. 
What I cannot stand in situations like these is the silence and ignore from only people who has power to change this. 

You said that Magelo addressed this issue somewhere last thursday? Can you please copy paste me here what he said regarding this?

[Victoria97 53]

2 hours ago, Yapopal said:

You are not alone in your problem. You're just the only ones who are looking for a solution with such tenacity.
The administration should roll back the client version to stable and then resolve the issue. 
I am surprised by the loyalty of the community to this company of fans of poles and bicycle wheels.

Usually when things suppose to work by all means but they don't I get this obsessive urge to find a solution asap.
I agree that they should roll black to previous version.
I am sad that you got identical problem but in same time I am happy because I know now that I am not alone in this.

At this point after decade of playing APB, I wouldn't call it loyalty anymore, I would call it an addiction lol