Windows 10: Unexpected_kernel_mode_trap

Page 1 of 5 123 ... LastLast
  1.    22 Jun 2016 #1

    Unexpected_kernel_mode_trap


    062216-6796-01.dmp 22/06/2016 22:56:42 UNEXPECTED_KERNEL_MODE_TRAP 0x1000007f 00000000`00000008 ffffd000`b18b4a30 ffffd000`b18d1010 fffff83b`9d1d79d


    this happen randomly , sometimes give me bsod but sometimes pc totally freeze with last sound freezing/buzzing , and i must force power off from power button..

    like this video
    PC freezes and makes buzzing noise - YouTube
      My ComputerSystem Spec


  2. Posts : 5,003
    Windows 10 Pro X64 15063.138
       22 Jun 2016 #2

    Counterfit installation:

    Troubleshooting a counterfeit installation is useless as it is not known what has been modified on your system.

    A counterfeit installation may contain modified code which causes the system to behave in unexpected ways.
    For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.

    Please install a genuine copy of Windows and activate it.

    If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

    Forum rules
    4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).
      My ComputersSystem Spec

  3.    01 Jul 2016 #3

    ok i buyed e activated my Windows with original key and new dump files come
      My ComputerSystem Spec


  4. Posts : 5,003
    Windows 10 Pro X64 15063.138
       01 Jul 2016 #4

    Thank you.

    The dump from the 29th may give us a clue:

    Code:
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. .
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: ffffd00026376a30
    Arg3: ffffd000203f6020
    Arg4: fffff83e87f67985
    I'd like you to run a CPU stress test and if that doesn't indicate any errors, Driver Verifier:

    Follow this tutorial to stress test your CPU:

    Run Driver Verifier:
    Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
    If neither shows an error then test your RAM:

    RAM:

    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    Information


    MemTest86+
    is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
      My ComputersSystem Spec

  5.    03 Jul 2016 #5

    02 oh and 50 min uptime now with driver verifier and no bsod at all -_- ... cpu stress no trouble . waiting for bsod
      My ComputerSystem Spec

  6.    04 Jul 2016 #6

    finally i got bsod with verifier on , thanks
      My ComputerSystem Spec


  7. Posts : 5,003
    Windows 10 Pro X64 15063.138
       04 Jul 2016 #7

    Dump wasa caused by WmBEnum.sys.

    The process known as Logitech WingMan Virtual Bus Enumerator Driver belongs to software Logitech Virtual Bus Enumerator Driver or Logitech WingMan Software by Logitech (Logitech | Mice, keyboards, remotes, speakers, and more - United States).
    The driver can be started or stopped from Services in the Control Panel or by other programs. The program has no visible window. The service has no detailed description. WmBEnum.sys is not a Windows system file. The WmBEnum.sys file is a trustworthy file from Microsoft. WmBEnum.sys appears to be a compressed file. Therefore the technical security rating is 17% dangerous, however you should also read the user reviews. Uninstalling this variant: If problems with Logitech Gaming Software or WingMan Software occur, you can uninstall the software using the Uninstall a Program function of Windows Control Panel (Windows: Start, Settings, Control Panel, Uninstall a Program).
    The driver is very old and needs to be updated or removed:
    Code:
    2: kd> lmvm WmBEnum
    start             end                 module name
    fffff801`86b80000 fffff801`86b84d00   WmBEnum  T (no symbols)           
        Loaded symbol image file: WmBEnum.sys
        Image path: \SystemRoot\system32\drivers\WmBEnum.sys
        Image name: WmBEnum.sys
        Timestamp:        Tue Apr 27 16:10:19 2010 (4BD744AB)
        CheckSum:         0000E6B8
        ImageSize:        00004D00
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My ComputersSystem Spec

  8.    05 Jul 2016 #8

    i will remove it in the evening , my question is why i have this driver on my system ? i have logitech webcam and also driving gt force ,
      My ComputerSystem Spec

  9.    05 Jul 2016 #9

    ok i found and removed Logitech Gaming Software was installed for logitech driving force ,
      My ComputerSystem Spec

  10.    05 Jul 2016 #10

    how can i delete all trace of the driver?
      My ComputerSystem Spec


 
Page 1 of 5 123 ... LastLast

Related Threads
BSOD Unexpected_kernel_mode_trap in BSOD Crashes and Debugging
Hello everyone, First time posting here and I am completely lost on what to do. I have tried everything I could think of to fix this issue and have not been able to find a solution. Hoping someone here can help. I have been getting random BSOD's...
Bsod unexpected_kernel_mode_trap in BSOD Crashes and Debugging
Hello all, I have a custom PC build and I have experienced 3 BSOD over the past maybe 2 months all being "UNEXPECTED_KERNEL_MODE_TRAP. I have done some "research" (by that I mean googling) and lots of people say its Drivers. My system is fairly new...
Hi, Been having several bsod-incidents after putting together my new windows 10 skylake gaming pc. So far I've had maybe 2 days of joy of gaming in the last month or so. After that two days of use, I started to experience bsod every now and then...
UNEXPECTED_KERNEL_MODE_TRAP (ntoskrnl.exe) in BSOD Crashes and Debugging
Hi folks, I've been getting frequent UNEXPECTED_KERNEL_MODE_TRAP crashes ever since I upgraded from Windows 8.1. Opening the Minidump in BlueScreenView points to ntoskrnl.exe. I am also experiencing other symptoms, perhaps related to this...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 02:54.
Find Us