Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.
Show DivPrimary Analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (
http://www.osr.com)
Online Crash Dump Analysis Service
See
OSR Online - The Home Page for Windows Driver Developers for more information
Windows 8 Kernel Version 16299 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff801`c8a94000 PsLoadedModuleList = 0xfffff801`c8df5fd0
Debug session time: Sat Nov 18 09:42:01.988 2017 (UTC - 5:00)
System Uptime: 16 days 19:07:16.807
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80edebfa2f2, The address that the exception occurred at
Arg3: ffffd2099c307738, Exception Record Address
Arg4: ffffd2099c306f80, Context Record Address
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nvhda64v+2a2f2
fffff80e`debfa2f2 4c8b11 mov r10,qword ptr [rcx]
EXCEPTION_RECORD: ffffd2099c307738 -- (.exr 0xffffd2099c307738)
ExceptionAddress: fffff80edebfa2f2 (nvhda64v+0x000000000002a2f2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
CONTEXT: ffffd2099c306f80 -- (.cxr 0xffffd2099c306f80)
rax=000000000000000a rbx=ffffc009a075e460 rcx=0000000000000000
rdx=0000000000000000 rsi=ffffc009a1c29010 rdi=fffff80edebe1ef0
rip=fffff80edebfa2f2 rsp=ffffd2099c307970 rbp=0000000000000080
r8=0000000000000000 r9=7fffc0099f91c828 r10=7ffffffffffffffc
r11=ffffd2099c307960 r12=00000000000000a7 r13=0000000000000001
r14=ffffc0099ceec040 r15=ffffd601b8db9000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nvhda64v+0x2a2f2:
fffff80e`debfa2f2 4c8b11 mov r10,qword ptr [rcx] ds:002b:00000000`00000000=0000000000000000
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
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
0000000000000000
FOLLOWUP_IP:
nvhda64v+2a2f2
fffff80e`debfa2f2 4c8b11 mov r10,qword ptr [rcx]
BUGCHECK_STR: AV
EXCEPTION_STR: 0x0
LAST_CONTROL_TRANSFER: from ffffc009a075e460 to fffff80edebfa2f2
STACK_TEXT:
ffffd209`9c307970 ffffc009`a075e460 : ffffc009`a1c29010 00000000`00000006 fffff80e`debe00bf ffffc009`9f91c000 : nvhda64v+0x2a2f2
ffffd209`9c307978 ffffc009`a1c29010 : 00000000`00000006 fffff80e`debe00bf ffffc009`9f91c000 00000000`00000001 : 0xffffc009`a075e460
ffffd209`9c307980 00000000`00000006 : fffff80e`debe00bf ffffc009`9f91c000 00000000`00000001 ffffd209`9c307900 : 0xffffc009`a1c29010
ffffd209`9c307988 fffff80e`debe00bf : ffffc009`9f91c000 00000000`00000001 ffffd209`9c307900 ffffd209`9c30791f : 0x6
ffffd209`9c307990 ffffc009`9f91c000 : 00000000`00000001 ffffd209`9c307900 ffffd209`9c30791f 00000000`00000000 : nvhda64v+0x100bf
ffffd209`9c307998 00000000`00000001 : ffffd209`9c307900 ffffd209`9c30791f 00000000`00000000 fffff80e`00000006 : 0xffffc009`9f91c000
ffffd209`9c3079a0 ffffd209`9c307900 : ffffd209`9c30791f 00000000`00000000 fffff80e`00000006 ffffc009`a0762010 : 0x1
ffffd209`9c3079a8 ffffd209`9c30791f : 00000000`00000000 fffff80e`00000006 ffffc009`a0762010 fffff80e`debfbeef : 0xffffd209`9c307900
ffffd209`9c3079b0 00000000`00000000 : fffff80e`00000006 ffffc009`a0762010 fffff80e`debfbeef ffff5db8`f4875c1f : 0xffffd209`9c30791f
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvhda64v+2a2f2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvhda64v
IMAGE_NAME: nvhda64v.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 59ba521e
STACK_COMMAND: .cxr 0xffffd2099c306f80 ; kb
FAILURE_BUCKET_ID: X64_AV_nvhda64v+2a2f2
BUCKET_ID: X64_AV_nvhda64v+2a2f2
Followup: MachineOwner
---------
This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
Show DivCrash Code Links
Show DivLoaded Module List
Show DivRaw Stack Contents
Show DivDump Header Information
Show DivStrings
