none
Random Bsods involving intelppm.sys RRS feed

  • Question

  • Hi everyone,
    I have a Win Server 2008r2 SP1 that recently suffered many Bsods for no thinkable reasons.

    Here is the crashdump :

    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: srv*c:\symbols\publics*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: Server, suite: TerminalServer SingleUserTS
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    Machine Name:
    Kernel base = 0xfffff800`0161b000 PsLoadedModuleList = 0xfffff800`0185f670
    Debug session time: Sat Jan 19 17:15:28.528 2013 (UTC + 1:00)
    System Uptime: 0 days 2:45:15.944
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................
    Loading User Symbols

    Loading unloaded module list
    ..............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 122, {b, 5, 5, 0}

    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    Probably caused by : intelppm.sys ( intelppm+39c2 )

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

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

    WHEA_INTERNAL_ERROR (122)
    Arguments:
    Arg1: 000000000000000b
    Arg2: 0000000000000005
    Arg3: 0000000000000005
    Arg4: 0000000000000000

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


    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x122

    PROCESS_NAME:  System

    CURRENT_IRQL:  f

    LAST_CONTROL_TRANSFER:  from fffff800017a7a52 to fffff80001699fc0

    STACK_TEXT: 
    fffff880`009c2bf8 fffff800`017a7a52 : 00000000`00000122 00000000`0000000b 00000000`00000005 00000000`00000005 : nt!KeBugCheckEx
    fffff880`009c2c00 fffff800`01c0f6be : fffffa80`00002140 fffffa80`040dabf0 fffff880`009c2cf0 fffff800`01c2d470 : nt!WheaReportHwError+0x1a2
    fffff880`009c2c60 fffff800`01749c31 : fffff880`009c2e30 00000000`00000001 00000000`00000001 fffffa80`04536b00 : hal!HalHandleNMI+0x66
    fffff880`009c2c90 fffff800`01697302 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiProcessNMI+0x131
    fffff880`009c2cf0 fffff800`01697163 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
    fffff880`009c2e30 fffff880`010039c2 : fffff800`016a2ae9 00000000`002a1d67 fffffa80`04536bb8 00000000`ffffffed : nt!KiNmiInterrupt+0x163
    fffff880`009cbc98 fffff800`016a2ae9 : 00000000`002a1d67 fffffa80`04536bb8 00000000`ffffffed 00001989`16c839f6 : intelppm+0x39c2
    fffff880`009cbca0 fffff800`01691c9c : fffff880`009b8180 fffff880`00000000 00000000`00000000 fffff880`03291084 : nt!PoIdle+0x52a
    fffff880`009cbd80 00000000`00000000 : fffff880`009cc000 fffff880`009c6000 fffff880`009cbd40 00000000`00000000 : nt!KiIdleLoop+0x2c


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    intelppm+39c2
    fffff880`010039c2 c3              ret

    SYMBOL_STACK_INDEX:  6

    SYMBOL_NAME:  intelppm+39c2

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: intelppm

    IMAGE_NAME:  intelppm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

    FAILURE_BUCKET_ID:  X64_0x122_intelppm+39c2

    BUCKET_ID:  X64_0x122_intelppm+39c2

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

     It looks like that intelppm.sys driver is responsible but I can't figure out any solution.

    Thanks in advance for any reply!!

    Saturday, January 19, 2013 5:22 PM

Answers

  • Any recent updates done to the server? Can you rollback if any of them are correlated to the time the server began to crash? Use reliability monitor to find out when this started.

    Also make sure you have the latest chipset drivers from Intel.

    It seems someone else had this issue: http://communities.intel.com/thread/30369

    If you've recently been getting errors with intelppm.sys it's recommend you uninstall and/or re-install any programs recently that may have generated this error. If this does not resolve your issue or you have not installed any program recently try recovering Windows back to a recent backup of Windows. Steps on how to do this can be found on document CH000589. - http://www.computerhope.com/cgi-bin/process.pl?p=intelppm.sys


    http://mariusene.wordpress.com/

    Saturday, January 19, 2013 11:05 PM
  • If you are seeing this problem repeatedly you can manually disable these drivers (with no negative side effect) by going to the following location in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Processor

    Or

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm

    And changing the 'Start' value to '4'.


    http://www.arabitpro.com

    Sunday, January 20, 2013 9:08 AM

All replies

  • Any recent updates done to the server? Can you rollback if any of them are correlated to the time the server began to crash? Use reliability monitor to find out when this started.

    Also make sure you have the latest chipset drivers from Intel.

    It seems someone else had this issue: http://communities.intel.com/thread/30369

    If you've recently been getting errors with intelppm.sys it's recommend you uninstall and/or re-install any programs recently that may have generated this error. If this does not resolve your issue or you have not installed any program recently try recovering Windows back to a recent backup of Windows. Steps on how to do this can be found on document CH000589. - http://www.computerhope.com/cgi-bin/process.pl?p=intelppm.sys


    http://mariusene.wordpress.com/

    Saturday, January 19, 2013 11:05 PM
  • If you are seeing this problem repeatedly you can manually disable these drivers (with no negative side effect) by going to the following location in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Processor

    Or

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm

    And changing the 'Start' value to '4'.


    http://www.arabitpro.com

    Sunday, January 20, 2013 9:08 AM