~Toughbooktalk~ Rob - 630-300-8877

The largest Toughbook discussion site on the net!
It is currently Tue Dec 11, 2018 4:59 pm

All times are UTC-06:00




Post new topic  Reply to topic  [ 8 posts ] 
Author Message
PostPosted: Thu Mar 31, 2016 3:24 pm 
Offline

Joined: Fri Jan 02, 2015 2:45 pm
Posts: 16
After multiple crashes/re-boots after waking from Sleep, I ran WhoCrashed diagnostic on my CF-30 Mk 3 with Win 10 and it identified a driver error etmdrvmgr.sys, which is associated with Intel Dynamic Power Performance Management (DPPM). Since there is no updated Win 10 driver for Intel's DPPM should I just delete this file? Should I uninstall the etmservice.exe file (in Windows/System32) as well in order to delete the DPPM program? (There is no way to uninstall it via Control Panel as it's not listed.)

I don't want to remove anything that will prevent boot-up, but I don't know if this file or program is necessary. Any thoughts would be appreciated.

Thanks.


Top
   
PostPosted: Thu Mar 31, 2016 6:51 pm 
Offline
User avatar

Joined: Tue Dec 21, 2010 12:51 pm
Posts: 1884
Location: Northeast Louisiana
But if you don't want to un-install you should be able to disable in services, then not to start at startup.

_________________
CF-28 MK2,Mk3 / CF-29 Mk3 / CF-30 MK2 / CF-25 Mk1 ATI / CF-19 MK3/Mk3/Mk5 / CF-U1 Mk1,Mk2 / CF-M34 Mk7/Mk3 / CF-17 Mk1 / CF-07
Voodoo Envy M355 / M360 / M515 / M780 / U703 / Voodoo Hexx / Voodoo Idol / Voodoo Rage F1 / Voodoo Rage F1 / Voodoo Rage F1 "signed case" / Voodoo Omen
Alienware M11x R1


Top
   
PostPosted: Thu Mar 31, 2016 9:01 pm 
Offline

Joined: Fri Jan 02, 2015 2:45 pm
Posts: 16
Thanks. I tried disabling it in the Services window but it did not solve the problem. The WhoCrashed program still identifies the etmdrvmgr.sys file as the culprit, even though the Intel DPPM program shows as Disabled in the Services window.

I'm not sure why a program that is disabled would still try to access its related .sys file. I also checked the Startup and Processes tabs in Task Manager and notice that the Intel DPPM program isn't listed there. Not sure where else to look at this point.

I wonder if I should try to uninstall the etmservice.exe file entirely and delete the etmdrvmgr.sys file... or maybe just rename the offending .sys file to etmdrvmgr.old and see what happens.

I appreciate the help in troubleshooting. Personally, I love my Toughbooks, and I'm glad to have a resource like this with folks who know a lot more than I do about these issues.


Top
   
PostPosted: Thu Mar 31, 2016 9:46 pm 
Offline

Joined: Fri Jan 02, 2015 2:45 pm
Posts: 16
Just to add info to my previous post, here is the WhoCrashed entry. Am I correct that the etmdrvmgr.sys file is the offender? If so, is it okay to rename or delete it?

Thanks again for the help.


On Fri 4/1/2016 03:31:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033116-26500-01.dmp
This was probably caused by the following module: etmdrvmgr.sys (EtmDrvMgr+0x19907)
Bugcheck code: 0x139 (0x3, 0xFFFFD0017D331610, 0xFFFFD0017D331568, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\etmdrvmgr.sys
product: Intel Dynamic Power Performance Management
company: Intel Corporation
description: Intel Dynamic Power Performance Management Driver

Bug check description: The kernel has detected the corruption of a critical data structure.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: etmdrvmgr.sys (Intel Dynamic Power Performance Management Driver, Intel Corporation).
Google query: Intel Corporation KERNEL_SECURITY_CHECK_FAILURE


Top
   
PostPosted: Fri Apr 08, 2016 8:07 am 
Offline

Joined: Fri Jan 02, 2015 2:45 pm
Posts: 16
Just to follow-up, I've pretty much exhausted all research avenues for this... I was told that deleting or changing the name of the etmdrvmgr.sys file could corrupt the OS and necessitate a complete reinstall. The only thing I haven't tried yet is running the Intel Dynamic Power Performance Manager (DPPM) program associated with this .sys file in Win 7 compatibility mode.

If that doesn't fix the issue then I guess it's back to a complete OS reinstall. Ugh.


Top
   
PostPosted: Fri Apr 08, 2016 8:51 am 
Offline
User avatar

Joined: Fri Jan 18, 2013 11:35 am
Posts: 2969
From what I read years ago. (May not still apply. I bet it does).
Intel has power management utils that work really well. The PROBLEM is Microsoft did not trust that Intel knew what they were doing. So Microsoft wrote their own power management stuff. Microsofts stuff can conflict with Intels and cause issues.
Personally I would run the Intel stuff and let it disable the Microsoft crapola.

_________________
Life will beat you into submission.


Top
   
PostPosted: Wed Apr 13, 2016 9:06 am 
Offline

Joined: Fri Jan 02, 2015 2:45 pm
Posts: 16
Shawn -- Thanks for the reply. But I'm not sure how to disable to Microsoft power management applications and only let the Intel apps run.

Additionally, I did run a Bug check analysis, which showed the following info. I think it confirms a problem with the etmdrvmgr.sys driver, but I don't know how to fix it. Any additional suggestions from the forum experts would be welcome. Thanks.


Microsoft (R) Windows Debugger Version 10.0.10586.567 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\041316-31015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
Machine Name:
Kernel base = 0xfffff801`54a75000 PsLoadedModuleList = 0xfffff801`54d53cd0
Debug session time: Wed Apr 13 10:04:55.669 2016 (UTC - 4:00)
System Uptime: 0 days 0:13:25.492
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, ffffd0004888c610, ffffd0004888c568, 0}

*** WARNING: Unable to verify timestamp for EtmDrvMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for EtmDrvMgr.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : EtmDrvMgr.sys ( EtmDrvMgr+19907 )

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

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

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0004888c610, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0004888c568, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.162.amd64fre.th2_release_sec.160223-1728

SYSTEM_MANUFACTURER: Panasonic Corporation

SYSTEM_PRODUCT_NAME: CF-30KCP512B

SYSTEM_SKU: CF-30KCP512B

SYSTEM_VERSION: 003

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: V3.01L23

BIOS_DATE: 10/08/2009

BASEBOARD_MANUFACTURER: Panasonic Corporation

BASEBOARD_PRODUCT: CF30-3

BASEBOARD_VERSION: 1

DUMP_TYPE: 2

BUGCHECK_P1: 3

BUGCHECK_P2: ffffd0004888c610

BUGCHECK_P3: ffffd0004888c568

BUGCHECK_P4: 0

TRAP_FRAME: ffffd0004888c610 -- (.trap 0xffffd0004888c610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe000f190f3d0 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80154be86d6 rsp=ffffd0004888c7a0 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000000 r10=00000000000005eb
r11=ffffe000f21daeb0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt! ?? ::FNODOBFM::`string'+0x225d6:
fffff801`54be86d6 cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffffd0004888c568 -- (.exr 0xffffd0004888c568)
ExceptionAddress: fffff80154be86d6 (nt! ?? ::FNODOBFM::`string'+0x00000000000225d6)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CPU_COUNT: 2

CPU_MHZ: 63c

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 17

CPU_STEPPING: a

CPU_MICROCODE: 6,17,a,0 (F,M,S,R) SIG: A0C'00000000 (cache) A0C'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000003

ANALYSIS_SESSION_HOST: ADMIN-PC

ANALYSIS_SESSION_TIME: 04-13-2016 10:12:56.0149

ANALYSIS_VERSION: 10.0.10586.567 x86fre

LAST_CONTROL_TRANSFER: from fffff80154bc22e9 to fffff80154bb7760

STACK_TEXT:
ffffd000`4888c2e8 fffff801`54bc22e9 : 00000000`00000139 00000000`00000003 ffffd000`4888c610 ffffd000`4888c568 : nt!KeBugCheckEx
ffffd000`4888c2f0 fffff801`54bc2610 : ffffe000`f1cd4338 ffffe000`f1cd4338 ffffe000`00000080 ffffe000`f1ccd7c0 : nt!KiBugCheckDispatch+0x69
ffffd000`4888c430 fffff801`54bc17f3 : ffffe000`f1c598a0 ffffe000`f16ba150 00000000`00000040 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffffd000`4888c610 fffff801`54be86d6 : 00000000`00000000 ffffd000`4888c830 ffffe000`f2d3f440 00000000`000007ff : nt!KiRaiseSecurityCheckFailure+0xf3
ffffd000`4888c7a0 fffff801`54af19bc : ffffe000`f190f398 fffff800`00000000 00000000`00000000 ffffe000`f164a490 : nt! ?? ::FNODOBFM::`string'+0x225d6
ffffd000`4888c810 fffff800`e9519907 : 00000000`00000005 00000000`00000000 ffffe000`f1659880 ffffe000`f16532d0 : nt!KeSetEvent+0xfc
ffffd000`4888c8a0 00000000`00000005 : 00000000`00000000 ffffe000`f1659880 ffffe000`f16532d0 00000000`00000001 : EtmDrvMgr+0x19907
ffffd000`4888c8a8 00000000`00000000 : ffffe000`f1659880 ffffe000`f16532d0 00000000`00000001 ffffd000`4888c930 : 0x5


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 7c47dc770db2b9a3c5d99104930644e45d9f7a89

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 68387bd5aa52b5cdc689cdddd4d411cbf2975c0d

THREAD_SHA1_HASH_MOD: 9b617c6f1e4cb0265f0e4eb5857d12daf221e9a8

FOLLOWUP_IP:
EtmDrvMgr+19907
fffff800`e9519907 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: EtmDrvMgr+19907

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: EtmDrvMgr

IMAGE_NAME: EtmDrvMgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d4374b7

BUCKET_ID_FUNC_OFFSET: 19907

FAILURE_BUCKET_ID: 0x139_3_EtmDrvMgr!Unknown_Function

BUCKET_ID: 0x139_3_EtmDrvMgr!Unknown_Function

PRIMARY_PROBLEM_CLASS: 0x139_3_EtmDrvMgr!Unknown_Function

TARGET_TIME: 2016-04-13T14:04:55.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-02-24 00:48:00

BUILDDATESTAMP_STR: 160223-1728

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.162.amd64fre.th2_release_sec.160223-1728

ANALYSIS_SESSION_ELAPSED_TIME: 5aa3

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_3_etmdrvmgr!unknown_function

FAILURE_ID_HASH: {70061d8d-96ef-6b24-fe58-e171301e806e}

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


Top
   
PostPosted: Wed Apr 13, 2016 12:02 pm 
Offline
User avatar

Joined: Fri Jan 18, 2013 11:35 am
Posts: 2969
Reinstall windows over the old version.
It will save all of your old stuff and repair any missing or corrupt drivers.

_________________
Life will beat you into submission.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 8 posts ] 

All times are UTC-06:00


Who is online

Users browsing this forum: No registered users and 5 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Limited