none
Bsod windows server 2012 - intelppm.sys RRS feed

  • Question

  • Dear all,

    My server is facing Bsod many times in September and again in Octorber. I see the crash dump file and get the error intelppm.sys. Please help with below last log file. Thanks you very much. It is very urgent because this server is based on remote site, I cannot reach it immediately.

    BugCheck 80, {4f4454, 0, 0, 0}

    Probably caused by : intelppm.sys ( intelppm!ReadIoMemRaw+e7 )

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

    18: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    NMI_HARDWARE_FAILURE (80)
    This is typically due to a hardware malfunction.  The hardware supplier should
    be called.
    Arguments:
    Arg1: 00000000004f4454
    Arg2: 0000000000000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000

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


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  6.3.9600.18790 (winblue_ltsb.170810-1616)

    SYSTEM_MANUFACTURER:  FUJITSU

    SYSTEM_PRODUCT_NAME:  PRIMERGY RX2540 M1

    SYSTEM_SKU:  S26361-K1495-Vxxx

    SYSTEM_VERSION:                        

    BIOS_VENDOR:  FUJITSU // American Megatrends Inc.

    BIOS_VERSION:  V5.0.0.9 R1.24.0 for D3289-A1x                    

    BIOS_DATE:  05/12/2015

    BASEBOARD_MANUFACTURER:  FUJITSU

    BASEBOARD_PRODUCT:  D3289-A1

    BASEBOARD_VERSION:  S26361-D3289-A13 WGS04 GS02

    DUMP_TYPE:  2

    BUGCHECK_P1: 4f4454

    BUGCHECK_P2: 0

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    CPU_COUNT: 18

    CPU_MHZ: 95a

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3f

    CPU_STEPPING: 2

    CPU_MICROCODE: 6,3f,2,0 (F,M,S,R)  SIG: 2E'00000000 (cache) 2E'00000000 (init)

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

    BUGCHECK_STR:  0x80

    PROCESS_NAME:  System

    CURRENT_IRQL:  f

    ANALYSIS_SESSION_HOST:  AAEVIVN100052N

    ANALYSIS_SESSION_TIME:  10-09-2017 13:12:01.0897

    ANALYSIS_VERSION: 10.0.15063.468 amd64fre

    LAST_CONTROL_TRANSFER:  from fffff801460501c2 to fffff801461d6da0

    STACK_TEXT:  
    ffffd001`5d0ce3c8 fffff801`460501c2 : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    ffffd001`5d0ce3d0 fffff801`46245909 : 00000000`00000001 fffff801`4605f8c0 fffff801`4605f8c0 ffffe001`04bcb968 : hal!HalBugCheckSystem+0x7e
    ffffd001`5d0ce410 fffff801`46050fa1 : ffffd001`000006c0 ffffd001`5d0ce620 00000000`00000001 00000000`00000000 : nt!WheaReportHwError+0x22d
    ffffd001`5d0ce470 fffff801`4626968c : ffffd001`5d0ce630 00000000`00000001 00000000`00000000 fffff801`4626c17b : hal!HalHandleNMI+0xfe
    ffffd001`5d0ce4a0 fffff801`461e02c2 : ffffe801`5d22a760 ffffd001`5d0ce6b0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x150
    ffffd001`5d0ce4f0 fffff801`461e0136 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
    ffffd001`5d0ce630 fffff801`763de78b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x176
    ffffd001`5d0ec8b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!ReadIoMemRaw+0xe7


    STACK_COMMAND:  kb

    THREAD_SHA1_HASH_MOD_FUNC:  9d74ab956d0a00c96ad46c0ba4e0a2e4ec10fd16

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  73f2607e9eab65805ca4bb36245d423d22a5f0de

    THREAD_SHA1_HASH_MOD:  57ff8b6ace84d1c8d0732ab0ca29024aa4fe813c

    FOLLOWUP_IP:
    intelppm!ReadIoMemRaw+e7
    fffff801`763de78b 0fb6c0          movzx   eax,al

    FAULT_INSTR_CODE:  c3c0b60f

    SYMBOL_STACK_INDEX:  7

    SYMBOL_NAME:  intelppm!ReadIoMemRaw+e7

    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:  e7

    FAILURE_BUCKET_ID:  0x80_intelppm!ReadIoMemRaw

    BUCKET_ID:  0x80_intelppm!ReadIoMemRaw

    PRIMARY_PROBLEM_CLASS:  0x80_intelppm!ReadIoMemRaw

    TARGET_TIME:  2017-10-09T02:42:42.000Z

    OSBUILD:  9600

    OSSERVICEPACK:  18790

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  272

    PRODUCT_TYPE:  3

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 8.1

    OSEDITION:  Windows 8.1 Server TerminalServer SingleUserTS

    OS_LOCALE:  

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2017-08-11 08:32:19

    BUILDDATESTAMP_STR:  170810-1616

    BUILDLAB_STR:  winblue_ltsb

    BUILDOSVER_STR:  6.3.9600.18790

    ANALYSIS_SESSION_ELAPSED_TIME:  5c9

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0x80_intelppm!readiomemraw

    FAILURE_ID_HASH:  {633641d2-a41f-9da8-6d46-c2218f6a87ea}

    Monday, October 9, 2017 6:52 AM

Answers

  • Hi,

    > BugCheck 80, {4f4454, 0, 0, 0} Probably caused by : intelppm.sys ( intelppm!ReadIoMemRaw+e7 ).
    ntelppm.sys is a Microsoft Intel processor driver that should be located in the "C:\Windows\System32\drivers" directory.

    If there is any change before problem happened, such as software installation/update, hardware installation/replacement, please try to undo the change and check the result.

    Besides, please try to using “sfc /scannow” to check/repair system files. also, make sure that Windows Server 2012 is fully patched using Windows Update/Hotfix. It would be helpful for resolving some known issues and improving the performance. Install the latest update rollup:
    https://support.microsoft.com/en-us/help/4038799

    If problem persists, I want to confirm with you whether it is a physical or virtual system? Any operation is relate, or, is there any event has been logged?

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 10, 2017 6:57 AM
    Moderator

All replies

  • Hi,

    > BugCheck 80, {4f4454, 0, 0, 0} Probably caused by : intelppm.sys ( intelppm!ReadIoMemRaw+e7 ).
    ntelppm.sys is a Microsoft Intel processor driver that should be located in the "C:\Windows\System32\drivers" directory.

    If there is any change before problem happened, such as software installation/update, hardware installation/replacement, please try to undo the change and check the result.

    Besides, please try to using “sfc /scannow” to check/repair system files. also, make sure that Windows Server 2012 is fully patched using Windows Update/Hotfix. It would be helpful for resolving some known issues and improving the performance. Install the latest update rollup:
    https://support.microsoft.com/en-us/help/4038799

    If problem persists, I want to confirm with you whether it is a physical or virtual system? Any operation is relate, or, is there any event has been logged?

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 10, 2017 6:57 AM
    Moderator
  • Hi,

    I uninstalled Processors drivers in Device Manager and re-installed. After one week, there is no BSOD again.

    Thanks for your support.

    Monday, October 16, 2017 1:42 AM
  • Hi,

    Thank you for taking the time to update the result. Your detail sharing might be helpful for other people who has the similar problem.

    If there is anything else we can do for you, please feel free to post in the forum.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 17, 2017 1:34 AM
    Moderator

  • When you have BSOD please post using one drive or drop box share links:

    1) mini dump files:  %SystemRoot%\Minidump or c:\windows\minidump

    2) memory dump file:  %SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMP

    Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

    3) msinfo32

    In left lower corner search type msinfo32 > wait 5 minutes for it to load > save to desktop > use share link to post into thread

    4) dxdiag

    In left lower corner search type dxdixg > wait 5 minutes for it to load > save to desktop > use share link to post into thread.

    Tuesday, October 17, 2017 4:08 AM