Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Collecting logs for the User-Mode Hooking (UMH) module for a system hang issue

    • Updated:
    • 28 Dec 2016
    • Product/Version:
    • OfficeScan 11.0
    • Platform:
    • Windows 10
    • Windows 2008 32-Bit
    • Windows 2008 64-Bit
    • Windows 2012
    • Windows 7 32-Bit
    • Windows 7 64-Bit
    • Windows 8 32-Bit
    • Windows 8 64-Bit
    • Windows 8.1 32-Bit
    • Windows 8.1 64-Bit
Summary

This article introduces how to collect the UMH logs for a system hang issue caused by the UMH module.

UMH is an engine in OSCE that supports the enhanced ransomware solution. It is installed in the Common Client Solution Framework (CCSF) service as a module. It provides API events for other modules, such as Behavior Monitoring, Predictive Machine Learning, etc. Those modules will make decisions according to the provided API events from UMH.

Below is the installation path for UMH in OSCE:

<OfficeScan Agent Installation Path>\CCSF\MODULE\20019\

UMH has been involved since OSCE 11.0 Service Pack 1 Critical Patch 6054 (Ransomware CP) and OSCE XG.

Details
Public

To collect the UMH logs:

  1. Enable the kernel dump.

    Enable kernel dump

    Enable kernel dump

    For more information, refer to the following article: Enabling a Kernel-Mode Dump File.

  2. Set a restore point for %systemdrive% and impacted disk/partition.

    Set restore point

    Set restore point

    Set restore point

  3. Set the following registry keys to Forcing a System Crash from the Keyboard:
    • For PS/2 keyboards, enable the keyboard-initiated crash in the registry. In the registry keyHKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters, create a value named CrashOnCtrlScroll, and set it equal to a REG_DWORD value of 0x01.
    • For USB keyboards, enable the keyboard-initiated crash in the registry. In the registry keyHKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbdhid\Parameters, create a value named CrashOnCtrlScroll, and set it equal to a REG_DWORD value of 0x01.
  4. Restart the system for the settings to take effect.
  5. After the system has restarted, the system hang problem should have been reproduced.
  6. After the problem reproduced, hold down the rightmost CTRL key then press the SCROLL LOCK key twice. A crash dump file is written at this point.
  7. Reboot the system again to get the dump file from %SystemRoot%\MEMORY.DMP.
  8. Get the UMH-related binary files:
    • <OSCE installation path>\CCSF\module\20019
    • %windir%\system32\tmumh
    • %windir%\syswow64\tmumh
    • %windir%\system32\drivers\tmumh.sys
  9. Get the UMH-related registry keys:
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tmumh
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\GlobalFlag
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
    • HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1115437
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.