Windows 10: Windows 10 BSOD related to ntoskrnl.exe, ntkrnlmp.e

  1.    28 Sep 2016 #1

    Windows 10 BSOD related to ntoskrnl.exe, ntkrnlmp.e


    Recently I began experiencing a frequent BSOD.
    Error: DRIVER_POWER_STATE_FAILURE

    WhoCrashed says the following;
    This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

    Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

    This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

    To obtain technical support visit www.resplendence.com/support

    Click here to check if you have the latest version or if an update is available.

    Just click the Analyze button for a comprehensible report ...



    Home Edition Notice


    This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

    Click here for more information on the professional edition.
    Click here to buy the the professional edition of WhoCrashed.


    System Information (local)


    Computer name: DESKTOP-G4JKG8Q
    Windows version: Windows 10 , 10.0, build: 14393
    Windows dir: C:\Windows
    Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., X99-DELUXE
    CPU: GenuineIntel Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz Intel586, level: 6
    12 logical processors, active mask: 4095
    RAM: 29972819968 bytes total




    Crash Dump Analysis


    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Thu 9/29/2016 12:05:57 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092816-12031-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
    Bugcheck code: 0x9F (0x3, 0xFFFF868505218B00, 0xFFFFDE8198D0DCB0, 0xFFFF86851300EAB0)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    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 9/29/2016 12:05:57 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: 0x9F (0x3, 0xFFFF868505218B00, 0xFFFFDE8198D0DCB0, 0xFFFF86851300EAB0)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    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 Wed 9/28/2016 1:51:32 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092716-12171-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
    Bugcheck code: 0x9F (0x3, 0xFFFF808F5BFFBE20, 0xFFFFF80093636CB0, 0xFFFF808F5DB4C640)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    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 Wed 9/28/2016 1:16:48 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092716-12609-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
    Bugcheck code: 0x9F (0x3, 0xFFFF8B0B33899920, 0xFFFFD7818ED06960, 0xFFFF8B0B2BB68AB0)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    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 Tue 9/27/2016 11:43:57 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092716-14812-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
    Bugcheck code: 0x9F (0x3, 0xFFFFC1047887F680, 0xFFFFD480FCBAA960, 0xFFFFC1047C46E960)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    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 Tue 9/27/2016 5:29:31 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092716-12921-01.dmp
    This was probably caused by the following module: wdf01000.sys (Wdf01000+0xFF18)
    Bugcheck code: 0x9F (0x3, 0xFFFFD700768D66B0, 0xFFFF918162FECCB0, 0xFFFFD7008037AA60)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\drivers\wdf01000.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Kernel Mode Driver Framework Runtime
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    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 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 Tue 9/27/2016 8:00:05 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092716-12531-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6BA3F7)
    Bugcheck code: 0x124 (0x0, 0xFFFF9A80B5FD3038, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Tue 9/27/2016 6:33:54 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092716-12890-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6BA3F7)
    Bugcheck code: 0x124 (0x0, 0xFFFF8E8E43C268F8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 9/26/2016 3:07:56 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092516-12218-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6BA3F7)
    Bugcheck code: 0x124 (0x0, 0xFFFFC5831C769038, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
    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 9/23/2016 1:14:23 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092216-9421-01.dmp
    This was probably caused by the following module: nvhda64v.sys (nvhda64v+0x833B)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFF8D00434998B8, 0xFFFF8D00434990E0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\nvhda64v.sys
    product: NVIDIA HDMI Audio Driver
    company: NVIDIA Corporation
    description: NVIDIA HDMI Audio Driver
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    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: nvhda64v.sys (NVIDIA HDMI Audio Driver, NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M





    Conclusion


    10 crash dumps have been found and analyzed. A third party driver has 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:

    nvhda64v.sys (NVIDIA HDMI Audio Driver, NVIDIA Corporation)
      My ComputerSystem Spec


  2. Posts : 11,487
    Windows 10 Pro
       01 Oct 2016 #2

    warning   Warning
    Programs that claim to update your drivers install either the wrong or corrupted drivers.
    If you have installed any driver with Driver Booster 3, please remove them as it may cause trouble.

    An easy way to get remove these drivers is by using a restore point prior the installation.
      My ComputersSystem Spec


 

Related Threads
Hello, I've recently upgraded to windows 10 and I've encountered this problem many, many times. I've also done a clean install of Windows 10 afterwards, but the problem persists. I'm currently on the Asus X550J Laptop, with 8gb ram, i7 4710...
BSOD playing GTA V (related to ntkrnlmp.exe) in BSOD Crashes and Debugging
I looked online before posting here and I found many things that could be the issue. I will list everything I did, in attempt to fix this issue: - Restoring the system to a point before Windows 10 update (KB3093266) - Checking BIOS settings for...
Solved BSOD - ntoskrnl.exe & ntkrnlmp.exe in BSOD Crashes and Debugging
Hi all! I've just encountered this BSOD and I tried to analyze it myself using WhoCrashed. It tells me that it was probably caused by ntoskrnl.exe & ntkrnlmp.exe. I've looked into it but I haven't been able to find a fix to this and I was wondering...
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 20:27.
Find Us