BSOD or Total freeze, UNEXPECTED_KERNEL_MODE_TRAP

Page 1 of 3 123 LastLast

  1. Posts : 15
    Windows 10 64bit
       #1

    BSOD or Total freeze, UNEXPECTED_KERNEL_MODE_TRAP


    Hi, recently I've been having system crashes where the mouse just freezes and I have to hard restart / shutdown my pc.
    Otherwise the computer bluescreens and dumps a log. I have two copies of the last two cases of this BSOD pasted below.
    I have ran memtest64+ overnight with no errors on my single 8gb stick of ram

    ==================================================
    Dump File : 062516-22156-01.dmp
    Crash Time : 25-Jun-16 9:53:15 PM
    Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
    Bug Check Code : 0x0000007f
    Parameter 1 : 00000000`00000008
    Parameter 2 : fffff801`9b1c5e70
    Parameter 3 : 00000000`9b1b5c50
    Parameter 4 : fffff801`998640fe
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+1427a0
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+1427a0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\WINDOWS\Minidump\062516-22156-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 10586
    Dump File Size : 279,564
    Dump File Time : 25-Jun-16 9:56:21 PM
    ==================================================
    ==================================================
    Dump File : 071016-35546-01.dmp
    Crash Time : 10-Jul-16 6:22:52 PM
    Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
    Bug Check Code : 0x0000007f
    Parameter 1 : 00000000`00000008
    Parameter 2 : fffff803`9b4a2e70
    Parameter 3 : 00000000`9b492c50
    Parameter 4 : fffff803`99c6e0fe
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+1427a0
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+1427a0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\WINDOWS\Minidump\071016-35546-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 10586
    Dump File Size : 279,948
    Dump File Time : 10-Jul-16 6:24:11 PM
    ==================================================
    Thanks for any advice in advance! (first post so sorry if I've done anything incorrectly!)
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    Dump indicates a problem with your AMD Radeon R9 200 Series driver.

    Code:
    fffff803`9b491868  fffff801`1fcd5168Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
     atikmpag+0x15168
    dxdiag output indicates you have two of these. Are you running SLI? That has been somewhat problematical in Windows 10.
    Your driver is fairly recent: 02-Jun-16 12:00:00 AM Version 16.200.1025.0

    There is a newer one available: Version 16.7.2 Desktop


    Code:
    Radeon Software    301 MB    Crimson Edition 16.7.2 Hotfix     7/9/2016
      My Computers


  3. Posts : 15
    Windows 10 64bit
    Thread Starter
       #3

    Hi Ztruker, thanks for the fast reply and your time!

    I'm not sure why this is indicating that I am running in SLI, this is not the case. My motherboard is capable of running SLI cards with 2x Pcie slots but only one of them is being used.

    I have since been reading and tried to use windows 10's driver verifier tool. After running the tool with the recommended settings my computer would BSOD every time it tried to load windows. The log like you said points to my graphics driver.
    Code:
    ==================================================Dump File         : 071116-32046-01.dmp
    Crash Time        : 11-Jul-16 1:32:53 AM
    Bug Check String  : DRIVER_VERIFIER_DETECTED_VIOLATION
    Bug Check Code    : 0x000000c4
    Parameter 1       : 00000000`00002003
    Parameter 2       : ffffe000`620d5ae8
    Parameter 3       : fffff800`6bf10240
    Parameter 4       : ffffd001`32d68620
    Caused By Driver  : atikmdag.sys
    Caused By Address : atikmdag.sys+240
    File Description  : 
    Product Name      : 
    Company           : 
    File Version      : 
    Processor         : x64
    Crash Address     : ntoskrnl.exe+1427a0
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\WINDOWS\Minidump\071116-32046-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 10586
    Dump File Size    : 275,156
    Dump File Time    : 11-Jul-16 6:51:08 PM
    ==================================================
    After the BSOD that the driver verifier caused finished i did a fresh install of my drivers using AMD's removal tool then re installing the latest driver (the one that you linked and recommended i try) and ran the verifier again.
    The same BSOD appeared on restart pointing to the graphics driver again even after the update.

    After I disabled the verifier my computer booted normally but after about 5 minutes blue screened again.
    Code:
    ==================================================Dump File         : 071116-39781-01.dmp
    Crash Time        : 11-Jul-16 6:58:40 PM
    Bug Check String  : HAL_INITIALIZATION_FAILED
    Bug Check Code    : 0x0000005c
    Parameter 1       : 00000000`00000201
    Parameter 2       : ffffffff`ffd01860
    Parameter 3       : ffffffff`c000000d
    Parameter 4       : 00000000`00000000
    Caused By Driver  : hal.dll
    Caused By Address : hal.dll+1af0b
    File Description  : 
    Product Name      : 
    Company           : 
    File Version      : 
    Processor         : x64
    Crash Address     : ntoskrnl.exe+1427a0
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\WINDOWS\Minidump\071116-39781-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 10586
    Dump File Size    : 171,516
    Dump File Time    : 11-Jul-16 7:00:22 PM
    ==================================================
    I checked to see if the verifier tool had been closed on reboot and has since been stable for a good 20-30 mins

    I will re run and re attach the full log file for you to analyze to this post!

    Thanks again, look forward to hearing from you or anyone with input on a possible solution to my problem!

    Cheers guys :)

    (really hope this isn't the death of my R9 290x)
      My Computer


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    The date of atikmpag.sys in the latest driver
    Code:
    Features
    
                                                       
    Name File Size Revision Number Release Date Download Link
    Radeon Software 301 MB Crimson Edition 16.7.2 Hotfix 7/9/2016
    should be 7/8/2016 2:46PM. The one you have installed is 02-Jun-16 9:25:56 PM C:\WINDOWS\system32\DRIVERS\atikmpag.sys so it looks like it's not the latest. Can you download it and try again.

    Desktop


    Hmmm, just noticed you still have Driver Verifier enabled. Please follow

    Part Three: Disable Driver Verifier

    to disable it.
      My Computers


  5. Posts : 15
    Windows 10 64bit
    Thread Starter
       #5

    Hi, sorry I failed to mention to revert driver verifier I had to do a system restore, but I did download and install the GPU drivers you provided and still got the BSOD from the verifier running after installing them!
    I did step 3 of the guide and I'm pretty sure verifier is no longer running!
    Any other ideas about why this could be happening? Thanks again
      My Computer


  6. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #6

    If you have another dump, rerun DM_Log_collector and upload the zip file.
      My Computers


  7. Posts : 15
    Windows 10 64bit
    Thread Starter
       #7

    Another "freeze" crash but a dump appears to have been made!

    Code:
    ==================================================Dump File         : 071116-39781-01.dmp
    Crash Time        : 11-Jul-16 6:58:40 PM
    Bug Check String  : HAL_INITIALIZATION_FAILED
    Bug Check Code    : 0x0000005c
    Parameter 1       : 00000000`00000201
    Parameter 2       : ffffffff`ffd01860
    Parameter 3       : ffffffff`c000000d
    Parameter 4       : 00000000`00000000
    Caused By Driver  : hal.dll
    Caused By Address : hal.dll+1af0b
    File Description  : 
    Product Name      : 
    Company           : 
    File Version      : 
    Processor         : x64
    Crash Address     : ntoskrnl.exe+1427a0
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\WINDOWS\Minidump\071116-39781-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 10586
    Dump File Size    : 171,516
    Dump File Time    : 11-Jul-16 7:00:22 PM
    ==================================================
    Have attached DM log zip to post
    This occured while playing Arma 3 and the computer force restarted on its own.
    The log will show me running the Previous drivers (not the new ones) as i did not bother to re install the latest after still getting the same BSOD.

    Thanks in advance!
      My Computer


  8. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #8

    Driver Verifier is still enabled. Are you following the directions under

    Part Three: Disable Driver Verifier

    Click Start, type verifier and press Enter. Check the Display existing settings and click Next. All should be set to No.
    Then go back and select Delete existing settings and click Next.

    From a Elevated Command Prompt, enter:

    >verifier /query

    You should get No drivers are currently verified. as a response if it's off.

    Also,

    verifier /reset

    Clears Driver Verifier flags and driver settings. This option requires system reboot to take effect.
      My Computers


  9. Posts : 15
    Windows 10 64bit
    Thread Starter
       #9

    Hi Rich,
    Thanks again for your continued support on this!
    I'm not sure why it is saying that the verifier is still running because it isn't for sure.
    When the verifier was running it would BSOD every time I tried to boot.
    I reverted back to a system restore image I had made BEFORE the verifier was even ran.
    Here is a screenshot of what my verifier /query reads and my "existing settings" without any changes, they are all listed as Enabled: No (even though the screen cap only shows some of these)

    Attachment 90392
      My Computer


  10. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #10

    I don't understand eirther. Oh well.

    See if there is a file C:\WINDOWS\MEMORY.DMP. If yes, zip it up and upload here please. It should be different then the small dumps in C:\Windows\minidump.
      My Computers


 

  Related Discussions
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 01:42.
Find Us




Windows 10 Forums