ntkrnlmp.exe causing most BSODs (including other driver issues?)

Page 1 of 3 123 LastLast

  1. Posts : 20
    Windows 10
       #1

    ntkrnlmp.exe causing most BSODs (including other driver issues?)


    HP Pavilion g6 Notebook PC, Hewlett-Packard, 1849
    CPU: AuthenticAMD AMD A8-4500M APU with Radeon(tm) HD Graphics AMD586, level: 21
    4 logical processors, active mask: 15
    RAM: 8Gb
    Windows version: Windows 10 , 10.0, build: 10586 (upgraded from 8.1)
    Windows dir: C:\WINDOWS

    Problem summary:
    Frequent restarts/BSODs requiring repeated restarts (problems started since 8.1 before Windows 10 upgrade)
    During freezes/BSODs, the laptop will heat up (fan whirring like crazy). Occasionally the HP repair software will update BIOS upon restart – but problem still happens often. But when the laptop is stable, I can run games (Call of Duty/Battlefield franchise/ARMA2 etc etc), video editing/rendering with expected smooth performance. Also on good days, until now the laptop has almost never crashed in the midst of playing games/video editing.

    SFC scannow will halt at 96%, and DISM will always give me the 0x800f081 error. I have gone through all possible command prompt/powershell/multiple tools methods to restore health from the Techbench ISO/WinSxs etc with no success Sfc scannow/dism failure – need help for manual fix - Windows 10 Forums
    Trying to reinstall Windows 10 from within Windows 10 but laptop always freeze/BSOD mid-installation (at random stages).

    Attached is the dm log collector zip file.

    I have also included a Whocrashed report below:
    Code:
    System Information (local)
    
    Windows version: Windows 10 , 10.0, build: 10586
    Windows dir: C:\WINDOWS
    Hardware: HP Pavilion g6 Notebook PC, Hewlett-Packard, 1849
    CPU: AuthenticAMD AMD A8-4500M APU with Radeon(tm) HD Graphics AMD586, level: 21
    4 logical processors, active mask: 15
    RAM: 8021880832 bytes total
    
    
    
    Crash Dump Analysis
    
    Crash dump directory: C:\WINDOWS\Minidump
    
    Crash dumps are enabled on your computer.
    
    On Sat 6/4/2016 9:00:20 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\060416-62078-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
    Bugcheck code: 0xA (0xD5, 0xFF, 0xB3, 0xFFFFF802D22680C2)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    On Sat 6/4/2016 9:00:20 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
    Bugcheck code: 0xA (0xD5, 0xFF, 0xB3, 0xFFFFF802D22680C2)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    On Sat 6/4/2016 8:57:28 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\060416-71015-01.dmp
    This was probably caused by the following module: Unknown () 
    Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
    Error: CUSTOM_ERROR
    A third party driver was identified as the probable root cause of this system error. 
    Google query:  CUSTOM_ERROR
    
    On Fri 6/3/2016 8:01:42 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\060316-50890-01.dmp
    This was probably caused by the following module: dxgmms1.sys (dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x1DFE) 
    Bugcheck code: 0x139 (0x3, 0xFFFFD00035519580, 0xFFFFD000355194D8, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    Bug check description: The kernel has detected the corruption of a critical data structure.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 
    
    On Fri 6/3/2016 7:49:30 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\060316-48375-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
    Bugcheck code: 0xA (0xFFFFF6E800288030, 0x2, 0x0, 0xFFFFF8011BA906D3)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    On Fri 6/3/2016 7:49:06 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\060316-35750-01.dmp
    This was probably caused by the following module: Unknown () 
    Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
    Error: CUSTOM_ERROR
    A third party driver was identified as the probable root cause of this system error. 
    Google query:  CUSTOM_ERROR
    
    On Fri 6/3/2016 7:43:20 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\060316-47437-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
    Bugcheck code: 0xA (0xD5, 0xFF, 0x53, 0xFFFFF80355CE20C2)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    On Thu 6/2/2016 10:41:16 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\060216-59500-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
    Bugcheck code: 0x139 (0x3, 0xFFFFF8005B926B30, 0xFFFFF8005B926A88, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    Bug check description: The kernel has detected the corruption of a critical data structure.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    On Thu 6/2/2016 10:19:30 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\060216-48515-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0x2A6DF) 
    Bugcheck code: 0x139 (0x3, 0xFFFFF801ECD43450, 0xFFFFF801ECD433A8, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    file path: C:\WINDOWS\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: Advanced Micro Devices, Inc.
    description: ATI Radeon Kernel Mode 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.). 
    Google query: Advanced Micro Devices, Inc. KERNEL_SECURITY_CHECK_FAILURE
    
    On Thu 6/2/2016 9:56:52 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\060216-40687-01.dmp
    This was probably caused by the following module: symefasi64.sys (SYMEFASI64+0x457EE) 
    Bugcheck code: 0x139 (0x3, 0xFFFFD000209704A0, 0xFFFFD000209703F8, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    file path: C:\WINDOWS\system32\drivers\N360x64\1606000.08E\SYMEFASI64.SYS
    product: EFA
    company: Symantec Corporation
    description: Symantec Extended File Attributes
    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: symefasi64.sys (Symantec Extended File Attributes, Symantec Corporation). 
    Google query: Symantec Corporation KERNEL_SECURITY_CHECK_FAILURE
    
    
    Conclusion
    
    41 crash dumps have been found and analyzed. Only 10 are included in this report. 5 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: 
    
    bhdrvx64.sys (BASH Driver, Symantec Corporation)
    srtsp64.sys (Symantec AutoProtect, Symantec Corporation)
    athw10x.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.)
    symefasi64.sys (Symantec Extended File Attributes, Symantec Corporation)
    atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
    P.S. I have an identical Windows 10 laptop which runs perfectly - so I can obtain files from that laptop to replace any corrupted ones on this one.
      My Computer


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

    Looks like there is a problem with your video driver for your AMD Radeon HD 7640G.

    Code:
    fffff802`d3b3c738  fffff800`d2744eadUnable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     atikmdag+0x84ead
    Looks lie AMD is not providing any more support beyond what is provided here: AMD Radeon™ Software Support for Legacy Graphics Products

    Try that driver, Catalyst and Crimson edition, see if that helps. If not you are looking at a new video card if you want to stay with Windows 10.

    Also check the power levels for your computer using a program like SpeedFan.
      My Computers


  3. Posts : 20
    Windows 10
    Thread Starter
       #3

    Thanks Ztruker for your analysis and suggestion. I'm not a technical person, so not quite sure about what you meant about the power levels reading that I can derive from Speedfan - so I have uploaded the Speedfan display here:


    I will definitely try the suggested Catalyst and Crimson drivers, and see how my PC behaves - thank you and I will be back to report the outcome(s).
      My Computer


  4. Posts : 20
    Windows 10
    Thread Starter
       #4

    I just noticed one curious point:

    My laptop has 8Gb RAM (been using it for 3 years). But sometimes system information reports it as only 4Gb RAM, while on occasions it says the actual 8Gb RAM.

    (Bios reports 8Gb RAM, and the msconfig 'Maximum memory' is not checked)

    Laptop's performance now is every bit as fast as it has always been with 8Gb RAM all these years (all my twenty graphic intensive games play great as normal).

    What is the reason for this inconsistency in RAM amount reporting, and should I worry about this?

    Thank you.
    Last edited by Coffeecup132; 07 Jun 2016 at 12:27.
      My Computer


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

    I don't know what is causing the inconsistent ram size.

    Try swapping the ram modules around. This is usually pretty easy, just remove the cover on the bottom of the laptop and the two ram modules should be accessible there. Maybe just re-seating them will solve it. Other than that I don't know.
      My Computers


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

    Have you tried the two ATI drivers I gave you the link to?
      My Computers


  7. Posts : 20
    Windows 10
    Thread Starter
       #7

    Hi Ztruker. The catalyst driver was the one that I was already using at the time the problems were occurring, so I installed the Crimson drivers. I have been traveling since then and haven't been using my laptop as much as I normally do, so waiting to come home for the real acid test, BUT, ever since the Crimson drivers, the number of BSODs have lessened very significantly. Instead of BSODs, it is more the PC restarts itself (and that occurs with less frequency to the pre-Crimson BSODs).

    I will report again in a few days time.
    Last edited by Coffeecup132; 13 Jun 2016 at 20:38.
      My Computer


  8. Posts : 20
    Windows 10
    Thread Starter
       #8

    Hi again Ztruker :)

    On the AMD Crimson graphic drivers, the BSODs are significantly less - now BSODs/crashes happening almost exclusively only during starting/restarting (needs a few attempts).
    Laptop will heat up during BSODs/crashes, thus waiting the laptop to cool down increases chance to start/restart successfully.

    However once I manage to get to the desktop, I can be video editing/rendering, running games (Battlefield 3, COD Ghosts etc) almost without BSODs/crashes for 24 hours or maybe even longer - during these times even when the laptop runs hot as a stove, there are still almost no BSODs/crashes, with no performance deterioration at all (as long as I don't try to restart Windows again).

    I have redone and reattached the new dm log collector zip file if you would like to have a second reassessment.

    Thank you!
    Last edited by Coffeecup132; 24 Jun 2016 at 00:14.
      My Computer


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

    The dumps aren't showing anything useful.

    You may want to try doing a Clean Boot, see if the boot up problem goes away.

    See here: How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts
      My Computers


  10. Posts : 20
    Windows 10
    Thread Starter
       #10

    Thank you very much for your advice! I am travelling now and will perform a clean boot once I get the chance.

    Will be reporting the outcome to you once I do it.

    Again, thank you!
      My Computer


 

  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 03:48.
Find Us




Windows 10 Forums