Need help on Probably caused by : PROCEXP152.SYS ( PROCEXP152+273a )

Below is the dump analysis. Need to identify the cause.

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\ajay\New folder\090117-35875-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *http://msdl.microsoft.com/download/symbols;SRV\*C:\debug\*http://msdl.microsoft.com/download/symbols

Executable search path is: 

Windows 8 Kernel Version 9600 MP (4 procs) Free x64

Product: Server, suite: TerminalServer SingleUserTS

Built by: 9600.18758.amd64fre.winblue_ltsb.170707-0600

Machine Name:

Kernel base = 0xfffff8038680f000 PsLoadedModuleList = 0xfffff80386ae1650

Debug session time: Fri Sep  1 05:45:26.536 2017 (UTC + 1:00)

System Uptime: 13 days 0:41:48.258

Loading Kernel Symbols

...............................................................

................................................................

......................

Loading User Symbols

Loading unloaded module list

........................................

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffc00181be800d, 0, fffff800672cf73a, 0}

*** WARNING: Unable to verify timestamp for PROCEXP152.SYS

*** ERROR: Module load completed but symbols could not be loaded for PROCEXP152.SYS

Could not read faulting driver name

Probably caused by : PROCEXP152.SYS ( PROCEXP152+273a )

Followup: MachineOwner

---

1: 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: ffffc00181be800d, memory referenced.

Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

Arg3: fffff800672cf73a, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000000, (reserved)

Debugging Details:

---

Could not read faulting driver name

READ_ADDRESS: fffff80386acf020: Unable to get special pool info

fffff80386acf020: Unable to get special pool info

unable to get nt!MmNonPagedPoolStart

unable to get nt!MmSizeOfNonPagedPoolInBytes

 ffffc00181be800d 

FAULTING_IP: 

PROCEXP152+273a

fffff800`672cf73a 80794d00        cmp     byte ptr [rcx+4Dh],0

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

BUGCHECK_STR:  AV

PROCESS_NAME:  Handle64.exe

CURRENT_IRQL:  0

TRAP_FRAME:  ffffd000266d92b0 -- (.trap 0xffffd000266d92b0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=000000000002ec8e rbx=0000000000000000 rcx=ffffc00181be7fc0

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff800672cf73a rsp=ffffd000266d9440 rbp=ffffd000266d9891

 r8=ffffe001eaf4e2d8  r9=ffffe001e0441001 r10=0000000083350001

r11=fffff8038696998b r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl zr na po nc

PROCEXP152+0x273a:

fffff800672cf73a 80794d00        cmp     byte ptr [rcx+4Dh],0 ds:ffffc00181be800d=??

Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80386972de4 to fffff8038695cda0

STACK_TEXT:  

ffffd000266d9048 fffff80386972de4 : 0000000000000050 ffffc00181be800d 0000000000000000 ffffd000266d92b0 : nt!KeBugCheckEx

ffffd000266d9050 fffff80386854ee9 : 0000000000000000 ffffe001ea1cf900 ffffd000266d92b0 0000000000000006 : nt! ?? ::FNODOBFM::`string'+0x5b14

ffffd000266d90f0 fffff8038696702f : 0000000000000000 ffffffffffffffff 0000000000000000 0000000000000000 : nt!MmAccessFault+0x769

ffffd000266d92b0 fffff800672cf73a : 0000000000000000 ffffe001e04a3680 ffffe001e04a3680 ffffe001e04a3680 : nt!KiPageFault+0x12f

ffffd000266d9440 0000000000000000 : ffffe001e04a3680 ffffe001e04a3680 ffffe001e04a3680 ffffd000266d9488 : PROCEXP152+0x273a

STACK_COMMAND:  kb

FOLLOWUP_IP: 

PROCEXP152+273a

fffff800`672cf73a 80794d00        cmp     byte ptr [rcx+4Dh],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  PROCEXP152+273a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PROCEXP152

IMAGE_NAME:  PROCEXP152.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  53bb8f8b

FAILURE_BUCKET_ID:  AV_PROCEXP152+273a

BUCKET_ID:  AV_PROCEXP152+273a

Followup: MachineOwner

---

1: kd> lmvm PROCEXP152

start             end                 module name

fffff800672cd000 fffff800672d9000   PROCEXP152 T (no symbols)           

    Loaded symbol image file: PROCEXP152.SYS

    Image path: PROCEXP152.SYS

    Image name: PROCEXP152.SYS

    Timestamp:        Tue Jul 08 07:28:27 2014 (53BB8F8B)

    CheckSum:         0000B54D

    ImageSize:        0000C000

    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4