Added 2 new drives to Storage Spaces and Getting PAGE_FAULT_IN_NONPAGED_AREA Spaceport.sys

  • Thread starter Thread starter JohnathanPenberthy
  • Start date Start date
J

JohnathanPenberthy

Guest
I just added 2 new drives to Windows 10 Storage Spaces, and now I am getting a PAGE_FAULT_IN_NONPAGED_AREA BSOD for Spaceport.sys when drives are attached, then sometimes randomly when they are not attached.


Already ran DISM Health Commands and SFC scan.


Dump Below:




Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64

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.





************* Path validation summary **************

Response Time (ms) Location

Deferred SRV*C:\Windows\symbol_cache*Symbol information

Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information

Executable search path is:

Windows 10 Kernel Version 19041 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff801`2da00000 PsLoadedModuleList = 0xfffff801`2e62a2b0

Debug session time: Mon Jan 11 01:26:51.717 2021 (UTC - 7:00)

System Uptime: 0 days 0:07:49.438

Loading Kernel Symbols

...............................................................

................................................................

............................................

Loading User Symbols



Loading unloaded module list

......

For analysis of this file, run !analyze -v

0: 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: ffffe6a2b1ae3a20, memory referenced.

Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

Arg3: fffff80130a8acff, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000002, (reserved)



Debugging Details:

------------------





KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 3



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on _____



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 15



Key : Analysis.Memory.CommitPeak.Mb

Value: 70



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: 50



BUGCHECK_P1: ffffe6a2b1ae3a20



BUGCHECK_P2: 0



BUGCHECK_P3: fffff80130a8acff



BUGCHECK_P4: 2



READ_ADDRESS: ffffe6a2b1ae3a20 Nonpaged pool



MM_INTERNAL_CODE: 2



IMAGE_NAME: spaceport.sys



MODULE_NAME: spaceport



FAULTING_MODULE: fffff80130a80000 spaceport



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXWINLOGON: 1



PROCESS_NAME: System



TRAP_FRAME: ffffe4082deca2c0 -- (.trap 0xffffe4082deca2c0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffffe6a2b1ae3a20 rbx=0000000000000000 rcx=ffffe6a2b1ae3a20

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80130a8acff rsp=ffffe4082deca450 rbp=0000000001000000

r8=00000000ffffffff r9=0000000000000004 r10=0000000000000002

r11=0000000000000001 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

spaceport!SIO_RAID::Initialize+0x59f:

fffff801`30a8acff 0fb700 movzx eax,word ptr [rax] ds:ffffe6a2`b1ae3a20=????

Resetting default scope



STACK_TEXT:

ffffe408`2deca018 fffff801`2de1e8bb : 00000000`00000050 ffffe6a2`b1ae3a20 00000000`00000000 ffffe408`2deca2c0 : nt!KeBugCheckEx

ffffe408`2deca020 fffff801`2dc0c960 : ffffe682`dc500000 00000000`00000000 ffffe408`2deca340 00000000`00000000 : nt!MiSystemFault+0x1f40ab

ffffe408`2deca120 fffff801`2de0395e : ffffe682`38107040 fffff801`2ddf103b 00000000`00000e6a 00000000`00000000 : nt!MmAccessFault+0x400

ffffe408`2deca2c0 fffff801`30a8acff : ffffe682`3e117700 ffffe682`add5ea90 00000000`00000000 00000000`00000060 : nt!KiPageFault+0x35e

ffffe408`2deca450 fffff801`30a95a7f : 00000000`00000000 00000000`00000003 00000000`00000003 ffffe682`add5ea90 : spaceport!SIO_RAID::Initialize+0x59f

ffffe408`2deca4f0 fffff801`30a912cf : ffffe682`ceac1e00 ffffe682`add5ea90 00000000`00000000 fffff801`30a890f9 : spaceport!SIO_RAID1::Initialize+0x3f

ffffe408`2deca610 fffff801`30a91128 : ffffe682`385f41c0 ffffe682`4b95c810 00000b71`70000000 00000000`00000000 : spaceport!SIO_RAID::Create+0xbb

ffffe408`2deca660 fffff801`30a913fb : 00000000`0000b717 ffffe682`4b95c810 00000000`00000000 ffffe682`385f41c0 : spaceport!SIO_SPAN::Initialize+0x90

ffffe408`2deca6a0 fffff801`30a917db : 00000000`00000000 ffffe682`add5ea90 ffffe682`add5ea90 00000000`00000000 : spaceport!SIO_SPACE::BuildIoTree+0x9f

ffffe408`2deca6d0 fffff801`30ae99e4 : ffffe682`add5ea90 ffffe682`c99d0170 00000000`00000000 ffffe682`385f41c0 : spaceport!SIO_SPACE::Initialize+0x39b

ffffe408`2deca720 fffff801`30ae25ac : ffffe682`385f41c0 00002267`a0000000 0000006b`70000000 00000006`2deca7b0 : spaceport!SP_SPACE::Initialize+0x24

ffffe408`2deca750 fffff801`30ae1658 : ffffe682`3b17b050 ffffe408`2deca890 ffffe408`2deca858 ffffe408`2deca854 : spaceport!SP_POOL::PrepareCommit+0x294

ffffe408`2deca810 fffff801`30afed88 : 00000000`00000000 ffffe682`3b17b050 ffffe682`3d40df10 00000000`00000000 : spaceport!SP_POOL::ExecuteTransactionInternal+0xd4

ffffe408`2deca890 fffff801`30a94ab8 : ffffe682`38891930 ffffe682`38891120 00000000`00000000 00000000`00000000 : spaceport!SpRebalanceCallback+0x3f8

ffffe408`2deca9a0 fffff801`2dd5a435 : ffffe682`38897cd0 00000000`00000000 fffff801`30a94a50 fffff801`30a43d60 : spaceport!SpWorkItemWorkerRoutine+0x68

ffffe408`2decaa00 fffff801`2dc25975 : ffffe682`38107040 ffffe682`38107040 fffff801`2dd5a300 ffffe682`00000000 : nt!IopProcessWorkItem+0x135

ffffe408`2decaa70 fffff801`2dd17e25 : ffffe682`38107040 00000000`00000080 ffffe682`37eb9040 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105

ffffe408`2decab10 fffff801`2ddfcdd8 : ffffd180`39c00180 ffffe682`38107040 fffff801`2dd17dd0 85ff428d`000000b2 : nt!PspSystemThreadStartup+0x55

ffffe408`2decab60 00000000`00000000 : ffffe408`2decb000 ffffe408`2dec4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28





SYMBOL_NAME: spaceport!SIO_RAID::Initialize+59f



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 59f



FAILURE_BUCKET_ID: AV_R_INVALID_spaceport!SIO_RAID::Initialize



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {9bd9c508-d0a3-9c1b-cebf-8137fb3b70aa}



Followup: MachineOwner

---------

Continue reading...
 
Back
Top