Windows 10 Bugcheck crash dump

[h3m1ngway]

So, computer is just rebooting randomly, creating an identical .dmp every time. Not getting a blue screen either just a reboot into normal. Any help is appreciated!

Setup:
Windows 10
Core i5 6400
NVIDIA GTX 960

Dump:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff800`1021e000 PsLoadedModuleList = 0xfffff800`1056a5c0
Debug session time: Fri Sep 22 21:07:43.136 2017 (UTC - 4:00)
System Uptime: 0 days 1:44:35.826
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffdb054e17b003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff806d5d974a7, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffdb054e17b003

CURRENT_IRQL: 2

FAULTING_IP:
NNSPRV+174a7
fffff806`d5d974a7 0fb64801 movzx ecx,byte ptr [rax+1]

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

TRAP_FRAME: fffff80012038a60 -- (.trap 0xfffff80012038a60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffdb054e17b002 rbx=0000000000000000 rcx=fffff806d5dc6140
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff806d5d974a7 rsp=fffff80012038bf0 rbp=ffffdb054e17aa12
r8=0000000000000001 r9=0000000000000000 r10=fffff806d5dc6140
r11=fffff80012038c98 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
NNSPRV+0x174a7:
fffff806`d5d974a7 0fb64801 movzx ecx,byte ptr [rax+1] ds:ffffdb05`4e17b003=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800103958a9 to fffff8001038a580

STACK_TEXT:
fffff800`12038918 fffff800`103958a9 : 00000000`0000000a ffffdb05`4e17b003 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`12038920 fffff800`10393e7d : fffff800`12038b70 fffff806`d48637cb 00000000`00000000 fffff806`d49a309f : nt!KiBugCheckDispatch+0x69
fffff800`12038a60 fffff806`d5d974a7 : fffff806`d5daa148 fffff806`d5daa148 ffffdb05`4e17aa00 fffff806`d5d97094 : nt!KiPageFault+0x23d
fffff800`12038bf0 fffff806`d5daa148 : fffff806`d5daa148 ffffdb05`4e17aa00 fffff806`d5d97094 00000000`00000000 : NNSPRV+0x174a7
fffff800`12038bf8 fffff806`d5daa148 : ffffdb05`4e17aa00 fffff806`d5d97094 00000000`00000000 fffff800`12038ce0 : NNSPRV+0x2a148
fffff800`12038c00 ffffdb05`4e17aa00 : fffff806`d5d97094 00000000`00000000 fffff800`12038ce0 fffff806`d5daa148 : NNSPRV+0x2a148
fffff800`12038c08 fffff806`d5d97094 : 00000000`00000000 fffff800`12038ce0 fffff806`d5daa148 fffff806`d5daa148 : 0xffffdb05`4e17aa00
fffff800`12038c10 00000000`00000000 : fffff800`12038ce0 fffff806`d5daa148 fffff806`d5daa148 fffff800`12038cd0 : NNSPRV+0x17094


STACK_COMMAND: kb

FOLLOWUP_IP:
NNSPRV+174a7
fffff806`d5d974a7 0fb64801 movzx ecx,byte ptr [rax+1]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: NNSPRV+174a7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NNSPRV

IMAGE_NAME: NNSPRV.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 589afb64

FAILURE_BUCKET_ID: X64_AV_NNSPRV+174a7

BUCKET_ID: X64_AV_NNSPRV+174a7

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

 

[axe0axe0]

Uninstall Panda and see if it goes away, else follow https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.html upload the zip to onedrive, google drive or dropbox and post a share link.

 

[johnbl]

you might also update your motherboards network (Ethernet driver) old versions can cause virus scanners to fail.