Jump to content

Search the Community

Showing results for tags 'gfac'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • GamersFirst Community
    • Announcements
    • GamersFirst Feedback
    • Articles
  • APB Reloaded
    • OPEN BETA
    • Announcements & Server news
    • Social District (General Discussion)
    • Community Corner
    • Bugs and Tech Issues
    • Game & Forum Suggestions
    • OTW general
    • Off-Topic Section
  • Fallen Earth
    • News & Announcements
    • General Discussion
    • Community Creations
    • New Player FAQs and Guides
    • Bugs and Tech Issues
    • Events
    • Feedback and Suggestions
    • Off-Topic Section
  • Unsung Story
    • News & Announcements
    • General Discussion
    • ​​​​​​​Help and Questions
    • Feedback & Suggestions 
    • Introductions 
    • Offtopic
  • Ships That Fight Underground
    • News & Announcements
    • General Discussion
    • Guides, Tips and Strategy
    • Game & Forum Suggestions
    • Communities & Promotions
    • Creations and Fan Art
    • Bugs and Tech Issues
    • Off-Topic Section

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 1 result

  1. @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?
×
×
  • Create New...