Hi Kritam,
Intelppm.sys is related to Microsoft intel processor driver.We can try to download the latest driver from the Intel download center then install the process driver manually to have a check.If the issue persists,we can try the other versions to have a check.
Here is the analysis results for reference:
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff800f617d1c0, 1, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : intelppm.sys ( intelppm!memset+c0 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800f617d1c0, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000001, Parameter 1 of the exception
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800b2964138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000001
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
intelppm!memset+c0
fffff800`f617d1c0 488911 mov qword ptr [rcx],rdx
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000001
BUGCHECK_STR: 0x1E_c0000005_W
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
EXCEPTION_RECORD: ffffd001709712c0 -- (.exr 0xffffd001709712c0)
ExceptionAddress: ffffd001709712c8
ExceptionCode: 00000006
ExceptionFlags: 00000000
NumberParameters: 0
TRAP_FRAME: 0000000000000001 -- (.trap 0x1)
Unable to read trap frame at 00000000`00000001
LAST_CONTROL_TRANSFER: from fffff800b27e2f9a to fffff800b2751ca0
STACK_TEXT:
ffffd001`70978738 fffff800`b27e2f9a : 00000000`0000001e ffffffff`c0000005 fffff800`f617d1c0 00000000`00000001 : nt!KeBugCheckEx
ffffd001`70978740 fffff800`b27591ed : ffffd001`70978eb0 00000000`00000000 ffffd001`709796a8 ffffd001`709788b0 : nt!KiFatalExceptionHandler+0x22
ffffd001`70978780 fffff800`b26ca0a5 : 00000000`00000001 fffff800`b2601000 ffffd001`70979600 fffff800`00000000 : nt!RtlpExecuteHandlerForException+0xd
ffffd001`709787b0 fffff800`b26ce45e : ffffd001`709796a8 ffffd001`709793b0 ffffd001`709796a8 00000000`00000000 : nt!RtlDispatchException+0x1a5
ffffd001`70978e80 fffff800`b275d8c2 : ffffd001`709712c0 ffffd001`70979600 00000000`00000001 fffff800`b26543a7 : nt!KiDispatchException+0x646
ffffd001`70979570 fffff800`b275c014 : 00000000`00000001 ffffd001`70965180 00000000`0000a000 ffffe001`8897e000 : nt!KiExceptionDispatch+0xc2
ffffd001`70979750 fffff800`f617d1c0 : fffff800`f617c1f7 ffffe001`80f80350 00000000`00000000 ffffe001`91812000 : nt!KiPageFault+0x214
ffffd001`709798e8 fffff800`f617c1f7 : ffffe001`80f80350 00000000`00000000 ffffe001`91812000 ffffd001`70965180 : intelppm!memset+0xc0
ffffd001`709798f0 fffff800`b263fdf8 : ffffd001`70965180 ffffd001`70979a00 ffffd001`70979a20 0000000d`b0473950 : intelppm!AcpiCStateIdleExecute+0x17
ffffd001`70979920 fffff800`b263f856 : ffffd001`70965180 ffffd001`70979b4c ffffd001`70979b50 ffffd001`70979b58 : nt!PpmIdleExecuteTransition+0x3e8
ffffd001`70979b10 fffff800`b27557bc : ffffd001`70965180 ffffd001`70965180 ffffd001`709712c0 00000000`0015f361 : nt!PoIdle+0x2f6
ffffd001`70979c60 00000000`00000000 : ffffd001`7097a000 ffffd001`70974000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
FOLLOWUP_IP:
intelppm!memset+c0
fffff800`f617d1c0 488911 mov qword ptr [rcx],rdx
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: intelppm!memset+c0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5215cfeb
IMAGE_VERSION: 6.3.9600.16384
BUCKET_ID_FUNC_OFFSET: c0
FAILURE_BUCKET_ID: 0x1E_c0000005_W_intelppm!memset
BUCKET_ID: 0x1E_c0000005_W_intelppm!memset
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1e_c0000005_w_intelppm!memset
FAILURE_ID_HASH: {aa7cca3f-5345-841f-b517-9d93b39e1e80}
Followup: MachineOwner
---------
1: kd> lmvm intelppm
start end module name
fffff800`f617b000 fffff800`f6199000 intelppm (pdb symbols) c:\symbols\intelppm.pdb\79BC4E9098AA405EBFB8ADC3ACDACCE01\intelppm.pdb
Loaded symbol image file: intelppm.sys
Mapped memory image file: c:\symbols\intelppm.sys\5215CFEB1e000\intelppm.sys
Image path: \SystemRoot\System32\drivers\intelppm.sys
Image name: intelppm.sys
Timestamp: Thu Aug 22 16:46:35 2013 (5215CFEB)
CheckSum: 00026EA5
ImageSize: 0001E000
File version: 6.3.9600.16384
Product version: 6.3.9600.16384
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft Windows Operating System
InternalName: intelppm.sys
OriginalFilename: intelppm.sys
ProductVersion: 6.3.9600.16384
FileVersion: 6.3.9600.16384 (winblue_rtm.130821-1623)
FileDescription: Processor Device Driver
LegalCopyright: Microsoft Corporation. All rights reserved.
Best regards