システムwiki

私は最近複数のBSODを取得し続けていますが、ほとんどの場合Page_Fault_in_nonpaged_area

JasonL9 受付中 最終更新日:2021-12-25 15:33

これは非常に一般的なバグチェックです. 通常、例外アドレスピンポイント
問題の原因となったドライバ/機能. 常にこのアドレスをメモ
同様に、このアドレスが含まれているドライバ/イメージのリンク日時など.
引数:
ARG1:ffffffff80000003、処理されなかった例外コード
ARG2:fffff8036ac52e03、例外が発生したことで、アドレス
ARG3:0000000000000000、例外のパラメータ0
ARG4:0000000000000000、例外のパラメータ1
デバッグの詳細:



***警告:Win32k.sysのチェックサムを確認できません
key_values_string:1
鍵 :Analysis.cpu.msec.
値:4187
鍵 :Analysis.debuganalySismanAger.
価値:作成者
鍵 :Analysis.elapsed.msec.
値:8027
鍵 :Analysis.init.cpu.msec.
値:359
鍵 :Analysis.init.ELapsed.msec.
値:3278
鍵 :Analysis.Memory.commitpeak.mb.
値:81
鍵 :wer.os.branch.
値:vb_release.
鍵 :wer.os.timestamp.
値:2019-12-06T14:06:00Z
鍵 :wer.os.version.
値:10.0.19041.1
bugcheck_code: 1E
BUGCHECK_P1:ffffffff80000003
BUGCHECK_P2:fffff8036ac52e03
BUGCHECK_P3:0
bugcheck_p4:0
BlackBoxBSD:1(!BlackBoxBSD)
BlackBoxNTFS:1(!BlackBoxNTFS)
BlackBoxPNP:1(!BlackBoxPNP)
BlackboxWinlogon:1
customer_crash_count: 1
process_name: システム
stack_text:
ffffb482`394599c8 fffff803`6ae9158f :00000000`0000001e ffffffff`80000003 fffff803`6ac52e03 00000000`00000000:!NT KeBugCheckEx
ffffb482`394599d0 fffff803`6ae07cac :ffffb988`fdabf728 00000000`c0000225 ffffb988`fdabf6e0 fffff803`68013b4c:!NT KiDispatchException + 0x166b2f
ffffb482`3945a090 fffff803`6ae01616 :ffffb988`e6317010 ffffb988`e27c10a0 ffffb988`dd55e010 ffffb988`fba89960:!NT KiExceptionDispatch + 0x12c
ffffb482`3945a270 fffff803`6ac52e04 :fffff803`6ad54290 00000000`00000000 ffffb482`3945a510 fffff803`6e295a20:!NT KiBreakpointTrap + 0x316
ffffb482`3945a408 00000000`00000000 :00000000`60000000 00000000`00000000 00000000`00000000 00000000`00000000:!NT IopVerifierExAllocatePoolWithQuota + 0x284
symbol_name: NT!IopVerifierExAllocatePoolWithQuota + 283
module_name:NT
image_name: ntkrnlmp.exe.
image_version: 10.0.19041.867
stack_command: .スレッド ; .cxr; k
bucket_id_func_offset: 283
failure_bucket_id: 0x1E_80000003_nt!IopVerifierExAllocatePoolWithQuota
OS_VERSION: 10.0.19041.1.
buildlab_str: vb_release.
osplatform_type: x64
オス名: Windows 10
failure_id_hash: {70502a4f-a4f6-a8ed-d4e0-85150b054c27}
ファローアップ: マシン看所

PAGE_FAULT_IN_NONPAGED_AREA(50)
Invalidsystemmemorywasreferenced.Thiscannotbeprotectedbytry-除きます.
Typicallytheaddressisjustplainbadoritispointingatfreedmemory.
引数:
ARG1:fffff805278dffff、memoryreferenced.
ARG2:0000000000000010、value0=読み出し動作、1=書き込み動作.
ARG3:fffff805278dffff、Ifnonゼロ、theinstructionaddresswhichreferencedthebadmemory
住所.
ARG4:0000000000000002、(予約)
DebuggingDetails:

KEY_VALUES_STRING:1
キー:Analysis.CPU.mSec
値:3578
キー:Analysis.DebugAnalysisManager
値:作成
キー:Analysis.Elapsed.mSec
値:4494
キー:Analysis.Init.CPU.mSec
値:343
キー:Analysis.Init.Elapsed.mSec
値:2743
キー:Analysis.Memory.commitPeak.Mb
値:73
キー:WER.OS.Branch
値:vb_release
キー:WER.OS.Timestamp
値:2019-12-06T14:06:00Z
キー:WER.OS.Version
値:10.0.19041.1
BUGCHECK_CODE:50
BUGCHECK_P1:fffff805278dffff
BUGCHECK_P2:10
BUGCHECK_P3:fffff805278dffff
BUGCHECK_P4:2
たread_address:fffff8042bafb390:UnabletogetMiVisibleState
UnabletogetNonPagedPoolStart
UnabletogetNonPagedPoolEnd
UnabletogetPagedPoolStart
UnabletogetPagedPoolEnd
unabletogetnt!MmSpecialPagesInUse
fffff805278dffff
MM_INTERNAL_CODE:2
BLACKBOXBSD:1(!blackboxbsd)
BLACKBOXNTFS:1(!のblackboxntfs)
BLACKBOXPNP:1(!blackboxpnp)
BLACKBOXWINLOGON:1
CUSTOMER_CRASH_COUNT:1
process_name:thejackboxpartypack6.exe
TRAP_FRAME:FFFFF984755E24E0-(.TRAP0XFFFFF9847555E24E0)
注:ThetrapFramedOsNotContainAllRegisters.
SomEregistervaluesSmaybezeroedorinkorrect
RAX= 0000000000000CRBX= 0000000000000000RCX= FFFFF805278DFFFF
RDX= FFFFF804278E0000RSI= 0000000000000000RDI= 0000000000000000
RIP= FFFFF805278DFFFFRSP= FFFFF984755E2670RBP= 000000000000000001
R8= FFFF80044J4A55F0R9= FFFF800444A54B0R10= FFFF80044FA4CCC0
R11= 0000000000000000 R13= 0000000000000000
R14= 0000000000000000 R15= 0000000000000000
iopl= 0nvupeingnznaponc.
FFFFF805 `278dffff?
リセットデフォルトスコープ
failed_instruction_address:
+0
FFFFF805 `278dffff?
stack_text:
FFFFF984`755E2238FFFFFF804 `2 B 2 2 2238FFFFF804` 2 B 2 REB01:00000000 $ prof 00000000000000000010FFFFFF984`755E24E0:NT!Kebugcheckex
FFFFF984`755E2240FFFFFF804 `200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000:NT!MisyStemFault + 0x1F42F1
fffff984`755e2340fffff804`2b203d5e:ffff8004`52f9a0c000000000000000000000000000000000000000000000000000000000000000000:NT!MMAccessFault + 0x400
fffff984`755e24e0fffff805`278dffff:ffff8004`40cc62a000000000000000300000000000000000000000000000000FFF8004 `41010000:NT!KipageFault + 0x35e
fffff984`755e2670ffff8004`40cc62a000000000FFF8004`000000000000000000000000000008:0xFFFFFF805`278DFFFF
000000000000000000000008FFFF804`278E7A70:0xFFFF8004`40CC62A0
fffff984`755e268000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000008FFFFFFFF8004`4E4A54B0:0x30
chkimg_extension:!chkimg-lo50-db!fltmgr
4RRORS:!FLTMGR(FFFFF804278E4C04-FFFFF804278E4C2C)
FFFFF804278E4C000F8484BB* D0003D1C841400758DE978BB ......= ....u..x.
fffff804278E4C100000488D* 60J048899424A80000004C8B...H ..$ ....l.
FFFFF804278E4C20030FB74A* 844C896C24604D8B* F8584C89 ...j.l.l $ `m..xl.
module_name:memory_corruption.
image_name:memory_corruption.
memory_corruptor:ストライト
stack_command:.thread; .cxr; k
failure_bucket_id:memory_corruption_stride.
OS_VERSION:10.0.19041.1
buildlab_str:vb_release.
osplatform_type:x64
OSNAME:windows 10.
failure_id_hash:{574DBC1B-92CB-FB09-CB7A-CACC1BB2C511}
フォローアップ:memory_corruption.

page_fault_in_nonpaged_area(50)
InvalidSystemMemoryWasReferenced.ThiscannotBeProtectedBytry-除きます.
通常はaddressisjustplainbadoritispointingAtfreedMemory.
引数:
ARG1:FFFFB0552AD7D8A8、認定されています.
arg2:0000000000000002、value0= readOperation、1=書き込み操作.
ARG3:FFFFB05541FD4D62、IFNON-0、THEINSTRUCTIONADDRESSWHICHERENCEDMEMORY
住所.
ARG4:0000000000000002、(予約)
DebuggingDetails:

key_values_string:1
key:Analysis.cpu.msec.
値:5093
キー:Analysis.DebuganalySismanAger.
価値:作成者
キー:Analysis.elapsed.msec.
値:7078
key:Analysis.init.cpu.msec.
値:390
key:Analysis.init.elapsed.msec.
値:3068
キー:Analysis.Memory.commitpeak.mb.
値:88
キー:wer.os.branch.
値:vb_release.
キー:wer.os.timestamp.
値:2019-12-06T14:06:00Z
キー:wer.os.version.
値:10.0.19041.1
bugcheck_code:50
BugCheck_p1:FFFFB0552AD7D8A8
BugCheck_p2:2
BugCheck_p3:FFFFB05541FD4D62
BugCheck_p4:2
read_address:FFFFF805488FB390:UnableTogetMivisiabibisiabibisiabibisia.
UNABLETOGETNONPARIDPOOLSTART
UnableToGetnonPagedPoolend.
UnableTogetPagedPoolStart.
UnableToGetPagedPoolend.
UNABLETOGETNT!MMSPecialPageSinuse.
FFFFB0552AD7D8A8
mm_internal_code:2
BlackBoxBSD:1(!BlackBoxBSD)
BlackBoxNTFS:1(!BlackBoxNTFS)
BlackBoxPNP:1(!BlackBoxPNP)
BlackboxWinlogon:1
customer_crash_count:1
process_name:csrss.exe.
TRAP_FRAME:FFFF8B8012E20BF0-(.TRAP0XFFFF8B8012E20BF0)
注:ThetrapFramedOsNotContainAllRegisters.
SomEregistervaluesSmaybezeroedorinkorrect
RAX= FFFFB05541FD4D60RBX= 0000000000000000RCX= 0000000000000000
RDX= FFFF012006278A0RSI= 000000000000000000RDI= 0000000000000000
RIP= ffffb05541fd4d62rsp= ffff8b8012e20d80rbp= ffffb012006278a0
R8= ffffffffffffffffr9= 0000000000000000r10= 0000ffffb05541fd
R11= ffff8ffcee600000r12= 0000000000000000r13= 0000000000000000
R14= 0000000000000000 R15= 0000000000000000
IOPL= 0nvupeiplnzacpecy
Win32kfull EditionIsGpqForegroundAccessibleExplicit + 0x2の!
ffffb055`41fd4d624883ec30subrsp、30H
リセットデフォルトスコープ
stack_text:
ffff8b80`12e20948fffff805`4801eb01:00000000`00000050ffffb055`2ad7d8a800000000`00000002ffff8b80`12e20bf0:!NT KeBugCheckEx
ffff8b80`12e20950fffff805`47e0c960:ffffe504`21bda34000000000`00000002ffff8b80`12e20c7000000000`00000000:!NT MiSystemFault + 0x1f42f1
ffff8b80`12e20a50fffff805`48003d5e:00000000`0000000000000000`0000004fffffe504`1701778000000000`00000110:!NT MmAccessFault + 0x400
ffff8b80`12e20bf0ffffb055`41fd4d62:ffffffff`ffffffffffffb055`41661bb7ffffb012`073edd30ffff8b80`12e20dd0:!NT KiPageFault + 0x35e
ffff8b80`12e20d80ffffb055`41661bb7:ffffb012`073edd30ffff8b80`12e20dd0ffff8b80`12e20e88ffff8b80`12e20e70:!Win32kfull EditionIsGpqForegroundAccessibleExplicit + 0x2の
ffff8b80`12e20d90ffffb055`41660644:ffffffff`ffffffffffff8b80`12e20ec900000000`0000004f00000000`00000000:!Win32kbase ApiSetEditionIsGpqForegroundAccessibleExplicit + 0x8b
ffff8b80`12e20de0ffffb055`41660432:ffff8b80`12e210e0ffff8b80`12e20fc900000000`00000000ffff8b80`12e210e0:!Win32kbase xxxUpdateGlobalsAndSendKeyEvent + 0x1d4
ffff8b80`12e20f10ffffb055`417b44fa:ffff8b80`12e20000ffff8b80`12e210d000000000`03bc8c3800000000`00000000:!Win32kbase xxxKeyEventEx + 0x1e2
ffff8b80`12e21010ffffb055`417b4177:ffffb012`00606a3000000000`00000000ffff8b80`12e21190ffffe504`226b20c8:!Win32kbase xxxProcessKeyEvent + 0x2da
ffff8b80`12e21090ffffb055`417a5b78:00000000`00000000ffffe504`29087870ffffb012`00606a30ffff8ffc`ee600000:!Win32kbase ProcessKeyboardInputWorker + 0x837
ffff8b80`12e211f0ffffb055`417a59f9:ffffb055`418566d0ffff8b80`12e2130100000000`00000000ffffe504`291d2c80:!Win32kbase CKeyboardProcessor :: ProcessInputNoLock + 0xdc
ffff8b80`12e21220ffffb055`417ae3ad:ffffb012`006069e0ffffe504`226b207000000000`0000000c00000000`00000000:!Win32kbase CKeyboardProcessor :: ProcessInputの+ 0x491
ffff8b80`12e21360ffffb055`417a76ba:ffffb055`4180b530ffff8b80`12e214a0ffffb012`006069e0ffffb055`4184c970:!Win32kbase CKeyboardSensor :: ProcessInputの+ 0x5d
ffff8b80`12e213a0ffffb055`41663719:00000000`00000040ffffb055`4180b53000000000`0000000100000000`00000006:!Win32kbase CBaseInput :: OnReadNotification + 0x52a
ffff8b80`12e214e0ffffb055`41663322:ffffe504`27233080ffffb012`006585b000000000`00000006ffff256e`b5602885:!Win32kbase CBaseInput :: OnDispatcherObjectSignaled + 0x31d
ffff8b80`12e21620ffffb055`4169da8e:ffffb055`418532b0ffffb012`006585b0ffffb055`4184c97000000000`00000001:!Win32kbase CBaseInput :: _OnDispatcherObjectSignaled + 0x12を
ffff8b80`12e21650ffffb055`4169d7e0:00000000`00000006ffffb055`418532b000000000`00000001ffffb012`006be300:!Win32kbase LegacyInputDispatcher ::派遣+ 0x52
ffff8b80`12e21680ffffb055`41fabbef:00000000`0000010a00000000`0000000100002000`0000000000000000`00000004:!Win32kbase LegacyInputDispatcher :: WaitAndDispatch + 0x100の
ffff8b80`12e217b0ffffb055`4160d063:ffffe504`27233080ffffe504`2723308000000000`0000000000000000`00000005:!Win32kfull RawInputThread + 0x7bf
ffff8b80`12e21970ffffb055`41f83a30:ffffe504`2723308000000000`0000000000000000`0000000500000000`00000005:!Win32kbase xxxCreateSystemThreads + 0xc3
ffff8b80`12e21aa0ffffb055`4194474d:ffffe504`27233080ffffe504`2723308000000000`0000000000000000`00000000:!Win32kfull NtUserCallNoParam + 0x70
ffff8b80`12e21ad0fffff805`480075b8:ffffe504`0000000500000000`00000005000001bc`57604a6000000000`000024c4:!Win32kのNtUserCallNoParam + 0x15の
ffff8b80`12e21b0000007ffb`045b10e4:00000000`0000000000000000`0000000000000000`0000000000000000`00000000:!NT KiSystemServiceCopyEnd +の0x28
00000087`89cbf7e800000000`00000000:00000000`0000000000000000`0000000000000000`0000000000000000`00000000:0x00007ffb`045b10e4
SYMBOL_NAME:!Win32kfull EditionIsGpqForegroundAccessibleExplicit + 2
MODULE_NAME:Win32kfull
IMAGE_NAME:Win32kfull.sys
するimage_version:10.0.19041.867
stack_command:.thread; .cxr; k
bucket_id_func_offset:2
failure_bucket_id:AV_INVALID_WIN32KFULL!EDISEISGPQFOREGROUNDACCESSIBLE非記号
OS_VERSION:10.0.19041.1
buildlab_str:vb_release.
osplatform_type:x64
OSNAME:windows 10.
failure_id_hash:{2CF6917F-D4F7-97F-6F89-5C19F280C6E1}
フォローアップ:MichineOwner

返信リスト(回答:1)

1 #
JasonL9

こんにちはNikhar、

私はRAM上でいくつかのテストを実行し、普通の何も検出されなかった.これはより多くのドライバの問題ですか?もしそうなら、私はそれを解決するのでしょうか?