BSOD PAGE_FAULT_IN_NONPAGED_AREA в Windows 10 - BSOD - Ответ 8046527

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


Loading Dump File [F:\Загрузки\Minidump\090315-50203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols;srv*c:\windows\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 10240 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10240.16463.amd64fre.th1.150819-1946
Machine Name:
Kernel base = 0xfffff803`7f210000 PsLoadedModuleList = 0xfffff803`7f535030
Debug session time: Thu Sep 3 16:08:07.495 2015 (UTC + 3:00)
System Uptime: 0 days 0:49:01.349
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
.................
Cannot read PEB32 from WOW64 TEB32 0000a259 - Win32 error 0n30
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6fb400037a8, 0, 0, 6}


Could not read faulting driver name
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )

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

*** Memory manager detected 41561 instance(s) of page corruption, target is likely to have memory corruption.

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6fb400037a8, 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:
------------------


Could not read faulting driver name

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffff6fb400037a8

MM_INTERNAL_CODE: 6

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 2

BAD_PAGES_DETECTED: a259

TRAP_FRAME: ffffd00087fc6600 -- (.trap 0xffffd00087fc6600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000ca41090 rbx=0000000000000000 rcx=000000000ca41f7f
rdx=00000000deadb000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8037f2d1198 rsp=ffffd00087fc6790 rbp=0000098000000000
r8=ffffe000ec000030 r9=00000000006f56d8 r10=ffffe000ec000000
r11=ffffe000e7d80000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!MmBuildMdlForNonPagedPool+0x88:
fffff803`7f2d1198 498b06 mov rax,qword ptr [r14] ds:0010:00000000`00000000=000000000000a259
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8037f37ce8e to fffff8037f35e240

STACK_TEXT:
ffffd000`87fc6318 fffff803`7f37ce8e : 00000000`00000050 fffff6fb`400037a8 00000000`00000000 fffff6fb`7da00018 : nt!KeBugCheckEx
ffffd000`87fc6320 fffff803`7f22f170 : 00000000`00000000 fffff6fb`400037a8 ffffd000`87fc6580 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1008e
ffffd000`87fc64b0 fffff803`7f3672bd : ffffe000`ec000000 00000000`00000801 00000000`00066000 fffff801`00000000 : nt!MmAccessFault+0x2d0
ffffd000`87fc6600 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13d


STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

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

*** Memory manager detected 41561 instance(s) of page corruption, target is likely to have memory corruption.