Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows 8.1 BSOD ntoskrnl.exe


  • Please log in to reply
3 replies to this topic

#1 jabail

jabail

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:51 AM

Posted 25 March 2017 - 09:24 PM

· OS - Windows 8.1

· x64 
· Windows 8.1 was originally installed.
· OEM version
· Age of system (hardware) 1 1/2 years
· Age of OS installation - have you re-installed the OS? OS is the original OS, so 1 1/2 years

· CPU
· Video Card - NVIDIA GeForce GTX 960M


· System Manufacturer - ASUS
· Exact model number - GL551JW-DS71

· Laptop

 

Hi. I'm having BSODs at random times, with the DRIVER_POWER_STATE_FAILURE error. Sometimes I can be on the internet, or on Word, or on some other application. I downloaded blue screen view and it says its caused by driver ntoskrnl.exe. I've ran a memtest, updated all my drivers, used ccleaner to check for registry problems, and updated Windows and nothing has worked. I've googled all kinds of information based on the blue screen view results and I've tried pretty much everything that has been suggested. Any help would be appreciated.

Attached Files



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,989 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:02:51 AM

Posted 25 March 2017 - 09:39 PM

Hi, jabail,

This looks like the standard case of the crashing graphics drivers. Anyway, we have a consistent pattern of crahses — STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE bugchecks... the easiest to debug:

7: kd> .bugcheck
Bugcheck code 0000009F
Arguments 00000000`00000003 ffffe001`b5a956a0 ffffd001`353bb960 ffffe001`b3f00c10

Looks like we have a blocked IRP, indicated by the fourth parameter (which makes it even easier):

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe001b5a956a0, Physical Device Object of the stack
Arg3: ffffd001353bb960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe001b3f00c10, The blocked IRP

Let's look at it:

7: kd> !irp ffffe001b3f00c10
Irp is active with 6 stacks 4 is current (= 0xffffe001b3f00db8)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 ffffe001b5a956a0 00000000 fffff8001aed137c-ffffd001351f18f0 Success Error Cancel pending
           \Driver\pci    dxgkrnl!DpiFdoPowerCompletionRoutine
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 ffffe001b8f01040 00000000 fffff80308722efc-ffffe001bbcfaea8 Success Error Cancel pending
          *** 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
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe001bbcfaea8    

            Args: 00000000 00000000 00000000 00000000

Yup, it's your NVIDIA graphics driver. Some information about it:

7: kd> lm k vm nvlddmkm
start             end                 module name
fffff800`1b47e000 fffff800`1bf63000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon Feb 15 01:30:57 2016 (56C170A1)
    CheckSum:         00AA0EE8
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Since this is a notebook, you'll want to get your drivers directly from ASUS's website. For your convenience, here's the download link. If for some reason you still get crashes, try this one. When reinstalling your NVIDIA graphics driver, please perform a Custom Installation, as demonstrated below:
3SKjXsp.jpg
Also, when you click Next, make sure you only install the Graphics Driver (and the PhysX System Software if you're a gamer). Also, check Perform a clean installation (see below):

Warning! Please read this first.
PLEASE DO NOT INSTALL ANY 3D DRIVERS!!! I've seen them cause odd issues before.


1bTMUDx.jpg

Good luck!

Regards,
bwv848

 


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 jabail

jabail
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:51 AM

Posted 26 March 2017 - 05:37 PM

Hi, jabail,

This looks like the standard case of the crashing graphics drivers. Anyway, we have a consistent pattern of crahses — STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE bugchecks... the easiest to debug:

7: kd> .bugcheck
Bugcheck code 0000009F
Arguments 00000000`00000003 ffffe001`b5a956a0 ffffd001`353bb960 ffffe001`b3f00c10

Looks like we have a blocked IRP, indicated by the fourth parameter (which makes it even easier):

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe001b5a956a0, Physical Device Object of the stack
Arg3: ffffd001353bb960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe001b3f00c10, The blocked IRP

Let's look at it:

7: kd> !irp ffffe001b3f00c10
Irp is active with 6 stacks 4 is current (= 0xffffe001b3f00db8)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 ffffe001b5a956a0 00000000 fffff8001aed137c-ffffd001351f18f0 Success Error Cancel pending
           \Driver\pci    dxgkrnl!DpiFdoPowerCompletionRoutine
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 ffffe001b8f01040 00000000 fffff80308722efc-ffffe001bbcfaea8 Success Error Cancel pending
          *** 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
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe001bbcfaea8    

            Args: 00000000 00000000 00000000 00000000

Yup, it's your NVIDIA graphics driver. Some information about it:

7: kd> lm k vm nvlddmkm
start             end                 module name
fffff800`1b47e000 fffff800`1bf63000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon Feb 15 01:30:57 2016 (56C170A1)
    CheckSum:         00AA0EE8
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Since this is a notebook, you'll want to get your drivers directly from ASUS's website. For your convenience, here's the download link. If for some reason you still get crashes, try this one. When reinstalling your NVIDIA graphics driver, please perform a Custom Installation, as demonstrated below:
3SKjXsp.jpg
Also, when you click Next, make sure you only install the Graphics Driver (and the PhysX System Software if you're a gamer). Also, check Perform a clean installation (see below):

Warning! Please read this first.
PLEASE DO NOT INSTALL ANY 3D DRIVERS!!! I've seen them cause odd issues before.


1bTMUDx.jpg

Good luck!

Regards,
bwv848

 

Okay! I installed the first driver you listed. I'll report back if I have any issues. Thanks a lot!


Edited by jabail, 26 March 2017 - 05:37 PM.


#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,989 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:02:51 AM

Posted 26 March 2017 - 05:41 PM

You're quite welcome. :) Please do let me know the final outcome.

Regards,
bwv848


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users