Question Page_Fault_In_Nonpaged_Area - - - win32kbase.sys ?

[iamchax]

I previously had BSOD's regarding EasyAntiCheat which I fixed using system explorer to limit the cores it used. I recently got a new one out of nowhere with the stop code Page_Fault_In_Nonpaged_Area, related to 'win32kbase.sys.' I am wondering if this is even related to EasyAntiCheat?

minidump: https://www.mediafire.com/file/igu61wwgrzbwytk/120824-17890-01.dmp/file

memory.dmp : https://www.mediafire.com/file/ipn1poyslce0slg/MEMORY.DMP/file

 

[ubuysa]

Yes, that BSOD was caused by EasyAntiCheat...

FAILURE_BUCKET_ID:  AV_R_(null)_EasyAntiCheat_EOS!unknown_function

Like all anti-cheat tools, EasyAntiCheat is a very well-known cause of BSODs, all you can do is contact them and see whether they can help. There is nothing you, or anyone else, can do, this is a problem with EasyAntiCheat - or something else on your system that EasyAntiCheat doesn't like.

 

[johnbl]

I previously had BSOD's regarding EasyAntiCheat which I fixed using system explorer to limit the cores it used. I recently got a new one out of nowhere with the stop code Page_Fault_In_Nonpaged_Area, related to 'win32kbase.sys.' I am wondering if this is even related to EasyAntiCheat?

minidump: https://www.mediafire.com/file/igu61wwgrzbwytk/120824-17890-01.dmp/file

memory.dmp : https://www.mediafire.com/file/ipn1poyslce0slg/MEMORY.DMP/file

I took a quick look at the memory dump. you have various issues with your installed drivers.

here is one you can fix very easy:
download and install Microsoft autoruns64.exe then find the entry
CorsairLLAccess64_fffff801fbe30000 CorsairLLAccess64.sys Mon Feb 5 01:17:49 2024
and delete it.
you have two copies of the same driver running from different directories
CorsairLLAccess64.sys

you might consider uninstalling or deleting all three corsair files, then installing the current version.

note: other issues with your build:
modified windows core files, old usb driver from 2010, windivert64 running
old usb drivers:
SiUSBXp.sys Thu Jul 15 15:27:13 2010
SiLib.sys Thu Jul 15 15:08:26 2010

generally usb drivers before 2012 will be broken, i would remove them using autoruns

you can repair the 3 modified windows core files using the dism.exe command:
run cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth