Windows 10: BSOD at random -error 0x0000009f - ntoskrnl.exe

  1.    03 Sep 2016 #1

    BSOD at random -error 0x0000009f - ntoskrnl.exe


    Hi all




    So I have this issue in windows 10 where the keyboard of my laptop stops responding at random instances . None of the keys work. That is soon followed by BSOD and a " Driver Power state failure error message". When forcing the computer to restart by pressing the power button resolves the issue . But the keyboard still stops at random intervals. I have already check all the drivers and they are up to date and there are no yellow explanation marks in device manager and updated
    i have run Blue screen viewer and attached the log from that . In all instances it appears the guilty party is " ntoskrnl.exe" but i cannot find any other info on how to resolve this . Can anyone please help?

    edit: also added the dump files as zip
    edit: also opened the dump file with WinDbg and uploaded it as word . Can please someone help me interpret it?
    Last edited by talos1307; 04 Sep 2016 at 19:38.
      My ComputerSystem Spec


  2. Posts : 5,151
    Windows 10 Pro X64 15063.483
       04 Sep 2016 #2

    Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions
      My ComputersSystem Spec

  3.    04 Sep 2016 #3

    Ztruker said: View Post
    Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions
    Sorry, I missed that. I have added it to my post now
      My ComputerSystem Spec


  4. Posts : 5,151
    Windows 10 Pro X64 15063.483
       04 Sep 2016 #4

    Got it, thanks. The latest dump indicates possible memory corruptuion:
    Code:
    BugCheck 9F, {3, ffff99084b3d4060, ffffcc8057442cb0, ffff99084992a010}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    ===================================================
    RAM:

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

    information   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   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   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.

    ===================================================
    Also a possible problem with your Nvidia card or driver:
    Code:
    !irp ffff898d08c6c190
    Irp is active with 6 stacks 4 is current (= 0xffff898d08c6c338)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
    >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0 e1 ffff898d043ca400 00000000 fffff80caa20edd0-ffff9a01150dd860 Success Error Cancel pending
               \Driver\ACPI    dxgkrnl
                Args: 00000000 00000001 00000001 00000000
     [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0 e1 ffff898d08025030 00000000 fffff802c5f9f4e0-ffff898d0c9f8e88 Success Error Cancel pending
              Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvlti.inf_amd64_561c3173c020f30d\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     \Driver\nvlddmkm    nt!PopRequestCompletion
                Args: 00000000 00000001 00000001 00000000
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-ffff898d0c9f8e88    
    
                Args: 00000000 00000000 00000000 00000000
    You already have the latest Nvidia driver version 372.70. You could try rolling it back in Device Manager to the previous level, see if that helps.
      My ComputersSystem Spec

  5.    05 Sep 2016 #5

    Thanks for your response . I have set up memtest to ran . I have 16 GB of RAM so it will take a while to complete . I will get back to you once is done.

    I had the previous Nvidia drivers (372.52 i think) when this was happening and updated to 372.70 to see if that helped but it did not.
      My ComputerSystem Spec

  6.    05 Sep 2016 #6

    Memtest completed 9 full passes . No errors found.
      My ComputerSystem Spec


  7. Posts : 5,151
    Windows 10 Pro X64 15063.483
       06 Sep 2016 #7

    Try rolling the Nvidia driver back via Device Manager. If that doesn't fix it then time to give Driver Verifier a try:
    ===================================================
    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

    Pay close attention to
    PART TWO
    and make sure the correct boxes are checked.

    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.
      My ComputersSystem Spec


 

Related Threads
Random BSOD errors(ntoskrnl.exe) in BSOD Crashes and Debugging
Hello. Since 2 months i'm getting several BSOD errors. They appear in random moments when i'm playing games, watching videos etc. I have really no idea how i can fix this :( Here is the dump file: ​051816-14187-01.dmp - Google Drive EDIT: added zip...
Random BSOD's ntoskrnl.exe in BSOD Crashes and Debugging
Hello, Quick history of my PC. Bought it pre-made back in 2010, with the last 2 years i have upgraded to a SSD and a new graphics card. Within the last 2 months or so I started getting intermittent BSOD's. I decided(probably stupidly) to...
Hello My computer BSOD about 9-10 times a day and it's quite annoying. Here is what I tried: 1. Upgraded from windows 7 to windows 10 2. Ran memtest - RAM had about 30 problems but then I put the ram in another computer and ran the test...
Random BSOD ntoskrnl.exe in BSOD Crashes and Debugging
Hi. I revamped an old X58 build some months ago. It was an inherited computer with several problems. I have been changing most of it (CPU, MOBO, RAM, HDD) but random BSODs keep happening. I'm running a fresh install of Windows 10 Home x64,...
I have had Windows 10 since the day it was released (upgrade from Windows 7 HP) and it has been great. However, I am having a very annoying and seemingly random problem when putting the computer into sleep mode. The computer appears to be going...
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:35.
Find Us