Windows 10: [Upgrade] - BSOD Page fault when updating to 20H2

Hello

I'm attempting to upgrade to 20H2 but have been stopped for the last couple of months by BSOD incurred by Intel Engine Management Interface.

I came across this thread which seemed promissing as the person involved had the same motherboard as and seemingly the same cause.
I tried all of the suggestions in that thread in order to figure out what the cause or fix could be. Sadly none of them worked.

These are the steps I undertook in order:
- Clean install (Failure to install upgrade)
- Installed msi intel Management provided by MSI (Failure to install upgrade)
- Disabled the device in device Management (Failure to install upgrade)

I've ran a short memtest to see if any quick issues popped and that was not the case.



-----------
MEMORY.DMP
-----------


Microsoft (R) Windows Debugger Version 10.0.19041.685 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`2ae00000 PsLoadedModuleList = 0xfffff803`2ba2a2f0
Debug session time: Sun Jan 17 00:38:07.204 2021 (UTC + 1:00)
System Uptime: 0 days 0:00:01.818
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols

Loading unloaded module list
....
For analysis of this file, run !analyze -v
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffffd8000000000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: 0000000000000000, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000006, (reserved)

Debugging Details:
------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 6

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-OGA4PO6

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 8

Key : Analysis.Memory.CommitPeak.Mb
Value: 70

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 50

BUGCHECK_P1: fffffd8000000000

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 6

READ_ADDRESS: fffffd8000000000

MM_INTERNAL_CODE: 6

PROCESS_NAME: System

TRAP_FRAME: ffffbf03477fdb20 -- (.trap 0xffffbf03477fdb20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffdfeff7fb000 rbx=0000000000000000 rcx=fffffd8000000000
rdx=fffffdfeff7fb000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8032b091580 rsp=ffffbf03477fdcb8 rbp=fffffdfeff7fb000
r8=fffffdfeff600000 r9=0000000000000002 r10=0000000000000002
r11=fffffd8000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MI_READ_PTE_LOCK_FREE:
fffff803`2b091580 488b01 mov rax,qword ptr [rcx] ds:fffffd80`00000000=????????????????
Resetting default scope

LOCK_ADDRESS: fffff8032ba44bc0 -- (!locks fffff8032ba44bc0)

Resource @ nt!PiEngineLock (0xfffff8032ba44bc0) Exclusively owned
Contention Count = 1
NumberOfExclusiveWaiters = 1
Threads: ffff9b07d58bd480-01<*>

Threads Waiting On Exclusive Access:
ffff9b07d37c5140
1 total locks

PNP_TRIAGE_DATA:
Lock address : 0xfffff8032ba44bc0
Thread Count : 1
Thread address: 0xffff9b07d58bd480
Thread wait : 0x74

STACK_TEXT:
ffffbf03`477fd798 fffff803`2b247f7f : 00000000`00000050 fffffd80`00000000 00000000`00000000 fffffdfe`ff600000 : nt!KeBugCheckEx
ffffbf03`477fd7a0 fffff803`2b00d227 : 00000000`00000000 00000000`00000000 ffffbf03`477fdb20 00000000`00000000 : nt!MiInPagePageTable+0x19619f
ffffbf03`477fd8f0 fffff803`2b00c6ca : 00000000`00000000 00000000`00000000 ffffbf03`477fdba0 00000000`00000000 : nt!MiUserFault+0x5e7
ffffbf03`477fd980 fffff803`2b20395e : ffffbf03`477fdc00 ffff9b07`d5bb5fe8 ffff9b07`d3002280 fffff803`2b04d21a : nt!MmAccessFault+0x16a
ffffbf03`477fdb20 fffff803`2b091580 : fffff803`2b03a621 00000000`00000200 00000000`00000000 00000000`00008030 : nt!KiPageFault+0x35e
ffffbf03`477fdcb8 fffff803`2b03a621 : 00000000`00000200 00000000`00000000 00000000`00008030 fffff803`2b7b1094 : nt!MI_READ_PTE_LOCK_FREE
ffffbf03`477fdcc0 fffff803`327b6c3a : ffff9b07`00000000 ffff9b07`d5bb0310 00000000`00000000 fffffd80`00008000 : nt!MmBuildMdlForNonPagedPool+0x1f1
ffffbf03`477fdd80 fffff803`327b0bda : 00000000`00000000 00000000`00000000 ffff9b07`d5bb0310 ffff9b07`d5bb03b8 : TeeDriverW8x64+0x16c3a
ffffbf03`477fde80 fffff803`327cd336 : ffff9b07`d5bb0310 ffffbf03`477fe0d0 ffff9b07`d5bb0310 00000000`00000000 : TeeDriverW8x64+0x10bda
ffffbf03`477fdfd0 fffff803`327cd712 : ffff8685`bf63ca40 ffffbf03`477fe2c0 fffff803`327c8050 ffff9b07`d3cb5270 : TeeDriverW8x64+0x2d336
ffffbf03`477fe250 fffff803`2c9f4c06 : 000064f8`2c34ad88 ffff9b07`d5552360 ffff9b07`d3cb5270 fffff803`2b050cb9 : TeeDriverW8x64+0x2d712
ffffbf03`477fe280 fffff803`2c9f4b2c : ffff9b07`d5552360 fffff803`2b15b38c ffff9b07`d5552360 00000000`00002710 : Wdf01000!FxDriver::AddDevice+0xc6 [minkernel\wdf\framework\shared\core\km\fxdriverkm.cpp @ 72]
ffffbf03`477fe6a0 fffff803`2b16aec7 : ffff9b07`d5a31680 fffff803`2b50aa85 00000000`00000000 00000000`00000000 : Wdf01000!FxDriver::AddDevice+0x2c [minkernel\wdf\framework\shared\core\km\fxdriverkm.cpp @ 47]
ffffbf03`477fe6d0 fffff803`2b5238b0 : ffff9b07`d5a31680 ffff9b07`d59f8510 00000000`00000003 ffff9b07`d378aa00 : nt!PpvUtilCallAddDevice+0x3b
ffffbf03`477fe710 fffff803`2b52709f : 00000000`00000003 00000000`00000000 00000000`6e657050 00000000`00000000 : nt!PnpCallAddDevice+0x94
ffffbf03`477fe7d0 fffff803`2b526427 : ffff9b07`d5527890 ffffbf03`477fea11 ffff9b07`d5527890 00000000`00000000 : nt!PipCallDriverAddDevice+0x827
ffffbf03`477fe990 fffff803`2b5bd3ac : ffff9b07`d5a81400 ffffbf03`477feb01 ffffbf03`477feab0 fffff803`00000000 : nt!PipProcessDevNodeTree+0x333
ffffbf03`477fea60 fffff803`2b16c25c : 00000001`00000003 ffff9b07`d5a81460 00000000`00000000 ffff9b07`d5a81460 : nt!PiProcessStartSystemDevices+0x60
ffffbf03`477feab0 fffff803`2b025975 : ffff9b07`d58bd480 ffff9b07`d36644a0 fffff803`2ba43420 ffff9b07`00000000 : nt!PnpDeviceActionWorker+0x4cc
ffffbf03`477feb70 fffff803`2b117e25 : ffff9b07`d58bd480 00000000`00000080 ffff9b07`d36a6080 000fa425`bd9bbfff : nt!ExpWorkerThread+0x105
ffffbf03`477fec10 fffff803`2b1fcdd8 : ffffd481`f7dec180 ffff9b07`d58bd480 fffff803`2b117dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffbf03`477fec60 00000000`00000000 : ffffbf03`477ff000 ffffbf03`477f9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: TeeDriverW8x64+16c3a
MODULE_NAME: TeeDriverW8x64
IMAGE_NAME: TeeDriverW8x64.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 16c3a
FAILURE_BUCKET_ID: AV_R_INVALID_TeeDriverW8x64!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b8743c3c-2120-f963-d94f-5279ab0f120d}

Followup: MachineOwner
---------

:)

 

BSOD Page fault when updating to 20H2 or monthly nov update

Hi Gang,

Have had issue of a BSOD on restart doing update to 20H2, or the nov monthly update.

The update will install, prompt me to restart, go through the blue screen of installing the update, then restart.

On this restart I get a page fault in non paged area. It will restart again, fail, then restart to automatic repair as it should, then diagnose pc, it then switched back tot eh blue screen where it says cannot install updates and rolls back, then puts me back to my desktop.

I had swapped my RAM sticks, and removed my CH products USB sticks throttle and rudder, making sure those might not be the culprit.

Windows Version 2004 Pro OS Build 19041.450

I'm hoping to get some direction in which to go, thanks beforehand!

 

Page Fault in Non-Paged Area BSOD

While installing windows 10 even before the setup started this BSOD of page fault in non paged area pops up and I am unable to install it.The same problem with other Windows OS installation.

 

BSoD error "page fault in non=page area"

I have recently been getting the BSoD error "page fault in non-page area" - three times today.

I also had a "Memory management" error.

Other issues that may or may not be related:

• MS Word in Office 365 has started loading automatically on startup w. blank page. Gives an error about the basic document template when I try to close. By opening any existing document, I can then close and exit.
• Firefox and AVG secure browser tabs are freezing - started today.

I found an earlier response to this error that suggested changes to the virtual memory settings. I checked mine and it is set for Windows to manage on all drives.

I have a copy of the memory dumps in a zip file if that would be helpful