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: fffff8047670049c, memory referenced.
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
Arg3: fffff8047670049c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
......
[COLOR="#008000"]Unter Windows 10 gibt der Debugger erst mal ein paar Systeminfos bekannt.
Dadurch brauch man nicht extra noch mal die Sysinfo abzufragen[/COLOR]
BUILD_VERSION_STRING: 10.0.14393.206 (rs1_release.160915-0644)
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7A59
SYSTEM_SKU: Default string
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 2.00
BIOS_DATE: 12/15/2016
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: Z270 GAMING PRO (MS-7A59)
BASEBOARD_VERSION: 1.0
.....
TRAP_FRAME: ffff9080fa9f9fb0 -- (.trap 0xffff9080fa9f9fb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff804f7c4c6b8 rbx=0000000000000000 rcx=ffffb70b37b4e230
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8047670049c rsp=ffff9080fa9fa148 rbp=ffff9080fa9fa250
r8=0000000000000000 r9=0000000000000003 r10=0000000000000000
r11=fffff804f7c2d84b r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
fffff804`7670049c ?? ???
[COLOR="#008000"]Der Trap ist in diesem Fall nicht besonders hilfreich.[/COLOR]
....
FAILED_INSTRUCTION_ADDRESS: [COLOR="#FF0000"]+0 [/COLOR]fffff804`7670049c [COLOR="#FF0000"]?? ???[/COLOR]
....
STACK_TEXT:
ffff9080`fa9f9cb8 fffff802`8ca066ca : 00000000`00000050 fffff804`7670049c 00000000`00000010 ffff9080`fa9f9fb0 : nt!KeBugCheckEx
ffff9080`fa9f9cc0 fffff802`8c8f7ffa : 00000000`00000010 00000000`00000000 ffff9080`fa9f9fb0 ffff9080`fa9f9eb9 : nt! ?? ::FNODOBFM::`string'+0x2623a
ffff9080`fa9f9db0 fffff802`8c9da8fc : ffff9080`fa9f9f68 00000000`00000008 ffff9080`fa9f9f80 00000000`00000008 : nt!MmAccessFault+0x9ca
ffff9080`fa9f9fb0 fffff804`7670049c : fffff804`f774a30b 00000000`00000000 ffff9080`fa9fa250 00000000`00000000 : nt!KiPageFault+0x13c
ffff9080`fa9fa148 fffff804`f774a30b : 00000000`00000000 ffff9080`fa9fa250 00000000`00000000 00000000`00008000 : 0xfffff804`7670049c
[COLOR="#FF0000"]ffff9080`fa9fa150 00000000`00000000 : ffff9080`fa9fa250 00000000`00000000 00000000`00008000 ffffb70b`285a45f0 : nvlddmkm+0x10a30b[/COLOR]
[COLOR="#008000"]Der Treiber nvlddmkm.sys hat sofort nach dem Aufruf ein PageFault im Speicher verursacht.
Dadurch kam es in der Folge zum Zugriffs-Fehler und zum BugCheckEx[/COLOR]
.....
SYMBOL_NAME: nvlddmkm+10a30b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
[COLOR="#FF0000"]IMAGE_NAME: nvlddmkm.sys[/COLOR]
....
BUCKET_ID: AV_INVALID_BAD_IP_nvlddmkm!unknown_function
[COLOR="#FF0000"]PRIMARY_PROBLEM_CLASS: AV_INVALID_BAD_IP_nvlddmkm!unknown_function[/COLOR]
[COLOR="#008000"]Der NVidia-Kerneltreiber hat eine unbekannte Funktion verwendet, was den Page_Fault auslöste[/COLOR]
....
[COLOR="#008000"]Der Aufruf des aktiven Thread brachte den gleichen Stack, wie weiter oben. Deshalb
spare ich mir den Thread.
Zum Schluss noch die Informationen über den NVidia-Treiber[/COLOR]
4: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff804`f7640000 fffff804`f8454000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
[COLOR="#FF0000"]Timestamp: Fri Jan 20 14:29:59 2017 [/COLOR](588210D7)
CheckSum: 00DCBC4D
ImageSize: 00E14000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4