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?

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

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

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.

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

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.