In this case I'll ask that you contact EVGA technical support. 

KuntryBoy
Hello forum,
 
After several hours of research and several clean installs of Windows 20H2 installs I've come here. I've finally figured out what's causing me so much headache. I updated Windows 10 1909 to version 20H2 because my system seemed to fail to update past 1909. No errors in Windows updates yet it would never update to version 2004 or 20H2. I also started having issues with the computer entering sleep mode automatically. So I did a clean install. It updated to 20H2.
 
First install I had all networking disconnected and I manually installed the EVGA Z97 Classified Motherboard drivers. Installing the Intel ME driver immediately BSOD the computer forcing recovery and repair options. Unable to get out of a BSOD loop I had to reinstall Windows again. After doing this several times I tried connecting ethernet during the installation... Windows starts doing updates in the background during the installation process and in the middle of it... BSOD! So I assume it was trying to automatically get a driver for this Intel Management Engine Interface during updates.
 
I finally got a stable install by disabling networking during installation, installing all other drivers and then connecting to network... still got a BSOD but the computer went into recovery and actually started up. I was given a message saying some updates were postponed. I did all Windows updates installed all of my programs etc. Did a system image backup since this was about the 10th time I tried installing Windows. Well... I went into device manager to look and sure enough Intel Management Engine was yellow banged under "other devices". Any attempt to click and update it in device manager, uninstall it and restart, or run the EVGA Intel ME driver setup would BSOD the computer causing a hard reset into recovery mode. Or fatal error and then have to reinstall Windows again.
 
So... what's the answer to the riddle? The BIOS. I have the latest BIOS installed... version 2.06. It's supposed to be for security etc. However with Windows 10 20H2 running the latest BIOS there's no way I could figure out how to install the Intel MEI without a BSOD. I even reinstalled the BIOS from USB. I flipped the BIOS switch in my motherboard to the base BIOS 1.0X and it will successfully boot. I was also able to install the Intel ME with no issue while using that bios. What's wrong with that? Well it's not the latest patched BIOS that's supposed to be for security for the processor etc. Also, switching back to BIOS 1 with 2.06 causes a BSOD even after successfully installing the Intel MEI under the base BIOS. 
 
So... EVGA I know this is older hardware but there's a problem here and I'm not the only one who has it... There needs to be a BIOS update for these motherboards. 

I believe you need to update the intel ME firmware on your board. Not the Intel Management Engine, but the actual board firmware.
You should find the version you need and the instructions here:
https://www.win-raid.com/...irmware-and-Tools.html

I just submitted a ticket ( I believe lol ) Wanted to confirm I'm having this issue on the Z97 FTW board, Havent tested audio as it goes through the display port cable on my GPU. I was able to update to 20h2 by disabling the device in device manager but now it looks like windows update is trying to update the driver for intel ME and is now bluescreening if I don't disable windows update entirely, so watch out for the "intel" driver that pops up in there. This is all just a mess... I really hope we hear something back from them... the 4790k I have in mine is still more than capable for what I do.

I reverted back to bios 1.07 and the system booted right up, new intel ME drivers via windows update installed and the device enabled in device manager. This appears to be some sort of bios issue.. I heard back from EVGA support today with no useful information. They told me to reset the cmos and try sfc /scannow via CMD recovery, all options that were already tried. Then they tried to blame my RAM or HDD. I mentioned these threads but it doesnt seem like they listened or cared. Shame really, cant say I would go with an EVGA product again after this. Guess for now Im stuck on an outdated bios. Havent tried legacy mode but intend to just for curiosities sake 

So, I don't normally respond back to any of the threads like this. But after spending a few days trying to figure this problem out, I found a solution which was incredibly simple and got me to a booted state. Backstory that got me here:
 
Fresh install of win10
Was running fine, until the BSOD "PAGE_FAULT_IN_NONPAGED_AREA" (which everything says it's bad RAM, but I knew it wasn't)
Ran SFC, DISM, chkdsk, etc, etc, etc. 
Srttrail.log file said no hard drive found in the WinRE command line, but I was accessing the file FROM the HDD that it said wasn't there... Rabbit hole.
Used windbg.exe to finally find the BSODs were from a driver called "teedriverw8x64", which led me to the IMEI issue. I noticed issues in my device manager immediately prior to all this happening, so I was fairly certain this was the cause. 
 
Resolution to get to boot:
In the WinRE command line, if your main drive is C:\,  :
move C:\Windows\System32\teedriverw8x64.sys C:\
ren C:\teedriverw8x64.sys teedriverw8x64.sys.bak
 
And that's it. Restarted and it booted right up. This resolution to get back to the desktop was much, much easier than anything else I had found and it worked first try. You might not even have to rename the file, but knowing C:\ can sometimes be in PATH, Windows might have still found it there. You might just be able to rename it inside the drivers folder, but I moved it just in case it was doing a regex check or similar to verify the file was there. Anyway, hopefully this helps. Good luck. 

I don't know if anyone is still having this issue (BSOD error of a page fault in a non paged area), but I spent many days trying to figure out the issue. I tried disabling the IME like everyone suggested when it popped up on Device Manager, but that was only a temporary reprieve from the BSOD. After swapping out video cards, removing sound cards, doing multiple fresh installs of Windows 20H2, and multiple SFC scans, I remembered that the mobo had multiple BIOS loads controlled by a dip switch. I was on BIOS position 3 (v2.06). I changed the dip switch to position 1 (v1.01) and everything loaded with no BSOD. I have since reverted dip switch position 3 (v1.07) and everything is working fine and is stable. BIOS v1.07 is the latest BIOS that was intended for Windows Vista/7 but it's been stable for the last 3-4 weeks. I have been able to install Windows 10 Pro 21H1, it has been able to update with all the latest Windows updates, and I have not had any BSOD errors at all. I haven't tried to move onto BIOS version 2.XX because that's when Windows 10 starts to be supported and I simply don't have the time to troubleshoot anymore.
 
FIX: Rollback BIOS to v1.xx - I currently use v1.07 but have also been successful on v1.01

I started having stability issues a couple days after the last post, of course. No BSOD, but the computer just locks up in the middle of a game. I've only noticed it happening when gaming, but I don't do much else but game on the computer. I have to hard power cycle it with a long press the power button to get it to reboot. A couple weeks ago I found v1.08 on the Australian EVGA download site but I get the same results. Locking up in the middle of gaming. This was a 2014 build, so I guess it lasted me a while. I'm probably going to end up just building or buying a new rig this winter. The most frustrating part is that before 20H2 my current set-up could still play any of the games I like at the highest settings (GTA5, Warzone, WoT, etc.).  

BiggyNewton
Bit late to this thread but have you guys tried just disabling Intel ME in device manager and seeing if the bsods go away?

I came up with a similar solution on my end, but had to take it a step further. For reference, I have an i7-4790k and an EVGA Z97 FTW, and am currently running Windows 10 Pro, 21H1 with no issues.
 
Even if I uninstalled the device/drivers (TeeDriverW8x64.sys) that triggered the BSOD (PAGE_FAULT_IN_NONPAGED_AREA) Windows Update would incessantly read it as a missing / out of date driver and automatically try to reinstall the faulty drivers, instantly triggering the BSOD again. One solution would have been to just totally disable Windows from auto-installing all devices/drivers, but for critical drivers like this, it did not seem to care, and for the most part it is convenient to leave this on (to me anyway).
 
So what I ended up doing was changing a Group Policy setting that restricts installation for this particular Intel ME device.
 
First thing I did was go into Device Manager to find the Hardware ID. Without proper drivers installed, the Intel ME device just shows up under "Other Devices" using the "PCI Simple Communications Controller" driver. To find the Hardware ID: Right-click the device > "Properties" > "Details" > Change the "Property" dropdown to "Hardware Ids". Under the "Values" section it will show all of the relevant Hardware Ids for it; we want the one that includes the Vendor, Device, and Subsystem Ids: "PCI\VEN_8086&DEV_8CBA&SUBSYS_103C3842". Copy that value; we will paste it elsewhere in a minute.
 
Next, we open gpedit.msc (Group Policy Editor). This requires Windows 10 Pro or above; there may be a Registry version of this workaround for Home users, but I have not looked into it. In GPEdit, in the left panel, we need to go to the following setting: "Computer Configuration" > "Administrative Templates" > "System" > "Device Installation" > "Device Installation Restrictions". Upon selecting the "Device Installation Restrictions" template, a bunch of settings will appear in the window to the right. We are looking for "Prevent installation of devices that match any of these device IDs". Double-click it or right-click it and select "Edit".
 
Once in the "Prevent installation of devices that match any of these device IDs" setting, at the top left, we will see by default it is set to "Not Configured". We want to change this to "Enabled". Once it is enabled, in the "Options" pane at the bottom of the same window, there should be an options that reads "Prevent installation of device that match any of these Device IDs" with a "Show..." button. Click the "Show..." button. This will bring up a list of the restricted devices (it is currently empty). Here is where we can enter/paste the device ID we copied earlier from Device Manager. So now there should be a field in here with its "Value" set to "PCI\VEN_8086&DEV_8CBA&SUBSYS_103C3842". Click "OK" after entering the Device ID and then click "Apply" on the setting window.  This will restrict installation of any device that matches this ID (the Intel ME and its driver TeeDriverW8x64.sys).
 
YMMV, but this is literally the only thing keeping my system from constantly BSOD'ing due to this faulty driver in Windows 10. At one point before figuring out this workaround, I even had to fully re-install Windows because I could not get it to boot or recover without instantly blue screening with the "PAGE_FAULT_IN_NONPAGED_AREA". After inspecting the dump files, I found it it was this driver (TeeDriverW8x64.sys). When I was reinstalling Windows, I actually had to disconnect my PC from the Internet to prevent Windows from trying to automatically install this as part of the initial updates.

LithiumThunder

BiggyNewton
Bit late to this thread but have you guys tried just disabling Intel ME in device manager and seeing if the bsods go away?

I came up with a similar solution on my end, but had to take it a step further. For reference, I have an i7-4790k and an EVGA Z97 FTW, and am currently running Windows 10 Pro, 21H1 with no issues.
 
Even if I uninstalled the device/drivers (TeeDriverW8x64.sys) that triggered the BSOD (PAGE_FAULT_IN_NONPAGED_AREA) Windows Update would incessantly read it as a missing / out of date driver and automatically try to reinstall the faulty drivers, instantly triggering the BSOD again. One solution would have been to just totally disable Windows from auto-installing all devices/drivers, but for critical drivers like this, it did not seem to care, and for the most part it is convenient to leave this on (to me anyway).
 
So what I ended up doing was changing a Group Policy setting that restricts installation for this particular Intel ME device.
 
First thing I did was go into Device Manager to find the Hardware ID. Without proper drivers installed, the Intel ME device just shows up under "Other Devices" using the "PCI Simple Communications Controller" driver. To find the Hardware ID: Right-click the device > "Properties" > "Details" > Change the "Property" dropdown to "Hardware Ids". Under the "Values" section it will show all of the relevant Hardware Ids for it; we want the one that includes the Vendor, Device, and Subsystem Ids: "PCI\VEN_8086&DEV_8CBA&SUBSYS_103C3842". Copy that value; we will paste it elsewhere in a minute.
 
Next, we open gpedit.msc (Group Policy Editor). This requires Windows 10 Pro or above; there may be a Registry version of this workaround for Home users, but I have not looked into it. In GPEdit, in the left panel, we need to go to the following setting: "Computer Configuration" > "Administrative Templates" > "System" > "Device Installation" > "Device Installation Restrictions". Upon selecting the "Device Installation Restrictions" template, a bunch of settings will appear in the window to the right. We are looking for "Prevent installation of devices that match any of these device IDs". Double-click it or right-click it and select "Edit".
 
Once in the "Prevent installation of devices that match any of these device IDs" setting, at the top left, we will see by default it is set to "Not Configured". We want to change this to "Enabled". Once it is enabled, in the "Options" pane at the bottom of the same window, there should be an options that reads "Prevent installation of device that match any of these Device IDs" with a "Show..." button. Click the "Show..." button. This will bring up a list of the restricted devices (it is currently empty). Here is where we can enter/paste the device ID we copied earlier from Device Manager. So now there should be a field in here with its "Value" set to "PCI\VEN_8086&DEV_8CBA&SUBSYS_103C3842". Click "OK" after entering the Device ID and then click "Apply" on the setting window.  This will restrict installation of any device that matches this ID (the Intel ME and its driver TeeDriverW8x64.sys).
 
YMMV, but this is literally the only thing keeping my system from constantly BSOD'ing due to this faulty driver in Windows 10. At one point before figuring out this workaround, I even had to fully re-install Windows because I could not get it to boot or recover without instantly blue screening with the "PAGE_FAULT_IN_NONPAGED_AREA". After inspecting the dump files, I found it it was this driver (TeeDriverW8x64.sys). When I was reinstalling Windows, I actually had to disconnect my PC from the Internet to prevent Windows from trying to automatically install this as part of the initial updates.

Here in 2022, just inherited a Z97 board with 4970K cpu, bsod constantly, this group policy fix worked like a charm. I probably didn't even need to go through 3 days of windows updates (over and over) if I would have installed this before swapping out the board in my machine :)
 
Thanks for the help!